AIO Copilot

Core Web Vitals Calculator

Type in a page's LCP, INP and CLS and see each against Google's good, needs improvement and poor thresholds. It rates figures you bring; to measure a page, run it through PageSpeed Insights.

Good: 2.5 s or less. Needs improvement: up to 4 s. Poor: over 4 s.
Good: 0.1 or less. Needs improvement: up to 0.25. Poor: over 0.25.
Good: 200 ms or less. Needs improvement: up to 500 ms. Poor: over 500 ms.

How to use the calculator

Four steps, starting from real field data.

  1. Get your field numbers

    Run the URL in PageSpeed Insights and read the 75th percentile values from real-user data, or open the Core Web Vitals report in Search Console for groups of pages.

  2. Enter the three values

    LCP in seconds, CLS as a unitless score, INP in milliseconds. Use the mobile figures or the desktop figures, not a mix, since each device type is judged separately.

  3. Read the ratings

    Each metric is rated good, needs improvement or poor. The overall line fails if any metric is poor and shows needs improvement if any metric misses good.

  4. Fix the worst metric first

    Start with anything rated poor on the templates that carry the most traffic, then recheck once 28 days of new field data have built up.

What are good Core Web Vitals scores?

Google rates a page's Core Web Vitals as good when, at the 75th percentile of visits, Largest Contentful Paint (LCP) happens within 2.5 seconds, Interaction to Next Paint (INP) is 200 milliseconds or less and Cumulative Layout Shift (CLS) is 0.1 or less, according to Google's web.dev guide. Poor starts above 4 seconds, 500 milliseconds and 0.25; everything in between needs improvement. The calculator above uses exactly those bands, and a value that sits on a threshold counts toward the better band, as it does in Search Console.

MetricWhat it measuresGoodNeeds improvementPoor
LCPLoading: when the largest visible element has rendered2.5 s or lessUp to 4 sOver 4 s
INPResponsiveness: from a click, tap or key press to the next painted frame200 ms or lessUp to 500 msOver 500 ms
CLSVisual stability: how much visible content moves unexpectedly0.1 or lessUp to 0.25Over 0.25

Source: Search Console Help, Core Web Vitals report, checked November 2026.

Why the 75th percentile?

It is the rule Google applies: web.dev says a good threshold to measure is the 75th percentile of page loads, segmented across mobile and desktop devices. A page meets a threshold when at least three in four visits do, and phones and desktops are judged separately. So enter the 75th percentile value for one device type, not an average and not your best lab run. A single fast load on a developer's laptop says little about a mid-range phone on a weak connection.

Where do I find my Core Web Vitals numbers?

PageSpeed Insights and Search Console both read the Chrome User Experience Report (CrUX), anonymized timings from real Chrome users. PageSpeed Insights shows a single URL's field data over the previous 28 days next to a Lighthouse lab test, per its documentation. Search Console's Core Web Vitals report groups URLs that offer a similar experience and needs a minimum amount of data before a group appears, so pages with little traffic may be missing. For those pages, the web-vitals JavaScript library measures the metrics on your own site.

Treat a Lighthouse report with care. web.dev notes that tools which load pages in a simulated environment without a user cannot measure INP, and names Total Blocking Time as the lab proxy. A Lighthouse run gives you LCP and CLS from one simulated load and no INP at all.

Why does PageSpeed Insights say failed when only one metric misses?

Because the assessment is all or nothing. PageSpeed Insights passes a page only if the 75th percentile of all three metrics is good, and in Search Console a URL group takes the status of its most poorly performing metric. This calculator splits the failing case in two: if no metric is poor but at least one misses good, it says needs improvement, so you can see how far off you are. In Google's tools the same page fails the assessment.

What usually fixes each metric?

LCP is mostly a loading problem. web.dev's LCP guide splits it into time to first byte, resource load delay, resource load duration and element render delay, and suggests that the first byte and the download should each take roughly 40% of the total, with the two delays under 10% each; it calls these guidelines, not strict rules. Its firmest advice is to make the LCP image discoverable in the HTML source and never to lazy-load it. The page speed analyzer flags blocking scripts in the head and heavy inline code in a page's HTML.

INP is a main thread problem. web.dev breaks each interaction into input delay, processing duration and presentation delay. Long tasks on the main thread cause the first, slow event callbacks the second, and a very large DOM adds rendering work to the third. The usual fix is to split the work in event callbacks into separate tasks so the browser can paint in between. INP replaced First Input Delay as a Core Web Vital on March 12, 2024.

CLS is mostly a reserved-space problem. web.dev's CLS guide lists images without dimensions among the most common causes and says to include width and height attributes on images and video elements, so the browser can work out the aspect ratio before the file arrives. The image SEO checker lists the img tags on a page that lack them.

How much do Core Web Vitals affect rankings?

A little. Google's page experience documentation says Core Web Vitals are used by its ranking systems, that there is no single page experience signal, and that good results in Search Console's report do not guarantee top rankings. It also says Search always seeks to show the most relevant content even if the page experience is sub-par, and that trying to get a perfect score just for SEO reasons may not be the best use of your time. Fix the metrics in the poor band, starting with the templates that carry the most traffic, and stop chasing points once a page is good. Our technical SEO audit checklist places Core Web Vitals in the order problems block rankings, after crawling and indexing.

Core Web Vitals questions.

Thresholds, data sources and what the ratings mean for rankings.

Is an LCP of exactly 2.5 seconds good?

Yes. Search Console's Core Web Vitals report counts 2.5 seconds or less as good for LCP, 200 milliseconds or less for INP and 0.1 or less for CLS, so a value sitting exactly on the line passes. The calculator treats boundary values the same way. Poor begins only above 4 seconds, 500 milliseconds and 0.25.

When did INP replace FID?

On March 12, 2024, according to Google's web.dev announcement. FID only measured the input delay of the first interaction on a page. INP observes clicks, taps and key presses throughout the visit and reports the longest interaction, ignoring one outlier for every 50 interactions.

Why does Lighthouse not report INP?

Lighthouse loads a page in a simulated environment with no user, so there are no interactions to measure. web.dev names Total Blocking Time as the lab-measurable stand-in for INP. For a real INP figure you need field data, from PageSpeed Insights, Search Console or the web-vitals JavaScript library running on your own site.

How long do Core Web Vitals take to update after a fix?

About four weeks. PageSpeed Insights reports field data over the previous 28-day collection period, so a fix shows up gradually as older visits drop out of the window. Search Console's Validate fix button starts a 28-day monitoring session and marks the issue fixed only if no URL on the site shows it during that time.

Do Core Web Vitals affect Google rankings?

Yes, a little. Google says Core Web Vitals are used by its ranking systems, but that Search shows the most relevant content even when the page experience is sub-par, and that good results in Search Console do not guarantee top rankings. Pages in the poor band are worth fixing; once a page is in the good band, further gains are mostly for visitors.

Does this calculator measure my website?

No. It rates the three numbers you type in against Google's published thresholds and suggests fixes; it does not load or test any page, and nothing you enter leaves your browser. To get the numbers, run the URL through PageSpeed Insights or open the Core Web Vitals report in Search Console.

Fixed your Core Web Vitals? Find out if search noticed.

Speed is a small ranking factor, so the honest test is a comparison. The free Did it work? checker sets the pages you changed against matched pages you did not touch, from two Search Console exports.

Check if it worked

What to do next.