Core Web Vitals are three measurements Google uses to judge real-world page experience: Largest Contentful Paint for loading, Interaction to Next Paint for responsiveness and Cumulative Layout Shift for visual stability. Google’s good thresholds are LCP within 2.5 seconds, INP within 200 milliseconds and CLS of 0.1 or less. Most local business sites miss them because of heavy themes, oversized images, third-party scripts and slow hosting.
What Core Web Vitals are
Core Web Vitals are a small set of measurements Google created to describe how a page feels to real visitors. They are not abstract lab scores. Google collects them from Chrome users who have opted into sharing usage data, in what is called the Chrome User Experience Report, and uses that field data in Search Console and as one of many signals in ranking.
There are three of them. Largest Contentful Paint, or LCP, measures loading. Interaction to Next Paint, or INP, measures how quickly the page responds when someone taps or clicks. Cumulative Layout Shift, or CLS, measures how much the page jumps around while it loads. Each has a threshold Google considers good, and Google judges a page by how the slower end of real visits performs, at the 75th percentile, not by the best case.
Core Web Vitals are not the most important ranking factor. Relevance and helpful content come first. But when two pages are comparable, the one that loads faster and behaves better has an edge, and the visitors who actually land on the page reward it regardless of what Google does.
Largest Contentful Paint: how fast the main content appears
LCP measures how long it takes for the largest visible element on the screen to finish rendering. On most local business sites, that is the hero image or the main headline at the top of the page. Google considers 2.5 seconds or less good, and anything over 4 seconds poor.
Slow LCP usually comes from one of four places. The server is slow to respond. The hero image is huge, uncompressed or loaded late. Fonts and stylesheets block the page from drawing anything until they finish. Or the main content is built by JavaScript after the page loads, so the browser has nothing to show until the scripts run.
The fixes follow the causes. Use fast hosting or serve static files from a content delivery network. Size the hero image for the screen it appears on, use a modern format such as WebP or AVIF, and tell the browser to load it first. Keep critical CSS small and inline it. Put the main content in the HTML so it appears without waiting for scripts.
Interaction to Next Paint: how fast the page responds
INP replaced an older metric, First Input Delay, in March 2024. It measures the delay between a visitor’s interaction, such as tapping a menu button, opening a FAQ or pressing a call button, and the moment the screen visibly updates. It looks across the interactions during a visit and reports one of the slowest. Good is 200 milliseconds or less; over 500 is poor.
Poor INP almost always means too much JavaScript running on the main thread. Chat widgets, tracking pixels, heatmap tools, review carousels, page builder animations and sliders all compete for the phone’s processor. When a visitor taps the menu while those scripts are busy, the tap waits in line.
The cure is to ship less JavaScript and load what remains later. Remove tools nobody looks at. Load chat widgets only when someone asks for them. Replace JavaScript sliders and accordions with simple HTML and CSS where possible. A local business site rarely needs much script at all.
Cumulative Layout Shift: whether the page jumps around
CLS measures unexpected movement of content while the page loads. Everyone has experienced it: you go to tap a link, an ad or image loads above it, and you tap the wrong thing. Google scores CLS as a unitless number, where 0.1 or less is good and above 0.25 is poor.
Common causes include images and videos without set width and height, banners and cookie notices that push content down after loading, web fonts that swap in at a different size than the fallback font, and embedded widgets such as maps or review feeds that appear late and take up space.
The fixes are straightforward. Always give images and embeds dimensions or an aspect ratio so the browser reserves space. Put notices in a fixed overlay instead of inserting them into the page. Choose fallback fonts with similar sizing, or adjust them so the swap is barely visible. Reserve room for anything that loads late.
Why phone speed matters so much for local businesses
Local searches happen on phones constantly: in a driveway looking at a leak, in a parking lot looking for a dentist, on a couch comparing contractors. Those visitors are often on cellular connections, sometimes with weak signal, on phones much slower than the laptop the site was designed on. A site that feels fine at the office can feel broken on a mid-range phone across town.
Local visitors also have choices one tap away. If your page sits blank while a competitor’s loads instantly, the visitor goes back to the results and calls the competitor. Speed does not need a ranking factor to cost you money. It costs you the customers who already found you.
Google indexes and evaluates sites based on their mobile version. That makes the phone experience the real experience as far as search is concerned. Test on a real phone, on cellular data, before you decide your site is fast.
Common causes of slow local business sites
Most slow small business sites share the same problems. None of them are exotic, and most come from tools added for convenience and never removed. Going through this list usually explains the bulk of a poor score.
- Multipurpose themes and page builders that load every feature on every page
- Hero images uploaded straight from a camera or stock site at full size
- Background videos on the homepage
- Several web fonts in several weights loaded from third-party servers
- Chat widgets, pop-ups and tracking scripts loading before the content
- Embedded maps, review feeds and social feeds on every page
- Cheap shared hosting with slow server response
- Plugins that each add their own CSS and JavaScript
- Content rendered by JavaScript instead of delivered in the HTML
Fonts, maps and widgets: the quiet speed killers
Some of the worst offenders on local business sites are features owners never think of as heavy. An embedded Google Map on every page loads a substantial amount of code before anyone touches it. A replacement is a static image of the map that links to your Business Profile or loads the interactive map only when tapped. Visitors still get directions, and the page stays light.
Review widgets and social feeds work the same way. They pull scripts, styles and images from another company’s servers, often late in the load, which hurts both LCP and CLS. Writing a few real customer reviews into the page as text, with a link to your full Google reviews, is faster and gives search engines readable content instead of an empty box.
Fonts deserve a hard look too. Each family and weight is a separate file. Two weights of one well-chosen font, hosted on your own domain and preloaded, usually look just as good as the five weights a theme loads by default. Small decisions like these are what separate a site that feels instant from one that feels sluggish.
How to check your site
Start with Google Search Console. The Core Web Vitals report groups your URLs into good, needs improvement and poor for mobile and desktop, based on real visitor data. It shows which metric is failing and which group of pages is affected, which helps when one template is causing problems across many pages.
PageSpeed Insights lets you test a single URL. The top section shows field data from real users when Google has enough of it; the lower section is a lab test from Lighthouse that simulates a mid-range phone. Use the field data to decide whether there is a problem and the lab data to find out why. Lab scores vary from run to run, so do not chase a perfect number.
Smaller sites may not have enough traffic for field data. In that case, lean on lab tests and on real phones. If the page feels slow on a typical phone over cellular data, it is slow.
Fixing it for good
Patching a slow site helps, but the gains often fade as new plugins and scripts creep back in. The lasting fix is to build the site so speed is the default: static HTML served from a content delivery network, images processed at build time, minimal JavaScript, system or self-hosted fonts and no third-party code unless it earns its place.
That is how we build every site, because local customers judge a business by how quickly its site answers them. If you are keeping your current site, start with the biggest wins: compress and resize images, remove unused plugins and scripts, delay chat widgets and move to better hosting. Then check Search Console over the following weeks, since field data takes time to reflect changes.
Want this done for you? Think SEO audits your site for free, sends a price in writing, and nothing is due until you reach page one of Google search. Get the free audit.