Core Web Vitals test: see if your page passes LCP, INP and CLS
This Core Web Vitals test shows 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 result:example-shop.hr
WordPress 6.8Sample shop · homepage · mobile Chrome · the same check you get for your own site
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 | 27 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 · 1 requests
- example.com/0 KB
What we found
Show 4 passed checks
What the Core Web Vitals test 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 the Core Web Vitals test 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.
Core Web Vitals test questions
How do I check Core Web Vitals for my site?
Enter a page above: the test reads LCP, INP and CLS from the Chrome UX Report, what real Chrome visitors experienced over 28 days, and runs a Lighthouse lab test beside it. For the whole site, open the Core Web Vitals report in Search Console, which groups similar URLs. The Performance panel in Chrome's developer tools shows live values for your own visit.
What are good Core Web Vitals scores?
Good means LCP within 2.5 s, INP within 200 ms and CLS at or below 0.1, measured at the 75th percentile of page visits. Poor starts above 4 s for LCP, 500 ms for INP and 0.25 for CLS; anything between needs improvement. The test colours each metric by these thresholds, for real users and for the lab run.
What happened to FID in Core Web Vitals?
Interaction to Next Paint replaced First Input Delay as a Core Web Vital in March 2024. FID only timed the delay before the first interaction was handled; INP looks at the interactions throughout a visit and reports one of the slowest, so it catches pages that react slowly after loading. This test reports INP from real users. Total Blocking Time is its lab stand-in.
Which Core Web Vital should I fix first?
The one rated poor for real users, and among those usually LCP, because it affects most pages and has the clearest fixes: a faster server, a lighter hero image and fewer render-blocking files. Fix INP next if the page runs heavy scripts, and CLS if content jumps while loading. The test links each metric to the guide that explains how to move it.
What does the 75th percentile mean in Core Web Vitals?
It means three out of four page visits were at least that fast. Google judges each metric at the 75th percentile of real Chrome visits over 28 days, so a page passes LCP when 75 % of visits show the main content within 2.5 s. A few slow visits on bad connections do not fail you, but a quarter of visitors having a poor experience does.
Why is INP missing from the lab results?
Because INP measures how quickly the page responds to real clicks, taps and key presses, and a lab test loads the page without touching it. Lighthouse shows Total Blocking Time instead, which roughly tracks INP: long JavaScript tasks make both worse. Real INP appears when the Chrome UX Report has enough visits to your page or site.
Why is there no field data for my page?
Google only publishes Core Web Vitals for pages and sites with enough Chrome visitors to be statistically meaningful. Smaller sites get origin-level data, all pages combined, or none at all. The lab run still shows what to fix, and Total Blocking Time points at the same JavaScript problems that make INP slow.
Is this Core Web Vitals test free?
Yes, with no sign-up. getReport is funded by donations, not plans, and the complete report with all seven modules is one click away, also free. It stays at its shareable link for 12 months, is not listed publicly and carries a noindex tag, and nothing about your visitors is collected.
Related free tools
All 59 tools →Free, funded by the people who use it
No account, no paid plan. Donations keep it running.