GTmetrix vs Google PageSpeed Insights: Which Should You Use?
GTmetrix and PageSpeed Insights are both popular speed testing tools — but they measure different things. Here's when to use each, and what each actually tells you.
GTmetrix and Google PageSpeed Insights are two of the most commonly used website speed testing tools. Developers often run both without being sure which one to trust or how to interpret disagreements between them.
They’re actually measuring different things. Understanding the distinction will help you use each more effectively.
What PageSpeed Insights Measures
PageSpeed Insights runs Lighthouse in a controlled lab environment (Chrome with simulated mobile throttling) to generate scores. But its unique value is the CrUX field data — real performance metrics from actual Chrome users who visited your site.
The field data section shows:
- Your Core Web Vitals as experienced by real users (not a simulation)
- Whether your site passes or fails Google’s thresholds
- Distribution of fast, moderate, and slow load times
This field data is what Google actually uses for ranking. If you’re worried about Core Web Vitals as an SEO factor, PageSpeed Insights is the source of truth. For a deeper dive, see PageSpeed Insights vs Lighthouse.
Data age: CrUX data is aggregated over the past 28 days. If you made a change recently, it won’t show up in field data immediately.
Limitation: No waterfall, no filmstrip, no video. The Lighthouse lab scores are a single simulated run.
What GTmetrix Measures
GTmetrix runs Lighthouse on their infrastructure and adds a more detailed diagnostic layer: waterfall chart, filmstrip, video recording, and historical tracking. GTmetrix now uses Lighthouse-based scoring exclusively, along with various timing breakdowns.
GTmetrix’s strength is in the diagnostic views — the waterfall especially is useful for understanding the sequence of requests and identifying bottlenecks.
Limitation: GTmetrix doesn’t have CrUX integration on the free tier. The scores it shows are Lighthouse lab scores, not field data. There’s also no indication of what real users experience.
The Core Difference
| PageSpeed Insights | GTmetrix | |
|---|---|---|
| Data type | Lab + real user (CrUX) | Lab only |
| Ranking factor relevance | High (same data Google uses) | Low (simulated only) |
| Diagnostic depth | Low (no waterfall, no video) | High (waterfall, filmstrip, video) |
| Free tier | Full access | Limited (no mobile, no custom location) |
| Account required | No | No (basic), Yes (advanced) |
When to Use Each
Use PageSpeed Insights when:
- You want to know what Google sees for ranking purposes
- You need CrUX field data for real user Core Web Vitals
- You’re doing a quick check and don’t need diagnostic detail
- You want to verify CrUX improvement after making changes
Use GTmetrix when:
- You need the waterfall to diagnose request ordering and timing
- You want the filmstrip to see the visual load progression
- You want to compare before/after performance changes
- You need to store historical test results
Why Both Might Disagree
If GTmetrix shows a 75 performance score and PageSpeed Insights shows 65, the difference is normal — they’re different test environments. Key variables:
- Test location — GTmetrix defaults to Vancouver, Canada; PageSpeed Insights uses a Google data center
- Network conditions — Both simulate mobile, but the exact throttling parameters can differ
- Run-to-run variance — Lighthouse scores can vary 5–10 points between runs
Don’t panic over small disagreements. What matters is the direction of change (is your score improving?) and the field data in PageSpeed Insights.
A Better Combination
For a broader comparison, see Best Website Speed Test Tools. For most workflows, use PageSpeed Insights for field data and debugutils.dev for diagnostic depth. debugutils.dev provides the complete picture — waterfall, filmstrip, video, LCP element, CrUX data — without the account requirements or paid-tier limitations of GTmetrix.