The Core Web Vitals checker reads 28 days of real-user data from Google's Chrome UX Report and tells you whether a page passes LCP, INP and CLS. Lab tests like the PageSpeed test show what could happen; this tool shows what your visitors actually get.
Key takeaways
- Uses the same field data Google uses for its page experience signals, not a one-off lab run.
- A page passes only when LCP, INP and CLS are all "good" at the 75th percentile.
- Low-traffic pages fall back to site-wide (origin) data, so you still get an answer.
Field data vs lab data
Lab tools load a page once on a simulated device. Field data is collected from real Chrome visitors on their own phones and networks. Google ranks with field data, so a page can score 95 in a lab test and still fail Core Web Vitals in the field. Use this checker to see the truth, then the lab test to find the cause.
The thresholds
| Metric | Good | Poor |
|---|---|---|
| LCP | ≤ 2.5 s | > 4 s |
| INP | ≤ 200 ms | > 500 ms |
| CLS | ≤ 0.1 | > 0.25 |
| TTFB | ≤ 0.8 s | > 1.8 s |
Each value is the 75th percentile: three out of four visits must be at or below it.
How to fix a failing metric
- LCP: serve the main image in WebP or AVIF, preload it, and cut server time (TTFB) with caching.
- INP: remove heavy third-party scripts and split long JavaScript tasks.
- CLS: set width and height on images, ads and embeds, and avoid injecting banners above content.
Changes take up to 28 days to show in field data, because the report is a rolling window.
From our audit experience
On most client sites the failing metric on mobile is LCP, and the cause is almost always an unoptimised hero image or a slow host. Fixing those two items usually moves a site from "failed" to "passed" within one data cycle.
Need more than a free tool?
Our team runs full audits, fixes and growth plans for sites in 10 languages.Frequently asked questions
Why does it say there is no data?
Why is my result different from PageSpeed Insights?
Is FID still a Core Web Vital?
How often does the data update?
How we built this tool: the checks and thresholds follow Google Search Central documentation, Schema.org and the IETF/W3C standards, and we tune them against what we see on client sites every month. We keep no record of the text or URLs you enter: generators and calculators run in your browser, while checkers fetch the page through our server and cache the result for a few minutes only to speed up repeat checks. Questions or a bug? Tell us.