Resources

Core Web Vitals for small business sites: what to fix first

What Core Web Vitals are, why they matter for SEO, and the highest-impact fixes for small business websites (especially on mobile).

Published: January 20, 2026Reading time: ~5 min

Core Web Vitals are Google's way of measuring user experience: how fast your site loads, how quickly it becomes interactive, and whether elements jump around while loading.

They're now a ranking factor. Slow, janky sites don't rank as well as fast, smooth ones. And more importantly—slow sites lose visitors. 40% of people abandon a site that takes more than 3 seconds to load.

This guide explains what Core Web Vitals are, why they matter, and which fixes give you the biggest improvement for the least effort.

What are Core Web Vitals? (plain English version)

Google measures three main metrics:

1. Largest Contentful Paint (LCP): How fast does your page load?

LCP measures how long it takes for the largest visible element on your page (usually an image or heading) to fully load.

Good: Under 2.5 seconds

Needs improvement: 2.5–4 seconds

Poor: Over 4 seconds

If your LCP is over 4 seconds, people are hitting the back button before your page even loads.

2. Interaction to Next Paint (INP): How quickly can people click things?

INP measures how long it takes for your site to respond when someone clicks a button, taps a link, or types in a form.

Good: Under 200 milliseconds

Needs improvement: 200–500 milliseconds

Poor: Over 500 milliseconds

If your INP is slow, buttons feel laggy and unresponsive. People think your site is broken.

3. Cumulative Layout Shift (CLS): Does your page jump around while loading?

CLS measures visual stability. If elements shift while the page loads—images popping in, text moving down, buttons jumping—that's a layout shift.

Good: Under 0.1

Needs improvement: 0.1–0.25

Poor: Over 0.25

Layout shifts are incredibly annoying. You try to click a button, but it moves right as you're about to tap it, and you click something else by accident.

Why Core Web Vitals matter (beyond rankings)

Yes, they're a ranking factor. But more importantly, they affect conversion rates.

Studies show:

  • If your page takes 1 second to load, conversion rates are X%.
  • If it takes 3 seconds, conversion rates drop by 32%.
  • If it takes 5 seconds, conversion rates drop by 90%.

A slow site costs you money—even if you're ranking well. People leave before your page loads.

How to test your site

Use Google PageSpeed Insights: pagespeed.web.dev

Enter your URL, and Google will give you a score (0–100) and show your Core Web Vitals metrics.

Test both desktop and mobile. Mobile is usually worse (slower connections, less powerful devices), and Google prioritizes mobile.

Don't panic if your score isn't 100. Scores in the 70–90 range are fine for most small businesses. Under 50 is a problem.

The highest-impact fixes (start here)

You don't need to optimize everything. Start with the fixes that give you the most improvement for the least effort.

Fix #1: Compress and optimize images

Images are usually the biggest performance problem on small business websites.

How to fix it:

  • Check your image file sizes: Right-click any image on your site, open it in a new tab, and look at the file size. If it's over 500KB, it's slowing you down.
  • Compress images: Use a free tool like TinyPNG (tinypng.com) or Squoosh (squoosh.app) to compress images to under 200KB without losing visible quality.
  • Use modern formats: WebP images are 30% smaller than JPEGs with the same quality. Most modern website platforms support WebP.
  • Use lazy loading: Images below the fold (not visible when the page first loads) should load only when someone scrolls down. Most modern platforms do this automatically.

This one fix can improve your LCP by 2–4 seconds.

Fix #2: Remove or defer unnecessary scripts

Every script (JavaScript) on your site adds load time. Common culprits:

  • Google Analytics, Google Tag Manager, Facebook Pixel (necessary, but often loaded inefficiently)
  • Chat widgets (Intercom, Drift, Tawk.to)
  • Social media embeds (Instagram feeds, Facebook widgets)
  • Old plugins or tools you installed and forgot about

How to fix it:

  • Audit your scripts: Use PageSpeed Insights to see which scripts are slowing you down.
  • Remove anything you don't use: Go through your plugins, widgets, and tracking codes. If you're not actively using it, delete it.
  • Defer non-critical scripts: Scripts for chat widgets or analytics don't need to load immediately—they can wait until after the page is interactive.

Fix #3: Fix layout shifts (reserve space for images and embeds)

Layout shifts happen when elements load without reserved space. The page shows text, then an image loads, and the text jumps down.

How to fix it:

  • Set width and height attributes on images: If your image is 800x600px, tell the browser that in your code. The browser will reserve space for it before it loads.
  • Reserve space for ads or embeds: If you have Google Ads, YouTube videos, or social media embeds, make sure they have fixed dimensions.
  • Avoid injecting content above existing content: Don't add banners or pop-ups that push content down after the page loads.

Fix #4: Use a fast hosting provider

If your hosting is slow, everything else is slow.

Signs your hosting is the problem:

  • Your site is fast when you test it locally, but slow when you visit the live URL.
  • Your Time to First Byte (TTFB) is over 600ms in PageSpeed Insights.
  • Your hosting costs $5/month.

Cheap shared hosting is cheap for a reason. If you're serious about performance (and SEO), upgrade to a better host.

Good options for small businesses: Vercel, Netlify (for modern sites), Kinsta, WP Engine (for WordPress).

Fix #5: Minimize custom fonts

Custom fonts (from Google Fonts, Adobe Fonts, etc.) add load time—especially if you're loading multiple weights and styles.

How to fix it:

  • Limit font weights: Don't load Regular, Medium, Semi-Bold, Bold, and Italic if you only use Regular and Bold.
  • Use font-display: swap: This tells the browser to show text in a system font while your custom font loads, preventing invisible text.
  • Consider system fonts: Fonts like Arial, Helvetica, Georgia, and San Francisco are already on users' devices—no download required.

What NOT to worry about (diminishing returns)

Don't obsess over getting a perfect 100 score. Scores in the 70–90 range are fine for most small businesses.

Don't spend hours micro-optimizing JavaScript if your real problem is a 5MB image on your homepage. Fix the big stuff first.

What to do next

Test your site with Google PageSpeed Insights. Look at your mobile score and Core Web Vitals metrics.

Start with images—that's usually the easiest, highest-impact fix.

If your score is under 50 and you're not sure how to fix it, get a free audit here or reach out for help.

FAQ

Do I need to fix Core Web Vitals on every page?

Focus on your most important pages first: homepage, top service pages, and contact page. Once those are fast, work on the rest. Google measures Core Web Vitals based on real user data, so the pages people actually visit matter most.

How often should I test my site?

Test after major updates (new images, new plugins, design changes). Otherwise, check every few months. Performance can degrade over time as you add content and features.

Want help applying this to your site?

Get a clear action plan and a build that holds up—based in St. Louis, working with small businesses nationwide.