← Back to Blog

Websites · July 7, 2026

How fast should your website load, and how to check

The number most owners never check

Ask a local business owner how fast their website loads and you'll usually get a shrug. It loads fine on their phone, so it must be fine for everyone. The trouble is they're testing it on a device that already has the site cached, on their home wifi, without paying attention to the two seconds before it appears. Their customers aren't doing any of that.

So let's put a real number on it and give you a way to check yours today.

The target: under 2.5 seconds

If you want one number to aim for, make it this: your main content should be visible in about 2.5 seconds or less on a normal phone connection. That's the threshold Google uses for what it calls Largest Contentful Paint, the moment the biggest thing on the screen, usually your header image or headline, actually shows up.

Between 2.5 and 4 seconds, you're in the "needs work" zone. Past 4 seconds, you're losing people, and you're losing them before they've read a single word about what you do.

That isn't a made-up standard. It's roughly the point where visitors start giving up. People are far less patient online than they think they are, and the drop-off gets steep fast.

Bar chart showing how a visitor's likelihood of leaving a website rises sharply as load time increases from one to ten seconds

The drop-off isn't gentle. By the time a page takes five seconds, a visitor is roughly twice as likely to give up as they'd be at one second.

For a local business, that bounce is expensive in a specific way. Someone searching "emergency plumber near me" at 9 p.m. isn't going to wait around. They tap your link, it hangs, they hit back, and they tap the next one. You paid to be in that search result, or you earned it, and the slow load handed the call to a competitor. We dug into that whole chain in why a slow website is costing you customers.

Google is timing you too

Speed isn't only about the visitor who's already on your page. It's also one of the things Google weighs when it decides who ranks.

Google measures a set of speed and stability signals it calls Core Web Vitals, and load time is the headline one. When two local businesses are otherwise close, the faster site has an edge. A slow site fights that ranking gravity every day, which means you're paying for it twice: once in the visitors who leave, and again in the visitors who never find you because you ranked a few spots lower.

None of this means you need a perfect score. It means a genuinely slow site is a leak in two places at once, and both drain the same bucket of leads.

How to check your own site in two minutes

You don't have to guess, and you don't need a developer to find out. Two free tools tell you almost everything.

Start with Google's PageSpeed Insights. Go to pagespeed.web.dev, paste in your website address, and hit analyze. Do it on the mobile tab, not desktop, because most of your customers are on a phone and mobile is where sites tend to be slowest. You'll get a score out of 100 and, more usefully, your actual load-time numbers. Anything under a green LCP is where you want to be. If you're in the orange or red, you've found your problem.

The second check is simpler and honest: open your site on your phone using cellular data, not wifi, after clearing the tab or opening it in a private window so nothing's cached. Count the seconds until you can actually read your headline. That's the experience a first-time customer gets, and it's often a rude awakening.

Run both. The tool gives you the technical read; the private-window test gives you the gut check.

What's usually slowing you down

When we audit a local site that's dragging, the cause is almost always one of a few ordinary things, not some deep technical mystery.

Oversized images are the number one culprit. A photographer or a well-meaning helper uploads full-resolution photos straight off a camera, and now every visitor's phone is downloading a 6-megabyte image to display it two inches wide. Compressing and properly sizing images alone fixes a huge share of slow sites.

Cheap, overloaded hosting is another. If your site sits on a bargain shared server with a thousand other sites, it responds slowly no matter how clean everything else is. Then there's plugin and tracking bloat, all those little add-ons and third-party scripts that each cost a fraction of a second until they add up to a wall. And a lot of older sites were simply never built with mobile speed in mind, so they're hauling around code and layout choices that made sense a decade ago.

The good news is that none of these are exotic. They're fixable, usually without a full rebuild.

When it's worth doing something about it

Here's a reasonable rule. If your mobile PageSpeed score is solidly green and your headline shows up in a couple of seconds on cellular, leave it alone and spend your energy elsewhere. Speed is a means to an end, not a trophy.

But if you're in the orange or red, or your own private-window test drags past three or four seconds, it's worth fixing, because it's quietly costing you calls and rankings right now. That might be as simple as compressing your images and moving to better hosting, or it might be a sign the site is due for a rebuild on a modern, conversion-focused foundation. Speed usually travels with a pile of other issues, so a slow site is often the symptom that gets you to look at the rest.

Not sure where your site stands? Send us your address and we'll run the check for you, free, and tell you straight whether it's a quick fix or something bigger. Either way, you'll finally know the number instead of shrugging at it. If it turns out the whole thing needs work, that's what we build websites for.