Core Web Vitals are Google's way of measuring whether a page feels good to use. The names are technical, but each one answers a simple question a visitor would ask. Here they are in plain English, with demos.
Three scores, three questions
- Is it loading?Largest Contentful Paint (LCP): how long until the main content shows up. Good is under 2.5 seconds.
- Is it stable?Cumulative Layout Shift (CLS): how much things jump around while the page loads. Good is under 0.1.
- Is it responsive?Interaction to Next Paint (INP): how quickly the page reacts when you tap or click. Good is under 200 milliseconds.
Google uses these as part of its page experience signals. They won't lift a weak page to the top of the results, but they reflect what visitors feel, and visitors decide whether to stay.
Loading: LCP
LCP measures when the biggest thing on the screen, usually a hero photo or headline, finishes showing. Watch the same page load at two different speeds. These timings are an illustration, not measurements of a real site.
The usual cause of a slow LCP is a hero photo straight from a camera, several megabytes when it only needs a few hundred kilobytes. Resizing and compressing it is often the single biggest speed win on a small business site. The post on how fast a site should load lists the other common causes.
Stability: CLS
You've felt this one: you go to tap a button, the page jumps, and you tap something else. That jump is layout shift. Try it below, then switch on the fix.
Press reload, then try to tap “Buy now” before the photo arrives.
The fix is to tell the browser how big things will be before they load. For images, that means setting their width and height, which most modern platforms do for you. The usual culprits on small business sites are banners and pop-ups injected at the top of the page, embedded videos and maps without set sizes, and web fonts that swap in late.
Responsiveness: INP
INP measures the delay between a tap and the page visibly reacting. When it's slow, menus feel sticky and buttons seem broken, so people tap again, or leave.
On small business sites, a poor INP almost always comes from too much third-party code: chat widgets, tracking scripts, pop-up tools, review widgets and apps that all run at once. Each is small; together they keep the browser busy. Removing the ones you no longer use is the first fix. Loading the rest only when needed is the second.
Checking your own
Google's PageSpeed Insights shows all three scores. Where Google has enough visitor data for your site, it shows real-world results from Chrome users; otherwise it shows a lab test only. Search Console has a Core Web Vitals report that groups your pages by status.
The free website check runs the same Google test on a simulated phone and explains the results in plain English. Test your homepage and your most important service or product page, not only one of them.
What to fix first
- Resize and compress the largest images, starting with the hero
- Give images, videos and embeds a fixed size
- Remove apps, plugins and scripts you no longer use
- Load chat and review widgets after the page, not before
- Keep fonts to two families
If the scores still won't move, the theme itself may be the problem. That's where a few hours of developer time, as part of a maintenance plan or a one-off fix, usually beats a full redesign.