HVAC website speed optimisation
A homeowner with no heat, on mobile data, in a cold house. Every second your site takes to load is a share of those people calling somebody else.
What makes contractor websites slow
It is almost always the same handful of things, and none of them require a rebuild to fix.
Enormous images. A three-megabyte hero photograph of a technician, uploaded straight from a phone camera. Compressing and converting images is usually the single biggest available gain.
Heavy page builders. Some builders load hundreds of kilobytes of CSS and JavaScript on every page whether the page uses it or not.
Plugin accumulation. Thirty-eight plugins, several doing the same job, most loading their assets site-wide.
Cheap shared hosting. A slow server response time caps how fast the site can possibly be, no matter what else is optimised.
Third-party scripts. Chat widgets, review widgets, tracking pixels and booking embeds, each adding requests before the page becomes usable.
What is included
Everything below is included. If something is not on this list, we will tell you before we invoice for it.
- Core Web Vitals diagnosis on field data
- Image compression and WebP or AVIF conversion
- Lazy loading below the fold
- Render-blocking CSS and JavaScript removal
- Critical CSS delivery
- Plugin audit and consolidation
- Caching and CDN configuration
- Font loading optimisation
- Third-party script deferral
- Server response time review
- Layout shift elimination
- Before-and-after measurement on real devices
How we do it
Measured on mobile throughout, because desktop numbers flatter almost every site.
Measure properly
Field data from real users, not just a lab score. Lab tools miss the conditions your actual customers are on.
Images and assets
Usually the largest single gain, and the lowest risk change on the list.
Code and scripts
Render-blocking resources, unused CSS, deferred third-party scripts.
Hosting and caching
Server response, caching layers, CDN. Worth reviewing if the site serves several countries.
Re-measure and hold
Verified improvement, plus monitoring so a plugin update does not undo it.
Questions about Site speed
What speed should we be aiming for?
Largest contentful paint under 2.5 seconds and cumulative layout shift under 0.1, measured on mobile field data. Beyond ranking, this is a conversion issue — slow sites lose calls.
Is speed actually a ranking factor?
Yes, though a modest one compared with relevance and links. The stronger argument is commercial: a homeowner in a hurry will not wait for a slow page when three competitors are one tap away.
Will we have to change hosting?
Sometimes. If server response time is consistently poor, no amount of front-end work fixes it. We will tell you if that is your bottleneck rather than optimising around it.
Can we keep our page builder?
Often yes, with careful configuration. Some builders can be made acceptably fast; a few cannot. We measure rather than assume.