Good reading to everyone working with webpages. For frontend designers and as well as CMS module developers. It's not only CMSMS speed that matters. At the end whatever is downloaded to from server to browser needs to be considered.
These are from Yahoo developer Network.
http://developer.yahoo.com/performance/rules.html
Good tool to check how your pages download on clientside with Firebug addon to Firefox.
http://getfirebug.com/net.html
http://getfirebug.com/index.html
Tip: Best practises for speeding up your website
Re: Tip: Best practises for speeding up your website
Good directions.
If I would get strict on these tips I would be writing sites to Lynx only. :)
And I think they forgot a important and the most basic one:
W3C compliant code
A compliant code avoids many IF's and ELSE's when the browser is rendering the code.
I can resume all that in:
1. Get a good hosting, geographically, near to you clients.
2. Use cache if it's possible
3. Know how to write a decent HTML/CSS
Great links
Thanks
If I would get strict on these tips I would be writing sites to Lynx only. :)
And I think they forgot a important and the most basic one:
W3C compliant code
A compliant code avoids many IF's and ELSE's when the browser is rendering the code.
I can resume all that in:
1. Get a good hosting, geographically, near to you clients.
2. Use cache if it's possible
3. Know how to write a decent HTML/CSS
Great links
Thanks
Re: Tip: Best practises for speeding up your website
Yes it' good list to start with 
It's good to have some kind of understanding how things work/affect between browser and server as well as inside browser and pay attention to them. You can get to pretty extreme with these things but if your server is taking .2 sec to do database searches and page still feel slow to download or nonresponsive it's obviously something else.

It's good to have some kind of understanding how things work/affect between browser and server as well as inside browser and pay attention to them. You can get to pretty extreme with these things but if your server is taking .2 sec to do database searches and page still feel slow to download or nonresponsive it's obviously something else.