How fast should a service business website load?

Website speed is easy to obsess over and easy to ignore, and both are mistakes. A service business site does not need a perfect score. It needs to load, become readable, and respond to a tap quickly enough that a person on a phone with one bar of signal can find the number and call. Google’s Core Web Vitals give that goal a definition, and the definition is more forgiving than most speed reports suggest.

What fast enough means

Google publishes thresholds for its three Core Web Vitals and evaluates them at the 75th percentile of real visits, meaning three out of four page loads should meet the target. The thresholds are a Largest Contentful Paint of 2.5 seconds or less, an Interaction to Next Paint of 200 milliseconds or less, and a Cumulative Layout Shift of 0.1 or less. Meet those on the pages that matter and the site is fast enough by Google’s definition.

Google also describes page experience, including these metrics, as one of many signals rather than a dominant ranking factor. Speed rarely moves a page from position twenty to position two. It does decide whether the visitor who arrives stays long enough to act, which is the outcome the business is paying for.

The three metrics, plainly

• Largest Contentful Paint measures how long the biggest visible element, usually a hero image or headline, takes to appear. It answers: how long until the page looks loaded?
• Interaction to Next Paint measures how quickly the page responds when someone taps, clicks, or types. It replaced the older First Input Delay metric and covers the whole visit, not just the first tap. It answers: does the page feel stuck?
• Cumulative Layout Shift measures how much the page jumps around while loading. It answers: did the button move as I tried to tap it?

Each maps to a real complaint. A slow paint makes visitors leave. A sluggish response makes them tap twice and submit a form twice. A layout shift makes them tap an ad instead of the phone number.

How to test without guessing

Use PageSpeed Insights first. It reports two kinds of data: field data from real Chrome visitors, when there is enough traffic, and lab data from a simulated load. Field data is the verdict; lab data is the diagnosis. A page can score poorly in the lab and pass in the field, or the reverse, and the field result is what Google evaluates.

Then check the Core Web Vitals report in Google Search Console, which groups pages by status and shows which templates fail. Finally, load the site yourself on a phone over cellular data, not office wifi, and try to call from the homepage and a service page. That test catches problems no tool reports, such as a cookie banner covering the phone number.

The fixes that usually matter

Most service business sites fail for a short list of reasons, and the fixes are not exotic:

• Images. Serve them at the size they are displayed, in a modern format such as WebP, with width and height attributes so the layout does not shift. Load the hero image early and everything below the fold lazily.
• Fonts. Self-host one or two font files, preload the one used above the fold, and let text show in a fallback font while it loads.
• Third-party scripts. Chat widgets, tag managers, embedded maps, tracking pixels, and review carousels are the usual cause of slow interaction. Remove the ones nobody uses and load the rest after the page is interactive.
• Hosting and caching. Use a host with a content delivery network and proper cache headers. A cheap shared server in another region adds a second before anything else happens.
• Page builders and plugins. Themes that ship every feature and plugins that each add a script are the reason many small business sites are slow. Fewer moving parts is faster.
• Reserved space. Give banners, embeds, and ads fixed dimensions so content does not jump when they arrive.

Force Digital builds sites as plain, fast pages with minimal scripts, which is why our web design work starts from performance rather than retrofitting it.

What not to chase

A score of 100 is not a business goal. Passing the three thresholds in field data on the pages customers use is. Do not stack optimization plugins on top of each other, do not strip useful content to shave a tenth of a second, and do not rebuild a site that passes because a lab report is orange. Fix what the field data and the phone test say is broken.

Speed is a conversion issue, not a badge

The reason to care about speed is the lead path. A homeowner with a flooded kitchen, a patient in pain, or a client with a court date is not going to wait for a slideshow. Once the page is fast, make sure the phone number is a tap-to-call link, the form asks only for what is needed, and the buttons are large enough to hit. Our guide to speed to lead covers what happens after the tap.

If you are choosing a vendor to fix speed, ask them to show field data before and after on a site they have worked on. Our guide on choosing a local SEO company lists the other questions worth asking.

Website speed checklist

• Key pages pass LCP, INP, and CLS thresholds in PageSpeed Insights field data.
• Search Console Core Web Vitals report shows no failing templates.
• Images sized, compressed, in modern formats, with dimensions set.
• One or two self-hosted fonts, preloaded, with fallback text visible.
• Unused third-party scripts removed; the rest deferred.
• Hosting with a CDN and cache headers.
• Banners and embeds have reserved space.
• Phone test on cellular: read, tap, and call from the homepage and a service page.

Fast enough is a clear, testable target. If the site passes and leads are still thin, speed is not the problem. Request an audit and we will look at the rest of the path.