Core Web Vitals: how site speed decides your Google ranking

Two businesses sell the same thing at the same price. One site loads in 1.5 seconds and feels instant; the other takes 6 seconds, jumps around as it loads, and lags when you tap a button. Google sees that difference — through real-world data from actual Chrome users — and it ranks the fast one higher. That gap is measured by Core Web Vitals.

The three Core Web Vitals, in plain English

1. LCP — Largest Contentful Paint (loading)

How long until the biggest, most important thing on screen — usually your hero image or headline — actually appears. It answers the visitor’s gut question: “is this page even working?”

Good: under 2.5 seconds. The usual culprits are huge unoptimised images, slow hosting and render-blocking scripts.

2. INP — Interaction to Next Paint (responsiveness)

When someone taps a button or opens a menu, how quickly does the page visibly respond? INP replaced the old FID metric in 2024 and is stricter — it measures real responsiveness across the whole visit, not just the first click.

Good: under 200 milliseconds. Heavy JavaScript is almost always the cause; the main thread is busy, so taps feel laggy.

3. CLS — Cumulative Layout Shift (visual stability)

Have you ever gone to tap a link and the page jumped, so you hit an ad instead? That’s layout shift. CLS scores how much your content moves around unexpectedly as it loads.

Good: under 0.1. Fix it by reserving space for images and embeds with explicit width and height, and never injecting content above what’s already on screen.

Metric	Measures	Good	Needs work
LCP	Loading speed	< 2.5s	> 4s
INP	Responsiveness	< 200ms	> 500ms
CLS	Visual stability	< 0.1	> 0.25

How to actually improve them

You don’t need to chase a perfect score — you need to be in the green for real users. The fixes that move the needle most:

• Compress and modernise images. Serve AVIF or WebP, size them correctly, and lazy-load anything below the fold. This is the single biggest LCP win on most sites — it’s why every image on this site ships as AVIF.
• Ship less JavaScript. Every heavy framework and third-party script taxes INP. Defer what you can, remove what you don’t use, and prefer lean code over bloated page builders.
• Reserve space for everything. Set explicit dimensions on images, videos and ads so nothing reflows. That alone usually fixes CLS.
• Host close to your audience. A fast server and a CDN cut the time-to-first-byte that LCP is built on.
• Load fonts smartly. Use font-display: swap and preconnect so text never blocks the paint.

Speed isn’t a technical nicety. It’s the first impression — made before a single word of your pitch is read.

Why “just add a caching plugin” rarely works

Plugins paper over symptoms. If a site is built on a bloated theme stacked with third-party scripts, no plugin rescues it — the weight is structural. Genuinely fast sites are engineered fast from the first line: lean markup, optimised assets and minimal JavaScript baked in, not bolted on. That’s the difference between a site that scores green in a lab test and one that’s fast for the customer holding a mid-range phone on patchy mobile data.

The business case, in one sentence

Faster pages rank higher, get crawled more, convert more visitors and cost less in ad spend per acquisition — which is why performance is never an afterthought in anything we build, and why it belongs in the brief from day one.

---

Keep reading: How much does a website cost in 2026? · How to choose a web design agency