ToolsHub4u

Check field metrics against the published web.dev thresholds

Paste LCP, INP, CLS, TTFB and FCP from a field or lab report. Each value is compared with the web.dev thresholds, with the rating and the gap to the nearest line shown.

  • Published thresholds
  • Field or lab data
  • No PageSpeed call
Ready SEO & Web
The numbers are yours, the thresholds are publishedThis is not a speed test. It classifies the values you enter against the Core Web Vitals bands documented on web.dev. It cannot measure a page for you, because that needs a real browser and a real visitor.
1Enter
2Adjust
3Copy result

Core Web Vitals Calculator

1

Metric values

ms

Largest Contentful Paint

ms

Interaction to Next Paint

Cumulative Layout Shift, unitless

ms

Time to First Byte

ms

First Contentful Paint

Where the numbers came from

Field data is what real visitors experienced. Lab data is one synthetic run and is usually faster or slower than the median visitor.

Device

Mobile is usually the slower experience and the one Google reports separately.

No data yet Live
2

Vitals assessment

Every Core Web Vital entered is in the good band

  • LCP: 2,400 ms — GoodWithin the good band with 100 ms of headroom before it leaves it.
  • INP: 180 ms — GoodWithin the good band with 20 ms of headroom before it leaves it.
  • CLS: 0.08 — GoodWithin the good band with 0.02 of headroom before it leaves it.
  • TTFB: 620 ms — GoodWithin the good band with 180 ms of headroom before it leaves it.
  • FCP: 1,600 ms — GoodWithin the good band with 200 ms of headroom before it leaves it.
Metric against the published thresholds
MetricYour valueGood up toPoor aboveRating
LCP2,400 ms2500 ms4000 msGood
INP180 ms200 ms500 msGood
CLS0.080.10.25Good
TTFB620 ms800 ms1800 msGood
FCP1,600 ms1800 ms3000 msGood
Metrics checked
5
In good band
5
Worst metric
FCP
Device
Mobile

Thresholds are the ones documented on web.dev for LCP, INP, CLS, TTFB and FCP. Core Web Vitals assessment in Search Console also requires a minimum amount of field data per URL group, which this tool cannot see.

This page compares the five performance numbers you paste with the thresholds Google publishes on web.dev. LCP, INP and CLS are the three Core Web Vitals; TTFB and FCP are supporting metrics that often explain why a core vital is slow. Each value is rated Good, Needs improvement or Poor, and the distance to the nearest threshold is shown.

It does not fetch your page, call the PageSpeed Insights API or read field data. You bring the numbers from a report, and the page does the comparison and the arithmetic in the browser tab.

The five metrics and their thresholds

LCP, Largest Contentful Paint, is when the main image or heading finishes rendering. Good is 2,500 ms or less; above 4,000 ms is poor. INP, Interaction to Next Paint, is the delay between a tap or keypress and the next frame. Good is 200 ms or less; above 500 ms is poor. INP replaced First Input Delay as a Core Web Vital in 2024.

CLS, Cumulative Layout Shift, measures unexpected movement. Good is 0.1 or less; above 0.25 is poor. TTFB, Time to First Byte, is the server's first response: good is 800 ms or less, poor above 1,800 ms. FCP, First Contentful Paint, is when the first text or image appears: good is 1,800 ms or less, poor above 3,000 ms.

The boundaries are inclusive. A value of exactly 2,500 ms, 200 ms or 0.1 is rated Good, which is why a page sitting on the line still passes. Google's published thresholds are assessed at the 75th percentile of page loads, separately for mobile and desktop, so a single fast load does not make a page pass.

A worked example

Five values were entered with the source set to mixed and the device to mobile: LCP 4,200 ms, INP 350 ms, CLS 0.30, TTFB 900 ms and FCP 3,100 ms. The gauge read 0 out of 100 and the band was Failing.

Five entered metrics and their ratings
MetricValueGood up toPoor aboveRating
LCP4,200 ms2,500 ms4,000 msPoor
INP350 ms200 ms500 msNeeds improvement
CLS0.300.10.25Poor
TTFB900 ms800 ms1,800 msNeeds improvement
FCP3,100 ms1,800 ms3,000 msPoor

All five rows were outside the good band, so the score was zero. The status line was narrower: it said 0 of 3 Core Web Vitals are in the good band, because the gauge divides by every metric entered while the headline counts only LCP, INP and CLS. With all three core vitals failing, both readings agree. With a mix of values they can disagree, and the gauge is the one to watch if you care about supporting metrics too.

