Core Web Vitals checker

Enter a page URL to see real-user field data collected from Chrome users and, where available, lab measurements, shown separately. LCP, INP and CLS are rated good, needs improvement or poor.

Want a free SEO report for your site?

Our team reviews your rankings, technical health and opportunities and prepares a report for you.

A free SEO report for your site

Leave your details; our team will prepare a report on your rankings, technical health and opportunities and get in touch.

Three metrics, three questions

Core Web Vitals measure user experience from three angles. The thresholds below are the ones published on web.dev:

MetricWhat it measuresGoodNeeds improvementPoor
LCP (Largest Contentful Paint)How quickly the main content appears≤ 2.5 s2.5–4 s> 4 s
INP (Interaction to Next Paint)How quickly the page responds to clicks, taps and key presses≤ 200 ms200–500 ms> 500 ms
CLS (Cumulative Layout Shift)How much content moves around while loading≤ 0.10.1–0.25> 0.25

According to web.dev, a page passes when these targets are met at the 75th percentile of page loads. So even if most visits are fine, a slow quarter of visits can push the result to "needs improvement".

How to use it

  1. Enter the full URL of the page you want to check.
  2. Start with the field data. It comes from the Chrome UX Report (CrUX) and reflects the last 28 days at the 75th percentile. web.dev recommends assessing mobile and desktop separately.
  3. Where configured, lab data from PageSpeed Insights / Lighthouse appears in its own section. Use it to understand where a problem comes from.
  4. Pick your focus based on which metric is red or amber.

Interpreting the results

Field data tells you what happens; lab data helps explain why. Real users arrive on all sorts of devices and connections, and field data reflects what they actually experience. A lab run is one controlled test, and its numbers can differ from field data. When the two disagree, trust the field data for user experience.

INP can't be measured directly in the lab. It requires real interactions. Lab tools run without a user clicking around, so they typically show indirect indicators, such as long tasks blocking the main thread, instead.

Common causes:

  • LCP: Large, uncompressed images; slow server response; a hero image discovered late; render-blocking CSS and JavaScript.
  • INP: Heavy JavaScript, third-party tags, event handlers that do too much work on a single click.
  • CLS: Images and ad slots without reserved dimensions, banners injected after load, text reflowing when web fonts swap in.

Limitations

  • Low-traffic pages may have no CrUX data, and the tool won't guess.
  • Field data summarises a 28-day window, so yesterday's fix may not be visible yet.
  • A lab run is a single test and can vary slightly each time you run it.
  • Google's page experience documentation points out that good results in Core Web Vitals reports don't guarantee your pages will rank at the top.

To watch field data for your whole site every day, alongside a weekly technical crawl, see the SEO site audit.

With SEOLOK

SEO site audit: catch technical problems before they cost you traffic

Every week SEOLOK crawls your site with a real browser, lists technical and content issues by importance and gives each page a 0–100 signal score. Core Web Vitals field data refreshes daily.

See how it works

Frequently asked questions

What's the difference between field data and lab data?

Field data comes from the real experiences of Chrome users who visited the page and summarises the last 28 days. Lab data is a single test in a controlled environment with an assumed device and connection. They answer different questions, which is why they're shown separately.

Why is there no field data for my page?

The Chrome UX Report only publishes data for pages and origins with enough real-user experiences. Low-traffic pages may have none; in that case the tool says so rather than estimating. When page-level data is missing, origin-level data can still give you a sense of the site as a whole.

Are Core Web Vitals a ranking factor?

Google's documentation says good Core Web Vitals, together with other aspects of page experience, align with what its core ranking systems seek to reward. The same documentation says Google still tries to show the most relevant content even when page experience is weaker, and that good scores don't guarantee top rankings. The clearest benefit is a better experience for the people using the page.

I fixed something. When will the results update?

Field data covers a rolling 28-day window, so improvements show up gradually and can take about four weeks to be fully reflected. Lab measurements reflect the change immediately.

Sources

  1. web.dev: Web Vitals
  2. web.dev: Largest Contentful Paint (LCP)
  3. web.dev: Interaction to Next Paint (INP)
  4. web.dev: Cumulative Layout Shift (CLS)
  5. Chrome for Developers: CrUX methodology
  6. Google Search Central: Understanding page experience in Google Search results

Technical SEO

How Do Core Web Vitals Affect SEO and Rankings?

How Core Web Vitals affect SEO: LCP, INP and CLS thresholds, field vs lab data, what Google says about page experience, and how much effort is worth it.

SEOLOK Editorial Team · · 7 min read

Rank tracking

Why Are Mobile and Desktop Google Rankings Different?

Why mobile and desktop Google rankings differ: mobile-first indexing, results layout, content parity, location and page experience, and how to track both.

SEOLOK Editorial Team · · 7 min read

Technical SEO

What Are Thin Content and Zombie Pages?

What thin content and zombie pages are, how to find them, and how to decide with data whether to update, merge and redirect, noindex or remove each page.

SEOLOK Editorial Team · · 7 min read