Your website has three seconds. Then they're gone.

Watch anyone use a phone at a bus stop. Tap, wait, and if nothing happens, back to the search results and tap the next one. There's no anger in it; it's a reflex. Three seconds is roughly the patience a stranger gives a business they don't know yet, and most small-business websites in this city blow through it on cell data. This article is the fix: how to time your own site properly, what's slowing it down (it's almost always the same four things), how to fix each one, what to say to whoever built it, and a worked example so you can put a dollar figure on what the delay is costing.

Test it now, the right way

Most owners have only ever seen their site on the shop wifi, on the designer's laptop, in a browser that had already loaded it a hundred times. That's not the test. The customer is on a phone, on cell data, loading it for the first time. Do it like this.

1. Turn off wifi on your phone. Settings, Wi-Fi, off. You want cell data only, and ideally not standing next to a window with five bars. The back of the shop is better.
2. Clear the site from memory. Open your browser in a private or incognito tab so the phone isn't reusing a copy it saved earlier. On Safari, tap the tabs icon then Private; on Chrome, tap the three dots then New Incognito tab.
3. Type your address and start counting the moment you tap go. Count "one thousand one, one thousand two." Stop when you can read the first screen and tap a button. Not when the spinner stops; when it's usable.
4. Write the number down. Then do the same for two competitors' sites. If yours is the slowest of the three, you already know where your customers are going.

If you want a second opinion with more detail, Google offers a free page-speed tool: search "PageSpeed Insights," open it, paste your website address into the box, and click Analyze. Look at the Mobile results, not desktop. You'll see a score out of 100 and a list of what's slowing the page, usually with photos at the top. You don't need to understand every line; the point is to hand that list to whoever maintains your site and say "fix the top three."

The stopwatch test is the one that matters, though. If you get bored before your own site loads, so does everyone else, and no score changes that.

What slows sites down

Slow sites are almost never slow for exotic reasons. It's one of these four, and often all four at once.

• Huge photos. A photo straight off a modern phone camera is 3 to 6 megabytes. A site needs it at about 200 kilobytes, roughly twenty times smaller. Upload ten camera photos to a page and you've asked every visitor to download a small movie before they can read your hours.
• Page-builder bloat. Drag-and-drop builders and plugin-based systems load dozens of invisible tools on every page: sliders, animation libraries, form builders, three fonts you don't use. Each one is a separate download before anything appears.
• Trackers and widgets. A chat bubble, a review carousel, an analytics tag, a pixel from an ad platform you tried once in 2022. Each is a call to another company's server, and your page waits for all of them.
• Cheap shared hosting and autoplay video. Budget hosting shares one machine with hundreds of other sites. And the full-screen video background that looked great on the designer's monitor is the single heaviest thing a page can carry on a phone.

If you get bored before your own site loads, so does everyone else.

Fix one: the photos

This fix alone usually cuts load time in half, and you can do most of it yourself.

1. Make a list of every photo on the site and how big it is. On a computer, right-click a photo and choose "Open image in new tab"; the pixel size usually shows in the tab title, and saving it shows the file size. If most are over 1 megabyte, that's the problem.
2. Resize before you upload. A photo on a website never needs to be wider than about 1600 pixels; for a small thumbnail, 600 is plenty. Any free online image compressor will do this: open it in your browser, drag the photo in, set the width, download the result. Aim for under 200 kilobytes per photo and under 100 for small ones.
3. Use the modern formats if your site allows it. Formats called WebP and AVIF make the same photo about a third the size of a JPEG. Whoever maintains the site can switch these in an afternoon.
4. Load photos as they're needed. Ask for "lazy loading," which means photos further down the page don't download until the visitor scrolls to them. It's a one-line change on most sites.
5. Cut the count. Ten photos that each say something beat forty that say the same thing. The gallery of every haircut you did in March can live on Instagram.

Fix two: everything else

These need whoever built or maintains the site, but you should know what to ask for.

• Remove every plugin, widget, and tracker you don't use. Ask for a list of everything installed and go through it together. The rule is: if you can't say what it does for a customer, it goes.
• Kill the autoplay video. Replace it with a single good photo. If you love the video, make it a play button.
• Move to proper hosting. A simple site can be served from a fast global network for a few dollars a month or free; there's no reason to share a slow machine with a thousand strangers.
• Ask for a static site if you can. A site that's just pages, with no database to query and no builder running behind it, has nothing to wait for. This is how we build: static pages, photos compressed to phone size, no trackers, fast hosting. Our pages typically show up in about a second on 4G, not because of a trick but because there's nothing extra to load. AI does the slow, repetitive part of that build, which is why it's cheap, and the website page spells out exactly what's included.

The worked example: what a slow site costs

Put your own numbers in, but here's the shape. Say your site gets 200 visits a week from phones; a busy dental office or a dental office with a decent Google listing sees more, a small shop maybe half. Say that, when the page loads properly, one visitor in ten does something useful: taps the phone number, books, or gets directions. That's 20 actions a week.

Now say the site takes six seconds on cell data and a third of visitors give up before it appears. That's about 67 people a week who never see the page, and at the same one-in-ten rate, that's roughly 7 actions a week lost. Call it 6 to be conservative. If a new customer is worth $35 on the first visit (a haircut, a basic service), that's 6 x $35 = $210 a week, or about $10,920 a year, walking back to the search results. If your ticket is a $150 dental cleaning or a $400 brake job, multiply accordingly.

Against that: a fast site is not more expensive than a slow one. Compressing the photos is free. Removing plugins is free. Better hosting costs a few dollars a month. Ours is $1,200 to set up inside a plan from $499 a month, speed is part of the build rather than an upgrade, and the whole first year is a fraction of one year of the loss above. The numbers are yours to change; the conclusion rarely does.

A fast site isn't more expensive than a slow one. It's just lighter.

What to say to whoever built it

You don't need the vocabulary. You need the test result and a short list. Send this, filled in:

"I timed the site on my phone over cell data in a private tab and it took (X) seconds to become usable. Google's PageSpeed tool on Mobile gives it (score) and lists these at the top: (paste the top three items). Can you: 1. compress every image to under 200KB and turn on lazy loading, 2. send me a list of every plugin, widget, and tracker on the site so we can remove what we don't use, 3. remove the autoplay video and replace it with a photo, 4. tell me what hosting we're on and what a faster option would cost. I'd like it under three seconds on cell data. What will this cost and when can it be done?"

A good developer answers with a price and a date. If the answer is "it's fast on my end" or "that's just how the platform works," you've learned what you needed to know, and it's worth reading the seven questions to ask any web designer before you hire the next one.

If you're on a monthly plan with us, the message is shorter: "Site feels slow on my phone, can you check?" Speed checks are part of the job, not a change request.

Common mistakes

• Testing on shop wifi. It hides the problem. Fix: wifi off, private tab, back of the shop, count out loud.
• Uploading photos straight from the phone. The single most common cause of a slow site. Fix: resize to 1600 pixels wide and under 200KB before anything goes up.
• Adding a widget for every idea. Chat bubble, review slider, Instagram feed, pop-up, each "just one more thing." Fix: one purpose per page, and remove anything you can't explain to a customer.
• Choosing hosting by price alone. The $3 plan shares a slow machine. Fix: ask for fast hosting on a global network; for a simple site it costs about the same or less.
• Chasing a perfect score. A 100 in the speed tool doesn't book a haircut. Fix: get under three seconds on cell data, then stop and spend the time on reviews.
• Fixing it once and forgetting. Someone uploads a 5MB photo next month and it's slow again. Fix: add the stopwatch test to a monthly check, and give anyone who uploads photos the 200KB rule.

Speed checklist

• I timed the site on my phone, wifi off, private tab, and wrote the number down.
• It's usable in under three seconds on cell data.
• Every photo is under 200KB and no wider than 1600 pixels.
• Lazy loading is on for photos below the first screen.
• I have a list of every plugin, widget, and tracker, and each one earns its place.
• No autoplay video.
• Hosting is a fast network, not a shared budget box.
• Whoever uploads photos knows the 200KB rule.
• The stopwatch test is on the monthly calendar.

Run the free website checklist for the rest of what a site needs, and if you'd rather not chase a slow site at all, tell us about your business; a fast, phone-first site in 2 to 4 weeks is the whole point of what we do.

Questions owners ask

My site is fast on my laptop. Why does it matter? Because your customer isn't on your laptop. They're on a three-year-old phone with two bars on the platform at Kings Highway. That's the connection you're designing for, and it's the only one that counts.

Is three seconds a real rule? It's a good working target, not a law. What's real is the behavior: people back out of a page that hasn't appeared, and they do it faster every year. Under three on cell data keeps you safely on the right side of that reflex.

Can I fix this without changing platforms? Usually most of it. Photos, plugins, and video are fixable on almost any platform. Some builders have a floor you can't get under, because their own code is the weight. If you've done everything above and you're still at five seconds, the platform is the problem.

Does speed affect my Google ranking? It's one signal among many, and a small one compared with your profile and reviews. The bigger effect is indirect: slow pages get abandoned, and abandoned pages don't turn into calls. Fix speed for the customer, not for the algorithm.

What does a fast site cost? Not more than a slow one. Ours is $1,200 to set up and then a plan from $499 a month, with the AI's usage cost passed through at cost with no markup, and speed is part of every build rather than an upgrade. Read what a website should cost for the full comparison.