The moment a lead is lost
Picture someone with water coming through their ceiling. They search “emergency plumber,” tap the first result and stare at a white screen. Maybe a spinner. Maybe a cookie banner and a chat bubble load before anything useful. They hit back and tap the next listing.
That plumber never finds out. There’s no record of a call that didn’t happen. That’s what makes speed easy to ignore: the cost is invisible. You won’t see it in your phone log, only in leads you assume you were never going to get.
Speed matters most on the visits that matter most: mobile, on a cellular connection, from someone in a hurry. That describes a large share of the people looking for plumbers, HVAC companies, locksmiths and urgent care.
Core Web Vitals in one minute
Google measures page experience with three Core Web Vitals, based on data from real Chrome users:
- LCP (Largest Contentful Paint): how long until the main content, usually the hero image or headline, appears. Google’s “good” threshold is 2.5 seconds or less.
- INP (Interaction to Next Paint): how quickly the page reacts when someone taps a button or opens a menu. Good is 200 milliseconds or less.
- CLS (Cumulative Layout Shift): how much things jump around while loading. Good is 0.1 or less.
Page experience is one ranking consideration among many, and relevance still comes first. But the thresholds are a useful definition of “fast enough,” and they line up with what matters to a caller: see the number, tap it, and not have it jump away right before the tap.
Where service business sites lose time
After auditing a lot of WordPress sites for local businesses, I see the same culprits over and over:
- Oversized hero images. A photo straight from a phone or a stock site, several megabytes, scaled down by the browser.
- Sliders and background videos on the first screen.
- Too many plugins each loading their own scripts and styles on every page, even where they’re unused.
- Third-party widgets: chat, review carousels, booking embeds, heatmaps and several tracking pixels all fighting for the first second.
- Cheap shared hosting that takes a long time just to start sending the page.
- Web fonts loaded from multiple sources in many weights.
- Heavy page builder layouts with deeply nested sections that produce a lot of markup.
How to measure without fooling yourself
Testing your site on your office Wi-Fi with a fast laptop tells you almost nothing about a customer on a phone in a parking lot. Better ways to look:
- Google Search Console, Core Web Vitals report. Shows real-user data grouped by page type, if your site has enough traffic.
- PageSpeed Insights. The top section shows field data from real users when it’s available; the lab score below is a simulation useful for diagnosing problems.
- Your own phone on cellular. Turn off Wi-Fi, clear the cache and load your homepage and a service page. Count how long until you could tap the phone number.
Don’t chase a perfect 100 lab score. I’ve seen owners spend money moving from 92 to 99 while the contact form was broken. Aim to pass Core Web Vitals and to have the call button usable quickly on a mid-range phone.
Fixes in order of payoff
| Fix | Effort | Typical impact |
|---|---|---|
| Resize and compress images, use WebP or AVIF | Low | Often the biggest single LCP improvement |
| Remove sliders and autoplay video above the fold | Low | Faster LCP, less layout shift |
| Set image dimensions and reserve space for embeds | Low | Fixes most CLS problems |
| Audit plugins and third-party scripts, delay non-essential ones | Medium | Better INP and LCP |
| Page caching and a CDN | Medium | Faster server response everywhere |
| Better hosting | Medium | Helps when the server is the bottleneck |
| Rebuild bloated templates | High | Worth it when the theme itself is the problem |
Start at the top. Many sites pass Core Web Vitals after the first three rows alone.
When speed work is worth paying for
If your site already loads quickly on a phone and passes Core Web Vitals, more speed work has diminishing returns, and your money is better spent on content, reviews or conversion. Speed work pays off when real-user data shows failures, when the site feels sluggish on your own phone, or when you’re paying for ads that send clicks to slow pages.
Sometimes a few days of cleanup is enough. Sometimes the theme and plugin stack are so heavy that a rebuild is cheaper in the long run. That’s a judgment call I make often in WordPress development and website redesign projects. Either way, re-test after every major change, and keep an eye on it after plugin updates or new marketing scripts get added, because speed tends to erode slowly over time.
If you want to know which camp your site falls into, send me the URL and I’ll tell you where the time is going.


