A home-services site went from a 9.7-second load to 0.13 seconds
Same site, same traffic — but the booking form finally loads before the visitor gives up and calls the next company. Here's exactly what was dragging it down and how we fixed it.
Get a Marketing PlanLargest Contentful Paint
A home-services homepage took 9.7 seconds to load. Visitors bounced back to Google before the booking form ever appeared — the traffic was there, the calls quietly went elsewhere.
Added server-side object caching, tracked down and killed a self-referencing request the theme fired on every page, and converted 32 uncompressed images to WebP.
Load time collapsed to 0.13 seconds. The booking form now paints before a visitor can second-guess the click — the same visitors reach it instead of the back button.
The problem: a page nobody waited for
A home-services client came to us with a site that looked fine and performed like a boat anchor. The homepage took 9.7 seconds to render. That is an eternity for someone who needs a service company now — phone in hand, deciding who to call. Most of them never made it to the booking form; they bounced long before the page settled.
Slow sites don't fail loudly. There is no error message. The calls just quietly go somewhere else, and the owner assumes the marketing “isn't working.” The traffic was there. The page just wasn't showing up fast enough to catch it.
What we did
We didn't rebuild the site from scratch. We diagnosed what was actually costing the seconds and fixed each lever directly.
Added object caching
The server was rebuilding the same content on every single visit. We added object caching so it serves ready-made results instead of doing the same work over and over — the biggest single jump in render time.
Killed a duplicate request the theme was making
The theme was firing a self-referencing request on every page load — the site was, in effect, waiting on itself. Once we tracked it down and cut it, a whole layer of hidden delay disappeared.
Converted 32 images to WebP
Home-services sites live on photos — jobs, crews, finished work. Thirty-two of them were loading at full uncompressed weight. We converted all 32 to WebP, cutting the page's payload without touching how the work looks on screen.
Why speed books more calls. Every second of load time bleeds off visitors who are ready to act. Service is bought under pressure — a dead AC in July, a furnace out on the coldest night, three other companies one tap away. When the page loads instantly, the same visitors reach the booking form instead of the back button. Faster site, same traffic, more booked calls.
The result
Load time dropped from 9.7 seconds to 0.13 seconds — the site now paints faster than a visitor can second-guess the click. Beyond the raw number, a fast, clean site is one Google can crawl and trust, which gives the SEO work a stronger foundation to compound on.
This is why we treat performance as the floor everything else stands on. When we build an HVAC website from the ground up, speed like this isn't a rescue project — it's the starting point.
Questions HVAC owners ask us
Why does a slow website lose service calls?
Visitors bounce before your booking form ever loads. When someone needs a service company, they are often on a phone, in a hurry, with three competitors one tap away. If the page stalls for nine seconds, most of them are already calling the next result. Speed is not a vanity score — it is the difference between a booked call and a lost one.
Do I need a whole new website to make it faster?
Not always. On this home-services site we did not rebuild from scratch — we fixed what was dragging: added object caching, killed a duplicate request the theme was firing on every page, and converted 32 images to WebP. Sometimes the fastest win is repair, not a rebuild. When the foundation is too far gone, a new website is the better call.
Does site speed actually affect Google rankings?
Yes — page experience and Core Web Vitals are ranking inputs, and a fast site gets crawled more thoroughly. But the bigger payoff is conversion: the same traffic books more calls when the page loads instantly. Speed and SEO compound on each other.
What was actually slowing the site down?
Three things stacked up: no object caching, so the server rebuilt the same content on every visit; a self-referencing request the theme made that doubled work behind the scenes; and 32 uncompressed images loading at full weight. Fix all three and a 9.7-second load collapses to 0.13.
Get a marketing plan built for your HVAC company
Tell us your service area and the calls you want more of. We’ll come back with a plan — no “guaranteed #1” nonsense, just what we’d actually do.
Get a Marketing Plan