SEO & Performance

Core Web Vitals in 2026: The Practical Optimization Checklist

By The Rankwyre StudioApril 15, 20269 min read

A Core Web Vitals dashboard with a 98 performance score and LCP, CLS and INP gauges

Core Web Vitals are the performance signals Google uses to measure real user experience, and they influence both rankings and conversion. Slow pages lose visitors before they ever see your offer.

This checklist focuses on what actually moves the numbers in 2026, in the order we tackle them on a typical web design project, so you spend effort where it pays off.

Quick answer

To pass Core Web Vitals in 2026, keep Largest Contentful Paint under 2.5 seconds, Cumulative Layout Shift under 0.1, and Interaction to Next Paint under 200 milliseconds. The biggest wins come from optimising the hero image, reserving space for media, and reducing heavy JavaScript on load.

Largest Contentful Paint: fix the hero first

LCP measures how long the largest visible element takes to render, usually the hero image or headline. The fastest wins are here.

Serve the hero image in a modern format such as WebP or AVIF and size it for the actual container.
Preload the LCP image and avoid lazy loading anything above the fold.
Cut render blocking CSS and fonts so text paints early.

Aim for an LCP under 2.5 seconds on a mid range mobile connection, since mobile is where most sites fall short.

Cumulative Layout Shift: reserve the space

CLS measures visual stability. Pages that jump around as they load feel broken and frustrate users on the verge of clicking.

Set explicit width and height on images and video, reserve space for ads and embeds, and load web fonts with a strategy that avoids a late layout jump. A stable page under 0.1 CLS feels calm and trustworthy.

Interaction to Next Paint: tame the JavaScript

INP replaced First Input Delay and measures how quickly the page responds to taps and clicks across the whole visit. Heavy JavaScript on the main thread is the usual culprit.

Ship less script, defer what is not needed for the first interaction, break long tasks into smaller pieces, and remove unused third party tags. Keep INP under 200 milliseconds so the interface always feels responsive.

Measure with field data, not just lab scores

Lab tools like Lighthouse are useful for diagnosis, but Google ranks on field data from real visitors collected in the Chrome User Experience Report.

Track field metrics in Search Console, fix the slowest real world pages first, and retest after each change. Performance is not a one time task, it is a habit you build into every release.

What to remember

Target LCP under 2.5s, CLS under 0.1, and INP under 200ms.
Optimise and preload the hero image for the biggest LCP win.
Reserve space for images, embeds and fonts to stop layout shift.
Reduce and defer JavaScript to keep interactions responsive.
Judge progress on field data from real users, not lab scores alone.

Frequently asked questions

Do Core Web Vitals really affect Google rankings?

Yes. Core Web Vitals are part of Google's page experience signals. They rarely outweigh strong, relevant content, but between two similar pages the faster, more stable one tends to win, and better performance also lifts conversion.

What is the most common cause of a failing LCP?

An oversized, unoptimised hero image that is not preloaded. Compressing it, serving a modern format, and preloading it is often enough to move LCP from failing to passing on its own.

How is INP different from the old First Input Delay metric?

First Input Delay only measured the first interaction. INP looks at the responsiveness of interactions throughout the visit, so it is a stricter and more realistic measure of how snappy a site feels.