Core Web Vitals in 2026: What's Actually Being Measured Now

The Current Three Metrics

Core Web Vitals are the specific, measurable signals Google uses to judge how a page performs in the real world, as one input among many ranking signals. As of now, there are three: Largest Contentful Paint (LCP), Interaction to Next Paint (INP), and Cumulative Layout Shift (CLS). If you've read older material about Core Web Vitals and remember a metric called First Input Delay, that's the one that got replaced — INP is its successor, and the swap is the single biggest change to this measurement system in the last few years. We cover the fundamentals of all three in Core Web Vitals explained; this post focuses on what's different now.

Why First Input Delay Got Replaced

First Input Delay only measured the delay before the browser started responding to a visitor's first interaction with a page — the first click, the first tap. It said nothing about interactions after that first one, and it said nothing about how long the response itself took once it started, only how long the browser took to begin processing it. A page could score well on First Input Delay and still feel janky on the fifth click of a session, which is a large blind spot for a metric meant to represent "does this page feel responsive."

Interaction to Next Paint fixes that by measuring the full responsiveness of a page across the entire visit — every click, tap, and key press — not just the first one, and it measures the complete delay until the browser visually updates in response, not just until it starts processing. It's a stricter, more honest measurement of what visitors actually experience as lag.

What INP Actually Captures

Picture clicking "Add to Cart" on a product page and watching nothing happen for a beat before the cart updates. Or tapping a mobile menu and having it open a half-second late. That gap — interaction to visible response — is exactly what INP measures, and because it tracks every interaction rather than just the first, a page with one fast click and then five sluggish ones will show that problem clearly instead of hiding it behind a good first-click score.

This shift matters most for pages with meaningful interactivity — filtering a product catalog, submitting a multi-step form, opening an accordion of FAQ answers, using an on-site search bar. A static brochure page with almost no interaction has less to worry about here; a booking widget or an e-commerce checkout has a lot to worry about.

What Commonly Causes Poor INP

Heavy JavaScript is the usual culprit — third-party scripts (chat widgets, ad trackers, analytics tags, embedded video players) all competing for the browser's attention at the same moment a visitor tries to interact with the page. Each one individually might be fine; stacked together, they can bog down the browser's main thread and delay how quickly it can respond to a click.

Complex logic running synchronously in response to an interaction is another common cause — for instance, a click handler that does a lot of calculation or DOM manipulation before allowing the browser to paint the update. Well-built modern frameworks, including the current React and Next.js stack with its built-in compiler optimizations discussed in what changed with React 19 and Next.js 16, reduce this class of problem by handling a lot of the update-scheduling automatically — but a site can still be built poorly on a good framework, so the framework alone isn't a guarantee.

LCP and CLS Haven't Fundamentally Changed

Largest Contentful Paint still measures how long the biggest visible element takes to load and render — usually a hero image or large heading — and Cumulative Layout Shift still measures how much visible content unexpectedly jumps around while a page loads. Neither metric has been replaced or redefined the way First Input Delay was. The common causes remain the same: unoptimized images and slow server response for LCP, and images or ads without reserved space for CLS.

What This Means for Your SEO Priorities

If your site has decent LCP and CLS scores but you haven't checked INP specifically, it's worth a look, especially if your site has forms, filters, carts, or other interactive elements. Google Search Console's Core Web Vitals report and PageSpeed Insights both report INP directly for pages with enough traffic to measure. A page can look "fast" by older standards and still have a sluggish, JavaScript-heavy interaction problem that only shows up once you check the current metric.

This isn't a reason to panic about rankings — Core Web Vitals are one signal among many, and strong content and relevance still matter more overall. But for sites competing in a tight local market where content quality is roughly equal across competitors, page experience signals like these can be the tie-breaker.

FAQ

What replaced First Input Delay?

Interaction to Next Paint (INP), which measures responsiveness across every interaction during a visit rather than just the first click or tap, and measures the full delay until the browser visibly responds.

Is a good INP score required to rank well on Google?

No single Core Web Vital is required for ranking — they're one input among many ranking signals, alongside content quality and relevance. But a poor INP can hurt user experience and, in competitive niches, may be enough to matter.

How do I check my site's current INP score?

Google Search Console's Core Web Vitals report and Google's PageSpeed Insights tool both report INP for pages with sufficient traffic data.

What kind of pages are most affected by poor INP?

Pages with significant interactivity — checkout flows, product filters, booking widgets, multi-step forms — are affected more than static brochure or information pages with minimal interaction.