Because every row failed, the page also printed a fix for each one: find the LCP element and the delay, split long JavaScript tasks for INP, reserve space for CLS, check hosting and caching for TTFB, and remove render-blocking work for FCP. The advice is generic on purpose; the tool cannot see which element or script is responsible.

Read the thresholds, not the headlineThe headline is a count of metrics. The table is the evidence. A page can show a green score while one core vital sits just inside the poor band, which is why the row-level ratings and the gap to the threshold matter more than the band label.

Two places where the wording misleads

The worst metric label is not reliable when everything passes. The page sorts by rating first, then by headroom, and for a good metric headroom is the distance to the good threshold. The largest headroom wins the sort, so a page with every metric passing can name its worst metric as the one with the most room to spare. In the all-good test, FCP was named as the worst metric with 200 ms of headroom while LCP had 100 ms.

The improvement figure is also measured to the wrong line for a metric in the middle band. For a value between the two thresholds, the page calculates the distance to the poor threshold, then calls it the improvement needed to reach the good band. A TTFB of 900 ms was told it needed 900 ms of improvement to reach 800 ms; the real gap is 100 ms. With INP at 350 ms the two distances happen to be equal, so that row reads correctly by coincidence.

Neither problem changes the rating. They change the sentence beside it, so read the table when the wording looks odd, and subtract the value from the good threshold yourself if you need the true gap.

Field data, lab data and the 75th percentile

The source control changes the warning, not the maths. Choose field for numbers from the Search Console Core Web Vitals report or the CrUX dashboard, lab for a single Lighthouse or PageSpeed Insights run, and mixed only when you are deliberately comparing the two. A lab score is one synthetic load; field data is what real visitors experienced.

Mixing the two produces a number that means nothing in particular, and the page says so. It also reminds you that Search Console needs a minimum amount of field data before it will assess a URL group. A new page can be missing from the report for weeks, and that absence is not a failure.

If you are checking a page you have just changed, compare lab runs before and after with the same device and the same network settings. For a pass or fail judgement that matches Search Console, use field data over 28 days and look at the 75th percentile rather than the average.

What to fix first

Start with poor ratings, then the largest gap. LCP and TTFB are often connected: a slow first byte delays everything after it, so check hosting, caching and redirects before compressing images. If TTFB is good and LCP is not, the delay is usually in the hero image, a render-blocking stylesheet or a late font.

For INP, look for long tasks on click and keypress rather than the total JavaScript bundle. For CLS, set width and height on images and embeds, and avoid inserting banners above existing content. These are the same priorities the tool lists, and none of them need a paid API.

The log file analyser is a useful companion when TTFB is the problem: a slow server response shows up in access logs as time on the request, and a 5xx burst explains a bad run that a lab test cannot reproduce.

Questions

Common questions

Short answers about this tool and its limits.

Does this tool test my website?

No. It has no URL field, makes no network request and does not call the PageSpeed Insights API. You copy LCP, INP, CLS, TTFB and FCP from a report and the page compares them with the thresholds.

Is a value exactly on the threshold good or poor?

Good. The comparison uses less than or equal to the good threshold, so 2,500 ms LCP, 200 ms INP and 0.1 CLS all pass. A test with those exact values returned 3 of 3 in the good band.

Why does the gauge count five metrics when there are three Core Web Vitals?

The gauge is a simple share of every metric you entered. The status line is the Core Web Vitals count, limited to LCP, INP and CLS. TTFB and FCP are supporting metrics, so they affect the gauge but not that headline.

Why is the worst metric wrong when everything passes?

The sort treats the largest headroom as the worst result. When every metric is good, headroom is the distance to the good threshold, so the metric with the most room to spare is named. Ignore the label in that case; the table is correct.

Why does it say my TTFB needs more improvement than it does?

For a value between the two thresholds, the figure is the distance to the poor threshold, not to the good one. A TTFB of 900 ms shows 900 ms because 1,800 minus 900 is 900; the gap to the 800 ms good threshold is 100 ms.

Should I enter lab or field data?

Use field data for a pass or fail judgement that matches Search Console, and lab data for debugging a change you just made. Do not mix them in one check: the page warns that the result then combines two different measurements.

What does the 75th percentile mean here?

Google assesses Core Web Vitals at the 75th percentile of page loads, separately for mobile and desktop. Three quarters of visits were at least as fast as the value; the slowest quarter can still be much worse. A single fast test does not represent that.

Can I save the result?

Yes. The copy button copies a plain-text summary with the device, the data source and one line per metric showing the value, the rating and both thresholds. There is no account and nothing is stored on a server.