Comments on: A Super Bowl experience: How third party scripts can hurt your website http://blog.browsermob.com/2010/02/a-super-bowl-experience-how-third-party-scripts-can-hurt-your-website/ All about browsers, performance testing, and load testing Thu, 02 Sep 2010 18:01:30 -0500 http://wordpress.org/?v=2.8.5 hourly 1 By: Peter Coles http://blog.browsermob.com/2010/02/a-super-bowl-experience-how-third-party-scripts-can-hurt-your-website/comment-page-1/#comment-1406 Peter Coles Mon, 01 Mar 2010 02:40:43 +0000 http://blog.browsermob.com/2010/02/a-super-bowl-experience-how-third-party-scripts-can-hurt-your-website/#comment-1406 Great example of an external script causing trouble! Testing a live site is a difficult task. I saw a similar example recently where an advertisement script was bogging down a page. I added the screen shots to my blog post (referenced at the top of this one) so people can see how it blocks all the useful content on the page (and load/ready events) from appearing until the ad finally timed out. Also, a minor clarification, the “on content ready” pseudo event will not get blocked by images, but it will get blocked by any slow scripts. So while it is a better/safer event than window.onload for applying functionality to a web page, it still has to wait for slow scripts. Great example of an external script causing trouble! Testing a live site is a difficult task. I saw a similar example recently where an advertisement script was bogging down a page. I added the screen shots to my blog post (referenced at the top of this one) so people can see how it blocks all the useful content on the page (and load/ready events) from appearing until the ad finally timed out.

Also, a minor clarification, the “on content ready” pseudo event will not get blocked by images, but it will get blocked by any slow scripts. So while it is a better/safer event than window.onload for applying functionality to a web page, it still has to wait for slow scripts.

]]>