Free tool, no account required

Free Core Web Vitals Checker (LCP, INP, CLS)

Check 75th-percentile real-user LCP, INP and CLS from Chrome field data and see whether all available metrics are within the published good thresholds.

Also known as: CWV, LCP, INP, CLS, FID, Core Web Vitals

Evidence shown with sourceNo account requiredNo invented metrics

Run a real check above

Submit a public URL, domain, or keyword. Novaverb will show only the evidence this tool can actually retrieve or measure.

Evidence model

Know what the result proves

This check proves what real Chrome users experienced on this address over the trailing collection window, at the 75th percentile, for LCP, INP and CLS. It is field data, not a lab test, so it cannot be produced on demand: a URL with too little traffic has no URL-level record and falls back to origin-level, which is labeled.

1. Source

Real-user field data from the Chrome User Experience report. The result identifies where its evidence came from.

2. Boundary

This reads real-user field data collected over the trailing 28 days for pages with enough Chrome traffic. Low-traffic pages fall back to origin-level data or report no field data - this is not a lab test.

3. Next action

Use the finding to verify a problem, then connect a workspace when you need history, monitoring, or site-wide analysis.

Core Web Vitals explained

Field data is how Google actually judges page experience

Core Web Vitals measure loading (LCP), interactivity (INP) and visual stability (CLS) from real Chrome users - not a lab simulation. Google uses this field data as a ranking signal, so the p75 value is what matters, not a one-off lab score.

The three metrics

LCP - Largest Contentful Paint: how long the main content takes to render. The result shows your p75 against Google's good and poor thresholds.
INP - Interaction to Next Paint: how quickly the page responds to taps and clicks across the whole visit. It replaced FID in 2024; the result shows your p75 against Google's thresholds.
CLS - Cumulative Layout Shift: how much the layout moves while the page loads. The result shows your p75 against Google's thresholds.

URL vs origin data

Low-traffic URLs may not have their own field data. In that case this tool falls back to origin (whole-site) data, which is clearly labeled - it reflects the site overall, not that single page.

Get the right answer

What to submit - and what to avoid

Submit the page address you care about. If the report falls back to origin level, the numbers describe the whole site rather than that page, and the scope label says so. Reading an origin-level figure as a page result is the misreading this section prevents, and a brand-new page will have no data at all.

Use it like this

yourdomain.comAny address form works - a URL with real traffic has the richest field data. http or https, with or without www, a bare domain or a full path - we normalize it for you.

https://www.yourdomain.com/The origin or a popular page is ideal; we fall back origin-level if a URL has no sample.

Avoid this

Reading 'no field data' as an errorA brand-new or low-traffic page simply has no Chrome UX Report sample, so we honestly say so instead of guessing.

Public methodology

Exactly how this result is produced

The address is normalized and 75th-percentile real-user field data is read from the Chrome UX Report. LCP, INP and CLS are reported against the official Core Web Vitals thresholds, unchanged. Where URL-level data is unavailable the report falls back to origin level, and the scope the numbers came from is stated on the result.

We normalize the address and read 75th-percentile real-user field data from the Chrome UX Report (CrUX).
We report LCP, INP and CLS against the official Core Web Vitals thresholds.
We fall back from URL-level to origin-level data and label which scope the numbers came from.

Built on public standards

The international standards this check applies

Core Web Vitals definitions supply the metrics and thresholds, while the Chrome UX Report supplies the 75th-percentile field dataset. The report applies those published thresholds unchanged and makes no ranking prediction from a passing or failing user-experience result.

GoogleCore Web Vitals

web.dev Web Vitals

Reports LCP, INP and CLS against the official Core Web Vitals thresholds.

Read the specification

GoogleCrUX

Chrome UX Report

Reads 75th-percentile real-user field data from the Chrome UX Report.

Read the specification

We list a standard only where this tool genuinely reads or measures against it. Where a signal is outside a live check, the result says so instead of implying coverage.

Common questions

Core Web Vitals Checker FAQ

What does the Core Web Vitals Checker report?

It reports real-user LCP, INP and CLS at the 75th percentile from Chrome field data over the trailing 28 days and whether all available metrics are within the published good thresholds.

What are good Core Web Vitals values?

Google publishes a good, a needs-improvement and a poor threshold for each metric, assessed at the 75th percentile of real visits. This checker applies the published thresholds and shows each metric's verdict beside its value, so you read a pass or a fail instead of comparing numbers by hand.

What do LCP, INP and CLS actually measure?

LCP, Largest Contentful Paint, measures loading speed. INP, Interaction to Next Paint, measures responsiveness to input. CLS, Cumulative Layout Shift, measures visual stability. Together they reflect real perceived page experience for users.

Why does my page show no Core Web Vitals data?

Field data needs enough real Chrome traffic. Low-traffic pages fall back to origin-level data or report none at all. No data means insufficient samples, not that the page performs badly.

What is the 75th percentile in Core Web Vitals?

It means 75 percent of real page visits were at least this fast or stable. Google uses the 75th percentile so the assessment reflects most users, not just the fastest or an average, experience.

What is the difference between field data and lab data?

Field data is measured from real users' devices and networks over time, as this checker reports. Lab data comes from a single controlled test. Field data reflects genuine experience; lab data is reproducible but simulated.

How do I improve my Largest Contentful Paint?

Serve the main image or text quickly by optimizing and preloading the largest element, reducing server response time, trimming render-blocking resources, and using efficient caching so the largest element paints inside Google's good band.

Does passing Core Web Vitals guarantee higher rankings?

No. Search ranking uses many systems, and good Core Web Vitals do not guarantee a higher position. Treat the result as user-experience evidence, not a ranking promise.

Why is INP replacing older responsiveness metrics important?

INP measures the latency of real user interactions across the whole visit, not just the first. An INP inside Google's good band means the page reliably responds quickly whenever users tap or click.

Is this checker a lab speed test?

No. It reports real-user field data at the 75th percentile from Chrome over 28 days. For a controlled lab audit with reproducible opportunities, use a Lighthouse-based tool like the PageSpeed Checker instead.

More free checks