GTmetrix vs PageSpeed Insights: Lab Filmstrips vs Field Core Web Vitals
GTmetrix and PageSpeed Insights both test speed, but they are not the same test. One is a lab waterfall you choose. The other mixes Chrome field data with Lighthouse. Here is how to read both — and why testing one URL is still the real limit.
Same question, different tests
GTmetrix vs PageSpeed Insights is the usual bake-off for a homepage launch. Google PageSpeed Insights (PSI) runs Lighthouse in the lab and, when enough Chrome users have loaded the URL, shows field Core Web Vitals from the Chrome User Experience Report (CrUX). GTmetrix also runs Lighthouse now, then adds the thing people actually open it for: a waterfall, a filmstrip, and a test location you pick. “GTmetrix Pagespeed” in older docs referred to a proprietary score; current GTmetrix is Lighthouse-based, so the headline grades can look similar while the diagnosis does not.
What PageSpeed Insights is for
Use PSI when you need the same lab recipe Google talks about in documentation, and when you care whether real Chrome users are passing LCP, INP and CLS for that URL (or origin). Field data lags and needs traffic. Lab data is a single simulated load — useful, noisy, easy to chase. PSI will not crawl your sitemap. You paste one URL. That is fine for a template you are mid-fixing; it is a poor way to run a site with hundreds of indexable pages.
What GTmetrix is for
Use GTmetrix when you need to see why the load is slow: request order, third-party scripts, font blocking, a video poster the size of a billboard. Region and browser options matter for a CDN or a market that is not “mobile US.” Historical filmstrips help a developer more than a 98 vs 94 Performance number. GTmetrix is still a one-URL (or small monitored set) tool. It is not Search Console, and it does not know which slow URL actually gets impressions.
GTmetrix vs PageSpeed Insights, side by side
| Need | PageSpeed Insights | GTmetrix |
|---|---|---|
| Field Core Web Vitals (CrUX) | Yes, when eligible | Not the same report |
| Lighthouse lab score | Yes | Yes (current GTmetrix) |
| Waterfall / filmstrip | Limited | Strong |
| Choose test city | No (Google’s lab) | Yes |
| Crawl every site URL | No | No (unless you script it) |
| Tie speed to ranking queries | No | No |
If scores disagree, believe the waterfall and the field vitals over the single number. Chasing a GTmetrix grade on a URL nobody searches for is a common waste of a sprint.
The limit both tools share
Both answer “this address, right now.” Slow category templates, bloated article chrome and missing meta on landing pages never get tested if you only paste the homepage. Seomatia gathers Page Insights across the pages that matter on the site, with speed and on-page issues next to the search queries for those URLs. You still open GTmetrix for a filmstrip and PSI for a CrUX check on a money page. You do not need to paste fifty URLs after every release.
A practical order of operations
- Search Console: which URLs have impressions and failing vitals. 2. PSI: field + lab on those URLs. 3. GTmetrix: waterfall on the ones still unclear. 4. Site-wide insights so the rest of the templates are not invisible. That last step is the one www.seomatia.com is built for. GTmetrix vs PageSpeed Insights is then a diagnosis choice, not a religion.