Comments on: High Performance Web Sites: Essential Knowledge for Front-End Engineers http://www.performanceengineer.com/blog/high-performance-web-sites/ Software Performance Engineering & Testing Fri, 13 Aug 2010 19:46:16 -0700 http://wordpress.org/?v=2.8.4 hourly 1 By: Andy King http://www.performanceengineer.com/blog/high-performance-web-sites/comment-page-1/#comment-284 Andy King Sat, 09 Aug 2008 11:52:52 +0000 #comment-284 Charlie, Hi, this is a great book. I cite it in my new book titled Website Optimization: Speed, Search Engine & Conversion Rate Secrets, also from O'Reilly. http://www.websiteoptimization.com/secrets/ Charlie,

Hi, this is a great book. I cite it in my new book titled Website Optimization: Speed, Search Engine & Conversion Rate Secrets, also from O’Reilly.

http://www.websiteoptimization.com/secrets/

]]> By: Charlie http://www.performanceengineer.com/blog/high-performance-web-sites/comment-page-1/#comment-22 Charlie Fri, 16 Nov 2007 17:43:13 +0000 #comment-22 If your page designers (or "front-end engineers" or web developers or UI developers or whatever they're called at your company) are not designing for performance, there might be nothing better to improve the performance (and capacity) of your site than to have them follow the 14 "rules" presented in this book. If you ask me, it should be essential reading for a performance engineer as there are many (often overlooked) areas that can negatively impact performance and can be easily identified by the performance test engineer. Furthermore, some of these things won't even be looked at by a developer. For example, are your developers making sure the "Expires" HTTP header is being set properly? Making web pages more efficient will not only make them faster to load, but it will put less load on your servers, increasing capacity and saving money. Here's the <a href="http://books.slashdot.org/article.pl?sid=07/10/10/1419247">book review on Slashdot</a>. If you don't want to buy the book, you can get a lot of the same material in the <a href="http://developer.yahoo.com/performance/">Performance area on Yahoo's Developer Network site</a>. If your page designers (or “front-end engineers” or web developers or UI developers or whatever they’re called at your company) are not designing for performance, there might be nothing better to improve the performance (and capacity) of your site than to have them follow the 14 “rules” presented in this book.

If you ask me, it should be essential reading for a performance engineer as there are many (often overlooked) areas that can negatively impact performance and can be easily identified by the performance test engineer. Furthermore, some of these things won’t even be looked at by a developer. For example, are your developers making sure the “Expires” HTTP header is being set properly?

Making web pages more efficient will not only make them faster to load, but it will put less load on your servers, increasing capacity and saving money.

Here’s the book review on Slashdot.

If you don’t want to buy the book, you can get a lot of the same material in the Performance area on Yahoo’s Developer Network site.

]]>