Why Your Website Should Load Before They Change Their Mind

Someone is standing on the subway platform at Bloor-Yonge with one bar of signal. They searched for your kind of business, tapped your link, and now they are watching a white screen. The train is coming. They hit back and tap the next result.

That is the whole story of website speed for a local business. Not benchmarks, not scores out of a hundred. Just a person with a thumb hovering over the back button, deciding whether you are worth the wait.

Most of the people finding you for the first time are on a phone, on a cellular connection, doing something else at the same time. Walking. Waiting. Sitting in a car that someone else is driving. They did not come to your site to admire it. They came to answer one question — are you open, what does it cost, can I book — and if the answer does not arrive quickly, they get it somewhere else.

Test your own site in the next two minutes

Do not take anyone's word for this, including ours. Do it yourself, right now.

Pick up your phone. Turn Wi-Fi off. Open a private or incognito browser window so you are not seeing a cached copy. Type your business name, tap your own website link, and count out loud. One Mississippi, two Mississippi.

If you get something readable by three, you are fine. By five, you are losing some people. Past eight seconds of blank screen or spinning wheel, you have a real problem that is costing you calls and orders every day.

Do it again somewhere with weak signal. A basement. A streetcar. The back of your own shop where the reception is bad. That is the condition most first-time visitors are in, and it is the condition nobody tests for, because the person who built the site tested it on office Wi-Fi with everything already loaded in their browser.

Then do one more thing: run your address through Google's PageSpeed Insights. It is free, it works in any browser, and you do not need to understand most of what it says. Look at the mobile tab. Look at the list of problems it flags at the top. You will usually see the same handful of items we are about to walk through, and you will be able to hand that list to whoever maintains your site.

Enormous photos are almost always the problem

Nine times out of ten, when a small business site crawls, it is pictures.

Here is how it happens. You take photos of your dining room, your salon chairs, your finished work. Modern phone cameras produce enormous files — a single photo can be four or five megabytes. You email them to your web person, or upload them yourself through whatever admin panel you were given. They go up exactly as they are. Nobody shrinks them.

Now your homepage has eight photos on it. Your visitor's phone has to download all eight before the page settles. On a good connection that is a couple of seconds. On a subway platform it is forever.

The fix is boring and completely effective. Every photo on a website should be resized to roughly the size it actually displays at and saved in a modern compressed format. A photo that fills a phone screen does not need to be the same file your camera produced. Done properly, the picture looks identical to a human eye and the file is a fraction of the size.

Good site builds do this automatically on upload. If yours does not, ask. This one change alone often takes a sluggish site and makes it feel instant.

The plugin pile

If your site runs on WordPress — and a lot of small business sites do — there is a decent chance it has accumulated plugins the way a junk drawer accumulates batteries.

A booking plugin. A gallery plugin. A popup for the newsletter. A chat widget nobody answers. A social media feed. A cookie banner. An analytics tag, plus a second analytics tag from the agency before last. Each one loads its own code on every page, whether that page uses it or not.

None of them is fatal on its own. Twenty of them together means the visitor's phone is downloading and running a small mountain of software just to show them your hours.

The audit is simple and you can do most of it yourself. Ask for a list of everything installed. Go down it and ask one question per item: what does this do for a customer? The newsletter popup that has collected eleven addresses in two years is not earning its keep. The chat widget you never open is actively hurting you — it slows the page and it makes people think they can reach you when they cannot. Cut anything you cannot justify in a sentence.

Hosting that falls asleep

The cheapest hosting plans save money by putting hundreds of websites on one machine and letting inactive ones go dormant. When a visitor arrives at a dormant site, the server has to wake up before it can send anything. That wake-up can take several seconds, and it happens to exactly the visitors you care most about — the first ones of the morning, the ones arriving from a search at an odd hour.

You can spot this pattern. If your site feels slow the first time you load it and quick on the second try, that is a server waking up, not photos.

The other hosting question is where the server physically is. If your customers are in Etobicoke and your site lives on a machine in Germany, every request takes a round trip across the Atlantic. It is not the biggest factor, but it is free to fix and there is no reason to pay that tax.

Decent hosting for a small business site is not expensive. It is the difference between a few dollars a month and a slightly less few dollars a month. If yours is the bargain-basement tier, the upgrade is one of the cheapest improvements available to you.

What to ask the person who built your site

You do not need to learn any of this in order to get it fixed. You need five questions and the patience to wait for straight answers.

• Are our images resized and compressed automatically when we upload them? If the answer is no, or vague, that is the first job.
• What is installed on the site right now, and what does each thing do for a customer? Ask for the actual list. Anything that cannot be explained plainly should go.
• What hosting plan are we on, and does the server go to sleep? You want a straight yes or no.
• Have you loaded our site on a phone, on cellular data, away from the office? The honest answer is often no.
• What is the slowest page on the site, and why? A good answer names a specific page and a specific cause. A bad answer is a general reassurance that everything is optimized.

If you get evasion on all five, you have learned something useful about your working relationship. We wrote more about that in how to choose a web agency in Toronto after a bad one.

Speed is a design decision, not a cleanup job

The fastest sites we build are not fast because someone came along afterward and squeezed them. They are fast because there was less on them to begin with.

A local business homepage needs to do a small number of things very well: say who you are, say where you are and when you are open, and give the visitor the one action they came for — call, order, book, get directions. Everything else is negotiable, and most of it should lose the negotiation.

The slideshow that rotates through five hero images is five images to download so the visitor can see one. The embedded map that loads a whole mapping application is slower than a link to directions. The video background is a lovely idea on a laptop and a hostile one on a phone with a data cap.

When you strip a page to what a customer actually needs, speed tends to arrive on its own. That is how we approach the sites we build — fewer moving parts, the important thing visible immediately, and the photos handled properly before they ever go up.

One last note. Speed also affects whether people find you at all, because search engines factor it in when they decide who to show on a phone. But that is the smaller reason. The bigger reason is the person on the platform with the train coming. Get the page in front of them before they change their mind, and the rest of your website has a chance to do its job.