Core Web Vitals are a set of metrics Google uses to measure how real people experience your web pages: how quickly the main content appears, how responsive the page feels and how visually stable it is. You do not need to be a developer to understand them, and knowing what they mean helps you brief your team, choose better plugins and hosting, and prioritise improvements. This guide explains Core Web Vitals in plain language.
Key takeaways
- The three Core Web Vitals are Largest Contentful Paint (loading), Interaction to Next Paint (responsiveness) and Cumulative Layout Shift (visual stability).
- Google assesses them using real-user data, looking at the experience of most visitors rather than a single test.
- Good scores support search performance and, more importantly, better user experience and conversions.
- Most common problems stem from heavy images, too much JavaScript, slow servers and content that loads without reserved space.

What are Core Web Vitals?
Core Web Vitals are part of Google’s broader page experience signals. They focus on three questions every visitor subconsciously asks:
- Is it loading? Measured by Largest Contentful Paint (LCP).
- Does it respond when I tap or click? Measured by Interaction to Next Paint (INP).
- Is it stable, or does it jump around? Measured by Cumulative Layout Shift (CLS).
The recommended thresholds
| Metric | What it measures | Good | Needs improvement | Poor |
|---|---|---|---|---|
| LCP | Time for the largest visible element to load | 2.5 seconds or less | 2.5 to 4 seconds | Over 4 seconds |
| INP | Delay between an interaction and the next visual update | 200 milliseconds or less | 200 to 500 milliseconds | Over 500 milliseconds |
| CLS | How much visible content shifts unexpectedly | 0.1 or less | 0.1 to 0.25 | Over 0.25 |
Google evaluates these at the 75th percentile of page visits, meaning most of your visitors, not just those on fast connections, should have a good experience. Always check Google’s official documentation for the latest guidance, as definitions can evolve.
Largest Contentful Paint (LCP) explained
LCP measures how long it takes for the biggest piece of content in the visible screen area, usually a hero image, banner or large heading, to appear. Visitors perceive this as “the page has loaded”.
Common causes of poor LCP
- Large, uncompressed hero images or background videos.
- Slow server response times from underpowered hosting.
- Render-blocking CSS and JavaScript that delay display.
- Lazy-loading the main image, which delays the most important element.
How to improve it
- Compress images and serve modern formats at the right size.
- Prioritise loading the hero image rather than lazy-loading it.
- Use caching and a content delivery network, ideally with servers close to your audience; for GCC visitors, that means regional points of presence.
- Upgrade hosting if server response is consistently slow.
Interaction to Next Paint (INP) explained
INP measures responsiveness. When someone taps a menu, clicks “Add to basket” or types into a form, how long does it take for the page to visibly respond? INP observes interactions throughout a visit and reports a value representing the slower end of the user’s experience. It replaced First Input Delay as the responsiveness metric because it captures the whole visit, not just the first interaction.
Common causes of poor INP
- Heavy JavaScript that keeps the browser busy.
- Too many third-party scripts, such as chat widgets, trackers and advertising tags.
- Complex page builders or plugins that add unnecessary code.
How to improve it
- Audit and remove unused scripts, tags and plugins.
- Delay non-essential scripts until after the page becomes interactive.
- Ask developers to break up long tasks so the browser can respond between them.
Cumulative Layout Shift (CLS) explained
CLS measures unexpected movement. You have likely experienced it: you go to tap a link and an advert loads above it, pushing everything down so you tap the wrong thing. CLS scores how much this happens.
Common causes of poor CLS
- Images and videos without defined width and height.
- Adverts, embeds or banners inserted without reserved space.
- Web fonts that swap in and change text size.
- Cookie notices or pop-ups that push content rather than overlaying it.
How to improve it
- Always specify image and video dimensions.
- Reserve space for ads, embeds and dynamic elements.
- Use font-loading strategies that minimise layout changes.
How to check your Core Web Vitals
- Google Search Console: the Core Web Vitals report groups URLs as good, needing improvement or poor, based on real-user data.
- PageSpeed Insights: shows field data where available, plus lab diagnostics and specific recommendations for a single URL.
- Browser developer tools: useful for developers diagnosing specific issues.
Remember the difference between field data (what real visitors experienced) and lab data (a simulated test). Field data is what counts for assessment; lab data helps you diagnose.
Briefing your developer or agency
Even without technical skills, you can manage improvements effectively:
- Share the Search Console report and identify the page templates affected, such as product pages or blog posts.
- Prioritise high-traffic and high-value pages first.
- Ask for a written plan listing each issue, the proposed fix and expected impact.
- Request before-and-after measurements, and allow time for field data to update.
A prioritised Core Web Vitals action plan
When reports show problems across many pages, it helps to work in a sensible order rather than attempting everything at once.
- Group by template. Pages built on the same template usually share the same issues, so one fix can improve hundreds of URLs.
- Start with the worst metric on your most important templates, such as the homepage, service pages or product pages.
- Tackle quick wins first: image compression, image dimensions, caching and removing unused plugins or tags.
- Plan structural fixes next: hosting upgrades, theme changes or rewriting heavy scripts.
- Validate the fix in Search Console once changes are live, then monitor field data over the following weeks.
Questions to ask before adding anything new
- Does this plugin, widget or tracking tag justify its impact on performance?
- Can it load later, after the main content, without affecting its purpose?
- Does the design reserve space for it, so it does not shift the layout?
Building these questions into your approval process keeps Core Web Vitals healthy as your site grows, rather than requiring repeated clean-up projects.
Frequently asked questions
Do Core Web Vitals affect rankings?
Core Web Vitals are part of Google’s page experience signals, but relevance and content quality remain far more important. Think of good scores as supporting factors and, above all, as a way to improve user experience.
Why do my PageSpeed scores change every time I test?
Lab tests vary due to network conditions and server load. Focus on field data trends in Search Console rather than single test scores.
Can plugins fix Core Web Vitals on WordPress?
Caching, image optimisation and script management plugins can help considerably, but they cannot fully compensate for slow hosting or a bloated theme. Sometimes the right fix is structural.
How long until improvements show up?
Field data is collected over a rolling period, so it typically takes several weeks for improvements to be reflected in reports.
Final thoughts
Core Web Vitals translate user frustration into measurable numbers. Understanding LCP, INP and CLS lets you ask the right questions, prioritise sensible fixes and hold partners accountable. Improve them steadily and you will build a faster, smoother site that visitors, and search engines, appreciate.

One Comment:
SEO in the Age of AI: What It Means for Brands in 2026
[…] and AI crawlers can reach your pages, keep important content in HTML text and keep pages fast. Core Web Vitals explained and the complete SEO checklist for 2026 walk through the […]