Friday, June 5th, 2009

Page Speed: New open source Firebug performance extension from Google

Category: Google, Performance, Utility

Richard Rabbat and Bryan McQuade have introduced a new tool called Page Speed that is a fully open source (e.g. it has a public bug database, process for accepting code contributions, roadmap, etc) performance Firebug plugin:

Page Speed is a tool we’ve been using internally to improve the performance of our web pages — it’s a Firefox Add-on integrated with Firebug. When you run Page Speed, you get immediate suggestions on how you can change your web pages to improve their speed. For example, Page Speed automatically optimizes images for you, giving you a compressed image that you can use immediately on your web site. It also identifies issues such as JavaScript and CSS loaded by your page that wasn’t actually used to display the page, which can help reduce time your users spend waiting for the page to download and display.

People will obviously compare it to YSlow (I wish they called it GFast ;) but there are some differences beyond the fact that it is Open Source which will hopefully allow a community to grow:

  • Not only will the tool note that images can be optimized, but it will do the work for you!
  • It automatically minifies your JavaScript for you and outputs it so you can use that
  • Profile Deferrable Javascript option will automatically identify candidates for lazy loading
  • An enhanced net panel with a better into cache hits and misses. I believe this is written in C++, so it gets around the “in process” limitations of Firebug’s Net Panel.
  • Many different rules and checks

A must see performance tool to add to your belt. You can check out all of the rules and enjoy the tool!

Posted by Dion Almaer at 12:53 am

4.3 rating from 49 votes


Comments feed TrackBack URI

The best thing about this is thats opensource.

Comment by V1 — June 5, 2009

A very interesting tool, which I will certainly spend some time with in the future.

One knee-jerk reaction though, is the opinions on writing CSS selectors: Let’s try and keep the discussion reasonable and keep our code readable, having code that is hard to read incurs added costs in the development and maintenance of all software projects… speed is not the only criteria for success.

Regarding comparisons and YSlow, then I might just add that YSlow is also Open Source.

Very nice of Richard Rabbat, Bryan McQuade to share this tool with the rest of us :-)

Comment by MorganRoderick — June 5, 2009


Speed is the goal of the *delivered* code.

The code you deliver to the tubez should be based on – not a copy of – the development code.

Comment by NickTulett — June 5, 2009

can someone provide an alternative link for this? stupid websense is blocking downloads from google, sigh.

Comment by daitro — June 5, 2009

now if only we could get a plugin to make firebug perform decently on very large scale enterprise level RIAs…

Comment by thnkfstr — June 5, 2009

@thinkfstr – yes please

Comment by genericallyloud — June 5, 2009

Doesn’t it already…?
Care to elaborate…?

Comment by ThomasHansen — June 5, 2009

Most application frameworks are too abstracted for Firebug to be of any real use.

Comment by Darkimmortal — June 5, 2009

Also this is incredible – using it I got Imgkk’s load speed (until fully rendered and ready for action) from 2 seconds down to 200ms (both on a primed cache) :D

Comment by Darkimmortal — June 5, 2009

Looks interesting. Given that both this and YSlow is open source perhaps the features can be combined as one plugin? Would be nice to see these companies working together.

Comment by eric2 — June 5, 2009

The page speed plugin is preety similar to yslow. The plugin generate a lot of ‘out of memory’ using js frameworks. Create also hugh temporary files. Wait ‘n’ see.

Comment by irss — June 6, 2009

Leave a comment

You must be logged in to post a comment.