Page speed is not a technical vanity metric. It changes how many people stay long enough to call, request a quote, or book. For a contractor generating steady organic leads, a two-second mobile improvement can be the difference between a visitor seeing the phone number and bouncing back to the Map Pack.
Start with Core Web Vitals
Use Google’s published Core Web Vitals guidance to interpret real field data. On service sites, common sources of delay include oversized images, render-blocking JavaScript, unnecessary third-party scripts, and hosting or caching configuration.
Fix the largest thing on the page
Start with the largest content on the page. Serve responsive image sizes, choose appropriate formats, and lazy-load images that are not needed for the first viewport. The result depends on the source asset, device, and page architecture, so compare before-and-after measurements instead of assuming a fixed gain.
Hosting and scripts matter too
Hosting and caching matter too. A slow origin or poorly configured cache can add latency for visitors. A CDN or edge strategy may reduce that delay, but the right approach depends on the application’s data, rendering needs, and origin performance.
The real cost of slow speed is invisible until you fix it. You do not see the customers who left before the page loaded. You do not see the calls that went to your faster competitor. Speed optimization is not about chasing a Lighthouse score. It is about removing friction between a customer who needs help right now and your phone number.
The baseline to aim for
A practical baseline for service-business mobile speed:
- LCP (Largest Contentful Paint): use Google’s “Good” threshold as a guide and inspect the largest element on real mobile pages.
- INP (Interaction to Next Paint): test the interactions customers actually use, such as calls, menus, and forms.
- CLS (Cumulative Layout Shift): reserve space for images, embeds, and dynamic components so the page does not jump under a user’s thumb.
A practical starting point is a hosting and architecture review: compress the hero image, reduce render-blocking scripts, self-host fonts when appropriate, and address the actual bottleneck. Some sites need a substantial rebuild; many improve through disciplined cleanup first.
Combine that with image and font discipline and you build an advantage that is hard to cross with ad budget. Competitors can pay for clicks, but they still have to serve the page when the customer lands.
Curious where your site falls? The free Lighthouse audit measures all three Core Web Vitals and breaks the result down in plain English. If mobile taps are the bigger issue, read Why Your Site Loses Calls on Mobile next.