Comments on: YSlow Review, add-on for the firebug add-on http://www.seifi.org/performance/yslow-review-the-firebug-addon.html A Web Development Blog by Joe Seifi - seifi.org Tue, 13 Jul 2010 18:09:52 +0000 hourly 1 http://wordpress.org/?v=3.0.1 By: xoox http://www.seifi.org/performance/yslow-review-the-firebug-addon.html/comment-page-1#comment-16431 xoox Mon, 07 Apr 2008 08:49:04 +0000 http://www.seifi.org/performance/yslow-the-firebug-extension-extension.html#comment-16431 Mine scores 100 with some heavy optimization. Forget the score, at the end of the day it is the render time - the total time it takes for the page to load. A simple text page would score high 80's. The trouble is when you start adding stuff to the site and when your visitors' base start hammering your server :) Peace! Mine scores 100 with some heavy optimization. Forget the score, at the end of the day it is the render time – the total time it takes for the page to load.

A simple text page would score high 80′s. The trouble is when you start adding stuff to the site and when your visitors’ base start hammering your server :)

Peace!

]]> By: Pablo http://www.seifi.org/performance/yslow-review-the-firebug-addon.html/comment-page-1#comment-2169 Pablo Wed, 15 Aug 2007 07:27:17 +0000 http://www.seifi.org/performance/yslow-the-firebug-extension-extension.html#comment-2169 Mojo congrats! great article. Reading it I was able to add the expire headers right and i was able to get rid of those nasty etgas. Now mi site ranks "Performance Grade: B(89)" Mojo congrats! great article.

Reading it I was able to add the expire headers right and i was able to get rid of those nasty etgas.
Now mi site ranks “Performance Grade: B(89)”

]]> By: Mojo http://www.seifi.org/performance/yslow-review-the-firebug-addon.html/comment-page-1#comment-1623 Mojo Wed, 01 Aug 2007 02:10:13 +0000 http://www.seifi.org/performance/yslow-the-firebug-extension-extension.html#comment-1623 Hi Grok2, I see your point as to the requirement with Google's TOS. What I don't get is 'why' the JavaScript file has to be included multiple times on the same page even though from what I can tell it is not dynamically generated. What I'm assuming is that Google probably looks at access statistics on the JS file and uses that to monitor its adsense publishers. Hi Grok2,

I see your point as to the requirement with Google’s TOS. What I don’t get is ‘why’ the JavaScript file has to be included multiple times on the same page even though from what I can tell it is not dynamically generated.

What I’m assuming is that Google probably looks at access statistics on the JS file and uses that to monitor its adsense publishers.

]]> By: Grok2 http://www.seifi.org/performance/yslow-review-the-firebug-addon.html/comment-page-1#comment-1426 Grok2 Thu, 26 Jul 2007 18:06:49 +0000 http://www.seifi.org/performance/yslow-the-firebug-extension-extension.html#comment-1426 Re. the google ad code being repeated -- this probably is due to Google's ToS which require that you use the code *exactly* as provided. Re. the google ad code being repeated — this probably is due to Google’s ToS which require that you use the code *exactly* as provided.

]]>