Core Web Vitals for Small Business: What to Fix First

White and blue analog gauge, a nod to the page speed scores behind Core Web Vitals for small business

Core Web Vitals for small business websites come down to three scores: loading speed, responsiveness and layout stability. Fewer than half of websites pass all three on mobile, and most failures trace back to a few fixable causes. This guide shows how to check your scores for free, what to fix first and how much speed matters for Google and AI search.

You don't need a developer to start. On Webflow, Squarespace, Wix, Shopify or WordPress, the biggest wins are settings and image choices you control. The harder fixes can wait until you know they matter.

Core Web Vitals for small business: what the three scores mean

Core Web Vitals are Google's measures of how a page feels to a real visitor. Google's Core Web Vitals guide sets a target for each one. Your scores come from real visits in Chrome, not from a lab test.

Largest Contentful Paint (LCP) measures loading. It times how long the biggest thing on the screen takes to appear, usually your hero photo or headline. Good is 2.5 seconds or less.

Interaction to Next Paint (INP) measures responsiveness. It times the gap between a tap or click and the page visibly reacting, such as a menu opening. Good is 200 milliseconds or less.

Cumulative Layout Shift (CLS) measures visual stability. It scores how much content jumps while the page loads, like a button sliding down just as you tap it. Good is 0.1 or less.

Core Web Vitals targets for small business websitesThe three Core Web Vitals and their targets75% of real visits must hit the green rangeGoodNeeds workPoorLCPLoadingHow fast the main content appears≤ 2.5 s2.5–4 s> 4 sINPResponsivenessHow fast the page reacts to a tap≤ 200 ms200–500 ms> 500 msCLSVisual stabilityHow much the layout jumps≤ 0.10.1–0.25> 0.25

Each score is judged at the 75th percentile. That means 75% of visits need to hit the target, so a fast experience on your office Wi-Fi doesn't count for much. Your slowest customers, often on phones with weak signal, decide whether you pass.

Most websites fall short. HTTP Archive's Web Almanac performance chapter draws on Chrome data from millions of websites. It finds that only 48% of sites pass all three on mobile.

LCP is the hardest: 62% of sites pass it on mobile, compared with 77% for INP and 81% for CLS.

That's good news for a small business. If you pass, you're ahead of most of the web. If you fail, the cause is usually one of a few common problems.

How to check Core Web Vitals on a small business website

Two free Google tools cover everything you need. PageSpeed Insights needs no setup, and Search Console only asks you to verify your site once.

Start with PageSpeed Insights

Go to PageSpeed Insights, paste in your homepage address and run the test. Check the mobile tab first, because that's where most sites fail and many customers browse.

The top section, labeled with real-user data, is the one that counts. It shows your actual LCP, INP and CLS from Chrome visitors over the last 28 days.

The performance score below it is a lab simulation. It helps you find causes, but Google doesn't use it for rankings.

Then test your three or four most important pages. Your homepage, main service page, contact or booking page and best-performing blog post make a good set. Very small sites may see a message that there isn't enough real-user data, in which case the lab results are your best guide.

Then use the Core Web Vitals report in Search Console

Search Console's Core Web Vitals report shows your whole site at once. It groups similar pages together and labels each group Good, Needs improvement or Poor. A group's label comes from its worst metric.

This report is the best way to spot a pattern. If every blog post fails LCP, the problem is probably your blog template, not one article. Fix the template once and every page in the group improves.

After a fix, open the issue in the report and start a validation. Google then watches real visits for 28 days before confirming the issue is gone, so don't expect an instant green label. Our guide to a weekly Search Console check shows where this report fits in a regular routine.

Which Core Web Vitals fixes to make first

Not every fix is worth your time. The ones below are ranked by how often they cause failures and how easy they are on a typical small business site. Start at the top and stop once your scores pass.

Fix list

Core Web Vitals fixes for small business sites, ranked

FixScore it helpsWhat it looks likeEffortPriority
Compress and resize the hero imageLCPA 4 MB phone photo at the top of the homepageLow, do it yourselfDo first
Stop lazy-loading the first imageLCPHero image set to load lazily by the builder or a pluginLow, one settingDo first
Set a width and height on every imageCLSText jumps down as photos loadLow to mediumDo first
Make banners sit on top of the pageCLSCookie or promo bar pushes the page down after it loadsLow, one settingDo first
Remove unused apps, pixels and widgetsINPOld ad pixels, a chat widget nobody answersMediumDo next
Load widgets only where they're neededINPBooking script running on every blog postMediumDo next
Switch to a lighter theme or faster hostLCP and INPHeavy theme on cheap shared hostingHigh, needs a developerLater

Work down the list and stop once all three scores pass.

Do first: fix your hero image

