The Core Web Vitals Checklist for 2026

Core Web Vitals are the closest thing the web has to an official performance scorecard — and in 2026 they matter for both Google rankings and conversions. Slow, janky pages lose visitors and lose positions. This is the practical Core Web Vitals checklist we use on every build, with 2026 targets and the fixes that actually move each metric.

What Core Web Vitals are (and why they matter in 2026)

Core Web Vitals are three field metrics Google uses to measure real-user experience: how fast the main content loads, how quickly the page responds to input, and how visually stable it is while loading. They're part of Google's page-experience signals, so they influence rankings — but more importantly, faster pages simply convert better.

Speed is not a vanity metric. Every 100ms you shave off load time is measurable revenue for a page that sells.

The three Core Web Vitals and their 2026 targets

LCP — Largest Contentful Paint

LCP measures how long the largest element (usually your hero image or headline) takes to render. Target: under 2.5 seconds on mobile; above 4s is "poor."

Common causes and fixes:

• Slow server response — use caching and a fast host/CDN.
• Huge hero images — serve modern formats (WebP/AVIF), correctly sized and compressed.
• Render-blocking CSS/JS — inline critical CSS, defer the rest.
• Late-loading fonts — preload key fonts and use font-display: swap.

INP — Interaction to Next Paint

INP replaced FID in 2024 and is now the responsiveness metric. It measures the delay between a user interaction (tap, click) and the page visibly responding. Target: under 200ms.

Common causes and fixes:

• Heavy JavaScript blocking the main thread — split bundles, ship less JS.
• Expensive event handlers — debounce and simplify.
• Large third-party scripts — load them lazily or remove them.

CLS — Cumulative Layout Shift

CLS measures unexpected movement of content as the page loads. Target: under 0.1 (ideally as close to 0 as possible).

Common causes and fixes:

• Images/videos without dimensions — always set width and height.
• Ads/embeds injected without reserved space — reserve the slot.
• Web fonts causing reflow — preload and match fallback metrics.

The 2026 Core Web Vitals checklist

• Largest image/hero is optimised, modern-format and properly sized
• Critical CSS inlined; non-critical CSS/JS deferred
• Key fonts preloaded with font-display: swap
• JavaScript bundle trimmed; third-party scripts lazy-loaded
• Every image and embed has explicit dimensions
• Fast hosting + caching + CDN in place
• Tested on a real mid-range mobile device, not just desktop

How to measure Core Web Vitals

Use PageSpeed Insights for a quick lab + field snapshot, Google Search Console → Core Web Vitals report for site-wide field data, and the Chrome UX Report (CrUX) for real-user trends. Always trust field (real-user) data over lab scores.

Key takeaways

1. Aim for LCP < 2.5s, INP < 200ms, CLS < 0.1 on mobile.
2. The biggest wins are usually image optimisation, less JavaScript, and reserving space for media.
3. Measure with real-user (field) data, and re-check after every major change.

Frequently asked questions

Do Core Web Vitals affect SEO rankings? Yes — they're a confirmed ranking signal as part of page experience. They rarely outrank great content, but between two similar pages, the faster one wins.

What replaced FID? INP (Interaction to Next Paint) replaced First Input Delay in 2024 and is a stricter, more complete responsiveness measure.

What's a good overall Core Web Vitals score? You want all three metrics in the "Good" range for at least 75% of real visits.

Build it fast from the start

The cheapest time to fix Core Web Vitals is before launch. Our website development and SEO services bake performance in from day one. Get a free site audit and we'll show you exactly what's holding your scores back.