Core Web Vitals for Local SEO: What Small Businesses Need to Know

Core Web Vitals became an official Google ranking factor in 2021, and since then the technical SEO community has debated how much they actually matter in practice. The honest answer for local businesses: they matter enough to be worth fixing, but they're not so dominant that a poor score automatically defeats a well-optimized competitor. Where they do matter most is on mobile, which is exactly where most local searches happen. Fixing your Core Web Vitals is one of the highest-leverage technical improvements a local business website can make.

Key Points

• Google's three Core Web Vitals are LCP (Largest Contentful Paint), INP (Interaction to Next Paint), and CLS (Cumulative Layout Shift).
• All three are measured from real user data via Chrome, not from synthetic lab tests — which means your actual site performance on real devices matters.
• Mobile performance is weighted more heavily in local search contexts because most local searches happen on mobile devices.
• Most Core Web Vital problems on small business sites come from a small number of fixable causes: unoptimized images, slow hosting, poorly implemented third-party scripts, and layout-shifting ads or fonts.
• You don't need a developer for many of these fixes, especially if you're on a common CMS like WordPress.

What Each Metric Measures

LCP — Largest Contentful Paint

LCP measures how long it takes for the largest visible element on the page — typically a hero image or headline — to fully load. It's the closest proxy Google has for "how fast does this page feel."

Target: Under 2.5 seconds. Poor: Over 4 seconds.

For most local business websites, the LCP element is a hero image on the homepage. If that image is large, uncompressed, or loading from a slow server, your LCP suffers.

INP — Interaction to Next Paint

INP replaced FID (First Input Delay) in March 2024. INP measures responsiveness — specifically, how long it takes for the page to visually respond after a user interacts with it (clicks a button, taps a link, fills out a form field).

Target: Under 200 milliseconds. Poor: Over 500 milliseconds.

Poor INP often comes from JavaScript that's blocking the main thread — typically third-party scripts like chat widgets, analytics, and social sharing buttons.

CLS — Cumulative Layout Shift

CLS measures visual stability. A high CLS score means your page elements are moving around as the page loads — images shifting content down, fonts loading and changing text size, ads popping in and displacing the layout.

Target: Under 0.1. Poor: Over 0.25.

This is the most user-experience-damaging of the three metrics. If someone tries to click your phone number and it shifts just as they tap, that's both a frustrating experience and a CLS problem.

How to Measure Your Core Web Vitals

Google Search Console (Free, Field Data)

Go to Search Console → Experience → Core Web Vitals. This shows your actual performance data from real Chrome users. It's the most authoritative source because it reflects what real visitors experience. Note: you need at least 100 URLs with sufficient data for metrics to appear.

PageSpeed Insights (Free, Both Lab and Field Data)

Visit pagespeed.web.dev and enter your URL. This gives you both Lighthouse lab scores (synthetic, run from a controlled environment) and CrUX field data (real user measurements). Pay more attention to field data — lab scores are useful for diagnosis but field data is what Google ranks you on.

Google Search Console's URL Inspection Tool

For specific pages (like your homepage or a key service page), the URL inspection tool shows page experience signals including Core Web Vitals status.

Common Problems and How to Fix Them

Slow LCP: Unoptimized Hero Images

This is the most common LCP problem on local business sites. A hero image that's 4MB and 4000px wide will dominate your load time.

Fixes:

• Compress images using a tool like Squoosh (free, web-based) or ShortPixel (WordPress plugin)
• Resize images to the actual display size — a hero image displayed at 1200px wide doesn't need to be a 3600px file
• Use modern formats: WebP is significantly smaller than JPEG or PNG at equivalent quality
• Add loading="eager" and fetchpriority="high" to your hero image's HTML so the browser prioritizes it
• Add <link rel="preload"> for your hero image in the page <head>

Slow LCP: Slow Hosting

