
Core Web Vitals Explained: A Practical Guide to Faster, Friendlier Websites
- November 17, 2026
- SEO , core web vitals
Every developer has had the conversation. A client opens the site on their phone in a car park, waits, taps a button that does nothing, then watches the page jump as an advert loads. "It feels slow," they say, and they are right. Core Web Vitals exist to turn that vague feeling into numbers you can measure, fix and track. They are also a confirmed part of how Google evaluates page experience, which makes them hard to ignore for anyone who builds or owns a website.
What Core Web Vitals Actually Measure
There are three metrics, and each one maps to a moment that users notice. The first is loading: how long until the main content appears. The second is responsiveness: how quickly the page reacts when someone taps, clicks or types. The third is visual stability: whether things stay where they are while the page finishes loading.
Google's own documentation on Web Vitals at web.dev sets out the thresholds and is the reference worth bookmarking, because the definitions do change over time. The most notable change so far came in 2024, when Interaction to Next Paint replaced First Input Delay as the responsiveness metric.
Largest Contentful Paint: The Loading Metric
Largest Contentful Paint (LCP) records when the biggest visible element in the viewport finishes rendering. On most pages that is a hero image, a large heading or a video poster. A good score is 2.5 seconds or less, measured at the 75th percentile of real visits.
The usual culprits are oversized images, slow server response times and render blocking CSS or JavaScript. In practice, the quickest wins tend to be serving the hero image in a modern format such as WebP or AVIF, sizing it correctly for each breakpoint, and adding a preload hint so the browser fetches it early. If the server itself takes more than half a second to respond, caching or a content delivery network will usually do more than any front end tweak.
Interaction to Next Paint: The Responsiveness Metric
Interaction to Next Paint (INP) looks at every click, tap and key press during a visit and reports one of the slowest. A good score is 200 milliseconds or less. Unlike its predecessor, which only measured the first interaction, INP captures the frustration of a page that becomes sluggish after a few minutes of use.
Poor INP almost always traces back to the main thread being busy. Heavy JavaScript bundles, third party scripts for chat widgets or analytics, and large event handlers that do too much work at once are the common causes. Breaking long tasks into smaller pieces, deferring non essential scripts and auditing third party tags quarterly will move this metric more than anything else.
Cumulative Layout Shift: The Stability Metric
Cumulative Layout Shift (CLS) measures how much visible content moves unexpectedly. A good score is 0.1 or less. Anyone who has tried to tap a link only to hit an advert that slid into its place understands why this matters.
The fixes are refreshingly simple. Always set width and height attributes, or an aspect ratio, on images and videos. Reserve space for adverts and embeds before they load. Avoid inserting banners above existing content, and load web fonts in a way that does not cause a large reflow when they arrive.
How to Measure Without Fooling Yourself
There are two kinds of data, and mixing them up causes a lot of wasted effort. Lab data comes from tools like Lighthouse, which run a simulated visit on a fixed device and connection. Field data comes from real users, collected through the Chrome User Experience Report and shown in PageSpeed Insights and Search Console. Google uses field data for ranking, so that is the number that ultimately counts.
Lab tools are still invaluable for diagnosing problems, as long as you know which figures deserve attention. This breakdown of website speed test results that actually matter is a helpful companion when a report throws dozens of numbers at you. For the broader engineering picture behind these metrics, the Wikipedia overview of web performance covers the history and the underlying concepts well.
Core Web Vitals on Multilingual Sites
Sites that serve several languages face a few extra traps. Each language version may load different fonts, longer strings can push layouts around and cause shifts, and translated pages are sometimes served from slower templates that nobody optimised. It is worth checking field data per language folder, not only for the homepage. Speed is only half of the story, of course, and translated pages also need properly localised keywords, as this piece on SEO friendly translation explains.
Where to Start This Week
If you only have a few hours, open Search Console, find the page group with the most "poor" URLs, and fix the single biggest issue on that template. One template change can repair hundreds of pages at once. Then set a reminder to check again in four weeks, because field data takes about a month to reflect improvements. Treat Core Web Vitals as ongoing maintenance rather than a one off project, and both your visitors and your search traffic will notice the difference.