Core Web Vitals for business websites: a practical fix list

What LCP, INP and CLS mean for your site, how to measure them and which fixes give the biggest gains.

Book a free consultation

Core Web Vitals for business websites are Google's way of measuring how a page feels to a real visitor: how quickly the main content appears, how fast it responds to input and how stable the layout is while loading.

You do not need to be a developer to act on them. This guide explains each metric in plain terms and gives a prioritised list of fixes that designers, marketers and developers can agree on.

The three metrics in plain language

  • Largest Contentful Paint (LCP): how long the biggest visible element, often a hero image or headline, takes to appear. Google's guidance treats 2.5 seconds or less as good.
  • Interaction to Next Paint (INP): how quickly the page responds when someone taps, clicks or types. Good is 200 milliseconds or less. It replaced First Input Delay in 2024.
  • Cumulative Layout Shift (CLS): how much content jumps around while loading. Good is 0.1 or less.

These thresholds are assessed at the 75th percentile of real visits, separately for mobile and desktop.

Why this matters for the business

Speed influences search visibility as one of many ranking signals, but its larger effect is on behaviour. A slow page loses visitors before the message lands, and a jumpy page causes mis-taps on buttons and forms.

Fast sites also feel more professional. Performance is part of the brand experience, even if visitors never name it.

How to measure properly

Use two kinds of data. Field data comes from real users, and lab data comes from simulated tests.

  1. Open the Core Web Vitals report in Google Search Console to see which page groups fail.
  2. Run key pages through PageSpeed Insights, which shows field data when available and lab data with specific recommendations.
  3. Use Lighthouse in Chrome DevTools for repeatable testing while you work.

Always test on a throttled mobile profile. Your office broadband and the latest laptop hide problems that real customers experience.

Fixes for slow LCP

The largest element is usually an image or a block of text waiting for a font.

  • Compress and resize hero images, and serve modern formats such as WebP or AVIF.
  • Do not lazy-load the hero image; load it with high priority.
  • Reduce server response time with decent hosting, caching and a content delivery network.
  • Limit custom fonts, subset them and use font-display so text appears immediately.
  • Remove render-blocking scripts and unused CSS.

Fixes for poor INP

INP problems usually come from too much JavaScript on the main thread. Chat widgets, tag managers loaded with dozens of tags, sliders and heavy animation libraries are frequent culprits.

Audit third-party scripts and remove any that no one uses. Load non-essential scripts after the page is interactive. Ask developers to break up long tasks and avoid heavy work on click handlers.

Fixes for layout shift

CLS is often the easiest to cure.

  • Set width and height attributes on images and video so space is reserved.
  • Reserve space for ads, banners and cookie notices.
  • Avoid inserting content above existing content after load.
  • Preload key fonts to reduce text reflow.

Design decisions that protect speed

Many performance problems begin in design. Full-screen autoplay video, multiple sliders, large parallax effects and long chains of animations all cost speed.

Agree a performance budget at the start: a maximum page weight, a limit on third-party scripts and a target score on key templates. Designers can then make trade-offs knowingly. A design system with lightweight, tested components makes this far easier to maintain.

Keep it fixed

Scores slip when new plugins, tags and campaigns are added. Re-test monthly, add performance checks to your launch process, and assign someone to own the numbers.

If your site needs a performance review as part of a wider redesign, see our web design services.

A simple order of work

  1. Pick the five pages that bring most traffic or revenue.
  2. Measure them on mobile using PageSpeed Insights and note the failing metric for each.
  3. Fix images and fonts first, because they affect LCP on nearly every page.
  4. Audit and remove unused third-party scripts.
  5. Reserve space for dynamic elements to cut layout shift.
  6. Re-test after each change and record the result.

Resist the urge to chase a perfect 100 score. The goal is passing thresholds for real users on your most important pages, then keeping them there as the site changes.

Who does what

Designers own image choices, animation and layout stability. Developers own code, hosting and caching. Marketers own tag managers and third-party tools. Agree these responsibilities, because performance problems usually appear in the gaps between teams.

Share the results in plain terms with leadership. "Our product pages now load in under two and a half seconds on mobile" is easier to support with budget than a table of metric names.

Frequently asked questions

Do Core Web Vitals directly affect rankings?

They are part of Google's page experience signals, but relevance and content quality matter more. Good scores help most when competing pages are otherwise similar.

What is a good first fix?

Compress and correctly size your hero image, set image dimensions and remove unused third-party scripts. These three changes help many sites.

Why do lab and field scores differ?

Lab tests use one simulated device and network, while field data reflects thousands of real devices and connections. Field data is what Google uses for assessment.

Want help with this? See our Web design & development service.

Explore Web design & development

Let's build your brand.

Book a free consultation