Front-end performance is a compound problem. You need to consider everything that sits between your customers and your data because it all has an impact on the

Front-end performance is a compound problem. You need to consider everything that sits between your customers and your data because it all has an impact on the actual and perceived performance. In regards to browser rendering performance, YSlow is a good place to start: http://developer.yahoo.com/yslow/help/. http://developer.yahoo.com/yslow/help/. The 13 performance rules is a succinct and accurate list of things to look out for. Steve Souders (creator of YSlow, but now works at Google) does a lot of great work in this area: http://stevesouders.com/cuzillion/ http://stevesouders.com/cuzillion/ http://stevesouders.com/ua/report.php http://stevesouders.com/ua/report.php http://stevesouders.com/blog/2008/09/30/hammerhead-moving-performance-testing-upstream http://stevesouders.com/blog/2008/09/30/hammerhead-moving-pe... Some more good stuff: http://www.websiteoptimization.com/speed/tweak/average-web-page/ http://www.websiteoptimization.com/speed/tweak/average-web-p... http://wtr.rubyforge.org/ http://wtr.rubyforge.org/ http://seleniumhq.org/ http://seleniumhq.org/ http://sahi.co.in/w/ http://sahi.co.in/w/