Core Web Vitals

LCP measures the render time of the largest visible content element in the viewport — usually a hero image, a large block of text, or a video poster — from navigation start. It is dominated by server response time, resource load time, render-blocking resources, and client-side rendering delays.

INP measures the latency between a user's interaction (click, tap, key press) and the next visual update the browser paints in response, sampled across all interactions during a page's lifetime and reported as a high percentile. It replaced First Input Delay (FID) in March 2024 because FID only measured the first interaction and only the delay before processing began, missing the far more common problem of slow processing after that.

CLS measures unexpected movement of visible page elements during the page's lifetime, calculated from the impact fraction (how much of the viewport shifted) multiplied by the distance fraction (how far it moved), summed across the worst burst of shifts in a session.

As classical organic clicks become scarcer on informational queries due to AI Overviews, the clicks that do arrive are disproportionately commercial and local-intent, high-conversion-value traffic — exactly the traffic where a slow, unstable page directly costs revenue rather than merely losing a ranking edge. Vitals have shifted from a modest ranking lever to a direct conversion-rate lever whose importance has, if anything, increased.

Use Google Search Console's Core Web Vitals report and the CrUX dashboard for authoritative, field-measured, ranking-relevant data, grouped by URL pattern rather than individual page where traffic is too low for a stable sample.

Use PageSpeed Insights or Lighthouse for lab-based diagnosis — identifying which specific resources or scripts are causing a failure — but never treat a Lighthouse score as equivalent to real field performance; a page can pass in the lab and fail in the field, and vice versa, especially on real-world device and network conditions Lighthouse doesn't fully replicate.

LCP failures are most often caused by unoptimised hero images, slow server response times (especially on shared or under-provisioned hosting), and render-blocking CSS or JavaScript loaded before the largest element can paint.

INP failures are most commonly caused by heavy client-side JavaScript execution triggered on interaction — large React component trees re-rendering unnecessarily, third-party analytics or ad tags running expensive work on the main thread, or poorly-optimised event handlers.

CLS failures typically come from images or embeds without explicit width and height attributes, web fonts that load late and reflow text (FOIT/FOUT), and ads or dynamically-injected content that pushes existing page content down after the initial layout.

Pull the CrUX-based Search Console report to identify which URL groups are actually failing in the field, rather than starting from a lab score on a single page.

For LCP: compress and correctly size the hero image, serve it via a CDN with modern formats (AVIF/WebP), add a `fetchpriority="high"` hint, and eliminate render-blocking resources above it in the load order.

For INP: audit third-party scripts and defer or remove non-essential ones, break up long JavaScript tasks, and avoid unnecessary large re-renders on interaction in client-side frameworks.

For CLS: set explicit dimensions on all images and embeds, reserve space for ads and dynamically-loaded content, and use `font-display: optional` or preloaded fonts to prevent layout-shifting text swaps.

Re-measure in the field (CrUX/Search Console) after 28 days, since field data accumulates over a rolling window and won't reflect a fix immediately.

Many local service sites run on templated platforms with heavy embedded booking widgets, chat tools, and marketing pixels stacked on top of each other — a common and avoidable cause of INP and CLS failures. Auditing and trimming that third-party script stack is frequently the single highest-leverage Vitals fix available to a small business site, ahead of any custom development work.

Faster, more stable pages are cheaper for search engines to crawl and render, which modestly improves crawl efficiency on larger sites, while the direct ranking effect remains a comparatively minor factor relative to content relevance. The larger, more reliable payoff is behavioural: passing Vitals correlates strongly with lower bounce rate and higher conversion, which indirectly supports rankings through engagement and business outcomes.