Friday, June 22nd, 2007

Pingdom: Load time tester

Category: JavaScript, Utility

Peter Alguacil and his team have created Pingdom, a free tool that tests the load time of websites and all included objects such as images, CSS files, scripts, etc, and shows this information graphically with an Ajax interface.


Posted by Dion Almaer at 8:30 am

4.2 rating from 37 votes


Comments feed TrackBack URI

so basically what firebug does but in a web-app which has delay.

Comment by Alex93053 — June 22, 2007


What’s with the hateful comments… I’ve been noticing a trend lately, and it’s a shame that we’re tossing out comments like this.

Whatever happened to applauding developer efforts? Isn’t there enough hate in this world?

Chill, peeps.

Comment by Frank — June 22, 2007

I completely dig this app. Its simple and works. Great job. 8)

Comment by jdalton — June 22, 2007

@Frank: I totally agree.

Comment by Marc — June 22, 2007

I’m loving that grid view, that’s an absolute masterpiece of xhtml/css based data visualisation.

Comment by Ben — June 22, 2007

Sure, but you can’t print what Firebug displays.

Comment by James MacFarlane — June 22, 2007

This is GREAT!! Sure firebug can do this but it doesn’t do first byte timing which is the most important thing (for us at least). Thank you so much for doing this!

Comment by Marcus — June 22, 2007

Really nice. The only mistake I noticed was it’s tendency to recurse through links that are just used for namespace references. For instance I have some embedded/inline CSS that uses “@namespace url(;”, and it proceeded to load all the XHTML and images from the site and included that on the results grid.

Comment by Deron — June 22, 2007

Well done, that is really nice work.

Comment by Sam — June 22, 2007

I agree with frank….there’s not enough love and appreciation in the world.

Comment by Stu — June 22, 2007

I think they have really managed to create a very stylish app, with some pretty slick functionality. Sure firebug does a similar thing, but it’s still neat to see.

Comment by Adam Sanderson — June 22, 2007

Nice, a stylish wheel with first byte timing.

Comment by Miguel Benevides — June 22, 2007

Firebug gives incorrect results by the way. Since it does not have direct access to the cache, it must reload all JS and CSS files, which will get put into your timings. So if you are trying to time second page views, etc., it will be wrong.

Comment by Steven — June 22, 2007

I apologize for not doing the legwork myself, but as a time saver perhaps someone who has already looked at it could reply:

Does the app have any capability to store the load times over a period of time (days, a week, etc.) so it can be used for analysis later?


Comment by Steve — June 22, 2007

I appreciate the developer efforts, but there is one thing i can’t help to notice (nothing connected to the quality of the site, mind you :).

Sure Firebug is wrong, but we at least know when it is and we can override it. For a site everything boils down to the current load and where in the nine hells our providers burn :)

For instance – i tried with my own site. I have two background gif images which are horizontally flipped and each weigh about 0.7K. The first time when i tested one of them loaded within a 0.2s, the other one after 1.5s.

So, i’ll prefer Firebug for now :)

Comment by Bundyo — June 23, 2007

I tried and it redirected to so, unlike Firebug, this tool has the advantage that one can compare response times to other external websites using the internet not your LAN.

Comment by maht — June 23, 2007

This tool is awesome. AFAIK, Firefox doesn’t distinguish between connection times and download times the way this does, which is extremely helpful.

Comment by Tom — June 23, 2007

McAfee’s SiteAdvisor gives Pingdom a RED badge! WTF Dion?

Comment by BillyG — June 23, 2007

What a COOL Tool. I never know about this before. Thank you so much to share this with us.

Comment by Eddy — June 25, 2007

Just would like to point out that Firebug is a far more useful and realistic tool (in 2009). Our CIO demanded to know why Pingdom showed we had twice as many “objects” as our competitors and over 1mb page load. Turns out all Pingdom does is parse stylesheets loading _every_ URL regardless of whether the rule is even applied to an element in the DOM. Firebug demonstrated – accurately – that in fact we have half the requests and half the page size of our competitors. Not sure what real-world usage Pingdom has these days with most browsers including a Resource/Net tab for this kind of thing.

Comment by rloaderro — November 7, 2009

Leave a comment

You must be logged in to post a comment.