
Core Web Vitals are a small ranking input, not a magic lever. Google uses three real-user metrics to judge how a page loads, responds and holds still, and good scores help most when your content is already as relevant as your competitors’. For a local service business, the practical goal is simple: get your money pages into the “Good” range, confirm it with real-user data, and then go back to the work that moves rankings more.
This guide covers the thresholds, what Google actually says about their weight, how to read your reports, and the order we would fix things in.
TL;DR
- Core Web Vitals are three metrics: Largest Contentful Paint (LCP) at 2.5 seconds or less, Interaction to Next Paint (INP) under 200 milliseconds, and Cumulative Layout Shift (CLS) at 0.1 or less.
- They are one signal among many. Relevance and content quality matter substantially more, and good scores do not guarantee a top spot.
- Real-user (field) data decides your status. A perfect Lighthouse score does not.
- Fix the “Poor” pages that drive calls and bookings first, and start by checking server response time, not just images.
- Field reports use a 28-day window, so wait up to a month to see an improvement reflected.
Table of Contents
- What Core Web Vitals measure
- Do Core Web Vitals affect rankings?
- Lab data vs. field data: the mistake that wastes the most time
- How to check your own site
- The fix order we recommend
- Core Web Vitals checklist for a local service site
- Core Web Vitals for local businesses specifically
- Our perspective: speed is infrastructure, not a score
- When to bring in help
- FAQ
- Sources
What Core Web Vitals measure
Google defines Core Web Vitals as metrics for real-world user experience: loading performance, interactivity and visual stability. Each one maps to something a customer on a phone notices.
| Metric | What it captures | Good threshold |
|---|---|---|
| Largest Contentful Paint (LCP) | How quickly the main content (usually a hero image or headline block) appears | 2.5 seconds or less |
| Interaction to Next Paint (INP) | How fast the page responds after taps, clicks and key presses | Under 200 milliseconds |
| Cumulative Layout Shift (CLS) | How much the layout jumps while the page loads and is used | 0.1 or less |
The thresholds above come from Google Search Central’s Core Web Vitals documentation. INP replaced the older First Input Delay metric, and it is stricter because it looks at the full lifecycle of an interaction, not only the delay before it starts.
How “Good” is decided
A page does not pass because it was fast once. Google assesses the 75th percentile of real page loads. If at least 75% of visits meet the Good threshold for a metric, the page or site counts as Good for that metric. The reasoning is that the 75th percentile surfaces the frustrating experiences instead of hiding them behind an average.
For a local business, that matters because your visitors are often on mid-range phones over cellular connections, standing in a driveway or a parking lot. Your office laptop on fiber is not the test that counts.
Do Core Web Vitals affect rankings?
Yes, but modestly, and Google is unusually direct about it. Its page experience documentation says Core Web Vitals are used by its core ranking systems, that good scores do not guarantee top placement, and that chasing perfect scores purely for SEO may not be the best use of your time. Relevance and content quality remain the bigger factors.
Two practical readings follow from that.
- They act as a tiebreaker in close contests. When two pages are similarly relevant and helpful, the one that is pleasant to use has an edge. Local markets such as dentists, roofers or personal injury lawyers in a mid-size city are often exactly this kind of close contest.
- They protect conversions regardless of rank. Even if the ranking effect were zero, a page that shifts under a thumb or takes five seconds to show a phone number loses the lead. That is the more reliable reason to fix them.
It also helps to see where this sits in the bigger picture. Google describes automated ranking systems that weigh many factors and signals across hundreds of billions of pages. If you want a plain-English view of how those pieces connect for a service business, this explanation of how Google weighs ranking signals together is a useful companion to the technical docs.
What about AI answers?
Google states that its generative search features are rooted in the same core ranking systems. There is no separate speed test for AI Overviews that we can point to. A fast, stable, clearly structured page is simply easier for every system to fetch, render and understand.
Lab data vs. field data: the mistake that wastes the most time
Most owners first meet Core Web Vitals through a Lighthouse score, a single number out of 100. That number comes from a simulated load on a predefined device and network. It is lab data.
Google’s own guidance on why lab and field data differ explains that lab tools are best for diagnosing specific, fixable problems, while field data from real users is the better indicator of how the page actually performs. Field data is what shows up in Search Console and in PageSpeed Insights, and it comes from the Chrome User Experience Report (CrUX).
The consequences:
- A 100 in Lighthouse is not the goal and is not a ranking factor. Vercel’s explainer on Core Web Vitals and SEO makes the same point: only field data from real users feeds into ranking.
- A page can score 95 in the lab and still fail in the field, because real visitors scroll, tap, open menus and load third-party chat widgets that a static test never touches.
- CLS is the classic example. Elements that stay put during a static test often shift once a visitor scrolls or interacts, so test the actual flows: scroll to the form, open the mobile menu, dismiss the cookie banner.
Use the lab to find the cause. Use the field to decide whether you are done.
How to check your own site
You need two free tools, both from Google.
- Search Console’s Core Web Vitals report. It groups your URLs by status as Good, Needs improvement or Poor, and by mobile and desktop. Start here because it shows how many URLs share each problem.
- PageSpeed Insights. PageSpeed Insights assesses a single URL on mobile and desktop using both lab and real-world data. If that URL lacks enough real-user traffic, it can fall back to origin-level data covering the whole site.
The fallback is worth knowing. A new service-area page with a few visits a week may show your site-wide numbers, not its own. That is normal, not a bug.
Why your fix does not show up right away
Field data is a trailing 28-day window. According to Google’s documentation, PageSpeed Insights field data is typically updated daily, while the CrUX dataset in BigQuery updates monthly, and both cover the previous 28 days. So a fix you ship on Monday improves the average gradually. Expect up to a month before the report fully reflects it, and do not keep re-tuning in the meantime.
The fix order we recommend
The temptation is to open a report with 400 flagged URLs and start at the top. Do not. Google’s guidance on prioritizing Core Web Vitals work points to the same logic we use with clients: handle “Poor” before “Needs improvement”, and fix the issues that affect the most URLs or the most important pages first.
For a local service site, “most important” is concrete:
- The home page.
- Your primary service pages (for example, emergency roof repair, teeth whitening, DUI defense).
- Location or service-area pages.
- Contact and booking pages.
- Blog posts, last.
If you want a framework for ranking fixes by severity, URL coverage and business impact, this site speed fix checklist walks through the same triage idea from a marketer’s angle.
Step 1: Check server response before touching images
Slow LCP is usually blamed on big images, and sometimes that is right. But Google’s web performance team notes in its piece on common LCP misconceptions that many LCP problems come from slow server response (Time to First Byte), not only image weight. Their data breaks LCP into four parts: TTFB, image load delay, image load duration and render delay. In their sample, pages rated Good spent around 600 ms on TTFB, while Poor pages spent around 2,270 ms.
That makes TTFB a high-impact and often overlooked fix. Common causes on small-business sites are cheap shared hosting, no page caching, a page builder generating every page on request, and heavy plugin stacks. Moving to better hosting or turning on caching can improve every page at once, which is why it comes first.
Step 2: Fix LCP on the hero
On most service pages the LCP element is the top banner image or a large headline block. Practical moves:
- Make sure the hero image is not lazy-loaded. It is the first thing visitors need.
- Serve it at the size it displays, in a modern format.
- Do not hide it behind a slider script or a background-image rule that the browser discovers late.
- Keep fonts from blocking the headline text.
Step 3: Stop the layout from jumping (CLS)
Below 0.1 usually comes down to reserving space. Set width and height on images and video embeds, reserve a fixed slot for review widgets, maps and ad units, and avoid inserting banners above content after load. Cookie notices and “call now” sticky bars are repeat offenders. Then test by scrolling and tapping, as noted above, because a static load will miss the real shifts.

