Core Web Vitals Audit
Treo CWV Audit loads your page, interacts with it like a visitor, finds the causes, tests each fix on the live page, and hands the proven ones to your coding agent.
Private beta for Treo account owners50 audits a month
A real auditwww.daals.co.uk/products/maru-round-4-6-seater-extending-oak-pedestal-dining-table-silver-oakdesktop
Largest Contentful Paint LCP
2.35sGood→1.72s
2 fixes tried1 proven11 loadsOpen this audit
Three real audits. Open one and click through the whole report.
A Core Web Vitals audit in seven steps. It measures LCP, CLS and INP the way a visitor gets them, finds what holds each one back, and proves which fixes work.
The audit loads your page on a phone and on a desktop and shows one load you can read like DevTools: LCP and its four parts, the shifts, the frames. A URL is enough: no script, no setup, no access to your code.
In this audit
Largest Contentful Paint LCP
2.35sGood
on a desktop

A page is more than its load. The audit writes the scenarios a visitor would take on this page and walks them step by step: it types, it presses, it waits for the next paint. Every press is measured, so INP comes with the press that set it and the script behind it. For INP the audit finds the cause today; testing its fixes, as it does for LCP and CLS, comes next.
In this audit
Interaction to Next Paint INP
600msPoor
on a desktop, set by the press “Add to Basket”

A finding names its place on the waterfall, what it costs and the experiment that tested it. Click one, and its requests, tasks and shifts light up on the chart. The one open here is “17 requests block the render”; the fix that defers the Convert A/B testing scripts is proven.
In this audit
Findings
10
3 of them high on this load

A fix is applied in the audit’s browser as the page loads, and the page is loaded again and again, with the fix and without it. One fix made this page faster and is marked proven. One made it slower. Each has its number. So the sprint goes to the one that works, and none of it to the one that does not.
In this audit
Fixes tried
2
1 proven11 loads

Your page
Name it. In the beta, Treo CWV Audit measures it, finds the cause and tests each fix on it.
Private beta for Treo account owners50 audits a month
Or see it on a real page first: live examples
Open any fix and see its load beside the untouched one, on one clock. The frames show the page painting sooner. The LCP parts show where the time went: here the render delay drops from 0.75 s to 0.21 s. The requests show what the fix changed.
In this audit
LCP with the fix
1.72s
2.35 s without it

A proven fix comes with the exact change and a prompt. Copy it into your coding agent, review what it writes, and ship it. Treo proves and shows; you decide. An API and a command line tool come next, so your agent can start an audit and read the proven fixes itself. Next
In this audit
Defer the Convert A/B testing scripts
−0.67s
Proven

The audit runs by itself first. After that it works for you: test your own fix, add your own scenario, and get the same proof, a number beside the untouched page. Any expert can tune it to their site.
In this audit
Your own tests and scenarios
In development

A fix is proven in the lab, on your live page, in the audit’s own browser: nothing on your site changes, and your real users confirm the gain after you ship. Pages behind a login are not audited.
One audit loads your page dozens of times in real Chrome, on a phone and on a desktop, to measure each fix. That takes real machines. So the beta is private only for Treo account owners.