Core Web Vitals explained for business owners

What Google's Core Web Vitals measure, why they matter for visitors and search, and the most common fixes for each one.

By the UK Technology Hub teamPublished 4 minute read

The short answer

Core Web Vitals are three measurements Google uses to judge how a page feels to real visitors: how quickly the main content appears (LCP), how quickly the page responds when someone interacts (INP), and how much the layout jumps around while loading (CLS). Good scores improve the experience for visitors and form part of Google's page experience signals.

Speed and stability affect whether people stay on your site. Google turned these ideas into a small set of measurements called Core Web Vitals, based on data from real Chrome users. Here's what each one means and what usually fixes it.

The three Core Web Vitals

MetricWhat it measuresGood score
Largest Contentful Paint (LCP)How long the biggest visible element, usually a hero image or heading, takes to appear2.5 seconds or less
Interaction to Next Paint (INP)How quickly the page responds visually after a tap, click or key press200 milliseconds or less
Cumulative Layout Shift (CLS)How much content moves unexpectedly while the page loads0.1 or less

Google assesses each metric at the 75th percentile of visits, so most of your visitors need a good experience, not just those on fast connections. INP replaced an older metric, First Input Delay, in 2024.

Why they matter

Core Web Vitals are part of how Google evaluates page experience. They aren't the most important ranking factor, as relevant, helpful content comes first, but they can make a difference between similar pages. More importantly, they reflect real frustrations: a slow page, a button that doesn't respond, or text that jumps just as you tap it.

How to check your scores

  • PageSpeed Insights shows field data from real users, where Google has enough traffic data, and lab tests for any URL.
  • Google Search Console has a Core Web Vitals report that groups your pages into good, needs improvement and poor. Our Search Console guide explains how to set it up.
  • Chrome's developer tools include Lighthouse for testing pages during development.

Lab tests are useful for diagnosing problems, but field data reflects what visitors actually experience.

Common fixes for LCP

  • Compress and resize images, and serve modern formats such as WebP or AVIF.
  • Don't lazy-load the main hero image; load it straight away.
  • Reduce render-blocking CSS and JavaScript.
  • Use good hosting with caching and a content delivery network.
  • Self-host fonts and preload the ones needed above the fold.

Common fixes for INP

  • Reduce heavy JavaScript, especially from third-party tools such as chat widgets, trackers and ad scripts.
  • Break up long tasks so the browser can respond between them.
  • Remove plugins that add scripts to every page but are only used on one.
  • Avoid page builders that generate excessive code.

Common fixes for CLS

  • Set width and height on images and video so the browser reserves space.
  • Reserve space for adverts, embeds and cookie banners.
  • Load fonts in a way that doesn't cause large text reflows.
  • Avoid inserting banners above existing content after the page has loaded.

Where to start if your scores are poor

Fix templates rather than individual pages. Most websites use a handful of page layouts, such as the home page, service pages, blog posts and product pages. If one template is slow, every page using it will be slow too, so improving that template fixes them all at once.

Start with the pages that matter most to the business: those that bring in enquiries, sales or search traffic. Then work through the issues in order of impact:

  1. Large, uncompressed images and hero banners.
  2. Third-party scripts loading on every page.
  3. Unused CSS and JavaScript from themes and plugins.
  4. Missing image dimensions causing layout shifts.
  5. Slow server response times, which may point to hosting problems.

Retest after each change so you know what made the difference. Field data in Search Console takes around four weeks to fully reflect improvements, because it's based on a rolling 28-day window of real visits.

Platform matters less than build quality

A carefully built WordPress site can pass all three metrics, and a carelessly built one on any platform can fail them. Heavy themes, stacks of plugins and unoptimised images are the usual causes. Our guide to speeding up a slow website goes into more detail.

Keeping scores healthy

Scores drift as content, plugins and tracking scripts are added. Check Search Console monthly and test new templates before they go live. Performance checks are part of our maintenance and support plans, and every site we build through our website development service is tested against these metrics before launch.

Frequently asked questions

Do Core Web Vitals affect Google rankings?

They're part of Google's page experience signals. Helpful, relevant content matters more, but between similar pages, a better experience can help.

Why are my lab and field scores different?

Lab tests simulate one device and connection. Field data comes from real visitors on many devices and networks, so it often differs.

What's a quick win for a slow site?

Compressing and resizing images often gives the biggest improvement for the least effort.

This guide is general information, not legal, tax or financial advice, and details such as prices, features and rules can change. Product and company names mentioned are trademarks of their respective owners and are used only to identify those products; UK Technology Hub is not affiliated with or endorsed by them.

Related guides

How to speed up a slow website

Why websites slow down, how to find the cause, and practical fixes for images, scripts, hosting, fonts and plugins.

How much does a website cost in the UK?

What drives the price of a business website, typical UK market ranges, the ongoing costs people forget, and how to get a quote you can rely on.

All websites & web design guides