Core Web Vitals Explained for Business Owners (Not Just Developers)

Why you should care about Core Web Vitals

In 2021, Google made Core Web Vitals a ranking factor for all search results. This means your site's performance metrics are not just a technical concern — they directly influence how high you appear in search results, how much organic traffic you receive, and therefore how many leads your site generates. For B2B companies relying on organic search, Core Web Vitals are a business metric, not just a developer one.

LCP: Largest Contentful Paint

LCP measures how long it takes for the largest piece of content visible in the initial viewport to finish loading. On most pages, this is either the hero image or the main headline. Think of it as: "How long before the visitor sees something meaningful?"

Good: Under 2.5 seconds. Needs improvement: 2.5–4 seconds. Poor: Over 4 seconds.

The most common causes of poor LCP are large, unoptimised hero images (not in WebP format, not properly sized), server response times over 600ms, and render-blocking JavaScript that delays the page from rendering. Fixing the hero image alone — converting to WebP, adding fetchpriority="high", and setting proper dimensions — often produces a 1–2 second improvement.

CLS: Cumulative Layout Shift

CLS measures visual stability — how much the page layout jumps around as it loads. You've experienced bad CLS when you're about to click a button and the page shifts and you click the wrong thing. It creates a jarring, unfinished feeling that undermines trust.

Good: Under 0.1. Needs improvement: 0.1–0.25. Poor: Over 0.25.

Common causes are images without defined dimensions (the browser doesn't know how much space to reserve), fonts swapping in after the page renders (causing text to reflow), and ads or embeds that load asynchronously and push content down. Fixing CLS is usually straightforward: add explicit width and height attributes to all images, and ensure fonts use font-display: optional or swap with preloading.

INP: Interaction to Next Paint

INP (which replaced FID in March 2024) measures how responsive your page feels when users interact with it — clicking, typing, tapping. It captures the worst-case interaction latency throughout the entire session, not just the first interaction. Think of it as: "How snappy does the site feel when I use it?"

Good: Under 200ms. Needs improvement: 200–500ms. Poor: Over 500ms.

Poor INP is usually caused by long-running JavaScript tasks that block the main thread. Offloading heavy work to Web Workers, breaking up long tasks, and deferring non-critical scripts are the primary fixes.

How to check your Core Web Vitals

The most accessible tool for non-developers is Google PageSpeed Insights. Enter any URL and you'll receive both lab data (simulated) and field data (real user measurements) for each Core Web Vital. Pay more attention to field data — it reflects what your actual visitors experience, not what a simulated test measures.

Google Search Console also provides aggregate Core Web Vitals data across your entire site, highlighting which page groups are failing and which are passing.