← Back to the blog

Site Speed & Revenue-Loss Audit

PageSpeed Insights vs GTmetrix vs Pingdom: Website Speed Test Comparison

By Hamza IqbalFounder, ToolsForge

Reviewed 5 min readHow we source numbers

Three speedometer gauges side by side

Which website speed test tool should you use?

Use Google PageSpeed Insights first. It's the only one of the four that shows the real-user Chrome data (CrUX) Google Search uses for Core Web Vitals. Use GTmetrix or WebPageTest when you or a developer need a request-by-request waterfall to find the cause, and Pingdom for a quick load-time check from a location you choose.

The scores won't match between tools, and that's expected. The table shows why.

PageSpeed Insights vs GTmetrix vs Pingdom vs WebPageTest

PageSpeed Insights GTmetrix Pingdom WebPageTest
Engine Lighthouse lab test plus CrUX real-user data Lighthouse Pingdom's own load test Real browsers on its test agents; Lighthouse report available
Default test Simulated mid-tier phone on a mobile network Desktop, unthrottled connection A load from the location you pick Device, connection and location you choose
Shows Google's real-user field data Yes, when your page or site has enough Chrome traffic No No No
Waterfall of every request No Yes Yes Yes, plus filmstrip and video
Best for Knowing what visitors and Google Search see Debugging load order A quick check from a specific region Reproducing a specific device or network
Cost Free, no account Free tests with an account; paid plans for more tests and monitoring Free one-off speed test; ongoing monitoring from about $10 a month Free Starter plan; paid plans for more test runs

All four have a free option, checked in November 2026. Paid plan limits (tests per month, locations, devices) change often, so check each tool's pricing page before you pay.

Why does GTmetrix give a different score than PageSpeed Insights?

Both run Lighthouse, but under different conditions. PageSpeed Insights' mobile test simulates a mid-tier phone on a mobile network. GTmetrix's own explainer says its default test is unthrottled and measures the load as it happens, so its scores usually come out higher.

Location and the moment you test matter too. Lighthouse scores also move between runs of the same tool: Chrome's scoring documentation lists changing ads or A/B tests, internet routing changes, different devices, browser extensions and antivirus software among the causes.

To compare tools fairly:

  1. Match the device (mobile vs desktop), the connection profile and, where you can, the test location.
  2. Run each test three times and use the middle result.
  3. Compare metrics such as LCP and Total Blocking Time, not just the 0–100 score.
  4. Pick one tool for tracking over time and stick with it.

Google PageSpeed Insights

PageSpeed Insights runs Lighthouse on Google's servers and, when your page or site has enough Chrome traffic, adds field data from the Chrome UX Report: real visitors' LCP, INP and CLS at the 75th percentile over the previous 28 days. That field data is what Google Search uses for its page experience signals. The 0–100 Performance score comes from the single lab run and is not itself a ranking input; does page speed affect SEO? covers what Google has said.

Its limit is depth. You get the score, the Core Web Vitals and a list of opportunities, but no full waterfall of every request. Core Web Vitals explained covers what each metric means.

GTmetrix

GTmetrix reports a Lighthouse-based score alongside a waterfall that shows when each image, script and stylesheet loaded and how long it took. That makes it good for finding the cause of a slow page once you know it's slow. Because its default test is an unthrottled desktop load, don't compare its score directly with a PageSpeed Insights mobile score.

Pingdom

Pingdom's free speed test asks for a URL and a test location, then reports load time with a request-by-request breakdown. It's quick to read for non-technical owners and useful if your customers are concentrated in one region. It doesn't show Core Web Vitals field data, so it can't tell you what Google Search sees.

WebPageTest

WebPageTest gives the most control: choose the device, browser, connection speed and location, run repeat views, and watch a filmstrip of the page rendering frame by frame. It's the tool for reproducing one specific scenario, and more than most owners need for a routine check.

Do you need to use all four tools?

No. Start with PageSpeed Insights' field data to see whether real visitors pass Core Web Vitals. If they don't, a waterfall from GTmetrix or WebPageTest shows which files are holding the page up. Our site speed audit runs PageSpeed Insights for you, lists the main causes in plain English, and estimates what the slow load may be costing in sales.

Related: does website speed affect conversions? and why is my website so slow?

FAQ

Its field data is the most accurate picture of what real Chrome visitors experienced over the last 28 days. Its lab score is a single simulated mobile load, so it can swing a few points between runs and often looks worse than what fast-connection visitors see.
Yes, for what it measures: one real page load under the test settings you choose. By default that's an unthrottled desktop test, so its score is usually higher than PageSpeed Insights' mobile score. Neither is wrong; they test different conditions.
GTmetrix's default test is desktop and unthrottled, while PageSpeed Insights' mobile test simulates a mid-tier phone on a mobile network. Match the device and connection settings and the gap usually narrows.
PageSpeed Insights, but read the field data, not the score. Google Search uses real-user Core Web Vitals from the Chrome UX Report. The 0–100 Lighthouse score is a lab test and is not itself a ranking signal, so judge SEO impact by the field LCP, INP and CLS at the top of the report.
For a quick load-time check from a chosen location, yes. It doesn't show Core Web Vitals field data, so pair it with PageSpeed Insights if search visibility matters to you.

Site Speed & Revenue-Loss Audit

Find out what slow load times are costing you.

Run the free tool

Written by

Hamza Iqbal

Founder, ToolsForge

Founder of ToolsForge and a WordPress & WooCommerce developer. Builds the free calculators on this site and writes the guides behind them — every guide pairs real, sourced numbers with a tool so you can run your own.