Core Web Vitals are the three numbers Google uses to judge how a page feels to use, not how good it looks. Here is what they measure, why they matter beyond SEO, and what to ask your developer to fix first.
Core Web Vitals measure loading speed, responsiveness and visual stability — not design or content quality.
They are one of several signals in Google's ranking system, not a guarantee of a higher position on their own.
Most poor scores on small business sites come from oversized images, too many scripts and crowded hosting, not big design choices.
Check your own scores for free with Google PageSpeed Insights and the Core Web Vitals report in Search Console.
Fix the pages that matter most first — your homepage and top landing pages — rather than chasing a perfect score everywhere.
What Core Web Vitals actually measure
Core Web Vitals are three measurements Google uses to judge how a page actually feels to a visitor, separate from how good your writing is or how the page looks.
Largest Contentful Paint (LCP) — how long it takes for the biggest visible thing on the page, usually a hero image or heading, to load. This is what most people mean by "page speed".
Interaction to Next Paint (INP) — how quickly the page responds when someone taps a button, opens a menu or fills in a form. A page can look fully loaded and still feel stuck if this is slow.
Cumulative Layout Shift (CLS) — how much the page jumps around while it loads. This is the "I was about to tap that button and something else popped in" problem.
Each one gets a score built from real visits to your site, not a single test, and Google sorts the result into good, needs improvement, or poor.
Why this is a business problem, not just a developer one
A slow or jumpy site costs you before Google even enters the picture. Someone searching for your service on their phone will not wait around for a page that takes a while to settle. The people who do stay have a harder time filling in your enquiry form, tapping to call, or checking your prices — the exact moments that turn a visitor into a customer.
Google has also said that page experience, including Core Web Vitals, is one of several signals it uses in search ranking, alongside content relevance and quality. It is not the only one, and strong, useful content still matters more. But on a page that is already competitive, a poor score can be what holds it back.
How to check your own scores
You do not need to buy a tool for this.
Google PageSpeed Insights — paste in any page URL and it shows your Core Web Vitals plus a list of specific problems, in plain enough language to forward to your developer.
Google Search Console — if your site is already verified there, the Core Web Vitals report shows real visitor data grouped by page, so you can see which pages actually need attention.
Chrome's built-in developer tools — opening a page in Chrome and running the Lighthouse panel gives a detailed one-off report, useful for checking a fix before it goes live.
Test your homepage and your two or three most-visited pages — usually the ones linked from your ads or your Google Business Profile — rather than every page on the site.
What usually causes poor scores on a small business site
The same handful of issues tend to show up again and again on small and mid-size business sites:
Oversized images. A photo straight from a phone camera can be several megabytes; a web page needs it closer to a few hundred kilobytes.
Too many plugins or embedded widgets. Every chat widget, review badge, extra font and tracking script adds a small delay on top of the last one.
Crowded or cheap hosting. If your site shares a server with hundreds of others, it can be slow no matter how well it is built.
Pop-ups and banners that load late. A newsletter pop-up, cookie banner or offer that appears after the page has already settled is the most common cause of layout shift.
Buttons that are not ready when the page is. If a button only becomes clickable a moment after the page appears to load, that counts as a poor response even though the page looks done.
Quick wins to ask your developer for
You do not need a full rebuild to see a real improvement. Ask your developer to start with:
Compress and resize every image before upload, and use a modern image format where the site supports it.
Load images below the first screen only once a visitor scrolls near them ("lazy loading").
Remove plugins, scripts and widgets you are not actually using any more.
Set a fixed size for every image, ad slot and embed so the page does not jump as they load in.
Delay chat widgets and similar add-ons by a second or two, so they load after the main content.
None of this touches your design or your copy. It is about how the same page is delivered.
Test on mobile, not just your office laptop
A site that scores well on a fast office laptop and broadband can still score poorly on an average phone over mobile data — and for most businesses, that is how most customers actually arrive. Google also builds its index primarily from the mobile version of a site, so the mobile experience is the one that counts most.
Test your own site on your own phone, on mobile data rather than wifi, so you see something closer to what a typical customer experiences.
If you are working with a developer or agency, a short, specific brief gets better results than "make the site faster":
Ask for your current scores on your homepage and top two or three pages, before any work starts.
Ask which specific issues are causing a poor score, not just the score itself.
Ask them to re-test after changes and show you the before and after, on the same pages.
Agree which pages matter most — usually the ones people land on from ads, search or your Google Business Profile — so effort goes where it is actually seen.
What you can safely ignore
Do not chase a perfect score everywhere.
Scores can vary a little between tests, your network and even the time of day. Judge the trend over a few weeks, not one single number.
A rarely visited page scoring poorly matters far less than your homepage or a page you are sending ad traffic to.
Third-party tools you rely on for real business reasons, such as a payment gateway or a booking widget, sometimes cost you a few points. That is usually a fair trade if the tool brings in business.
The goal is a site that feels fast and steady to a real customer on their phone, not a trophy score in a testing tool.
Common questions
Do Core Web Vitals affect my Google ranking?
They are one of several signals Google uses, alongside the relevance and quality of your content. A poor score alone will not sink a strong, relevant page, but between two otherwise similar pages, the one with the better experience can have an edge. Treat it as one input, not the whole game.
What counts as a good score?
Google publishes threshold bands for each metric covering good, needs improvement and poor, and it updates these from time to time. Rather than memorising a number, check your own pages in PageSpeed Insights, which tells you directly which band each page falls into.
How often should I check my scores?
Check once after any major change to your site, such as a new theme, a redesign or a new plugin, and every few months otherwise. A quick look at the Core Web Vitals report in Search Console is usually enough for routine monitoring.
Can I improve this without hiring a developer?
Some of it, yes. Compressing images before you upload them and removing plugins you no longer use are both things a site owner can often do directly inside their CMS. Fixes to code, hosting and how scripts load are better left to a developer.
Where we can help
If you are not sure where your site stands, a performance check as part of our build services can show you exactly which pages to fix first, or start a conversation and we will point you to the biggest win.
