Core Web Vitals Checker
Read saved CrUX or PageSpeed Insights data for page and origin. Review field p75 ratings for LCP, INP and CLS alongside any supplied Lighthouse lab metrics.
Compare Page and Origin Web Vitals
Open a saved CrUX API or PageSpeed Insights response, or a Lighthouse report for lab readings.
Core Web Vitals Checker: how to use it
- Paste or open saved CrUX API or PageSpeed Insights JSON. Load the example to compare page and origin readings.
- Check the source, URL or origin, device evidence and collection window. Review the 75th-percentile values and find which required measurement controls the assessment.
- Add a second saved report if needed. Export the readings and field scope as JSON.
Limits and notes
Reads up to two saved JSON documents of 6,291,456 UTF-16 code units each. A Lighthouse-only report can show lab metrics. Field ratings depend on actual supplied percentiles. No query to CrUX or Google is made from this workspace.
How your privacy works →Core Web Vitals Checker: common questions
Why is the origin good when the page needs improvement?
Origin readings aggregate experiences across an origin. A single page has a different sample, so its metrics can fall into a different band.
Can total blocking time fill in missing field INP?
TBT measures blocking during a lab run. Treat a missing field INP as unavailable and obtain an eligible field record for that scope.
Which values determine the Core Web Vitals assessment?
The assessment uses the p75 values of LCP, INP and CLS. The PageSpeed rule can assess LCP and CLS when field INP is unavailable. FCP and TTFB are supplemental.