Core Web Vitals for Small Business Websites: A Plain-English Guide

What Core Web Vitals are

Core Web Vitals are three measurements Google uses to describe how a page feels to a real visitor: how quickly the main content appears, how quickly the page responds when you interact, and how stable the layout is while loading. They are one of several page-experience signals, and more importantly they closely track whether visitors stay or leave.

The three metrics

Largest Contentful Paint (LCP) measures how long it takes for the biggest visible element, usually a hero image or headline, to render. Google's guidance treats 2.5 seconds or less as good.

Interaction to Next Paint (INP) measures how long the page takes to visually respond after a tap, click, or key press. A value of 200 milliseconds or less is considered good.

Cumulative Layout Shift (CLS) measures how much visible content jumps around while the page loads. A score of 0.1 or less is good. Everyone has experienced tapping a button just as an ad or image pushes it out of the way; CLS quantifies that.

How to measure your own site

Two kinds of data matter. Field data comes from real visitors and is reported in Google Search Console's Core Web Vitals report and in PageSpeed Insights. Lab data comes from running a test on your page, such as Lighthouse in Chrome DevTools. Field data tells you whether there is a problem; lab data helps you find the cause.

Test on a mid-range phone with a throttled connection, not your fast laptop. Most small business traffic is mobile.

Highest-impact fixes for LCP

• Compress and properly size the hero image, and serve modern formats such as WebP or AVIF.
• Do not lazy-load the main above-the-fold image; load it with high priority instead.
• Reduce server response time with caching or a CDN.
• Limit web fonts to the weights you actually use and use font-display: swap.
• Remove render-blocking scripts from the page head where possible.

Highest-impact fixes for INP

Poor responsiveness is almost always caused by too much JavaScript running on the main thread. Audit third-party scripts first: chat widgets, tag managers loaded with many tags, and heatmap tools are frequent culprits. Remove what you do not use, delay what you do until after the page is interactive, and break up long tasks in your own code.

Highest-impact fixes for CLS

• Always set width and height (or an aspect ratio) on images and video embeds.
• Reserve space for ads, banners, and cookie notices so they do not push content down.
• Avoid inserting content above existing content after load.
• Preload critical fonts to reduce the visible swap between fallback and web fonts.

Where to start

Pick your three most important pages, usually the home page, your top service or product page, and your contact page. Measure them, fix the single biggest issue on each, and re-measure. Small, verified improvements beat a large redesign done on assumptions.