If Google Search Console is flagging your site for Core Web Vitals issues, you’re not alone — most small business websites built on page builders, stock themes, and a pile of plugins run into at least one of these problems. The good news is that the three metrics Google checks are specific and fixable, even if you’re not a developer.
Table of Contents
This guide walks through what Core Web Vitals actually measure, how to find your site’s numbers, and the most common fixes for each metric — starting with the changes that give you the biggest improvement for the least effort.
Quick Answer
Core Web Vitals are three Google metrics — Largest Contentful Paint (LCP), Interaction to Next Paint (INP), and Cumulative Layout Shift (CLS) — that score how fast a page loads, how responsive it feels, and how visually stable it is. Google measures and uses these as a ranking signal for both mobile and desktop results, scored separately for each. Most small business sites fix their scores by compressing and properly sizing images, removing unused plugins/scripts, enabling caching through their host or a CDN, and reserving space for ads, embeds, and web fonts so the layout doesn’t jump around while loading.
What Core Web Vitals Actually Measure
Largest Contentful Paint (LCP) tracks how long it takes the biggest visible element on the page — usually a hero image, banner, or headline — to fully render. A good score is 2.5 seconds or less. This is almost always a loading-speed issue: a huge unoptimized image, a slow host, or render-blocking scripts delaying everything else.
Interaction to Next Paint (INP) measures how quickly the page responds when someone clicks a button, taps a menu, or fills out a form. A good score is 200 milliseconds or less. INP replaced an older metric called First Input Delay in March 2024, and it’s a better signal because it checks responsiveness throughout the whole visit, not just the first click. High INP almost always comes down to too much JavaScript running on the main thread at once — often from chat widgets, ad scripts, or heavy page-builder plugins.
Cumulative Layout Shift (CLS) measures how much content jumps around as the page loads — think of text shifting down because an ad or image loaded late. A good score is 0.1 or less. This is usually caused by images or embeds without a defined size, web fonts swapping in late, or ad slots that reserve no space until content fills them.
You can check your own scores for free in Google Search Console under the Core Web Vitals report, which groups your actual pages by Good, Needs Improvement, or Poor using real visitor data — reported separately for mobile and desktop, since Google evaluates and ranks both. For a single-page, on-demand check, use Google’s PageSpeed Insights tool, which gives you both lab data and field data for each device type, plus a prioritized list of opportunities.
The Fixes That Matter Most
Start with images, since oversized images are the single most common cause of poor LCP on small business sites. Resize images to the dimensions they’re actually displayed at (don’t upload a 4000px-wide photo into a 600px slot), compress them, and serve modern formats like WebP or AVIF where your platform supports it. Many hosting platforms and CMS plugins can do this automatically once enabled.
Turn on caching and use a CDN. Most web hosts offer built-in page caching, and a content delivery network like Cloudflare caches your site’s static files closer to each visitor, cutting load time regardless of where they’re browsing from. If you’re on WordPress, a caching plugin plus image optimization usually solves LCP on its own.
Audit your plugins and third-party scripts. Chat widgets, popup tools, analytics snippets, and page-builder add-ons each add JavaScript that has to run before the page feels responsive. Remove anything you’re not actively using, and for the scripts you keep, see if your platform lets you load them asynchronously or delay them until after the page is interactive — this directly improves INP.
Reserve space for anything that loads after the initial page render. Add explicit width and height attributes to images and embedded videos, give ad containers a fixed minimum height, and load custom fonts with font-display: swap or optional so the browser doesn’t reflow text once the font finishes loading. These changes target CLS specifically.
If you’re on a drag-and-drop builder (Wix, Squarespace, Shopify, WordPress with Elementor or similar), check whether the platform has a built-in performance or speed setting — many have added one-click image optimization and script-deferral options precisely because Core Web Vitals became a ranking factor.
Tips / Common Mistakes
Don’t chase a perfect PageSpeed Insights score — that tool runs a single simulated test (lab data). What actually matters for SEO is the field data in Search Console’s Core Web Vitals report, which reflects real visitors over a rolling window and can take a couple of weeks to update after you make fixes.
Don’t install a ‘speed’ plugin on top of an already slow theme and call it done — if your underlying theme or template is bloated, a caching plugin can mask the slowdown on one device type while the other still struggles.
Don’t check only one device, and don’t assume Core Web Vitals is a mobile-only check. Google applies Core Web Vitals as a page-experience ranking signal to both mobile and desktop results, scoring each independently from its own real-world visitor data, so test and fix both — a site that scores well on desktop can still fail its mobile thresholds (and vice versa).
Fix one thing at a time when possible, and re-test. Image size, caching, and script cleanup each move different metrics, and testing after each change makes it much easier to see what actually worked.
Explore more: More small business tech guides.
Core Web Vitals FAQs
Do Core Web Vitals affect my Google ranking?
Yes, they’re part of Google’s page experience signals, applied to both mobile and desktop results, but they act more as a tiebreaker between pages of similar relevance and quality rather than a dominant ranking factor on their own. Good content and relevance still matter more — but a slow, jumpy site can hold you back against competitors with similar content.
How do I check my site’s Core Web Vitals score?
Use Google Search Console’s Core Web Vitals report for real-visitor data across your whole site, or PageSpeed Insights for an instant check on a single URL. Both tools let you check mobile and desktop separately, since Google scores and ranks each device type independently.
What’s the fastest fix for a bad Core Web Vitals score?
Compressing and resizing your largest images almost always delivers the biggest improvement with the least work, since oversized images are the most common cause of poor LCP.
Did FID get replaced?
Yes. First Input Delay (FID) was replaced by Interaction to Next Paint (INP) as an official Core Web Vital in March 2024, because INP reflects responsiveness across the full visit rather than just the first interaction.
Build It With GTStudios
Need help with your website, app, or small-business tech? GTStudios builds web, apps, and software for small businesses. See how GTStudios can help.
Want dev news in your inbox? Subscribe to the free newsletter.
Photo: Sia Karamalegos / CC BY-SA 4.0, via Wikimedia Commons.