If your web host is slow, there's a ceiling to how much image optimization can help. A request for your page has to reach a server, be processed, and return — if that takes 2 seconds before anything loads, you're already behind.

Fixes:

• Move to a faster host (Cloudflare Pages, WP Engine, SiteGround, or Kinsta for WordPress)
• Enable server-side caching on your CMS
• Use a CDN (Content Delivery Network) — Cloudflare's free tier is excellent and easy to set up

Poor INP: Blocking JavaScript

Third-party scripts are the most common INP culprit. Live chat widgets, marketing pixels, social sharing buttons, and analytics scripts all execute JavaScript that can block the browser's main thread.

Fixes:

• Audit which third-party scripts are loading using PageSpeed Insights or Chrome DevTools
• Defer non-critical scripts using the defer attribute
• Load third-party chat and marketing scripts after user interaction (lazy loading) rather than on page load
• Remove scripts you don't actually use — it's common to find 5–10 tracking scripts on small business sites from past marketing experiments

High CLS: Unsized Images

If an <img> tag in your HTML doesn't have explicit width and height attributes (or CSS aspect-ratio), the browser doesn't know how much space to reserve for it. When the image loads, everything below it shifts down — CLS.

Fix: Add width and height attributes to all images in your HTML. For WordPress users, this is handled automatically for images added through the media library in recent versions.

High CLS: Web Font Loading

When a system font displays first and then your custom web font loads and replaces it, text can shift in size and position. This is called FOUT (Flash of Unstyled Text) and it generates CLS.

Fixes:

• Use font-display: optional in your CSS — this tells the browser to only use the custom font if it loads very quickly, otherwise use the system font
• Preload your most critical web font: <link rel="preload" as="font">
• Self-host fonts instead of loading from Google Fonts (reduces a DNS lookup and speeds up delivery)

Prioritizing Fixes by Impact

Not every Core Web Vitals fix is worth the same effort. Prioritize in this order:

1. Fix critical LCP issues (image size and host speed) — highest ranking impact
2. Fix CLS issues (image sizing, font loading) — most visible user experience impact
3. Audit and remove unnecessary third-party scripts — improves both INP and LCP
4. Address remaining INP issues after script cleanup

Tools to Help

• Semrush Local SEO Tools — Site audit identifies technical issues including page speed problems
• Ahrefs — Site audit includes performance checks
• Google PageSpeed Insights — Free, authoritative Core Web Vitals measurement

Next Steps

1. Run your homepage through PageSpeed Insights and record your LCP, INP, and CLS scores
2. Check Google Search Console → Core Web Vitals report for site-wide field data
3. Identify your LCP element (usually a hero image) and check its file size
4. Compress and resize any images over 200KB that appear above the fold
5. Audit your third-party scripts in PageSpeed Insights and identify candidates for removal or deferral
6. Re-measure after each change to track improvements

Frequently Asked Questions

Q: My PageSpeed score is 65/100 but my rankings are fine. Should I still fix this? A: PageSpeed scores are Lighthouse lab scores — they don't directly map to Google's field data scoring. If your Search Console Core Web Vitals report shows "Good" for most URLs, your rankings aren't being penalized. Focus on Search Console data over Lighthouse scores.

Q: Will fixing Core Web Vitals improve my local pack rankings specifically? A: Core Web Vitals primarily affect organic ranking signals, not local pack rankings directly. However, the local pack often shows organic results beneath it, and a fast website improves organic performance. Additionally, page experience signals have indirect effects on local visibility through engagement metrics.

Q: My WordPress site uses a page builder. Can I still improve Core Web Vitals? A: Yes, but it's more work. Page builders like Divi, Elementor, and Visual Composer add significant JavaScript and CSS overhead. Install a performance plugin like WP Rocket or Perfmatters to manage asset loading. For severe cases, consider switching to a lighter theme with a page builder that has better performance characteristics.

Learn More

Get your free Local SEO Audit Template to evaluate your site's technical performance and prioritize fixes.