It depends upon architecture of your backend code plus your server setup.
First of all the set up your server plays a big role in speeding up thing. Having server like lighttpd add boost in compare to native apache. If you are serving good amount of static files then nothing is best than setting up reverse proxy with nginx to serve static files.
Whatever server you use don't forget to configure to properly according to type of traffic. Most of the time apache becomes pain just because of misconfiguration.
Just Google about setting up apache correctly and using reverse proxy to server static files (like images,css,videos etc)
Now your code architecture come up. You must write code that reduces the no. of http connections, reduce mysql queries as much as possible.
The framework you use much be tested for its performance. Do unit tests, benchmark to ensure of its performance.
Write modern application with html5 so that you could reduce the bandwidth consumption and file i/o consumption by using JSON between server and front-end.
Making cache in backend for configuration parts. Like why to query for setting/config data on sql tables every time when you can compile all queried data from sql to a configuration file which can be read by your app on every request.
Setting up a cache server could also add a boost to your website.
BTW these days there are nothing like pages in website. Most of the sites are dynamic and server dynamic content based on users request. Don't worry about pages. Just see how much request you are receiving and try to optimise load on server.
First of all the set up your server plays a big role in speeding up thing. Having server like lighttpd add boost in compare to native apache. If you are serving good amount of static files then nothing is best than setting up reverse proxy with nginx to serve static files.
Whatever server you use don't forget to configure to properly according to type of traffic. Most of the time apache becomes pain just because of misconfiguration.
Just Google about setting up apache correctly and using reverse proxy to server static files (like images,css,videos etc)
Now your code architecture come up. You must write code that reduces the no. of http connections, reduce mysql queries as much as possible.
The framework you use much be tested for its performance. Do unit tests, benchmark to ensure of its performance.
Write modern application with html5 so that you could reduce the bandwidth consumption and file i/o consumption by using JSON between server and front-end.
Making cache in backend for configuration parts. Like why to query for setting/config data on sql tables every time when you can compile all queried data from sql to a configuration file which can be read by your app on every request.
Setting up a cache server could also add a boost to your website.
BTW these days there are nothing like pages in website. Most of the sites are dynamic and server dynamic content based on users request. Don't worry about pages. Just see how much request you are receiving and try to optimise load on server.