Step 4: Improve INP by removing weight
INP gets worse when the browser’s main thread is busy with JavaScript. On local sites the culprits are rarely your own code. They are chat widgets, call-tracking scripts, heatmap tools, booking embeds, social feeds and multiple tag manager containers. Audit what loads on each key page, remove what no one looks at, and delay what is not needed for the first interaction. Test the tap targets that matter: the menu, the phone button, the form fields.
Step 5: Re-measure in the field
After changes ship, run a lab test to confirm the fix worked mechanically, then watch Search Console over the next 28 days. Mark the date of each change so you can tie movement to action.
Core Web Vitals checklist for a local service site
Use this as a quick pass before you hand anything to a developer.
- [ ] Pulled the Search Console Core Web Vitals report for mobile and desktop.
- [ ] Listed Poor URLs and grouped them by template (home, service, location, blog).
- [ ] Tested the top five revenue pages in PageSpeed Insights and noted field vs. lab data.
- [ ] Checked TTFB and hosting quality before optimizing images.
- [ ] Hero image sized correctly, not lazy-loaded, loads early.
- [ ] Width and height set on all images, embeds and widget containers.
- [ ] Third-party scripts audited and trimmed (chat, tracking, heatmaps, feeds).
- [ ] Tested real interactions on a mid-range phone: menu, scroll, form, call button.
- [ ] Logged each change with its date and rechecked after 28 days.
Core Web Vitals for local businesses specifically
Local visibility has three layers: your Google Business Profile, your website, and the wider entity signals (citations, reviews, mentions) that tell search systems who you are. Page speed lives only in the second. That is why we would not put Core Web Vitals ahead of the basics.
If you are missing from the map pack, a slow site is rarely the main reason. Profile completeness, category choice, reviews and proximity usually dominate, and we cover those in our GBP-first local SEO audit checklist and our 30/60/90-day plan for ranking on Google Maps. Once those are in order, Core Web Vitals become a worthwhile layer on top, and they directly affect the visitor who clicks your listing and lands on your site.
Our perspective: speed is infrastructure, not a score
We work with local service businesses, from single-location practices to franchises, and the same pattern repeats. Owners arrive with a screenshot of a red Lighthouse number and a belief that it explains why they are not ranking. Usually it does not.
Here is how we think about it:
- Entity first, speed second. Search engines and AI tools need to understand clearly who you are, what you do and where. A fast page that says little still loses to a slower page that defines the business well. That is the idea behind our stack of SEO, GEO and AEO working together.
- Build it right once. Most Core Web Vitals failures are baked in at build time: heavy themes, unreserved space, a pile of plugins. It is cheaper to design pages that are fast by default than to patch them every quarter. This is why our SEO-native website design treats structure, speed and entity clarity as one job.
- Fix what drives calls. We would rather get your five service pages firmly into Good than spend weeks polishing a blog archive that produces no leads.
- Report plainly. You should see which URLs were Poor, what changed, when, and what the field data did afterward.
, NSYGHT
When to bring in help
You can handle a lot of this yourself: running the reports, trimming scripts, resizing images. Bring in a developer or an agency when the cause sits in the platform, such as a theme that cannot be made fast, hosting you do not control, or a template problem spread across hundreds of URLs.
If you want Core Web Vitals handled as part of a broader local visibility plan, our local SEO packages cover technical SEO alongside Google Business Profile work and on-page optimization. If you only need a second opinion on a specific report, consulting is $125 per hour. And if the site itself is the bottleneck, we can talk about a rebuild through our web design service. You can also start from our home page to see how we work with local service businesses.
FAQ
Are Core Web Vitals a ranking factor?
Yes, they are used by Google’s core ranking systems, but as one signal among many. Google says good scores do not guarantee top placement and that relevance and content quality remain more important. Treat them as a way to remove a handicap, not as a shortcut.
What are the Core Web Vitals thresholds?
For a Good rating, LCP should be 2.5 seconds or less, INP under 200 milliseconds and CLS 0.1 or less. Google measures these at the 75th percentile of real page loads, so at least 75% of visits need to meet each threshold.
How long until improvements show in Search Console?
Up to about a month. The field data behind the report is a trailing 28-day window, so old slow visits age out gradually. Lab tests will show a change immediately, but they are not what the report is based on.
Does a 100 PageSpeed score help me rank?
No. Lighthouse lab scores are a diagnostic tool and are not a ranking factor. What counts is field data from real users. A site with a lab score in the 80s and Good field data is in better shape than a lab 100 with Poor field data.
Where should a local business start?
Open the Search Console Core Web Vitals report, find the Poor URLs, and focus on the pages that bring in calls and bookings. Check server response time and hosting before you spend hours compressing images.
Sources
- Understanding Core Web Vitals and Google search results
- Understanding Google Page Experience
- A Guide to Google Search Ranking Systems
- Why lab and field data can be different
- How Core Web Vitals affect SEO (Vercel)
- Core Web Vitals report in Search Console
- About PageSpeed Insights
- Top Core Web Vitals recommendations
- Common misconceptions about how to optimize LCP