7 min left

All articles Build 7 min read

Core Web Vitals in 2026: Why INP and Page Speed Still Decide Rankings (and Sales)

Core Web Vitals are still a ranking and conversion lever — and since INP replaced FID, the metric most sites now fail is responsiveness. Here's what the three numbers mean and how to pass them.

Written by Global iMatrix team Design · Build · Grow · Evolve

Placeholder — the article's featured image.

Every so often someone declares that site speed no longer matters for SEO. They're wrong, and the businesses that believe them tend to lose ground quietly. Core Web Vitals — Google's measurable standards for how fast, stable and responsive a page feels — are still a ranking signal, and more importantly they're a conversion signal. A slow, janky page loses customers whether or not Google is watching.

What has changed is which vital trips people up. In March 2024, Google retired First Input Delay and replaced it with a tougher metric called Interaction to Next Paint. Two years on, INP is the vital most sites still fail — and most site owners have never heard of it.

01The three numbers, and what "good" means

Each vital measures a different part of how a page feels to a real person, and each has a published threshold. Google grades you at the 75th percentile of real visits — meaning three-quarters of your visitors need a good experience, so you can't hide a slow site behind a fast average.

≤ 2.5s Largest Contentful Paint (LCP): time until the biggest thing on screen has loaded. Good is 2.5 seconds or less; over 4 seconds is poor.
≤ 200ms Interaction to Next Paint (INP): how quickly the page visibly responds to taps and clicks, across the whole visit. Good is 200 milliseconds or less; over 500ms is poor.
≤ 0.1 Cumulative Layout Shift (CLS): how much the page jumps around as it loads. Good is 0.1 or less; over 0.25 is poor.

LCP is loading: has the main content actually appeared? INP is responsiveness: when I tap something, does the page react promptly, or does it hang for a beat? CLS is stability: does the button stay where I'm about to tap, or does an ad push it down so I hit the wrong thing? Together they're Google's attempt to measure the difference between a site that feels quick and trustworthy and one that feels slow and cheap.

02Why INP catches so many sites out

First Input Delay, the old metric, only measured the delay before the browser started handling your very first interaction. It was easy to pass — so easy that almost everyone did, which is precisely why Google replaced it.

INP is stricter in two ways. It measures every interaction through the whole visit, not just the first. And it measures the full journey from tap to visible response — including the time the page spends running its own JavaScript before it can paint the result. That means a modern, script-heavy site can load its main image quickly (good LCP) and still feel sluggish every time someone taps a menu, opens a filter, or adds to a cart (poor INP).

03The fixes that actually move the numbers

Performance work has a good return because the same fixes usually help all three vitals and lift conversions at the same time. Roughly in order of impact:

Cut and defer JavaScript (helps INP most)

The biggest INP wins come from asking the browser to do less work when someone interacts. That means shipping less JavaScript, breaking up the long tasks that block the main thread, deferring anything not needed for the first interaction, and being honest about whether every third-party script and tracker earns its place. Heavy pages feel heavy because the browser is busy running code instead of responding to the person.

Optimise the largest element (helps LCP)

LCP is usually decided by one big hero image or heading. Serve images in modern formats at the right size, don't lazy-load the one above the fold, preload the critical asset, and make sure your server and hosting respond quickly. A fast host is part of performance, not separate from it.

Reserve space for everything (helps CLS)

Layout shift comes from content that arrives without a reserved place — images without dimensions, ads and embeds that push text down, fonts that reflow when they swap in. Set explicit sizes, reserve space for dynamic content, and load fonts in a way that doesn't jolt the layout.

Measure real visits, not just lab scores

A lab test on a fast connection can look perfect while real visitors on real phones struggle. Trust the field data — the Core Web Vitals report in Search Console — because that's what Google uses. Lab tools are for diagnosing, field data is for grading.

text
Where to look:
  • Google Search Console → Core Web Vitals report   (real-world / field data — this is what's graded)
  • PageSpeed Insights                                (field data + a lab diagnosis, per URL)
  • Chrome DevTools / Lighthouse                      (lab diagnosis while you develop)

04It's about sales, not just rankings

Here's the part that matters even if you never think about Google. The Core Web Vitals thresholds line up closely with the point where real people give up. A page that takes too long to load, hangs when tapped, or shifts under a thumb loses customers — they leave, or they abandon the form, or they buy somewhere that feels more reliable. Passing Core Web Vitals is, in effect, Google paying you to remove friction your customers were already feeling. That's why we treat it as part of conversion, not a technical checkbox.

05Frequently asked questions

What are the three Core Web Vitals in 2026?

Largest Contentful Paint (LCP), which measures loading; Interaction to Next Paint (INP), which measures responsiveness; and Cumulative Layout Shift (CLS), which measures visual stability. INP replaced First Input Delay as a Core Web Vital in March 2024.

What is a good INP score?

200 milliseconds or less, measured at the 75th percentile of real visits. Between 200 and 500ms needs improvement, and over 500ms is considered poor. INP measures the delay between a user interaction and the page visibly responding.

Do Core Web Vitals still affect SEO rankings?

Yes. They're part of Google's page-experience signals. They're rarely the single deciding factor — relevance and content quality matter more — but among comparable pages, the faster, more stable, more responsive one has the advantage. And they affect conversions regardless of rankings.

How do I check my Core Web Vitals?

Use the Core Web Vitals report in Google Search Console for your real-world (field) data — that's what Google grades. Use PageSpeed Insights for a per-URL view and Lighthouse in Chrome for diagnosing issues while you build.

Why did my scores drop without any redesign?

Usually accumulated weight: new scripts, trackers, embeds, or unoptimised images added over time, or a third-party service that got slower. Performance decays gradually as things are added, which is why it needs periodic review.

06Where this leads

Core Web Vitals reward exactly what you'd want anyway: a site that loads fast, responds instantly, and doesn't jump around. In 2026 the metric to watch is INP, because responsiveness is where modern, script-heavy sites quietly fail — and where visitors quietly leave.

If you're not sure where your site stands, our web development team can run a performance audit against the current thresholds and tell you what's actually costing you speed. Ask us for a performance audit, and if you have a redesign coming, build it in from the start — see protecting performance during a redesign.

Sources referenced: web.dev, "Interaction to Next Paint is officially a Core Web Vital" and INP launch guidance (Google, 2024); Google Search Central documentation on Core Web Vitals thresholds. INP good threshold ≤200ms; LCP good ≤2.5s; CLS good ≤0.1, each measured at the 75th percentile.

Written by Global iMatrix team Design · Build · Grow · Evolve
  • Performance
  • Web
  • SEO

Useful?This is how we work.

Everything in this journal comes from projects like yours.