If your business website feels slow or jumpy, Google has a set of measurements for exactly that. They are called Core Web Vitals, and they are the fastest way to find out whether your site is giving visitors a poor experience. For most small business owners, you do not need to become a developer to use them. You need to know what the three scores mean, where to check them and which fixes usually matter most.
What Core Web Vitals for small business actually measure
Core Web Vitals are three user experience measurements that Google publishes and tracks across real visits to your pages. Google's published thresholds for a good score are a Largest Contentful Paint of 2.5 seconds or less, an Interaction to Next Paint of 200 milliseconds or less, and a Cumulative Layout Shift of 0.1 or less. Each one answers a simple question a customer asks without thinking about it.
Largest Contentful Paint: does the page look ready?
This measures how long it takes for the main thing on the page, usually a hero image or a large heading, to appear. A visitor who waits several seconds staring at a blank screen often leaves. If your homepage banner is a 4 MB photo, this is where you will see it.
Interaction to Next Paint: does the page respond?
This measures how quickly the page reacts when someone taps a menu, types in a form or clicks an add to cart button. It replaced an older measure in 2024. A page that loads but freezes for a moment after each tap feels broken, even when it looks finished.
Cumulative Layout Shift: does the page jump?
This measures how much content moves around while the page loads. You have probably seen it: you go to tap a button, an advert or image loads above it, and you tap the wrong thing. Shifting layouts cost trust, and on checkout or booking pages they cost money.
Why these scores affect your sales
Google has said that page experience is one signal among many in search rankings, so Core Web Vitals will not lift a weak site to the top on their own. Their real value is commercial. Every second a visitor spends waiting or fighting the layout is a second they can spend on a competitor's site. The scores give you a shared, measurable target for your developer, so the conversation moves from "the site feels slow" to "the product page's largest element takes too long to appear on phones."
How to check your Core Web Vitals score for free
You do not need to buy a tool. Two free options cover most small businesses:
- Google Search Console: the Core Web Vitals report groups your pages into good, needs improvement and poor, using real visitor data. Check it monthly.
- PageSpeed Insights: enter any page address to see both the field data and a lab test with specific suggestions. Test your most important pages first: the homepage, your top service page, and the page where people pay or book.
Note that the lab test is run on a simulated device, while the field data reflects real visitors. If your field data is poor, it matters more than a single good lab result.
What usually causes poor Core Web Vitals
In most small business sites, the same problems come up again and again:
- Oversized images uploaded straight from a camera, with no resizing or modern formats.
- Too many scripts from chat widgets, tracking tags, sliders and pop-ups loaded before the page is usable.
- Fonts that download late and swap the text after the page appears, causing shifts.
- Adverts, banners or cookie notices that push content down after it has loaded.
- Themes and plugins that were added over the years and never removed.
Many of these are cheap to fix. Compressing and sizing images, delaying non-essential scripts and reserving space for banners often improve scores without a redesign.
How Next.js helps with Core Web Vitals
Next.js is a React framework, and it gives developers tools that address these causes directly. Its image component resizes and lazy loads images, its font handling avoids late text swaps, and its script handling lets non-essential code wait until the page is ready. Server Components can also reduce the amount of JavaScript the browser has to run, which helps responsiveness on mid-range phones.
A framework is not a guarantee, though. A Next.js site with twelve heavy tracking scripts and unoptimised video will still score poorly. The gain comes from building with these tools on purpose. If you are weighing a rebuild, our website and web app development work starts with measuring the current scores so we can show you what changes the numbers.
A simple order for fixing Core Web Vitals
- Check Search Console and identify the pages marked poor, starting with those that earn revenue or enquiries.
- Fix images on those pages first. This is often the largest single gain.
- Remove or delay scripts you do not use or do not need at page load.
- Reserve space for banners, embeds and images so nothing jumps.
- Retest in PageSpeed Insights and watch the field data over the following weeks, since it updates gradually.
Keep a record of what you changed and when. If sales or enquiries move, you will know which change to credit.
Frequently asked questions
Do Core Web Vitals affect Google rankings?
They are part of Google's page experience signals, which are one factor among many in ranking. Strong content and relevant links still matter more. Poor scores can hold back a page that is otherwise competitive, and they always affect how many visitors stay long enough to act.
What is a good score for a small business site?
Google's published good thresholds are 2.5 seconds or less for Largest Contentful Paint, 200 milliseconds or less for Interaction to Next Paint, and 0.1 or less for Cumulative Layout Shift. Aim for good on your key pages, judged on real visitor data rather than a single test.
Can I fix Core Web Vitals without a developer?
Some fixes are within reach, such as compressing images and removing unused plugins or apps. Script timing, font loading and layout reservation usually need someone who can edit the site's code. Your developer can start with a free audit of your top pages.
How often should I check my scores?
Check Search Console monthly and test key pages after any major change, such as a new theme, a new tracking tool or a redesign. Field data can take weeks to reflect a fix, so avoid judging a change after one day.
If your site is slow, jumpy or losing people at checkout, we can measure it and tell you what to fix first. You can review our shipped client work to see how we approach performance, then start a project brief and we will reply with a clear plan.
