WebPagetest Forums
Pingdom "Response time" vs Webpagetest - Printable Version

+- WebPagetest Forums (https://www.webpagetest.org/forums)
+-- Forum: Web Performance (/forumdisplay.php?fid=3)
+--- Forum: Testing Tools/Services (/forumdisplay.php?fid=6)
+--- Thread: Pingdom "Response time" vs Webpagetest (/showthread.php?tid=3770)

Pingdom "Response time" vs Webpagetest - Joppe - 09-16-2011 03:00 AM


I would be happy to have some help clearing out the following:

What is relation between "response time" as used by for example pingdom.com and the different parameters at webpagetest.org? Is "response time" the same as "Time to first byte"?

What is a good "response time" when using Pingdom.com?

Another question: In Google Webmaster tool, there is a graph under "Statistics for crawling" giving the time to get one page. The average right now is 891 milliseconds.
What time should I aim for? Exactly what is the meaning of this figure, is it responsetime, time to first byte or time to fully loaded (obviously not...)

Hoping for assistance!


RE: Pingdom "Response time" vs Webpagetest - pmeenan - 09-16-2011 04:32 AM

Response time on pingdom is equivalent to the base page download time on WebPagetest. It's only exposed in the raw data/xml interface though. The time to first byte is close but you also need to include the time to transfer the base page (so the time to first byte measurement is only a part of the response time).

As far as a good response time, "it depends" :-D It mostly depends on where your servers are located relative to their test agents. If they are in the same region then under 100ms is a reasonably good time.

The google webmaster tools time is the same as the pingdom response time measurement (though it's the average of all of the pages it crawled on your site, not just the pages that are being tested by pingdom). 891ms is pretty high (mine is running ~90ms in webmaster tools).

Neither of them has much relation to the time it takes to load for real users (which is just about always significantly higher because of other resources on the page). The google labs performance information is the end-user performance.

For real data for users you can add the server processing time to your access logs which will tell you how long each request takes, use the google analytics support for end-user performance or use something like new relic which will give you both in a pretty dashboard.