Why Your Small Business Website Is Slow (and What It's Costing You)

Of all the things that quietly cost small businesses customers, a slow website might be the most common, and it’s certainly the least visible to the owner. You built the site on your office wifi, you look at it on your office wifi, and on your office wifi it seems fine. I said speed is a conversion feature in my guide to conversion-optimized websites and gave it a few paragraphs there. It deserves the longer version.

Your customers are somewhere else entirely.

What slow feels like when you’re the visitor

Picture the person you actually want to reach. She’s standing on a Queen West sidewalk with a dead furnace at home, two bars of signal, and a phone that’s a couple of years old. She searches, taps your listing, and gets a white screen. One second passes. Two. A logo appears, then the page jumps around as pictures load in, and the button she was about to press moves just as her thumb comes down.

Nobody makes a conscious decision at that point. There’s no moment where she thinks “this business must be disorganized.” She just drifts back to the results and taps the next listing, the same way you and I have done a thousand times. The whole event takes maybe six seconds and leaves no trace. You’ll never know she visited, because most basic analytics won’t even register someone who bailed before the page finished loading.

That’s the maddening part of a speed problem. A rude employee gets complained about. A slow website just produces silence, month after month, while you wonder why the phone is quiet.

Google has studied this for years, and their published research keeps pointing the same direction: as mobile load time climbs, the share of people who give up climbs with it, and it gets steep fast. I won’t quote you an exact percentage because the figures vary by study and by year, and I’d rather be vague and truthful than precise and made up. The direction is what matters. Every extra second of waiting costs you a slice of the people who had already chosen to visit you. Those are the cheapest leads you’ll ever get, and a slow page throws a portion of them away before you’ve said a word.

Test it properly, and for free

You don’t need me or anyone else to tell you whether your site is slow. Google gives away the same tool the pros use. It’s called PageSpeed Insights and it lives at pagespeed.web.dev. Type in your website address, wait about thirty seconds, and it hands you a report.

The report can look intimidating. There are lab scores, field data, waterfall charts, and a pile of acronyms like LCP and CLS. Here’s what a non-developer should actually take from it.

Look at the big score near the top, and make sure you’re on the Mobile tab, because it shows mobile first for a reason. The score runs from 0 to 100. Green is 90 and up, orange is 50 to 89, and red is below 50. If your mobile score is deep in the red, you don’t need to understand a single acronym to know you have a problem worth fixing. A lot of small business sites I test land in the 20s and 30s on mobile, and their owners are always surprised, because the site felt fine on the desktop in the back office.

If you want one metric beyond the score, glance at “Largest Contentful Paint.” Ignore the jargon; it’s roughly “how long until the main thing on the page shows up.” Under about two and a half seconds is the target Google suggests. If yours says six or eight seconds, that’s the white screen your customer stared at.

Then do the test that matters more than any number. Take your own phone, turn wifi off so you’re on cellular data, and load your site somewhere ordinary. The parking lot outside your shop. A grocery store aisle. The streetcar. Count in your head while it loads. Does it feel quick? Would you wait for it if it belonged to a stranger? Your gut answer to that question, on cellular data, on your real phone, is worth more than any lab score, because it’s exactly the experience your customers get.

One caution: run the test a couple of times and on a few pages, your homepage plus your busiest service page at minimum. Scores wiggle a bit between runs. You’re looking for the pattern.

What the mobile score means versus the desktop score

Almost every site scores better on desktop, sometimes dramatically better. I’ve seen the same website score 92 on desktop and 31 on mobile in the same afternoon. Owners see the 92, feel relieved, and stop reading.

The mobile number is the one that counts, for two reasons. First, for most local businesses the majority of visitors arrive on phones, so the mobile experience simply is the experience. Second, the mobile test deliberately simulates a mid-range phone on a mediocre connection, which is far closer to real life than a plugged-in desktop on fibre. Powerful hardware and a fast connection will hide bloat that an ordinary phone forces out into the open.

So when someone tells you “your site scores fine,” ask which tab they were looking at. The desktop score is a bit like testing a car’s fuel economy going downhill. Pleasant, and beside the point.

The usual culprits, in plain English

Here’s the reassuring bit. After auditing a lot of small business sites, I can tell you the causes of slowness are rarely exotic. The same handful of problems show up over and over, and none of them requires a computer science degree to understand.

Giant images straight off a phone camera. This is culprit number one by a wide margin. A modern phone takes photos around 4 to 6 MB each. That resolution is wonderful for printing a poster and absurd for a website, where the image might display at the width of a chocolate bar. Upload ten of those to your gallery page and a visitor’s phone has to pull down more data than a whole album of music before it can show your storefront. Most site platforms don’t stop you or even warn you. The photo looks great in the editor, so up it goes.

Page-builder themes stacking plugins. A lot of DIY sites get built on flexible drag-and-drop themes, and flexibility has a cost. The theme ships with code for every feature anyone might ever want, whether your site uses it or not. Then plugins get added over the years: a slider here, a booking widget there, a gallery, a form builder, a pop-up tool, an SEO helper, something for social feeds. Each one loads its own scripts and styles on every single page. Individually they’re small. Together they’re a crowd of strangers your visitor’s phone has to greet before it’s allowed to show your phone number. I’ve opened sites carrying more than two dozen active plugins where the owner could tell me what maybe eight of them did.

Cheap shared hosting. The $4-a-month hosting plan puts your website on a server shared with hundreds or thousands of other websites, and everything on the server is fighting over the same resources. When your site is built the traditional way, every visit means the server has to assemble the page on demand, and an overworked shared server assembles it slowly. That delay happens before a single image starts downloading, which is why some sites feel sluggish even though the pages themselves aren’t heavy.

Too many fonts, and scripts doing who knows what. Every decorative font is a file the phone must download before your text displays properly, and some sites load five or six font families plus multiple weights of each. Scripts are worse. Chat bubbles, heat-map trackers, old analytics snippets from a marketing agency you stopped using in 2023, embedded social feeds, all of it runs on the visitor’s phone at their expense. Sites accumulate this stuff like a junk drawer, because adding a script takes a minute and nobody ever goes back to remove one.

Autoplaying video. A background video on the homepage looks impressive in a design mockup. On a phone in a parking lot it’s a multi-megabyte download the visitor never asked for, shoving aside the phone number and hours they actually came for. If video matters to your business, and for some it truly does, let people press play.

Image compression, explained over coffee

Since images are the biggest offender, let’s take one extra minute on them, because the fix is easier than most owners expect.

That 4 MB photo from your phone and a properly prepared 150 KB version of it will look identical on your website. Genuinely identical, side by side, to your eyes and your customers’ eyes. The difference is that one is roughly twenty-five times more data to download. Compression works by resizing the image to the dimensions it will actually be displayed at, then squeezing the file with clever math that throws away detail no screen was going to show anyway.

You don’t need Photoshop for this. Free tools like Squoosh (squoosh.app, made by Google) or TinyPNG run in your browser: drag the photo in, drag the smaller file out, upload that one instead. The whole ritual adds under a minute per image.

While you’re at it, you may see the term WebP. That’s just a newer image format that produces noticeably smaller files than the old JPEG at the same visual quality, and every modern browser handles it fine.

The habit that matters: compress before you upload, every time, forever. It’s the single highest-value five minutes of website maintenance a non-technical owner can do.

What a “static site” is, and why I build them

When I say I build static websites, here’s the plain meaning of that.

A traditional site, say a typical WordPress install, keeps your content in a database. When a visitor shows up, the server assembles their page on the spot: fetch the content, run it through the theme, execute the plugins, then send out the finished page. All of that happens for every visit, and every step is a chance to be slow, especially on the cheap shared hosting most small sites sit on.

A static site does the assembling once, ahead of time. The pages are prebuilt into plain finished files, and when a visitor arrives, the server just hands the file over. There’s nothing to compute and no database to consult. The closest kitchen analogy I’ve got: one approach cooks your meal from scratch after you order, the other has it plated and waiting because the menu was known in advance. For a small business site whose content changes occasionally rather than by the minute, prebuilt is the obvious model.

Static files are also cheap to serve from data centres all over the world, so the page comes from a computer physically near your visitor instead of one province away. That’s a big part of why the sites I build tend to score in the green on mobile without any heroics. The speed comes from the architecture itself, so it doesn’t decay as the site ages, and there’s no stack of plugins waiting to slow things down two years from now.

Quick wins you can do yourself this week

You don’t have to rebuild anything to make progress. If your mobile score came back ugly, start here.

1. Compress your images. Find the heaviest pages, usually the homepage and any gallery, and run every photo through Squoosh or TinyPNG, then re-upload. On image-heavy sites this alone can move a mobile score by a surprising amount.
2. Uninstall plugins you don’t use. Walk the plugin list and ask of each one, “what does this do for a customer?” If you can’t answer, deactivate it and watch the site for a week. Deactivated and nothing broke usually means delete. Fewer plugins also means fewer security holes, which is a nice side effect.
3. Cut your fonts down. Pick one font for headings and one for body text and remove the rest from your theme settings. Your site will look more consistent as well as loading faster.
4. Remove autoplay. Swap any background or autoplaying video for a nice still photo with a play button if the video earns its keep, or drop it if it doesn’t.
5. Clear out zombie scripts. If an old marketing tool, chat widget, or tracker is still pasted into your site and nobody’s looked at its dashboard in a year, take it out.

Then re-run PageSpeed Insights and compare. Watching your own mobile score climb from the red into the orange is weirdly satisfying, and the improvement is real for every visitor from that day forward.

When it’s the platform, and a rebuild is the fix

Sometimes the ceiling really is the platform itself. I want to be fair here: plenty of platform-built sites can reach acceptable speed with disciplined images and a short plugin list.

But there’s a point where you’re optimizing a traffic jam. If your theme loads half a megabyte of code before your content appears, if the builder itself injects scripts you can’t remove, if your hosting takes two full seconds to respond before anything else even starts, then no amount of image compression gets you to fast. You can tell you’re in this territory when you’ve properly worked through the quick wins above and the mobile score barely moved out of the red. The stuff you can control was never the main problem.

At that stage the question stops being “how do I speed this up?” and becomes “what’s my time worth, and what are the lost enquiries worth?” A rebuild on a fast foundation solves the problem structurally instead of managing it forever. For a five-page local business site, that’s neither a big project nor a big cost, whatever memories you have of what the original site cost in 2019.

A quick word on hypotheticals, and this is an invented example, but a realistic one: imagine an Etobicoke plumber whose site takes eight seconds to load on cellular. If even a modest share of mobile visitors give up at that point, and Google’s research says the share grows as the seconds pile up, then a couple of lost jobs a month would dwarf the cost of fixing the site. That’s the math I’d encourage you to sketch for your own business, with your own job values, rather than trusting any percentage a stranger on the internet quotes at you.

Run the test today

Ten minutes, and you’ll know where you stand. Put your site through pagespeed.web.dev, note the mobile score, then load your site on your own phone with wifi off and count the seconds. If it comes back green and feels quick, wonderful, go worry about something else.

If it comes back red, you now know something most of your competitors don’t know about their own sites, and everything in this post is yours to act on.

And if you’d rather hand the whole thing to someone who does this every week, that’s my job. I build fast, static, conversion-focused websites for small businesses. The standard build is $1,000, new clients currently pay $500, and your first year of hosting and support is included, then $250 a year after that if you’d like me to keep looking after it. The details live at hughmcnamara.com/new-clients. Send me your web address and I’ll run the speed test myself, then tell you plainly whether your site needs a tune-up or a fresh start.