Core Web Vitals explained for business owners

If you’ve run your website through a speed test or opened Google Search Console, you’ve probably seen the term Core Web Vitals, along with a set of acronyms and coloured ratings. It’s tempting to leave them to the developers. They’re worth understanding, though, because they measure something every business owner cares about: whether visitors have a good experience on your site.

This guide explains what the metrics mean, why they matter, how to check yours and what usually improves them, without assuming any technical background.

What are Core Web Vitals?

Core Web Vitals are a small set of metrics Google uses to measure the real-world experience of using a web page. They cover three things visitors notice immediately:

• Loading: how quickly the main content appears
• Responsiveness: how quickly the page reacts when someone taps, clicks or types
• Visual stability: whether things jump around while the page loads

Google uses Core Web Vitals as part of its page experience signals. Importantly, the scores that count are based on data from real Chrome users visiting your site, not on a single test run from someone’s office.

The three metrics in plain English

Google assesses each metric at the 75th percentile of page visits. In practice, that means most of your visitors, not just those on fast connections and new devices, need a good experience for a page to pass.

Largest Contentful Paint (LCP)

LCP measures when the largest visible element, usually a hero image, banner or main heading, finishes loading. It’s the metric closest to the feeling of “has this page loaded yet?”

Common causes of poor LCP:

• Large, uncompressed hero images or background videos
• Slow hosting, or a server that takes too long to respond
• Stylesheets and scripts that block the page from displaying
• Sliders and carousels that load several large images at once

Interaction to Next Paint (INP)

INP replaced an older metric, First Input Delay, in March 2024. It measures how long the page takes to respond visibly after someone interacts with it: opening a menu, adding to the basket, typing in a form. A poor INP makes a site feel sluggish or broken, even if it loaded quickly.

Common causes of poor INP:

• Heavy JavaScript running in the background
• Third-party scripts such as chat widgets, trackers and advertising tags
• Bloated themes and page builders that load far more code than each page needs

Cumulative Layout Shift (CLS)

CLS measures how much content moves around unexpectedly as the page loads. Most of us have tried to tap a link only for a banner to appear and push it down the screen. That’s layout shift.

Common causes of poor CLS:

• Images and videos without set dimensions
• Banners, notices or adverts inserted above existing content
• Web fonts that load late and change the size of the text

Why they matter to your business

Your visitors notice. Slow pages, laggy buttons and content that jumps around are frustrating, and frustrated visitors leave. That’s especially true on mobile, where connections and devices are often slower than the ones in your office.

They’re part of how Google evaluates pages. Core Web Vitals contribute to Google’s page experience signals. Google has been clear that relevant, high-quality content matters more, so a fast page won’t outrank a better answer on speed alone. Where competing pages are similar, though, experience can make a difference, and a poor experience never helps.

You may be paying for visits that never see your offer. If you run paid campaigns, every visitor who gives up before the page loads is spend that produced nothing.

How to check your scores

• PageSpeed Insights. Enter a URL to see real-user data for the page and the wider site, where Google has enough of it, plus a lab test with specific recommendations.
• Google Search Console. The Core Web Vitals report groups your URLs into good, needs improvement and poor, separately for mobile and desktop.
• Lighthouse in Chrome’s developer tools. Useful for testing changes before they go live.

It helps to understand the difference between field data, collected from real visitors, and lab data, from a simulated test. Lab results are useful for diagnosing problems, but field data is what Google uses. Field data is gathered over a rolling 28-day period, so improvements take a few weeks to show. Smaller sites may not have enough traffic for field data at all, in which case lab tests and careful judgement are your guide.

What usually fixes them

You don’t need to understand every technical detail, but it helps to know what good fixes look like:

• Optimise images. Resize them to the dimensions actually displayed, compress them, use modern formats such as WebP or AVIF, and lazy-load images further down the page, but never the main hero image.
• Improve hosting and caching. A faster server, page caching and a content delivery network (CDN) cut the time before anything appears.
• Audit third-party scripts. Remove tools nobody uses, and load the rest after the main content.
• Reduce JavaScript. Trim plugins, replace heavy page builders on key templates and split code so each page loads only what it needs.
• Reserve space for everything. Set dimensions on images, videos and embeds, and avoid inserting banners above content after the page has loaded.
• Load fonts sensibly. Limit the number of font files and use loading settings that avoid invisible or shifting text.

Questions to ask your developer or agency

1. What are our current Core Web Vitals from real visitors, on mobile and desktop?
2. Which templates (home, service, product, checkout) are failing, and why?
3. What will you change, and which metric will each change improve?
4. How will we stop scores slipping as new features, plugins and marketing tags are added?

Good answers are specific. A vague promise to “make the site faster” is not a plan.

Keeping scores healthy

Performance tends to decay over time. Every new plugin, tracking tag or homepage video adds weight. Agree a simple rule that changes are checked against Core Web Vitals before they go live, review Search Console each month, and treat performance as part of routine maintenance rather than a one-off project.

How UPTECHTURE can help

If you’d like to know where your site stands, our free website audit checks speed alongside SEO, accessibility and security, and shows your scores and top issues in under a minute. Our website and app upgrades service then covers speed optimisation, Core Web Vitals fixes and ongoing maintenance, so the improvements last.