Core Web Vitals in 2026: The Numbers Google Actually Cares About

Every business owner has heard "your site needs to be faster" at some point, usually without much explanation of what that means in practice. Google's Core Web Vitals are the closest thing to an objective answer: three measurements of what a real visitor actually experiences, used as a ranking signal and, more importantly, as a decent proxy for whether people stick around or bounce.

The three numbers

• &Largest Contentful Paint (LCP) — how long until the biggest visible thing on the page (usually a hero image or headline) has actually rendered. Anything past 2.5 seconds starts to feel slow.
• &Interaction to Next Paint (INP) — how quickly the page responds when someone taps a button or link. This replaced the older First Input Delay metric because it measures responsiveness throughout the visit, not just on the very first tap.
• &Cumulative Layout Shift (CLS) — how much the page jumps around as it loads. The classic example is tapping a button just as an image above it pops in and pushes everything down, so you end up tapping the wrong thing.

All three are measured on real visitors' devices and connections, not a lab benchmark — so a site that scores well in a testing tool but poorly in the field usually has a problem specific to older phones or slower mobile networks, which is exactly the audience most local businesses can't afford to lose.

What actually causes bad scores

In practice, for most small business sites, it's rarely one dramatic issue — it's an accumulation of small ones. Unoptimised images sized for a desktop monitor and served to a phone. A hero image with no explicit width and height, so the browser doesn't know how much space to reserve for it and the whole page shifts once it loads. Third-party embeds — booking widgets, chat plugins, review carousels — each adding their own script that has to load and run before the page settles. Web fonts that block rendering until they download.

The fixes that actually move the needle

• &Serve images at the size they're actually displayed, in a modern format (WebP or AVIF), and reserve their space in the layout up front.
• &Load anything below the fold lazily, so the browser isn't fetching images a visitor hasn't scrolled to yet.
• &Be ruthless about third-party scripts — every embedded widget is a request to a server the business doesn't control, and it should have to earn its place.
• &Host fonts yourself with a fallback that renders instantly instead of a blank space while the custom font downloads.

None of this is exotic. It's mostly discipline — testing on an actual mid-range phone on a real mobile connection, not just a fast office wifi on a new laptop, because that's the gap between what a site's owner sees and what most of its customers experience.