I hope that "decrease" load time instead of "increase"
Generally, it depends on the stickiness of your visitors.
For visitors who visit more than one page, minimize html (by using css), consolidate and compress css and javascript. Set reasonable expire times in the response headers. This will promote client caching and allow subsequent pages to load faster (ie... less to download).
For visitors who most likely see only one page, moving the css and js into the page will work out better.
In either case, smaller image sizes and fewer images will help. Some people merge images into one big one and use css to show the right part in the right place. This might be overkill but, it will reduce pings to the server. Avoid inline css, it can bloat pages quickly.
If you must send big pages, gzip compression works wonders. For a high traffic site, I recommend using a gzip accelerator card instead of doing it with code (definitely use a card for ssl).
Besides load time, for some pages render time can be a big deal. Especially with data tables. For those, giving rendering hints to the browser can help a great deal. Use thead, tfoot, and tbody (in that order). Avoid colspans and rowspans because they can cause the rendering engine in the browser to have to start over.
Including javascript at the bottom of the document will help render time too. Try to avoid the use of document.write in js as well.
|