Core Web Vitals Checker

Paste a URL to run a real Lighthouse check — actual Largest Contentful Paint, Cumulative Layout Shift, and Interaction to Next Paint, plus real-world Chrome UX Report field data when it's available. Free, no signup.

What Core Web Vitals actually measure

Google's three Core Web Vitals each measure a different piece of real user experience: LCP (how long the largest visible element takes to render), CLS (how much the page unexpectedly shifts around while loading), and INP (how responsive the page feels when someone actually interacts with it). All three came from research into what visitors notice and complain about, not arbitrary technical thresholds.

How to fix what it finds

A slow LCP is usually a large hero image or unoptimized web font blocking render — compress images, preload critical assets, and avoid render-blocking resources. Layout shift almost always traces back to images or ads without a reserved size, or content injected above what's already loaded. A weak INP usually means heavy JavaScript tying up the main thread when a visitor tries to click or type.

Frequently asked questions

How is this different from the Page Speed & Size Check tool?

Page Speed & Size Check measures a plain fetch — server response time and how much HTML/resources a page weighs. This tool runs an actual Lighthouse audit in a real browser, the same engine behind Google's own PageSpeed Insights, giving real rendering metrics: Largest Contentful Paint, Cumulative Layout Shift, and Interaction to Next Paint — the three official Core Web Vitals.

What's the difference between the "lab" and "field" numbers?

Lab data is this specific Lighthouse run, right now, on Google's test infrastructure — reproducible, but from one simulated visit. Field data comes from Google's Chrome UX Report: real numbers from real Chrome visitors who've actually loaded this page over the past 28 days. Field data is what genuinely affects rankings; lab data is what you use to debug and fix issues, since it's consistent and repeatable.

Why does it say "no real-world data available"?

Google's Chrome User Experience Report only publishes data for origins with enough Chrome traffic to be statistically meaningful and preserve visitor privacy — many smaller or newer sites simply don't have enough volume yet. The lab result is unaffected either way; it's a fresh, real Lighthouse run regardless of traffic.

Why does this take so much longer than your other tools?

Every other check on this site is a fast HTTP request. This one is different — it's a full Lighthouse audit: Google spins up a real Chrome instance, loads the page, and measures its actual rendering behavior end to end. That takes real time, typically 15-60 seconds depending on the page and current load on Google's infrastructure.

Is this mobile or desktop data?

Mobile — Google's ranking-relevant Core Web Vitals evaluation is mobile-first, so that's what this tool checks by default to match what actually matters for search.

Related tools

Command Palette

Search for a command to run...