.svg){kind=small}
To improve Core Web Vitals on a small business site, fix the three things that cause most failures. Make the main image load fast, give every image and embed a fixed size so the page doesn't jump, and cut the scripts that make taps feel slow. Measure first with PageSpeed Insights, change one thing at a time, and measure again. This guide explains what each metric means, how to read your scores, and which fixes are worth your time.
What are Core Web Vitals?
Core Web Vitals are three measurements Google uses to describe how a page feels to real visitors. According to Google's web.dev guide to Web Vitals, the targets for a good experience are these.
Metric | What it measures | Good | Poor |
|---|---|---|---|
Largest Contentful Paint (LCP) | How fast the main content appears | 2.5 seconds or less | Over 4 seconds |
Interaction to Next Paint (INP) | How fast the page responds to taps and clicks | 200 milliseconds or less | Over 500 milliseconds |
Cumulative Layout Shift (CLS) | How much the layout jumps while loading | 0.1 or less | Over 0.25 |
A page passes when at least 75% of visits meet the "good" target for all three. INP replaced an older metric, First Input Delay, in 2024, so older guides you find may still talk about FID.
Do Core Web Vitals affect SEO?
Yes, a little. Google's documentation on page experience says Core Web Vitals are used by its ranking systems. The same page also says good scores don't guarantee top rankings, and that chasing a perfect score just for SEO may not be the best use of your time.
For a small business, read that as a priority order. Relevant, useful pages and a complete Google Business Profile matter more. Speed matters most when your site is so slow that people leave before it loads, and when you're close to a competitor on everything else. It also matters for a simpler reason. A visitor who taps through from Google Maps on a weak phone signal won't wait long.
How do you check your Core Web Vitals?
Use two free tools from Google.
PageSpeed Insights. Paste in a page address. The top section, labelled with real-user data, shows how visitors on Chrome visitors experienced the page over the last 28 days. The section below it is a lab test, a single simulated load that helps explain why the numbers are what they are. If the top section says there isn't enough data, your site doesn't get enough Chrome traffic for Google to report on it. That's common for small sites. Use the lab results as a guide instead.
Search Console's Core Web Vitals report. This groups your pages into good, needs improvement and poor, on mobile and desktop. It's the best way to spot a whole template, such as every service page, failing at once.
Test on mobile first. Phones have slower processors and patchier connections, so problems show up there before they show up on a laptop.
How to improve Largest Contentful Paint (LCP)
LCP is usually the hardest metric to pass. Google's web.dev team says about 40% of sites in its real-user data miss the LCP target. On most pages, the largest element is an image, typically the big photo at the top of the home page.
These fixes do the most good.
- Shrink the hero image. A photo straight off a camera can be 4,000 pixels wide and several megabytes. Resize it to the largest size it appears at, and save it as WebP or AVIF.
- Don't lazy-load the top image. Lazy loading is good for images further down the page. On the main image it delays the thing LCP measures. Remove
loading="lazy"from it, and addfetchpriority="high"so the browser fetches it early. - Make sure the image is in the page's HTML. Sliders and page builders that load the main image with JavaScript make the browser wait. A plain image tag is faster.
- Speed up the server. If the first byte takes over a second to arrive, nothing else can start. Page caching and a content delivery network (CDN) help most here.
On WordPress, see how we handle slow WordPress sites.
How to improve Cumulative Layout Shift (CLS)
CLS is the one you've felt. You go to tap a button and it moves because an image or banner loaded above it. Most sites pass this one, but it's often the easiest to fix when they don't.
- Give every image a width and height. Without them, the browser doesn't know how much space to save, so the page jumps when the image arrives. Google's list of the most effective Core Web Vitals fixes notes that 66% of pages have at least one image without a set size.
- Reserve space for embeds. Maps, videos, review widgets and booking forms often load late. Put them in a box with a fixed height or aspect ratio.
- Watch the cookie banner. A banner that slides in and pushes content down causes layout shifts, and web.dev notes that even animating one that sits over the page can count. Let it appear in place without sliding.
- Load fonts carefully. A custom font that swaps in late can reflow a whole headline. Preloading the main font file usually helps.
How to improve Interaction to Next Paint (INP)
INP measures the delay between a tap and the screen responding. Poor INP almost always comes from too much JavaScript running at once.
- Audit your third-party scripts. Chat widgets, heatmaps, old tracking pixels and social feeds each add code. Remove the ones nobody looks at. If you use a tag manager, clear out old tags.
- Cut plugins that load everywhere. A slider plugin that loads its scripts on every page, including pages without a slider, slows all of them.
- Simplify heavy pages. Very long pages with hundreds of elements take longer to update after each tap. Splitting a giant page into a few focused ones can help both speed and SEO.
If you have a developer, web.dev's INP guidance on breaking up long tasks is worth sending them. If you don't, removing scripts is the fix you can do yourself.
A simple order of work for small business owners
If you only have an afternoon, do this.
- Run your home page and your most important service page through PageSpeed Insights on mobile. Note the three numbers.
- Resize and convert the biggest images, starting with the one at the top of each page.
- Set sizes on images and embeds that cause the layout to jump.
- Remove one unused plugin or script at a time, testing the site after each.
- Run the same pages again and compare.
Change one thing at a time. If you change five things and the score drops, you won't know which one did it. And remember that the real-user numbers take up to 28 days to fully reflect a fix.
When is it worth paying for help?
If you've done the easy fixes and the site is still slow, the problem is usually deeper. Common culprits are slow hosting, a heavy page builder, or a theme that loads everything on every page. Those take a developer.
We offer a speed and accessibility check for $150, listed on our pricing page. Our SEO audit, from $59, includes speed alongside indexing, errors and a review of your main pages, with a prioritized list of fixes you can hand to anyone. If your WordPress site needs a deeper fix, our WordPress service covers rebuilding slow sites without a heavy page builder. Every new website we build ships with loading-speed checks before launch.
FAQ
What is a good Core Web Vitals score?
Google's targets are LCP of 2.5 seconds or less, INP of 200 milliseconds or less, and CLS of 0.1 or less, met by at least 75% of visits. A page needs all three to pass.
Why does PageSpeed Insights say there's not enough data?
The real-user section needs enough visits from Chrome users over 28 days. Many small sites don't have that much traffic. Use the lab results below it to find problems, and check Search Console as your traffic grows.
Are Core Web Vitals a ranking factor?
Google says its ranking systems use them, but good scores don't guarantee a top ranking and relevance comes first. Fix pages that are genuinely slow or jumpy. Chasing a perfect 100 rarely pays off.
What is the fastest way to improve Core Web Vitals?
Resize and compress the large image at the top of your main pages, stop it from lazy-loading, and set sizes on every image and embed. If you'd like a second pair of eyes, request a fixed quote or book a free 30-minute call.
