How fast should a home-service website load?
Short answer
Fast enough that a person on a phone with an ordinary connection sees the page and can use it without waiting. No single number suits every site. Google publishes its own current thresholds for three measurements called the Core Web Vitals, taken from real visitors' phones, and those are the figures to check your site against.
A home-service website should load fast enough that a person on a phone with an ordinary connection sees the page and can use it without waiting. I’m not going to give you a number of seconds. Any figure printed here could go out of date, and a single stopwatch time hides most of what a customer feels: when the content appears, whether the page reacts to a tap, and whether it stays still.
What Google measures
Each of those has a name and a definition in Google’s Core Web Vitals.
| Measurement | What it measures | What the customer notices when it’s poor |
|---|---|---|
| Largest Contentful Paint (LCP) | How long it takes for the main content of the page to become visible | A blank or half-drawn screen |
| Interaction to Next Paint (INP) | How quickly the page reacts after a tap or click | Tapping the menu or the call button and nothing happening |
| Cumulative Layout Shift (CLS) | How much the layout moves while the page is loading | A button jumping away just as a thumb reaches it |
Google publishes a threshold for a good result on each one, and it has changed the set of measurements before. Check Google’s current documentation, or the Core Web Vitals report in Google Search Console, and don’t rely on a figure quoted in an article, this one included.
Measure on real phones, not on the office computer
A lab test loads the page once on a simulated device and produces a score. Field data is collected from people who visited the site in the Chrome browser, on their own phones and their own connections, and it’s the kind to go by. Google’s PageSpeed Insights shows both when a site has enough visitors, and the Search Console report is built on field data.
The gap between the two can be wide. A site that feels instant on office Wi-Fi in Kearny Mesa can be slow for a homeowner in Ramona or Alpine standing in a garage with a weak signal and a four-year-old phone. That homeowner is the one deciding whether to call. For a small site with too few visitors to produce field data, the next best thing is a lab test set to imitate a mid-range phone on a slower mobile connection.
What usually slows a home-service site down
The list is short, and nothing on it’s unusual.
- Photos uploaded straight from a camera or phone, many times larger than the screen that shows them. The big picture of the crew and the trucks at the top of the homepage is the usual suspect.
- A slideshow or background video above everything else on the page.
- Scripts loaded from other companies’ servers: chat widgets, review carousels, booking tools, call tracking and advertising tags.
- A heavy theme or page builder with a long list of plugins, loading code on every page whether that page uses it or not.
- Slow hosting, where the server takes a long time to send anything at all.
Removing one script can do more than a week of smaller adjustments, and a widely recommended setting sometimes changes nothing. Which of these matters on your site is something to measure, not assume, and measuring is where site speed and Core Web Vitals work begins.
When fast is fast enough
Once real visitors on phones get pages that pass Google’s current thresholds and feel immediate, further speed work has little left to give. I’d tell you at that point to spend the money elsewhere. A perfect lab score isn’t the goal.
Speed is also only part of the experience on a phone. A page can load quickly and still fail on mobile usability, with a phone number that can’t be tapped or a quote form that is painful on a small screen. Whether site speed affects Google rankings is a separate question.