Why page speed is your site's silent salesperson

Speed is the only part of your website's design that every single visitor experiences, including the ones who leave before seeing anything else. It's also the one nobody compliments. No customer has ever said your site felt fast — they just stayed.

What they do notice is slow. And they don't report it; they close the tab and try someone else, which is why a slow site looks exactly like a site nobody wanted to visit.

Why it costs money

Three mechanisms, and they compound.

Abandonment

Patience online is measured in a small number of seconds, and it falls off a cliff rather than declining gently. The people you lose this way are disproportionately new visitors — someone who already knows and likes you will wait; a stranger who found you in a search result absolutely will not.

Ranking

Search engines use page experience, including load speed, as a factor in ranking. It's not the biggest one, but it acts as a multiplier on everything else: a slow site is competing with a handicap on every query.

Perception

The subtlest and possibly the most damaging. A site that stutters, shifts under a thumb, or takes a moment to respond to a tap feels cheap — and people transfer that impression to the business. A slow checkout in particular feels untrustworthy, right at the moment you least want doubt.

Nobody abandons a site because it was slow. They abandon it because they lost interest — which is what slow feels like from the inside.

What actually gets measured

You'll see three metrics referenced constantly. In plain terms:

• How fast does the main thing appear? Usually your hero image or headline. This is the one visitors subjectively experience as “loading speed.”
• How fast does it respond when tapped? The delay between a tap and something happening. Long delays feel broken rather than slow, and prompt a second tap — which is how people accidentally order two of something.
• Does the page move about while loading? The infuriating one: content shifts as late-arriving elements push things around, and you tap the wrong thing. Usually caused by images without reserved space, or by third-party widgets inserting themselves after the fact.

All three are about the same underlying question: how much work is the visitor's device being asked to do before your page is usable?

What's handled underneath you

A meaningful share of speed work is infrastructure, and on a managed platform it isn't yours to do.

Pages are served from close to your visitor

Your site sits behind a global content network, so a visitor two countries away isn't waiting on a round trip to wherever your content is stored. Popular pages are served from the edge rather than being rebuilt for every request — which is why a site that suddenly gets busy doesn't get slower.

That caching is careful about who it applies to: anything personalised — a cart, a checkout, a signed-in view — always comes fresh, so nobody is ever served somebody else's page.

Images are optimised on upload

This is where most of the weight on a small-business site lives. When you upload an image it's converted to a modern compressed format and resized to sensible dimensions on the way in, and your pages then serve appropriately-sized versions per device — a phone downloads a phone-sized photograph rather than a desktop-sized one.

Practically, this means you cannot ruin your site by uploading a photo straight off a camera, which is the most common way small-business sites become slow.

There are no third-party scripts

Reviews, bookings, forms, subscriptions, search and the cart are all built into the platform rather than injected by other companies' code. That removes an entire category of weight — and an entire category of layout shift, since nothing is inserting itself into your page after it's drawn. It's the quietest benefit of an all-in-one platform and one of the largest. Our guide to add-on stacks covers what that usually costs elsewhere.

Hosting, SSL and scaling

Fast hosting, HTTPS everywhere, and capacity that handles a traffic spike are included on every plan rather than being upgrades.

What's still yours

Infrastructure sets the floor. You can still build a slow page on fast foundations, and it's almost always one of these four.

Too many images on one page

Optimised images are still images. A home page with a forty-image gallery is heavy no matter how well each file is compressed. Twelve well-chosen photographs will look better and load faster than forty mixed ones — and visitors judge a gallery by its weakest picture anyway.

Video used carelessly

A background video is the heaviest thing most small sites carry. Sometimes it earns its place. Frequently it's decoration that costs several seconds on a phone. If you use one, keep it short, keep it muted, and check what it does on a bad connection rather than on your office Wi-Fi.

An enormous page

Fifteen sections is a long page on desktop and an expedition on a phone. Every section is content to load and process. This is the same advice as everywhere else in this series, arriving from a different direction: delete the sections you can't fill honestly.

Uncropped uploads

The platform resizes, but it can't know your intent. Crop before you upload — both because the composition should be yours, and because a tightly-cropped image carries less data than a wide one you're only using the middle of.

How to test it honestly

Your own impression of your site's speed is worthless. It's cached in your browser, you're on good internet, and you know what's coming.

• Use a free speed test such as PageSpeed Insights. Test the mobile score, not the desktop one — it's the harder number and the more representative one.
• Test a real page, not just the home page. Test your best-selling product page and your busiest landing page.
• Test on a phone with mobile data, away from your Wi-Fi. Better still, somewhere with one bar of signal.
• Compare against yourself. Score once, make a change, score again. The absolute number matters less than the direction.

And don't chase a perfect score. The difference between a good score and a perfect one is rarely perceptible to a human, and the effort is nearly always better spent on your photography or your copy.

Perceived speed matters as much as real speed

How fast a site feels isn't the same as how fast it is, and feeling is what visitors act on.

• The top of the page should arrive first. If your headline and hero image appear quickly, people begin reading and stop counting.
• Nothing should move once it's drawn. A page that jumps as images arrive feels much worse than a page that took the same total time and stayed still.
• Taps should acknowledge themselves. A button that shows it's been pressed is forgiven a delay that a silent one isn't.

Keeping it in perspective

Speed is necessary and not sufficient. A fast site with unclear copy, weak photographs and no obvious next step will lose to a slightly slower site that gets those right. Nobody ever bought something because the page loaded quickly.

Think of it as a floor rather than a ceiling. Below a certain speed you're losing people who never see your work at all — and that loss is invisible, which is what makes it dangerous. Above it, the returns diminish sharply and your attention belongs elsewhere.

The platform gets you above that floor by default. Your job is mostly not to undo it: fewer, better images, no gratuitous video, pages that stop when they've said what they need to say.

---

Ten minutes, today

• Run a mobile speed test on your busiest page.
• Open that page on your phone with Wi-Fi off and count the seconds.
• Find the heaviest thing on it — almost always a video or a large gallery — and ask whether it's earning its cost.
• Delete one section you never really wanted.

That's usually the whole job. The silent salesperson doesn't need training — it needs you to stop putting furniture in the doorway.