Why website speed matters: what your customers notice and what Google pays attention to
A slow website loses customers before they ever read what you sell: someone on a phone, on mobile data and in a hurry, leaves if the page drags. Google knows that and prefers to show pages that load fast. The good news is you can check it without any technical knowledge.
A slow website loses customers before they ever read what you sell. Someone on a phone, on mobile data and in a hurry, doesn't wait: if the page drags, they go back to Google and tap the next result. Google knows that, so between two similar pages it prefers to show the one that loads fast.
You don't need any technical background to tell whether your site has this problem. In this post I'll show you what it looks like from your customer's side, a few checks you can do today, and what to ask whoever built or maintains your site.
What it looks like from your customer's side
You open your website on the office computer, on a good connection, with the page already stored from all your past visits. Your customer doesn't. They open it standing at a bus stop with a weak signal, on a phone that isn't the latest model, right after tapping an ad or a search result. For them, a few seconds of blank screen feels like forever.
And they don't always leave annoyed. Sometimes a text comes in, the bus shows up, something distracts them. A slow site doesn't kick people out; it just doesn't hold them. That's why it's a problem you can't see anywhere, except in the inquiries that never arrived.
Why Google cares too
Google wants people to keep using Google. If it sends someone to a page that takes forever and that person bounces back frustrated, it's the search engine that looks bad. So between two pages that answer a search equally well, it tends to show the one that gives a better experience first, especially on phones.
Speed doesn't replace content: a fast site with nothing useful to say won't rank. But a site with good content that's slow is competing with one hand tied behind its back. For the rest of what Google looks at, I have a guide on how to rank higher on Google.
Three checks you can do today
No tools or technical knowledge needed:
- Open it on a phone that isn't yours, on mobile data, not WiFi. Borrow a family member's. Watch how long it takes until there's something you can actually read.
- Open it somewhere with bad signal. A subway, an elevator, a rural road. If it stays blank there, a lot of your customers see the same thing.
- Tap your own ad or your own search result and look at what loads first for someone arriving. If it's a video or a huge photo that's slow to appear, that's your first suspect.
What you notice and what to ask
| What you notice | What it usually is | What to ask whoever built your site |
|---|---|---|
| Photos load in chunks | Photos far heavier than they need to be | Are images sized for each screen? |
| A few seconds of blank screen | The site loads everything before showing anything | What does a visitor see first, and how long does it take? |
| Text jumps around while loading | Things that show up late and push the rest down | Can each element's space be held so nothing jumps? |
| Fine on a computer, bad on a phone | The site wasn't built with phones on mobile data in mind | Have you tested it on an ordinary phone, on data? |
| It used to be fast and now it isn't | Things added over time | What's been added lately, and is it actually used? |
Where a second shows: the menu at the table
For some businesses, speed isn't a detail. At Boca de Lobo, a steakhouse with two locations in Buenos Aires, the digital menu opens by scanning a QR code at the table: more than 250 items, plus promotions and locations. The customer is seated and hungry, and if the menu doesn't show up, they flag down a server and ask for a paper one. Or worse, they order the usual and never see the specials.
That's why, on a project like that, the test that matters is the customer's own phone on whatever connection they get in the dining room. If you run a restaurant, I cover what else a menu needs in QR code digital menu for restaurants.
See the Boca de Lobo caseIf you pay for ads, speed is money
Every time someone taps your ad, you pay for that click. If the page is slow and they leave before it loads, you paid for nothing. So before you raise your ad budget, make sure the page people land on opens quickly on a phone. I go deeper in landing pages for ad campaigns.
The same goes for heavier content, like a 3D walkthrough of an apartment: it has to be designed for phones from the start. The Recorrido 3D blog has a piece on 3D walkthroughs on mobile phones.
How I check a site
When someone asks me to look at their website, the first thing I do is open it the way a customer would: an ordinary phone, mobile data, nothing saved from earlier visits. Then I tell you in plain words what's slowing it down and whether it can be fixed or is better rebuilt. I work remotely from Buenos Aires, Argentina (UTC−3), and quote each case separately. Speed is also part of what website maintenance includes.
Frequently asked questions
Is my website slow, or is it my internet?
To find out, open it on someone else's phone, on mobile data rather than WiFi, and compare it with a well-known site at the same moment. If the others load fine and yours doesn't, the problem is the website.
Can it be fixed without rebuilding the whole site?
Often, yes: photos that are far too heavy, videos that autoplay, or add-ons nobody uses. Other times the slowness comes from how the site was built, and rebuilding makes more sense. Whoever looks at it should be able to tell you which case you're in.
Does a good-looking website have to be slow?
No. A site can have great photos, subtle animation and look sharp while still loading fast. What makes it slow isn't the design, it's how what you see gets prepared and delivered.
If your site feels slow, send me the link on WhatsApp at +54 9 11 6193-3176 or email contacto@facundocampo.com.ar. I answer in English and Spanish. I'll open it the way your customers do and tell you what's holding it back.