StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
text
Body
copied!<p>Your first port of call is using <a href="http://developer.yahoo.com/yslow/" rel="nofollow noreferrer">YSlow</a> or <a href="http://code.google.com/speed/page-speed/" rel="nofollow noreferrer">Google Speed</a> to figure out what is going slowest on your site. Sometimes a badly compressed (large) image or two can be slowing the entire thing down. You are told to reduce HTTP requests because each request has a setup cost associated with it but if taken to the extreme can lead to worse performance. In your case having a CSS file for each page is bad form as it means it is harder for browsers to cache.</p> <p>Taking one method to the extreme is bad practice and you should attempt to approach this problem from a wide angle such as:</p> <ul> <li>Properly compress images or use CSS sprites (reduces HTTP requests)</li> <li>Implement proper web caching using Expres, ETag etc (so clients don't have to rerequest everything)</li> <li>Optimise your CSS and Javascript files using <a href="http://developer.yahoo.com/yui/compressor/" rel="nofollow noreferrer">YUI</a> or another similar tool</li> <li>Improve your CSS / javascript code for performance. Certain CSS selectors can lead to the browser taking longer to render a page</li> <li>Replace images with pure CSS where possible i.e. background colors etc.</li> <li>Use GZip compression on any text output i.e. html, css, js</li> </ul> <p>If in doubt, look at the source page for the Google home page. They optimise that page heavily and it will give you good clues on what to do.</p>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload