PageSpeed vs GTmetrix vs WebPageTest Compared

The Short Answer

Google uses PageSpeed Insights data for rankings. If you only check one tool, check PageSpeed Insights on mobile. But each tool has a different strength:

• PageSpeed Insights: The score Google uses. Check this for rankings impact.
• GTmetrix: The best waterfall chart. Check this to diagnose specific slow resources.
• WebPageTest: The most detailed analysis. Check this for deep technical debugging.

They often show different scores for the same URL because they test from different locations, on different simulated devices, with different network conditions. This is normal. Focus on PageSpeed Insights mobile as your primary metric.

PageSpeed Insights

PageSpeed Insights is Google's own tool. It shows two types of data:

Lab data: Simulated test on a mid-tier mobile device (Moto G Power) with a throttled 4G connection. This produces the 0-100 Performance score. It is consistent and reproducible but represents a slower experience than most users have.

Field data: Real user data from Chrome browsers over the past 28 days (Chrome User Experience Report / CrUX). This is what Google uses for rankings. Not all sites have field data: you need enough Chrome traffic to generate it.

Use it for: Checking the score Google cares about. Comparing mobile vs desktop performance. Seeing if you pass Core Web Vitals thresholds.

GTmetrix

GTmetrix shows a performance waterfall: a visual timeline of every resource your page loads. Each resource (HTML, CSS, JavaScript, images, fonts, third-party scripts) appears as a horizontal bar showing when it started loading, how long it took, and its size.

The waterfall makes it immediately obvious which resources are slow. A 2-second bar for a 4MB image jumps out visually. A chain of render-blocking CSS files shows as stacked bars that delay everything after them.

Use it for: Diagnosing which specific files or resources are causing slowness. Understanding the loading sequence. Identifying third-party scripts that add unexpected delays.

Note: GTmetrix uses Lighthouse (same as PageSpeed Insights) but may test from a different location with different settings. Scores can differ by 5-15 points. PageSpeed Insights is authoritative for Google rankings.

WebPageTest

WebPageTest is the most configurable tool. You can test from 30+ global locations, on specific devices, with custom network speeds, and with or without ad blockers.

Its unique features:

• Filmstrip view: Frame-by-frame screenshots of your page loading. See exactly what the user sees at each second.
• Video comparison: Test two URLs side by side and watch them load simultaneously.
• Repeat view testing: Shows performance for returning visitors (with cached resources) vs first-time visitors.
• Connection view: Shows TCP connections, DNS lookups, and TLS handshakes for every request.

Use it for: Deep technical analysis. Comparing your site against a competitor visually. Testing from specific geographic locations. Understanding caching behavior.

Score Differences Explained

You will almost always get different scores from each tool for the same page. Here is why:

• Test location: PageSpeed Insights tests from a nearby Google data center. GTmetrix defaults to Vancouver, Canada. WebPageTest lets you choose. A page hosted in Dallas will score higher from a Dallas test server than from London.
• Device simulation: PageSpeed Insights simulates a Moto G Power (mid-tier Android). GTmetrix uses its own device profile. The CPU throttling and memory limits differ.
• Network throttling: Each tool simulates a different connection speed. PageSpeed Insights uses a throttled 4G. GTmetrix simulates an unthrottled broadband connection by default.
• Test variability: Any single test can fluctuate 3-8 points based on server load, network conditions, and third-party script timing. Run each test 3 times and take the median.

The scores are not contradicting each other. They are measuring the same page under different conditions. A page scoring 95 on GTmetrix desktop and 72 on PageSpeed Insights mobile is performing well on fast connections and struggling on throttled mobile, which is common.

A Practical Testing Workflow

Use all three tools in sequence for a complete picture:

Step 1: PageSpeed Insights mobile. Run your URL at pagespeed.web.dev. Check the performance score and Core Web Vitals status. If you score 90+ and pass all Web Vitals, speed is not holding your SEO back.

Step 2: GTmetrix waterfall. If your PageSpeed score is below 90, run the same URL on GTmetrix. Open the waterfall tab. Sort by load time or size to find the biggest bottlenecks. This tells you exactly what to fix first.

Step 3: WebPageTest (if needed). For complex issues (third-party script conflicts, geographic latency, caching problems), run a WebPageTest from the location closest to your target audience. Use the filmstrip view to see what users experience second by second.

For more on what causes slow scores, read why your website loads slowly and our guide to hitting a 90+ PageSpeed score.

Which to Trust

For SEO and rankings: PageSpeed Insights mobile score. This is the data Google uses. If your PageSpeed Insights mobile score is 90+, your site passes Core Web Vitals and receives the ranking boost.

For diagnosing problems: GTmetrix waterfall. When PageSpeed Insights tells you to "reduce render-blocking resources" or "optimize images," GTmetrix shows you exactly which resources and how much time they cost.

For deep debugging: WebPageTest. When you need to understand exactly why a specific metric is off, WebPageTest's detailed views provide the answer.

Start with PageSpeed Insights. If your score is below 90, use GTmetrix to identify the specific issues. If the issues are complex (third-party script interactions, caching problems, geographic latency), use WebPageTest for the deep dive.

Want us to run the analysis for you? Our free audit covers all three tools. View our pricing for optimization packages. PageSpeed optimization starts at $1,000. Contact us.