Skip to content
Web design

Core Web Vitals explained for business owners

What LCP, INP and CLS measure, what good scores look like, and what usually needs fixing to make a business website fast, in plain language.

MS Comp team · 3 min read

Core Web Vitals are three measurements Google uses to judge how a page feels to a real visitor: how fast it shows its main content, how quickly it responds when tapped, and how stable it stays while loading. They're part of Google's page experience signals, and more importantly they track closely with whether visitors stay or leave.

You don't need to be a developer to understand them. Here's what each one means, what a good score is, and what usually needs fixing.

LCP: how fast does the main content appear?

Largest Contentful Paint measures when the biggest image or block of text in the visible part of the screen finishes rendering. It's the moment a visitor feels the page has loaded.

  • Good: 2.5 seconds or less.
  • Needs improvement: 2.5 to 4 seconds.
  • Poor: over 4 seconds.

Common causes of a slow LCP are oversized hero images, slow hosting, sliders and video backgrounds, web fonts that block text from appearing, and scripts that must load before anything is shown.

INP: how quickly does the page respond?

Interaction to Next Paint measures the delay between a visitor's tap, click or key press and the page visibly reacting. It replaced an older metric, First Input Delay, in March 2024, and it's stricter because it looks at interactions throughout the visit, not just the first.

  • Good: 200 milliseconds or less.
  • Needs improvement: 200 to 500 milliseconds.
  • Poor: over 500 milliseconds.

Heavy JavaScript is almost always the cause: page builders, plugins, chat widgets, tracking tags and third-party embeds all compete for the phone's processor.

CLS: how much does the page jump around?

Cumulative Layout Shift measures unexpected movement while the page loads. You've felt it: you go to tap a button and an image loads above it, pushing the button away.

  • Good: 0.1 or less.
  • Needs improvement: 0.1 to 0.25.
  • Poor: over 0.25.

Typical causes are images and videos without set dimensions, ads and embeds that load late, cookie banners that push content down, and web fonts that swap in with different widths. On this website we matched the fallback font widths to our real fonts so headings don't rewrap when the fonts arrive.

Lab data vs field data: which scores count?

There are two kinds of measurement. Lab data comes from a test run on demand, such as Lighthouse or PageSpeed Insights, on a simulated phone. It's great for finding problems. Field data comes from real Chrome users visiting your site over the past 28 days, collected in the Chrome UX Report. Google uses field data, and a page passes when at least 75% of visits meet the good threshold for each metric.

Smaller sites may not have enough visits for field data. In that case, aim for good lab scores on a mobile test, since that's your best predictor.

Where to check your scores

  • Google Search Console: the Core Web Vitals report groups your pages into good, needs improvement and poor, using field data.
  • PageSpeed Insights: test any single page and see both field data (if available) and a lab report with suggestions.
  • Chrome DevTools: developers can record a page load and see exactly what delays each metric.

Do Core Web Vitals affect rankings?

Yes, but modestly. Google has said relevance and helpful content come first, and page experience helps decide between pages of similar quality. The bigger effect is on visitors: slow, jumpy pages lose people before they read a word, and that costs enquiries regardless of rank.

What usually gets the biggest improvement?

  1. Compress and correctly size images, and use modern formats such as WebP or AVIF.
  2. Remove plugins, widgets and tags you don't need, and delay the rest until after the page loads.
  3. Move to faster hosting with caching and HTTP/2 or HTTP/3.
  4. Preload the main image and fonts, and give every image set dimensions.
  5. Replace heavy page builders with a lighter, purpose-built site when a rebuild is due.

Our web design projects are built to pass Core Web Vitals on mobile, and we can audit an existing site and tell you what's worth fixing. See also how to speed up a slow website.

FAQ

Quick answers

What is a good PageSpeed Insights score?

A score of 90 or above on mobile is good. The score is a lab test, though: one simulated visit on a mid-range phone. Passing Core Web Vitals in the field data section, which reflects real visitors over the past 28 days, matters more for rankings and for how fast your site feels to customers.

Why are my mobile scores lower than desktop?

PageSpeed Insights simulates a mid-range phone on a slower mobile connection, while the desktop test assumes a fast computer and network. That exposes heavy scripts, large images and slow fonts that a powerful computer hides. Since most local customers browse on phones, the mobile score is the one to improve first.

Does a WordPress site fail Core Web Vitals by default?

No. Many WordPress sites fail because of heavy page-builder themes, too many plugins and unoptimized images, not because of WordPress itself. A lean theme, a small set of well-built plugins, compressed images, caching and good hosting can pass Core Web Vitals comfortably. The setup matters more than the platform you choose.

Want help with this?

Tell us about your business and we'll send a free quote, or call 1-800-944-3688.