How fast should a business website load?

Aim for the main content of each page to appear within 2.5 seconds on a phone, for the page to react to a tap within 200 milliseconds, and for nothing to shift around while it loads. Those three numbers are the "good" thresholds for Google's Core Web Vitals, and they are the most practical speed target a business can set because Google measures them from real visits.

A full page can keep loading in the background after that. What matters to a visitor is how soon they can see your headline, your phone number and your booking button, and whether tapping them works right away.

Core Web Vitals are three measurements Google uses to describe loading speed, responsiveness and visual stability. Google's web.dev guidance says a page passes when it meets all three targets at the 75th percentile of page loads, measured separately for mobile and desktop. In practice that means three out of four real visits need to be at or better than the target.

The 75th percentile point is important for a service business. Your average visitor on office wifi may see a fast page while a customer on a weak phone signal in a parking lot sees a slow one. The target is set so the slower visits count.

Yes. Portent, a digital marketing agency, analyzed just over 100 million page views across 20 sites (14 B2B lead generation sites and 6 ecommerce sites) and published the results in 2022. For the B2B lead sites, pages that loaded in 1 second had an average conversion rate of almost 40%, falling to 34% at 2 seconds and 29% at 3 seconds. Portent reported that a site loading in 1 second converted about 3 times better than one loading in 5 seconds.

The ecommerce sites showed the same pattern: the highest conversion rates were between 1 and 2 seconds, averaging 3.05% at 1 second and 0.67% at 4 seconds. Twenty sites is a small sample and these were not all service businesses, so treat the exact figures as directional. The direction is consistent with Google's own research. Google and SOASTA reported in 2017 that as mobile page load time went from 1 second to 7 seconds, the probability of a visitor bouncing increased 113%.

For a service business the cost is easy to picture. A slow page loses the visitor before they see the phone number, and that lost call never shows up in your analytics as a lost lead.

Fewer than half on mobile. The HTTP Archive 2025 Web Almanac, based on July 2025 Chrome user data across millions of websites, found 48% of mobile websites and 56% of desktop websites had good Core Web Vitals, up from 44% and 55% in 2024.

Loading speed is the most common failure. The same report found 62% of websites had a good LCP on phones, 25% needed improvement and 13% were poor. On desktop, 74% had a good LCP. If your competitors are in that slower half, a fast site is a practical way to stand out to people comparing options on their phones.

It plays a part, but it does not outrank good content. Google's Search Central documentation says it highly recommends site owners achieve good Core Web Vitals for success with Search, and that this, along with other page experience aspects, aligns with what its core ranking systems seek to reward. It does not describe speed as a factor that lifts a thin page above a more useful one.

The sensible reading: fix speed because it helps visitors become customers, and expect the search benefit to come mainly when your pages are already relevant and helpful.

Start with real visitor data, then use lab tests to find the cause.

• PageSpeed Insights: enter a page address and read the field data section first. It shows your real users' LCP, INP and CLS when Chrome has enough data for the page or site.
• Search Console Core Web Vitals report: groups your pages into good, needs improvement and poor for mobile and desktop, so you can see which templates (service pages, location pages, blog posts) are the problem.
• Test your top pages, not just the homepage: the service pages and landing pages your ads and Google Business Profile send people to.
• Check on a phone over cellular, not only on office wifi. The mobile number is the one most of your visitors experience.

On most service business sites the same few causes account for most of the delay, and they can be fixed without a full rebuild.

• An oversized hero image or video at the top of the page. This is often the LCP element itself, so compressing it, sizing it correctly and serving a modern format gives the biggest single gain.
• Slow hosting or server response. If the server takes over 1.8 seconds to start sending the page, the Web Almanac classes that response time as poor, and everything else waits on it.
• Third-party scripts: chat widgets, review carousels, booking embeds, multiple tracking tags and pop-ups. Each adds work for the phone, and they often cause slow taps (INP).
• Page builder themes that load every feature on every page. Heavy themes ship code your page never uses.
• Images and ads without set dimensions, which push content down as they load and hurt CLS.
• Web fonts loaded from several sources. Two font families from one source is usually enough.

Set a written standard and check it whenever the site changes. A practical version for most service businesses: every service, location and landing page passes Core Web Vitals on mobile in the Search Console report, the largest content on key pages appears in under 2.5 seconds on a phone, and no new script or widget goes live without a speed test before and after.

Hold vendors to the same standard. A new chat tool, booking embed or tracking tag that adds a second to every page load may cost more in lost calls than it brings in.