Core Web Vitals Explained for Business Owners

Someone has sent you a PageSpeed report with a red circle in it. Maybe a new agency used it in a pitch, maybe your developer ran it after a redesign. The report talks about LCP, CLS and INP, and none of that tells you the thing you actually want to know: is my website losing me business.

Core Web Vitals are Google's three measurements of how a page feels to a real visitor. They are not a full report card on your site, and a red score does not mean your site is broken. Here is what each one measures, which of them your customers genuinely notice, and how much weight they carry in search.

What Google is actually measuring

A search engine cannot feel impatience, so Google picked three things a browser can measure and treated them as a rough stand in for frustration: how long a visitor waits before seeing something useful, whether the page jumps around while it loads, and how quickly the page reacts when they tap. That is the whole idea behind Core Web Vitals.

Each of the three has a published target, and a page is graded on what most visits look like, not on the best one. A score counts as good when roughly three out of four visits hit the target. One quick test on your office wifi, on a laptop, proves very little.

Two more things to know before you read any report. Scores are measured per page, not per site, so your home page and your service pages can be graded differently. Mobile and desktop are also scored separately, which matters a lot here, because most of your visitors arrive on a phone and often on a patchy mobile connection.

LCP: how long before the page shows something

LCP stands for Largest Contentful Paint. In plain terms, it is the time until the biggest thing on the screen has loaded: usually your hero image, a banner, or the main heading. Google's target is 2.5 seconds on a phone.

This is the measurement that costs you customers. A person clicks your Google Ads link, looks at a white screen, gets bored and goes back to try the next business in the list. You paid for that click either way.

In our experience the causes are boring and repeatable:

• A hero image or slider uploaded at full camera size and then shrunk by the browser
• A slider or animation plugin loading on every page, including pages that use neither
• Cheap shared hosting that takes a second or more just to start sending the page
• Five or six web fonts, or a font pulled from another server before any text can appear

None of that needs a rebuild. It needs somebody to open the site and look.

CLS: the page that moves while you are reading it

CLS stands for Cumulative Layout Shift. It is a score rather than a time, and Google's target is 0.1 or lower. The score goes up when content moves after it has already appeared. You start reading a line and an image pushes it down. You reach for a button and an offer bar shoves it out from under your thumb.

Customers do notice this, even if they cannot name it. On an enquiry form or a booking page, a shift that moves a field or the submit button at the wrong moment becomes a mis-tap, and sometimes a lost lead.

The usual causes are images and ads dropped in without space reserved for them, banners that load late at the top of the page, and pop-ups that appear a second after everything else. A developer fixes most of it by telling the browser in advance how much room each block will need.

INP: how fast the page answers a tap

INP stands for Interaction to Next Paint. It measures the gap between a visitor tapping something and the page visibly responding, and Google's target is 200 milliseconds, about a fifth of a second. It replaced an older measurement called FID, so a report you were sent last year may not mention it at all.

Poor INP feels like a phone that has stopped listening. You tap the menu, nothing happens, you tap again, and now the menu opens and closes. On a WordPress site the cause is usually the sheer number of scripts piled up by plugins, chat widgets, tracking tags and the page builder, all competing for a cheap phone's attention at the same moment.

If your site carries a live chat widget, three analytics tags and a page builder, INP is the score most likely to be sitting in the red. Removing what you no longer use will help more than any setting inside a speed plugin.

How much of this really moves rankings

This is the part a sales pitch tends to skip. Core Web Vitals are a genuine ranking signal, and Google has said so openly. They are also a small signal next to whether your page answers what the searcher asked. A fast page with thin content does not beat a slower page that answers the question properly.

So treat a red report as a customer experience problem first and a search problem second. The business case is simpler that way: pages that load quickly waste fewer paid clicks, collect more form fills, and make your company look like it is still open.

It also means speed is one line item in a wider check, not the whole job. Our technical SEO audit checklist shows where it sits next to indexing, mobile usability and internal links. And if that same report also revealed an eight year old layout squeezed onto a phone screen, the honest fix may be bigger than caching, so it is worth reading the signs a website needs a redesign before you spend money on tuning.

What to do with the red report you were sent

Start by checking that the problem is real. Open Search Console and read the Core Web Vitals report there, because it uses data from actual visits over the past few weeks instead of one test on one machine. If Search Console says your pages are fine and a single PageSpeed run says they are terrible, believe Search Console.

Then work in roughly this order:

• Fix the pages that earn money first: home page, top service or product pages, and whatever page your ads point to
• Resize and compress images properly, which usually buys the biggest gain for the least risk
• Remove plugins and tracking scripts you have stopped using, then test again
• Add caching and a sensible asset setup, and take a full backup before you change anything
• Only then argue about hosting, and move only if your server is genuinely slow to respond

Most WordPress sites move from red to acceptable on images, cleanup and caching alone, with no rebuild involved. If you would rather not touch these settings yourself, our Performance Enhancer plugin handles caching and script loading while leaving cart and checkout pages alone, and a careful developer can finish the rest in a day or two. A site that loads fast and holds still while people read it is also doing quiet work for your credibility, the same job as the other things that build trust on a business website.

FAQs