Core Web Vitals in 2026: what still moves the needle

Core Web Vitals have been part of Google’s ranking signals for years now, and they’ve settled into something more useful than a ranking trick: a decent, shared definition of a page that feels fast. Here’s where things stand, and what we actually check before a site goes live.

The three numbers

Google measures three things, using data from real visitors on real devices:

• Largest Contentful Paint (LCP): how quickly the main content appears. Aim for 2.5 seconds or less.
• Interaction to Next Paint (INP): how quickly the page responds when someone taps, clicks or types. Aim for 200 milliseconds or less.
• Cumulative Layout Shift (CLS): how much the page jumps around while it loads. Aim for 0.1 or less.

To pass, at least three quarters of your visits need to hit each target. That “real visitors” part matters: a perfect score on your office fibre connection tells you very little about a commuter on a mid-range phone.

INP is the one that catches people out

INP replaced First Input Delay in 2024, and it’s much stricter. FID only measured the delay before the first interaction was handled. INP looks at every interaction during the visit and reports one of the slowest.

That means a page can load beautifully and still fail if opening the menu, filtering a product list or typing in a search box makes the browser stall. The usual culprits are heavy JavaScript running on the main thread: tag managers full of old scripts, chat widgets, analytics added three agencies ago, and frameworks re-rendering more than they need to.

Our pre-launch checklist

These are the checks we run on every site before it goes live:

• Serve the hero image in a modern format, at the right size, and tell the browser to load it first.
• Give every image, video and ad slot fixed dimensions, so nothing pushes the text down.
• Load fonts early, and use a fallback that’s close in size, so the text doesn’t jump when the real font arrives.
• Audit every third-party script. If nobody can say who uses it, it goes.
• Break up long JavaScript tasks, and delay anything that isn’t needed for the first screen.
• Test on a mid-range Android phone over a throttled connection, not just on a MacBook.

Do they still affect rankings?

Yes, but modestly. Relevant, useful content still wins; Core Web Vitals help decide between pages that are otherwise close. The bigger reason to care is your own numbers. Faster pages convert better, bounce less and make your paid traffic cheaper, because you stop paying for clicks from people who leave before the page appears.

So treat the scores as a health check, not a target. If your real visitors have a fast, stable, responsive experience, the rankings tend to take care of themselves.