Your hero image is usually what LCP measures. The Web Almanac finds that an image is the largest element on 76% of mobile pages. A slow hero image is one of the most common reasons small business sites fail LCP.

Start by shrinking the file. Export hero photos at the size they actually display, usually around 1,600 to 2,000 pixels wide, and compress them. Saving them as WebP or AVIF instead of JPEG makes them smaller still.

Then check that the image isn't set to lazy-load. Lazy loading delays images until they're needed, which suits photos further down the page but slows the first one a visitor sees.

Google's guide to improving LCP is clear: never lazy-load your LCP image. Yet the Web Almanac finds that about one in six pages still does.

Do first: give every image a fixed size

Images without a set width and height are the classic cause of layout shift. The browser doesn't know how much room to save, so the text below jumps when the image arrives. The Web Almanac finds that 62% of mobile pages have at least one image without set dimensions.

Most website builders handle this for you if you use their own image blocks. Problems usually come from custom code embeds, older templates or images pasted into rich text. Google's guide to fixing layout shift also flags ads, embeds and banners that appear after the page loads.

Cookie banners and promo bars deserve a second look. If yours pushes the page down, it adds layout shift on every visit. Many consent tools let you show it as an overlay instead.

Do next: cut the extra scripts

Every chat widget, pop-up tool, review badge, heatmap and tracking pixel adds JavaScript. That code competes with your visitor's taps, which is what drags INP down. Google's guide to improving INP notes that scripts loading on the page can delay how quickly it responds.

Make a list of every app and script on your site, then remove anything you haven't used in three months. Old tracking pixels from ad platforms you no longer use are common culprits. On Shopify and WordPress, apps and plugins you've uninstalled sometimes leave code behind.

For the scripts you keep, ask whether they need to load on every page. A booking widget only needs to run on your booking page. Our post on landing page mistakes covers how slow pages cost you leads, even when they pass Core Web Vitals.

Leave for later: hosting and theme rebuilds

A slow server, a heavy theme or a page builder that adds lots of code can all hurt scores. These fixes usually mean moving hosts, switching themes or hiring a developer. Only take them on if the cheaper fixes above don't get you to a pass.

If your site is on a hosted builder like Webflow, Squarespace or Shopify, you can't change the server anyway. Those platforms already deliver your site from fast servers around the world. Focus on what you put on the page, not on what the platform runs underneath.

Do Core Web Vitals affect Google rankings and AI search?

Yes, but less than many people assume. Google says good Core Web Vitals align with what its core ranking systems reward. Its page experience guide also says passing scores don't guarantee top rankings.

The same guide says Google always tries to show the most relevant content, even when its page experience is poor. In practice, speed works like a tiebreaker: a slow page with the best answer can still outrank a fast, thin one.

So don't pause your content work to chase a perfect score. Fix the obvious problems, then get back to answering your customers' questions.

The same applies to Google's AI features. Google's guide to AI features and your website says AI Overviews and AI Mode have no extra technical requirements. It lists a great page experience among the normal SEO basics that still count.

ChatGPT, Gemini and Perplexity don't publish Core Web Vitals as a factor in which businesses they recommend. What they need is a page they can load and read that answers the question clearly. Our guides to getting recommended by AI search and whether to block AI crawlers cover the parts that matter more there.

The bigger payoff from speed is with customers. A page that loads fast and doesn't jump keeps more visitors long enough to call, book or buy. Treat Core Web Vitals as a customer experience fix first and an SEO bonus second.

Your next step is a five-minute check. Test your homepage in PageSpeed Insights on mobile and note which score fails. Then start with the matching fix in the table above.

Frequently asked questions

What are Core Web Vitals for a small business website?

Core Web Vitals are three Google scores that measure how a page feels to real visitors. Largest Contentful Paint measures loading, and Interaction to Next Paint measures how fast the page responds to taps. Cumulative Layout Shift measures how much the layout jumps.

What is a good Core Web Vitals score?

Google's targets are an LCP of 2.5 seconds or less, an INP of 200 milliseconds or less and a CLS of 0.1 or less. At least 75% of visits to a page need to meet each target for it to pass.

How do I check my Core Web Vitals for free?

Use PageSpeed Insights to test individual pages and look at the real-user data at the top. Then open the Core Web Vitals report in Google Search Console to see which groups of pages pass or fail across your whole site.

Do Core Web Vitals affect Google rankings?

Yes, but they act more like a tiebreaker than a main factor. Google says good scores align with what its ranking systems reward but don't guarantee top rankings. The most relevant content can still rank with a weaker page experience.

Do Core Web Vitals matter for ChatGPT, Gemini and Google AI Mode?

Google says AI Overviews and AI Mode have no extra technical requirements beyond normal SEO, which includes a good page experience. ChatGPT, Gemini and Perplexity don't publish Core Web Vitals as a factor, but they still need a page that loads and reads easily.