GTmetrix vs Treo in 2026: Lab-Based Page Speed Testing vs Real-World Core Web Vitals Monitoring
GTmetrix tells you what Chromium sees when it loads your page. Treo tells you what real Chrome users actually experienced, pulled straight from Google's own Chrome UX Report.
Treo pulls real Chrome UX Report (CrUX) field data from actual users; GTmetrix relies entirely on synthetic Lighthouse-based testing through Chromium, with no field data source.
GTmetrix has a genuinely free tier with full waterfall diagnostics and Core Web Vitals included. Treo's free tier is limited to one site with no competitive benchmarking or API access.
Treo automatically discovers URLs through sitemap scanning; GTmetrix requires manually adding each page you want monitored, up to the cap of your plan.
Competitive benchmarking against named domains is available on Treo's $75/month Vital plan and above. GTmetrix has no competitor-tracking feature at any tier.
GTmetrix's waterfall chart remains the clearest free diagnostic visualization for a single page; Treo's interface is built around CrUX trend charts and multi-site dashboards rather than per-request waterfalls.
Both tools gate API access behind a paid plan: GTmetrix from its $18/month Starter tier, Treo from its $75/month Vital tier.
Treo's multi-site dashboard is built to scale across hundreds of client domains; GTmetrix caps monitored pages at 20 on its top Growth tier, priced at $40/month.
GTmetrix and Treo both report on Core Web Vitals, but they start from different data sources and different use cases. GTmetrix runs a synthetic Lighthouse-based test through Chromium and hands back a waterfall chart, a score, and (on paid tiers) scheduled monitoring, all through a free-to-start web interface. Treo skips synthetic-only scoring in favor of the Chrome UX Report, real field data from actual Chrome users over the trailing 28 days, and pairs it with on-demand Lighthouse audits, automated sitemap scanning, and competitive benchmarking against named domains. GTmetrix is the faster way to diagnose one page for free. Treo is the better choice if you need to know what real visitors experienced across a portfolio of sites, and are willing to pay $75 a month to get competitive benchmarking and API access once you're past the single-site free tier.
The tools at a glance
GTmetrix
Page speed analysis with Lighthouse, Web Vitals, waterfall charts, and performance monitoring.
GTmetrix loads a page through Chromium and returns a Lighthouse-based Core Web Vitals score alongside a full waterfall chart that breaks down every request into DNS, TCP, TTFB, and download timing. It is a lab test, not a measurement of what real visitors experienced, but the payoff is speed and clarity: run a URL, get an answer in under a minute, no account required for basic use.
Paid tiers add multi-location testing, mobile emulation, and monitoring slots that alert when a metric crosses a threshold, which turns GTmetrix from a one-off diagnostic into light ongoing tracking. The catch is that every monitored page has to be added by hand, and the cap rises with the plan: 1 page on Solo, 20 on Growth. There is no way to point GTmetrix at a sitemap and have it discover new URLs on its own.
What GTmetrix does not do is show you field data. It has no connection to the Chrome UX Report or any other real-user data source, so a page that scores well in GTmetrix could still be loading slowly for a meaningful share of actual visitors on weaker connections or older devices. For quick diagnosis and light monitoring, that gap rarely matters. For understanding real-world performance at scale, it does.
| Feature | Free Free | Solo $5.50/mo | Starter $18/mo | Growth $40/mo |
|---|---|---|---|---|
| On-demand tests | Limited | 50/mo | 200/mo | Unlimited |
| Monitored pages | 0 | 1 | 5 | 20 |
| Test locations | 1 | 7 | 14 | 22+ |
| Mobile testing | No | Yes | Yes | Yes |
| API access | No | No | Yes | Yes |
Treo
Core Web Vitals monitoring using real-world Chrome UX Report data.
Treo builds its entire product around a distinction GTmetrix does not make: the difference between a synthetic lab score and what a real Chrome user actually experienced. It pulls field data from the Chrome UX Report, which reflects real visitor sessions over the past 28 days, and pairs it with on-demand Lighthouse audits so a team can see the lab number and the real-world number side by side rather than trusting one in isolation.
Setup leans on automation rather than manual configuration. Point Treo at a domain and it reads the sitemap to discover URLs on its own, no tagging script, no hand-built monitoring list. For an agency managing many client sites, that removes the single biggest friction point in rolling out monitoring across a portfolio, and the multi-site dashboard is built specifically for tracking hundreds of domains from one account.
The pricing curve is steeper than it first looks. Free covers exactly one site, which is fine for checking your own domain but not for running an agency practice. The jump to Vital at $75 a month unlocks competitive benchmarking and API access, but only for up to five sites; scaling past that means Pro at $185 or Scale at $375. It is still a fundamentally different pricing model than GTmetrix, priced around real user data and portfolio scale rather than per-page monitoring slots.
| Feature | Free $0/month | Vital $75/month | Pro $185/month | Scale $375/month | Enterprise Contact for pricing |
|---|---|---|---|---|---|
| Sites monitored | 1 | Up to 5 | Up to 15 | Up to 50 | Custom |
| CrUX field data | Yes | Yes | Yes | Yes | Yes |
| Lighthouse audits | Limited | Hourly | Hourly | Hourly | Custom |
| Competitive benchmarking | No | Yes | Yes | Yes | Yes |
| API access | No | Yes | Yes | Yes | Yes |
Head-to-head feature comparison
| Feature | ||
|---|---|---|
| Data source | Synthetic lab testing (Chromium) | Chrome UX Report (CrUX) field data plus on-demand Lighthouse |
| Core Web Vitals tracking | Yes (LCP, CLS, INP via Lighthouse) | Yes (LCP, CLS, INP) |
| Waterfall / per-request diagnostics | Yes, detailed waterfall with DNS/TCP/TTFB breakdown | No dedicated waterfall; Lighthouse lab data plus CrUX trend charts |
| Automated URL discovery | No, monitored pages added manually | Yes, automatic sitemap scanning |
| Competitive benchmarking | No | Yes, Vital plan and up |
| Multi-site dashboard | No (single dashboard, tiered page caps) | Yes, built for hundreds of domains |
| Scheduled monitoring | Yes, 1 to 20 monitored pages by tier | Yes, continuous CrUX plus scheduled Lighthouse audits |
| API access | Yes, Starter plan ($18/mo) and up | Yes, Vital plan and up |
| Free tier | Yes | Yes, limited to 1 site |
| Pages/sites on entry paid tier | 1 monitored page (Solo, $5.50/mo) | Up to 5 sites (Vital, $75/mo) |
| Starting paid price | $5.50/month (Solo) | $75/month (Vital) |
Which should you choose?
The real split here is lab versus field data, and it drives everything else about how each tool is priced and built. GTmetrix is optimized for a fast, free, single-page answer: it does not need real-user data because it is not trying to represent your whole traffic base, just what Chromium sees on one load. Treo starts from the opposite assumption, that a lab score can hide what actual visitors experience, and builds sitemap discovery and multi-site dashboards around monitoring that gap at scale. Treo's one-site free tier is not a real substitute for GTmetrix's free diagnostic depth, and GTmetrix's manual page-adding workflow is not a real substitute for Treo's automated portfolio monitoring.
Bottom line
Reach for GTmetrix, free tier included, when you need a fast answer to why one page is slow and want a waterfall chart you can hand to a developer. Choose Treo, starting at $75 a month for Vital, if you're monitoring Core Web Vitals across multiple sites and need real Chrome UX Report data plus automated URL discovery rather than a hand-maintained list. An agency running both a diagnostic practice and ongoing multi-site monitoring will likely end up using GTmetrix to investigate what Treo's CrUX data flags as a problem.
Frequently asked questions
What is the difference between GTmetrix's scores and Treo's Core Web Vitals data?
GTmetrix scores come from a synthetic lab test run through Chromium under controlled conditions. Treo's core numbers come from the Chrome UX Report, real field data collected from actual Chrome users over the trailing 28 days, which can differ meaningfully from a lab score if your visitors use slower devices or connections than the test environment simulates.
Is Treo worth it over GTmetrix for a small business with one website?
Not usually. Treo's free tier only covers one site and lacks competitive benchmarking and API access, so a small business gets more practical value from GTmetrix's free tier or $5.50/month Solo plan, both of which include waterfall diagnostics that Treo does not lead with. Treo starts to pay off once you're monitoring several sites or specifically need real CrUX field data.
Does GTmetrix use real user data like Treo's Chrome UX Report integration?
GTmetrix relies entirely on synthetic testing through Chromium and has no connection to the Chrome UX Report or any other field data source. Treo is built specifically around CrUX field data, which is the main functional difference between the two tools.
Can GTmetrix automatically discover and monitor all the URLs on my site the way Treo does?
GTmetrix cannot do this: it requires you to manually add each page you want monitored, up to the cap set by your plan (1 page on Solo, 20 on Growth). Treo's sitemap scanning discovers URLs automatically without any manual list-building, which is a meaningful time saver for large sites.
Which tool is cheaper for tracking Core Web Vitals across multiple client sites?
Treo is usually the better value once field data and competitive benchmarking matter, since its $75/month Vital plan covers up to 5 full sites with real CrUX data and competitor tracking bundled in, features GTmetrix does not offer at any price. GTmetrix's Growth plan is cheaper in absolute terms at $40/month and covers up to 20 monitored pages, but it is answering a narrower question, page speed alone, without field data or competitor context.
What happens if a URL doesn't have enough traffic for Treo's CrUX data to show up?
Treo will still show on-demand Lighthouse lab data for pages that lack sufficient real-user traffic in Chrome, since CrUX only includes URLs that meet Google's minimum traffic threshold. GTmetrix does not have this limitation since it never relies on field data in the first place, every test it runs produces a synthetic result regardless of a page's traffic volume.

