Core Web Vitals Explained for Business Owners

Google wants to send searchers to websites that are pleasant to use. To measure this, it uses a set of metrics called Core Web Vitals, based on data from real visitors using Chrome. You do not need to be a developer to understand them.

The three Core Web Vitals

1. Largest Contentful Paint (LCP): how fast the main content appears

LCP measures how long it takes for the biggest visible element, usually a hero image or headline, to appear. Google considers 2.5 seconds or less as good.

Common causes of slow LCP: huge images, slow hosting, too many scripts, and fonts that block the page.

2. Interaction to Next Paint (INP): how quickly the page responds

INP measures the delay between a tap or click and the page responding visibly. Good is 200 milliseconds or less. INP replaced the older First Input Delay metric in 2024.

Common causes of poor INP: heavy JavaScript, chat widgets and tracking scripts that keep the browser busy.

3. Cumulative Layout Shift (CLS): how stable the page is

CLS measures how much content jumps around while the page loads. You have experienced this when you try to tap a button and an ad pushes it down. Good is 0.1 or less.

Common causes: images without set dimensions, late-loading banners, and fonts that change size when they load.

Why business owners should care

• Rankings: Core Web Vitals are part of Google's page experience signals. Good content still matters most, but speed can be the tie-breaker against competitors.
• Conversions: visitors leave slow websites before they see your offer. Faster pages generally mean more calls and enquiries.
• Mobile users: on 4G connections and budget phones, poor performance is felt even more.

How to check your website

1. Open PageSpeed Insights and enter your website address.
2. Look at the "Discover what your real users are experiencing" section for field data.
3. Check Google Search Console's Core Web Vitals report for problems across your site.

Quick wins that usually help

• Compress images and serve them in WebP format.
• Set width and height on all images.
• Remove plugins, sliders and scripts you do not need.
• Load chat widgets and analytics after the main content.
• Use good hosting with server-side caching.
• Use a content delivery network if your visitors are spread across regions.

When a rebuild is better than patching

Websites built with heavy page builders and dozens of plugins sometimes cannot be made fast without a rebuild. A lean, custom-coded site is often cheaper in the long run than endless optimisation of a bloated one.