If you've ever checked your website's speed and thought "good enough, my homepage loads fast" — that's no longer the full picture.
Google's Core Web Vitals used to be judged mostly page by page. Your homepage could pass with flying colors even if your service pages, blog, or gallery lagged behind. As of Google's March 2026 core update, that's changed. Vitals are now increasingly evaluated as a site-wide, aggregate score — meaning your slowest, most-visited pages can drag down how Google (and your visitors) judge your entire site, not just the page that's actually slow.
If you run a plumbing, HVAC, dental, salon, or contracting business, this matters more than it sounds. You'll learn in this article: what actually changed, why one weak page can now be a whole-site problem, and a simple checklist to find and fix your worst offenders — no developer jargon required.
A note on sourcing: the shift to more holistic, site-wide Core Web Vitals evaluation has been reported by industry outlets tracking Google's March 2026 core update (e.g. Technadigital, SEOcrawl). Treat the specifics as reported industry analysis rather than an official line-by-line Google announcement — Google has historically been vague about exact ranking mechanics.
What Actually Changed
For years, the mental model was simple: each page on your site got its own Core Web Vitals grade for three things:
- LCP (Largest Contentful Paint) — how fast the main content appears
- INP (Interaction to Next Paint) — how quickly the page responds when someone taps or clicks
- CLS (Cumulative Layout Shift) — how much the page jumps around while loading
A fast homepage and a slow "Contact Us" page used to be treated somewhat independently. Under the newer site-wide scoring approach, Google appears to be leaning more heavily on an aggregated view across your templates and most-visited URLs — so a chronically slow template (a blog archive, a service-area page generator, a gallery page loaded with unoptimized photos) can weigh down the perceived health of your whole domain, even on pages that individually pass.
In practice, this means the old strategy of "just make the homepage fast" is no longer enough. Google is looking at the pattern across your site, not just your best page.
Why This Actually Matters for a Local Service Business
Here's the part most website speed tools don't explain to a business owner: this isn't just about a technical score. It changes where the real risk sits on your site.
Your Homepage Was Never the Problem
Most local service sites get real design attention on the homepage — a nice hero image, a clean layout, a fast-loading first impression. That's exactly why homepage speed usually looks fine.
The templates that get ignored are the ones built once and never revisited:
- Service-area pages (e.g. "Plumber in [City]" pages generated for SEO, often dozens or hundreds of them)
- Photo galleries and before-and-after pages, frequently stuffed with full-resolution phone photos
- Blog or resource pages built on a generic template with no image optimization
- Booking or contact pages loaded with third-party embeds (calendars, chat widgets, maps)
If any one of these templates is consistently slow, it's now more likely to color how Google — and increasingly, your customers — perceive the whole site's speed and reliability.
Customers Don't Judge Page-by-Page Either
This mirrors real customer behavior. A homeowner doesn't think "the homepage was fast, so I trust this roofing company." They click through to the gallery to see finished work, and if that page crawls, the impression of the whole business drops — regardless of how fast the homepage was.
How to Check Where Your Site Actually Stands
You don't need to become a performance engineer to get a real answer. Here's a practical, no-jargon way to check:
- Open Google's PageSpeed Insights (free, just paste in your URL) and test more than your homepage. Test your service pages, your gallery, and your contact/booking page individually.
- Look for the pattern, not just one number. If your homepage scores well but three other page types consistently score poorly, that's your site-wide risk — even if no single page looks catastrophic.
- Check your busiest pages, not just your favorite ones. Use your analytics to see which pages actually get the most visits (often it's a service page or the gallery, not the homepage) and prioritize testing those.
- Repeat the test on mobile. Most local-service traffic is mobile, and mobile scores are typically worse than desktop — this is usually where the real gap shows up.
A Simple Site-Wide Speed Checklist
Use this checklist to triage instead of trying to fix everything at once:
- Homepage passes Core Web Vitals on mobile
- Top 3 service pages (by traffic) pass Core Web Vitals on mobile
- Photo gallery / before-and-after page loads images in a compressed, modern format (not raw phone-camera JPEGs)
- Contact/booking page doesn't visibly jump around as widgets load (that's a CLS problem)
- No page relies on more than 2-3 third-party scripts (chat widgets, booking calendars, review badges) loading immediately on page load
If you can't check even two or three of these boxes, that's a strong sign your site is carrying hidden risk that a homepage-only speed test would never have caught.
Fixing the Common Offenders
You don't need a full rebuild to close most of the gap. The fixes tend to repeat across the templates local service sites use most:
Photo galleries and before-and-after pages Compress images before upload, or better, let your site automatically serve modern formats (WebP/AVIF) at the right size. This single fix often does more for a gallery page's score than anything else, since oversized photos are almost always the biggest offender.
Service-area page templates If you have dozens of near-identical city or neighborhood pages built from one template, fixing that template once fixes the problem everywhere it's used — which is exactly why the site-wide scoring shift makes this worth doing.
Booking and contact pages Delay loading calendar and chat widgets until a visitor actually interacts with the page (a simple "click to open" button instead of an embed that loads instantly) rather than loading them immediately. This also protects your Call Now or Book Now button from feeling sluggish, which is what actually costs you leads.
Blog or resource pages If these were built on a generic theme or template you haven't touched, they're a common source of a bad aggregate score simply because they're the most-neglected part of the site.
The Bottom Line
A fast homepage used to be enough to look good to Google. Now, the pages you never think about — the gallery, the service-area pages, the booking flow — are just as much a part of how your whole site gets judged, and they're usually the parts getting the least attention.
The good news is you don't need to fix everything overnight. Test your actual highest-traffic pages, not just your homepage, find the one or two templates dragging things down, and fix those first.
If you're not sure where your site's weak points are, or you want a proper site-wide speed audit rather than a homepage-only check, reach out through the contact page and we can walk through it together.