Core Web Vitals explained

Core Web Vitals are three numbers Google uses to describe how a page feels to a real visitor: how fast the main content loads, how stable the layout is, and how quickly the page responds to a tap or click. Google's ranking systems use them — with no published weight, and no substitute for relevant content — and the bigger payoff is a page with less friction, which can only help visitors complete an inquiry or purchase.

The three metrics in plain terms

• LCP — Largest Contentful Paint (loading). How long until the largest eligible image or text block visible in the viewport has rendered — often a hero image or large heading. Good: 2.5 seconds or less.
• CLS — Cumulative Layout Shift (visual stability). How severe the largest burst of unexpected layout movement is during the visit — including shifts after the initial load, from late banners or injected content. You have felt this when you go to tap a button and an image pushes it down. Good: 0.1 or less.
• INP — Interaction to Next Paint (responsiveness). INP watches clicks, taps, and key presses across the whole visit and summarizes the slowest (or near-slowest) delay between your input and the next visible update. It replaced the older FID metric in March 2024. Good: 200 milliseconds or less.

Google assesses each metric at the 75th percentile of real visits, separately for mobile and desktop: "good" means at least three-quarters of measured visits meet the threshold — all your visitors may well be inside it — and all three metrics must qualify for the page to assess as good.

How to measure them

• PageSpeed Insights — paste a URL for lab results and, where available, real-world field data. One catch: the automated lab run never interacts with the page, so it cannot measure INP — treat its Total Blocking Time as a clue, then test important interactions by hand.
• The Search Console Core Web Vitals report — groups similar indexed URLs with enough field data, and a group's status comes from its worst metric. Test representative URLs individually when diagnosing a group.
• Field data (CrUX) — the Chrome User Experience Report, the anonymized real-visitor data behind the "field" numbers. It covers the previous 28 days and only qualifying Chrome visits — no Safari or Firefox — and low-traffic pages may have no individual data, so fixes take weeks to show.

Use field data to judge real-world performance and lab tests to reproduce and diagnose problems — neither tells the whole story alone. A page can score well in a clean lab test yet stumble for real users on slower phones and networks.

Common fixes

• LCP: first identify the LCP element — it can be text, and it can differ between mobile and desktop — and find the slow phase in its timeline. If it is an image: right dimensions, modern format, never lazy-loaded, discoverable in the initial HTML, prioritized where appropriate. Also check server response time and render-blocking CSS or scripts. If a critical third-party origin's connection starts late, preconnect to it — sparingly, not to every host. See optimize your images.
• CLS: reserve space for images, ads, and embeds by setting explicit width and height (or an aspect-ratio box), and avoid inserting banners above existing content. Then hunt the remaining sources: web-font swaps, consent notices, and dynamically injected content can shift layout even when every image has dimensions.
• INP: break up long main-thread tasks and cut or defer scripts you do not need. JavaScript is the usual culprit, though expensive style, layout, or rendering work can block the main thread too.

Keep it in proportion

Core Web Vitals matter, but good scores do not guarantee rankings, and relevant, helpful content remains essential — page experience tends to count when several results are otherwise similarly useful. Chase them because a fast, stable, responsive site serves visitors better; treat any ranking nudge as a bonus.

Aim for "good" on all three, then move on. A CDN such as Cloudflare can help with delivery speed, but it will not fix a heavy page for you.

What to do

1. Run your homepage and top landing pages through PageSpeed Insights.
2. Open the Search Console Core Web Vitals report and fix the "poor" group first — testing representative URLs, not just the group label.
3. Identify the LCP element on each key page, mobile and desktop; if it is an image, fix its sizing, discovery, and loading.
4. Set width and height on every image, then check for shift from fonts, banners, and injected content.
5. Audit your JavaScript and defer or drop anything non-essential.