Treo vs WebPageTest in 2026: CrUX monitoring dashboard vs free diagnostic depth
Treo turns Chrome UX Report data into a multi-site monitoring dashboard starting at $75 a month. WebPageTest gives you the deepest free diagnostic output in performance testing, run one URL at a time.
Treo
WebPageTest- WebPageTest's free public instance produces deeper diagnostic output than Treo, including frame-by-frame filmstrip playback, a full request waterfall, and raw HAR exports.
- Treo automates the collection step: point it at a domain and sitemap scanning discovers URLs on its own, pulling CrUX field data and Lighthouse scores without anyone triggering individual tests.
- Treo's Free tier covers one site; the first paid tier, Vital, is $75/month for up to 5 sites. WebPageTest's entire public tool is free, with a $9.89/month Pro API layer for automation and priority queuing.
- WebPageTest has no scheduled monitoring or trend dashboard on the free tier; that only arrives with the Pro API. Treo is built around continuous multi-site monitoring starting at its Free plan.
- Both support competitive benchmarking, but the mechanics differ: Treo tracks a competitor's Core Web Vitals scores against yours over time, while WebPageTest compares two test runs side by side for a single moment.
- WebPageTest is open source, maintained by Catchpoint, and can be self-hosted for testing staging or internal environments. Treo has no self-hosted option.
- Treo bundles API access starting at the $75/month Vital plan. WebPageTest's API sits behind a separate $9.89/month Pro tier layered on top of an otherwise free tool.
Treo and WebPageTest both measure Core Web Vitals, but they solve different problems. Treo reads your sitemap, pulls real-user CrUX data plus Lighthouse scores for every URL it finds, and rolls that into a dashboard you can monitor across dozens of client sites at once. WebPageTest runs a single test against a single URL through a real browser at one of 30-plus global locations and hands you a full waterfall, filmstrip, and raw HAR file, more diagnostic detail than almost any commercial tool provides, for free. One is built to watch performance trend over time across a portfolio; the other is built to tell you exactly why one page is slow right now. Which you need depends on whether you are monitoring or diagnosing.
The tools at a glance
Treo
Multi-site Core Web Vitals monitoring built on real CrUX field data.
Treo is a site speed monitoring platform built around the Chrome UX Report rather than synthetic testing alone. Give it a domain and it scans the sitemap to discover URLs automatically, then pairs real-world CrUX field data with Lighthouse lab scores for each one. There is no script to install and nothing to tag manually, which matters once you are tracking more than a handful of pages.
The dashboard is designed for portfolios, not single sites. Competitive benchmarking lets you track a rival domain's Core Web Vitals alongside your own, and the multi-site view scales to hundreds of domains, which is what makes it useful for agencies reporting on several clients from one screen. An API is available from the Vital plan up, so teams with existing Looker Studio or BI pipelines can pull the data out rather than living inside Treo's own dashboard.
The catch is price and scope. Free covers exactly one site, and the jump to Vital at $75/month for up to five sites is steep for a tool that is, underneath, a well-built layer on top of a public Google dataset. It also does one job: performance monitoring. There is no crawling, no content auditing, no log file analysis, so it sits alongside a broader technical SEO toolkit rather than replacing one.
| 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 |
WebPageTest
The open-source standard for deep, real-browser performance diagnostics.
WebPageTest is an open-source performance testing tool originally built by AOL engineer Patrick Meenan and now maintained by Catchpoint. It runs tests through real Chrome, Firefox, or Edge instances at more than 30 global locations, with full control over connection throttling and device profile, and it has been the reference benchmark front-end engineers compare other tools against for over fifteen years.
Where it separates from monitoring dashboards is depth. Every test returns LCP, CLS, INP, and TTFB alongside a full request waterfall with DNS, connection, and SSL timing, a frame-by-frame filmstrip showing exactly what a user saw as the page loaded, and a raw HAR export. Lighthouse runs alongside the waterfall so you get performance and SEO or accessibility findings from one test. No-Code Experiments lets you simulate a change, like removing a third-party script, before any engineering time is spent on it.
None of that comes with a monitoring layer on the free tier. There is no scheduled testing, no trend dashboard, and no API without the $9.89/month Pro plan. The interface also assumes you already know what you are looking at; it rewards performance expertise rather than guiding a beginner toward an answer. For a one-off deep dive it is close to unbeatable. For tracking Core Web Vitals across a client portfolio week over week, it is the wrong tool by design.
| Feature | Free Free | Pro API (Starter) $9.89/month |
|---|---|---|
| On-demand tests | Shared queue | Priority access |
| Global test locations | 30+ | 30+ |
| Filmstrip and video replay | Yes | Yes |
| Lighthouse integration | Yes | Yes |
| API access | No | Yes |
| Continuous monitoring | No | Yes |
Head-to-head feature comparison
| Feature | Treo | WebPageTest |
|---|---|---|
| Core measurement approach | CrUX field data (real Chrome users) plus Lighthouse lab scores | Real browser testing (Chrome, Firefox, Edge) plus Lighthouse |
| Automated sitemap-wide discovery | Yes, sitemap scanning discovers URLs automatically | No, tests are run per URL, not across a sitemap |
| Global real-browser test locations | Not specified, relies on the public CrUX dataset rather than its own test locations | 30+ locations |
| Filmstrip / video replay | No | Yes, frame-by-frame filmstrip and video replay |
| Full waterfall / HAR export | No | Yes, full waterfall with connection-level timing and HAR export |
| Competitive benchmarking | Yes, on Vital and above | Yes, side-by-side comparison of two test runs |
| Lighthouse integration | Yes | Yes |
| Continuous monitoring dashboard | Yes, on every paid tier | No on the free tier; Pro API adds scheduled testing |
| API access | Yes, Vital plan and above | Yes, Pro API at $9.89/month |
| Self-hosted / open source | No | Yes, open source and self-hostable |
| Multi-site portfolio dashboard | Yes, up to 50 sites on Scale, custom on Enterprise | No, built around single tests rather than a portfolio view |
| Free tier | Yes, 1 site | Yes, the full public instance |
| Starting paid price | $75/mo (Vital) | Free (Pro API adds $9.89/mo) |
Which should you choose?
TreoWebPageTestTreoWebPageTestWebPageTestWebPageTestWebPageTestTreo and WebPageTest rarely compete for the same task. Treo automates collection and turns CrUX data into something you check weekly across a portfolio; WebPageTest is what you open when you need to know exactly why a page is slow and are willing to read a waterfall to find out. Treat Treo as the dashboard and WebPageTest as the microscope, not as two versions of the same product.
Bottom line
Use WebPageTest first, it is free and gives you more diagnostic detail than Treo ever will, especially for a one-off audit or a migration baseline. Add Treo once you are responsible for tracking Core Web Vitals across more than a couple of sites on an ongoing basis and need a dashboard instead of a queue of manual tests; the $75/month Vital plan is the point where that automation starts paying for itself. Running both is not redundant: WebPageTest for the deep dive, Treo for the weekly check-in.
Frequently asked questions
Is Treo worth paying for when WebPageTest is free?
Treo is worth paying for once you are monitoring Core Web Vitals across more than a couple of sites on an ongoing basis, because it automates URL discovery and pulls CrUX field data continuously instead of requiring you to run and re-run individual tests. WebPageTest's free tier is the better choice for a one-off audit or a single diagnostic deep dive; it just is not built as a recurring monitoring dashboard.
Does WebPageTest replace a Core Web Vitals monitoring tool like Treo?
No, WebPageTest does not replace a monitoring tool on its free tier because there is no scheduled testing or trend dashboard built in. The Pro API at $9.89/month adds programmatic scheduling, but even then it lacks the automatic sitemap-wide discovery and multi-site view that Treo is built around.
Which tool gives more detail on why a specific page is slow?
WebPageTest gives far more diagnostic detail on a specific page, including a full request waterfall, frame-by-frame filmstrip, and raw HAR export. Treo shows you CrUX field scores and Lighthouse lab scores, which tell you a page is slow and roughly why, but not the request-by-request breakdown WebPageTest provides.
Can I use Treo and WebPageTest together for client reporting?
Yes, and they complement each other well for client reporting: Treo's dashboard and API supply the recurring trend data and competitive benchmarking, while WebPageTest's filmstrip and waterfall provide the evidence for a specific optimization recommendation. Agencies commonly use Treo for the ongoing tracking layer and pull in a WebPageTest run when a client asks why a particular page regressed.
Does either tool require installing tracking code on my site?
Neither tool requires installing tracking code. Treo reads public CrUX data from Google and runs Lighthouse audits on demand, and WebPageTest runs tests against your live URL through its own browser instances, so there is nothing to add to your codebase for either one.
Is WebPageTest better than Treo for a one-time site migration audit?
WebPageTest is the better tool for a one-time site migration audit, since a single detailed test with filmstrip and waterfall data is exactly what you need to document a before-and-after baseline. Treo is designed for continuous monitoring across many URLs over time, which is more than a one-time audit requires.