Strict Standards: Declaration of Walker_Page::start_lvl() should be compatible with Walker::start_lvl(&$output) in /home/gxtvmhaz/public_html/trisis/blog/wp-includes/classes.php on line 1199

Strict Standards: Declaration of Walker_Page::end_lvl() should be compatible with Walker::end_lvl(&$output) in /home/gxtvmhaz/public_html/trisis/blog/wp-includes/classes.php on line 1199

Strict Standards: Declaration of Walker_Page::start_el() should be compatible with Walker::start_el(&$output) in /home/gxtvmhaz/public_html/trisis/blog/wp-includes/classes.php on line 1199

Strict Standards: Declaration of Walker_Page::end_el() should be compatible with Walker::end_el(&$output) in /home/gxtvmhaz/public_html/trisis/blog/wp-includes/classes.php on line 1199

Strict Standards: Declaration of Walker_PageDropdown::start_el() should be compatible with Walker::start_el(&$output) in /home/gxtvmhaz/public_html/trisis/blog/wp-includes/classes.php on line 1244

Strict Standards: Declaration of Walker_Category::start_lvl() should be compatible with Walker::start_lvl(&$output) in /home/gxtvmhaz/public_html/trisis/blog/wp-includes/classes.php on line 1391

Strict Standards: Declaration of Walker_Category::end_lvl() should be compatible with Walker::end_lvl(&$output) in /home/gxtvmhaz/public_html/trisis/blog/wp-includes/classes.php on line 1391

Strict Standards: Declaration of Walker_Category::start_el() should be compatible with Walker::start_el(&$output) in /home/gxtvmhaz/public_html/trisis/blog/wp-includes/classes.php on line 1391

Strict Standards: Declaration of Walker_Category::end_el() should be compatible with Walker::end_el(&$output) in /home/gxtvmhaz/public_html/trisis/blog/wp-includes/classes.php on line 1391

Strict Standards: Declaration of Walker_CategoryDropdown::start_el() should be compatible with Walker::start_el(&$output) in /home/gxtvmhaz/public_html/trisis/blog/wp-includes/classes.php on line 1442

Strict Standards: Redefining already defined constructor for class wpdb in /home/gxtvmhaz/public_html/trisis/blog/wp-includes/wp-db.php on line 306

Strict Standards: Redefining already defined constructor for class WP_Object_Cache in /home/gxtvmhaz/public_html/trisis/blog/wp-includes/cache.php on line 431

Strict Standards: Declaration of Walker_Comment::start_lvl() should be compatible with Walker::start_lvl(&$output) in /home/gxtvmhaz/public_html/trisis/blog/wp-includes/comment-template.php on line 1266

Strict Standards: Declaration of Walker_Comment::end_lvl() should be compatible with Walker::end_lvl(&$output) in /home/gxtvmhaz/public_html/trisis/blog/wp-includes/comment-template.php on line 1266

Strict Standards: Declaration of Walker_Comment::start_el() should be compatible with Walker::start_el(&$output) in /home/gxtvmhaz/public_html/trisis/blog/wp-includes/comment-template.php on line 1266

Strict Standards: Declaration of Walker_Comment::end_el() should be compatible with Walker::end_el(&$output) in /home/gxtvmhaz/public_html/trisis/blog/wp-includes/comment-template.php on line 1266

Strict Standards: Redefining already defined constructor for class WP_Dependencies in /home/gxtvmhaz/public_html/trisis/blog/wp-includes/class.wp-dependencies.php on line 31

Strict Standards: Redefining already defined constructor for class WP_Http in /home/gxtvmhaz/public_html/trisis/blog/wp-includes/http.php on line 61

Strict Standards: Non-static method CodeColorerLoader::Enable() should not be called statically in /home/gxtvmhaz/public_html/trisis/blog/wp-content/plugins/codecolorer/codecolorer.php on line 254
Performance counts « Simon Kenyon Shepard :: justLikeThat.
Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method CodeColorerLoader::LoadStyles() should not be called statically in /home/gxtvmhaz/public_html/trisis/blog/wp-includes/plugin.php on line 339

Performance counts


Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method CodeColorerLoader::CallBeforeHighlightCodeBlock() should not be called statically in /home/gxtvmhaz/public_html/trisis/blog/wp-includes/plugin.php on line 166

Strict Standards: Non-static method CodeColorer::GetInstance() should not be called statically in /home/gxtvmhaz/public_html/trisis/blog/wp-content/plugins/codecolorer/codecolorer.php on line 214

Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method CodeColorerLoader::CallAfterHighlightCodeBlock() should not be called statically in /home/gxtvmhaz/public_html/trisis/blog/wp-includes/plugin.php on line 166

Strict Standards: Non-static method CodeColorer::GetInstance() should not be called statically in /home/gxtvmhaz/public_html/trisis/blog/wp-content/plugins/codecolorer/codecolorer.php on line 222

I’ve been watching the frontend optimization video’s on Yahoo.

They have some startling statistics and case studies which I felt were worth sharing,
The first is from Steve Souders talk 18 months ago:
On average 10% of user experience load time is due to backend page serving, this means that 90% of the load time experienced by users is controlled by the frontend. So for example if you optimize your backend by 50% at most you are optimizing the overall user experience by 5%, however if you optimize the frontend by 50% this would result in a 45% overall saving in user experience load time.

This then goes on to be even more pertinent when you consider the information from the Nicole Sullivan’s talk:

Amazon did two tests where they artificially increased the load times of their pages, it gave the following results:

100ms - 1% drop in sales

400ms - 5-9% full page traffic drop off

Google had similar results:

500ms - 20% fewer searches

lemanianerostopwatchlg
I think this highlights just how important load times and by proxy frontend sitedevs are, when you consider that in a big build you will have an approximate ratio of say 1 sitedev to 10 backend devs, it really doesn’t make sense and we should be looking to sell in as many sitedevs as possible into projects for optimization purposes as this is what will really increase the load times and hence drive profit for the client. These are some powerful statistics, that I will be adopting in the future to help back up my case, but this in turn raises some interesting questions. ┬áLike how do we measure performance increase to show metrics of increase justifying the cost and how should this be implemented -should an extra optimization effort occur post build, how do we bake front-end performance into continuous integration environments? How do we replicate what back end devs have achieved which is to get clients to pay for the extra work?

somebody pointed out to me that it might be nice to have some links to relevant source material:

Nicole Sullivan: "Design Fast Websites" @ Yahoo! Video
Steve Souders: "High Performance Web Sites: 14 Rules for Faster Pages" @ Yahoo! Video

Some other helpful links courtesy of Per Swantesson:

http://www.svennerberg.com/2008/12/page-load-times-vs-conversion-rates/

http://news.zdnet.com/2422-13568_22-197145.html

http://stnor.wordpress.com/2009/02/01/speed-sells

http://www.hobo-web.co.uk/seo-blog/index.php/your-website-design-should-load-in-4-seconds/

http://specialistonlinemarketing.wordpress.com/2008/06/21/why-load-time-now-matters-in-google-search/

Leave a Reply