1. Home
  2. Free tools
  3. Core Web Vitals test

Core Web Vitals test

Check the three Core Web Vitals for any public page: loading (LCP), visual stability (CLS) and responsiveness (INP, measured in the lab as Total Blocking Time). Each result is shown against Google's thresholds, with what to change.

No sign-up.Try:

How to use it

  1. Enter the page address and choose Mobile (the strict default) or Desktop.
  2. Open the report and go to the Core Web Vitals section. Each metric is coloured: green is good, amber needs work, red is poor.
  3. Open the guide for the metric that is not green, apply the fixes, then run the test again.

What it checks

  • Largest Contentful Paint (loading speed of the main content)
  • Cumulative Layout Shift (how much the page jumps while loading)
  • Total Blocking Time, the lab metric that predicts Interaction to Next Paint
  • First Contentful Paint and Speed Index for context
  • The element Lighthouse picked as LCP, and the layout shifts it saw
  • Opportunities ranked by time saved

Limits

  • Measures lab data from one simulated run. Search Console reports field data from real users over 28 days, and the two often differ.
  • Interaction to Next Paint needs real interaction, so a lab run shows related measures such as Total Blocking Time instead.
  • Results are cached for a short time and can vary between runs.

Public pages only, one page at one point in time. See the methodology and terms.

The three Core Web Vitals

  • Largest Contentful Paint (LCP): how long the biggest visible element (often a hero image or heading) takes to appear. Good: 2.5 s or less.
  • Cumulative Layout Shift (CLS): how much content moves unexpectedly while the page loads. Good: 0.1 or less.
  • Interaction to Next Paint (INP): how quickly the page reacts to taps and clicks. Good: 200 ms or less. INP needs real user interactions, so a lab test cannot measure it directly. Lighthouse reports Total Blocking Time (TBT) instead, which tracks it well.

Lab data and field data

Google ranks pages using field data: measurements from real Chrome users over 28 days, available through the Chrome UX Report when a page has enough traffic. This test produces lab data: one controlled run. Lab data is ideal for finding the cause of a problem and checking a fix straight away; field data is the final judge. This site does not show field data because it needs a Google API key.

Frequently asked questions

What are Core Web Vitals?

Three measurements Google uses to describe real-world page experience: loading (LCP), visual stability (CLS) and responsiveness (INP). They are part of Google's page experience signals, a small ranking factor next to relevance.

Does this test show INP?

Not directly. INP is measured from real visits. The lab report shows Total Blocking Time, which indicates whether long JavaScript tasks are likely to make interactions slow.

Why do my results differ from Search Console?

Search Console reports field data from real users over 28 days. This test is a single lab run on a simulated device, so the numbers are related but not identical.

How do I improve LCP?

Make the main image or text load first: serve a right-sized, compressed hero image, preload it, avoid render-blocking CSS and JavaScript, and reduce server response time.

How do I fix layout shift?

Give images, videos and ads explicit width and height (or aspect-ratio), reserve space for late content, and avoid inserting banners above existing content.

Do I need to pass all three for good rankings?

No. They are one signal among many. Content that matches the search comes first, but a slow, jumpy page loses visitors and conversions regardless of ranking.

↑ ↓ to moveEnter to openEsc to closeAll results