How fast should a small business site load?

Somebody in Heber City searches "nail salon near me" on their phone, taps your site, and stares at a white screen. Three seconds in, most people hit back and tap the next result. You never know they existed, and neither does your booking calendar.

So how fast is fast enough? My plain answer: your site should show something useful in under 3 seconds on a phone, on cell data, not on your shop wifi. Under 2 is better. Under 1 is what I aim for.

The 3-second phone test

Forget scores and dashboards for a minute. Do this instead:

1. Take out your phone.
2. Turn off wifi so you are on cell data, like a customer driving around town.
3. Open a private or incognito tab so nothing is cached.
4. Type your site's address and count "one Mississippi, two Mississippi."

If you can read your business name, what you do, and how to contact you before three Mississippi, you pass. If you are still watching a spinner, you have a problem worth fixing.

Why 3 seconds? Google has published research for years showing that a big share of mobile visitors leave when a page takes longer than about 3 seconds. You do not need the exact percentage. You already know it from your own behavior. When was the last time you waited 8 seconds for a site to load?

What actually slows small sites down

I audit local sites around Heber and Park City, and it is almost never something exotic. It is the same two or three things every time.

Huge photos. This is the number one cause by a wide margin. A photo straight off a modern phone is often 4 to 8 MB. Put six of those on your homepage and you are asking visitors to download more data than a music album before they can see your prices. A photo on a website should usually be under 200 KB. It can still look sharp. When I built the site for Susy Nails, a salon here in Heber City, every one of her real nail photos got compressed before it went up. The page stays light and loads fast on a phone in a parking lot.

Builder bloat. Site builders like Wix, Squarespace, and heavy WordPress themes load a lot of code you never asked for: sliders you do not use, fonts you do not need, popups, chat widgets, tracking scripts. Each one is another thing a phone has to download and run before your page shows up. Builders are fine tools, and I am not telling you to leave one you like. But a builder page often ships 3 to 5 MB where a lean page needs well under 1 MB.

Too many add-ons. A booking widget, a reviews widget, an Instagram feed, a Facebook pixel, two custom fonts, and a video header. Each one seemed small when it got added. Together they are why the page crawls. Landscapers and groomers are the worst cases I see, usually because five different tools each promised "just paste this one line of code."

Notice what is not on the list: your hosting. For a small local site, the fix is almost always about what the page is loading, not where it lives. You almost never need to pay for a bigger server.

How to check yours for free

You do not have to guess, and you do not have to pay anyone.

• PageSpeed Insights. Google's free tool. Search the name, paste your address, and look at the mobile result first, because that is how your customers arrive. Skip the jargon and look at two things: the performance score and the "Largest Contentful Paint" time. If LCP is over 2.5 seconds on mobile, start with your images.
• The phone test above. Do it once a month. Tools measure, but your thumb is the customer.
• Ask a friend across town to open your site on their phone and time it. A different carrier or an older phone can tell a different story.

One honest caveat. A fast site will not fix a bad offer, missing hours, or a phone number nobody answers, and a perfect speed score does not bring in customers by itself. Speed just removes a reason for people to leave before they see what you charge and where you are. That is all it does, and it is still worth caring about.

If your numbers come back rough, the fix order is boring and effective: compress the photos first, remove the widgets you do not actually use second, and only then worry about anything fancier.

And if you would rather not dig through reports yourself, I do a free 24-hour audit, three real findings, yours to keep either way. Drop your address at /audit and I will run these same checks on your site and tell you in plain language what is slowing it down. If it is already fast, I will tell you that too.