Core Web Vitals:Does your page pass Google's Core Web Vitals?
See LCP, INP and CLS from real Chrome users next to the lab values, each rated good, needs improvement or poor against Google's thresholds.
- Free, no account
- Results in under a minute
- Real-user and lab data for any public URL
example-shop.hr
WordPress 6.8Sample shop · homepage · mobile Chrome · the same check you get for your own site
4 passed · 0 failed · 0 warnings. Nothing to fix here.
Lab data from Google PageSpeed Insights (Lighthouse 12.8.2) · desktop score 100 · no field data: not enough real Chrome users visit this page yet
Lab (Lighthouse 12.8.2)
| Metric | Value | Rating |
|---|---|---|
| First Contentful Paint | 0.8 s | good |
| Largest Contentful Paint | 0.8 s | good |
| Total Blocking Time | 0 ms | good |
| Cumulative Layout Shift | 0 | good |
| Speed Index | 4.3 s | needs work |
| Time to First Byte | Root document took 30 ms | good |
LCP element: <p>
Field (Core Web Vitals)
Filmstrip
0.4 s- 0.8 s
- 1.2 s
- 1.6 s
- 2.0 s
- 2.4 s
- 2.8 s
3.2 s
Waterfall · top 1 of 1 requests
- example.com/0 KB
What we found
Show 4 passed checks
What this tool checks
The three Core Web Vitals from real users and from a lab run, with TTFB and FCP as supporting metrics.
Largest Contentful Paint
How long the biggest element on screen takes to appear, which visitors and Google judge speed on.
Interaction to Next Paint
How quickly the page reacts to taps and clicks for real Chrome users, so it never feels frozen.
Cumulative Layout Shift
How much the page jumps around while loading, one of Google's three Core Web Vitals.
Real-user Largest Contentful Paint
How long the biggest element takes to appear for real Chrome users, against Google's 2.5 s target.
Real-user Interaction to Next Paint
How fast the page reacts to taps and clicks for real Chrome users, against Google's 200 ms target.
Real-user Cumulative Layout Shift
How much the page jumps around on real visitors' devices, against Google's 0.1 target.
Time to First Byte
How long the server takes to start answering, which delays everything else on the page.
Real-user Time to First Byte
How long real visitors wait for the server's first byte, against Google's 800 ms target.
First Contentful Paint
How long visitors stare at a blank page before the first text or image appears.
Real-user First Contentful Paint
How long real visitors wait to see the first text or image, against Google's 1.8 s target.
Show 6 more checks
Real-user Interaction to Next Paint
How fast the page reacts to taps and clicks for real Chrome users, against Google's 200 ms target.
Real-user Cumulative Layout Shift
How much the page jumps around on real visitors' devices, against Google's 0.1 target.
Time to First Byte
How long the server takes to start answering, which delays everything else on the page.
Real-user Time to First Byte
How long real visitors wait for the server's first byte, against Google's 800 ms target.
First Contentful Paint
How long visitors stare at a blank page before the first text or image appears.
Real-user First Contentful Paint
How long real visitors wait to see the first text or image, against Google's 1.8 s target.
How it works
Read real-user data
We read LCP, INP and CLS from the Chrome UX Report, the 75th percentile of real Chrome visitors over 28 days.
Run a lab test
A Lighthouse lab run measures the same page, with TTFB and FCP as supporting metrics.
Rate each metric
Each metric is rated against Google's thresholds (2.5 s, 200 ms, 0.1) and linked to the guide that explains how to move it.
Real-user data exists only for pages and sites with enough Chrome visitors, and INP needs real interactions, so it never appears in the lab run.
Questions
Is this really free?
Yes. getReport is funded by donations, not plans. This tool runs the full report and shows you the part it is about; the complete report with all seven modules is one click away, also free.
Why is there no field data for my page?
Google only publishes Core Web Vitals for pages and sites with enough Chrome visitors. Smaller sites get origin-level data or none; the lab run still shows what to fix.
Is INP measured in the lab?
No. INP needs real interactions, so it only exists in field data. Total Blocking Time is the lab stand-in and usually moves together with INP.
Do you store my results?
The report is kept for 12 months at its shareable link so you can come back to it. Reports are not listed publicly and carry a noindex tag; nothing about your visitors is collected.
Why do Core Web Vitals matter?
Since 2021 Google uses page experience as a ranking signal, and Core Web Vitals are the measurable part of it. A page that fails LCP or INP is competing with one hand tied. The field data is what Google actually uses. If your page has too few Chrome visitors for field data, the lab numbers are the best prediction, and the fixes are the same.
Related free tools
All 41 tools →Free, funded by the people who use it
€0 of €75 this month. At €75, site crawl up to 500 pages + weekly re-check switches on for everyone.