Core Web Vitals 2026: INP Update and Action Plan for Your Site

What Are Core Web Vitals?

Core Web Vitals are a set of metrics that measure real-world user experience for speed, responsiveness and visual stability. They are a confirmed Google ranking signal. The three current metrics are: LCP (Largest Contentful Paint) — loading performance, INP (Interaction to Next Paint) — interactivity, and CLS (Cumulative Layout Shift) — visual stability.

INP: The New Interactivity Metric

INP measures the time between a user interaction (click, tap, or keyboard press) and when the browser paints the next frame in response. Unlike FID which only measured the delay before the browser started processing the event, INP measures the full interaction duration — making it a much more meaningful measure of page responsiveness.

Common causes of poor INP: heavy JavaScript execution blocking the main thread, third-party scripts (chat widgets, analytics, ad tags) adding processing overhead, large DOM size making layout recalculations slow, and synchronous JavaScript in event handlers.

LCP and CLS in 2026

LCP targets: good is ≤2.5 seconds, needs improvement is 2.5–4 seconds, poor is over 4 seconds. The most common LCP elements are hero images and large text blocks. To improve: preload your LCP image using <link rel="preload">, serve images in WebP or AVIF format, use a CDN for faster delivery, and eliminate render-blocking resources above the fold.

CLS targets: good is ≤0.1, needs improvement is 0.1–0.25. CLS is caused by images without defined dimensions, dynamically injected content (ads, banners, cookie notices) and web fonts causing text reflow (FOUT). Always define width and height attributes on images and reserve space for dynamic content.

4-Step Action Plan

1. Measure: Run PageSpeed Insights on your key pages. Use Chrome UX Report for field data (real user measurements, not just lab data). Identify which metric is failing first.
2. Fix INP: Audit your JavaScript bundles. Break up long tasks (>50ms) using setTimeout or scheduler.postTask(). Defer non-critical third-party scripts. Use web workers for heavy computations.
3. Fix LCP: Identify your LCP element in PageSpeed Insights. Preload it, optimize its file size, and ensure the server responds within 600ms (TTFB). Use Next.js or similar frameworks with automatic image optimization if applicable.
4. Fix CLS: Add explicit dimensions to all images and video elements. Use font-display: optional or swap with size-adjusted fallbacks to minimize layout shift from web fonts.