Core Web Vitals Explained for Small Business Owners

Design & Tech Guide · 9 min read · Published 29 October 2026

Core Web Vitals are three measurements Google uses to describe how a page feels to visit. The names sound technical, but each answers a simple question a visitor would ask: how soon can I see the content, does the page react when I tap, and does it jump around? This guide explains each one, shows where to check yours for free and how to fix the common causes on WordPress, page-builder and custom sites.

The three metrics at a glance

How Google judges them

Three points owners often miss. Mobile and desktop are judged separately. Google looks at the 75th percentile of real visits, so a page passes a metric when three quarters of visits are in the good range. And real-visitor data and a lab test are different things, so they can disagree. If pages feel slow in general, start with why websites load slowly.

Largest Contentful Paint: when the main content appears

LCP is the time until the biggest visible element, usually a hero image or a large block of text, has loaded. In PageSpeed Insights, the diagnostics list the exact element, so you know what to fix.

What usually slows it

Typical causes: a large hero image, slow server response, or styles and scripts that block the page from showing.

• Resize and compress the main image, and use a modern format such as WebP.
• Don’t lazy-load the main image. Mark it as high priority, for example <img src="hero.webp" width="1200" height="600" fetchpriority="high" alt="…">.
• Check server response and caching. Our hosting and domain guide covers the basics.
• Remove or delay scripts and styles that load before the content. On WordPress, a caching plugin or your host’s caching usually handles much of this.

Interaction to Next Paint: how fast the page reacts

INP measures the time from a tap or click until the screen visibly updates, across the whole visit. It replaced First Input Delay in March 2024. A lab test can’t measure real taps, so PageSpeed shows Total Blocking Time instead, a related measure of how long scripts keep the page busy. INP itself appears in real-visitor data.

What usually slows it

Typical causes: heavy scripts, too many plugins, and chat widgets or trackers that keep the page busy.

• Remove plugins and scripts you don’t use, and delay chat widgets until after the page has loaded.
• Load non-essential scripts with defer so they don’t block the page.
• Keep menus and buttons simple. A laggy menu is often an INP problem; see mobile navigation mistakes.

Cumulative Layout Shift: does the page jump?

CLS scores how much visible content moves while the page loads. It’s the metric behind the frustration of tapping a button just as the page shifts and hitting the wrong thing.

What usually causes it

Typical causes: images without set sizes, banners or embeds that load late, and fonts that swap in with a different size.

• Give every image and embed a width and height, or use the CSS aspect-ratio property, so space is reserved before it loads.
• Reserve space for banners and late-loading elements, for example with min-height.
• Avoid inserting content above what the visitor is already reading.
• Limit custom fonts to what you use and let text show while they load.

Where to check your scores

1. PageSpeed Insights. Open pagespeed.web.dev, enter a page and read the mobile results first. If a “real users” section appears, that is field data from actual visitors. Then read the diagnostics under it.
2. Search Console. Its Core Web Vitals report groups your pages by status for mobile and desktop using real-visitor data. It covers a rolling window of about 28 days, so fixes show up gradually.
3. Chrome developer tools. The Lighthouse and Performance panels give quick lab checks while you work.

Test your busiest page and your enquiry page, not just the homepage, and run each more than once because scores vary. For ongoing checks see tracking website performance.

A real example: LCP from 3.1 to 0.8 seconds

On a client site we optimised (name withheld), a desktop PageSpeed test showed a Largest Contentful Paint of 3.1 seconds and a Performance score of 88. After the work, LCP was 0.8 seconds and the score was 98. The score moved ten points, but the 3.1-second LCP sat above Google’s 2.5-second line, so the timing is what visitors would have felt. These are lab results from one desktop test each, and mobile should be measured separately. The full before-and-after is in why websites load slowly.

What to fix first

Fix LCP first if pages feel slow to appear, CLS first if things jump, and INP if taps feel laggy. Retest after each change.

Do they matter for a small business?

They are part of how Google judges page experience, but one factor among many, so chasing a perfect score is rarely the best use of your time. What matters more is what they point to: a page that appears slowly, ignores taps or jumps while someone is trying to press a button will lose visitors. Treat the scores as a checklist for those problems rather than a target in themselves.

Fix it yourself or get help?

To find out exactly which metric fails on your key pages and why, start with a website audit. Website maintenance keeps the causes from building up again, and our WordPress vs custom guide helps if a rebuild is on the table.