Why your website feels slow on a phone — and what it’s costing you.

Picture your best lead of the month: someone standing in their kitchen with water pooling under the sink, phone already in hand. They search "plumber near me" and tap your site.

They're not on office wifi. They're on cell data, maybe two bars, mid-crisis. Your homepage starts loading... and loading. A hero image crawls in from the top. They hit back and tap the next plumber on the list.

That's the whole problem in one scene. Google and SOASTA's research found that 53% of mobile visits are abandoned when a page takes longer than three seconds to load. Not "engagement drops." Abandoned. Gone. And the moments people need a roofer, a plumber, or a fence company most urgently are exactly the moments they're standing outside on a phone.

Your site probably feels fine to you — because you look at it on your desktop, on your own wifi, with the whole thing already cached from your last hundred visits. Your customers get none of those advantages.

Here's why small-business sites are slow on phones, and what to fix first.

Culprit #1: Images that were never sized for the web

This is the most common problem we see, and the cheapest to fix.

A photo straight off a phone or camera is often 4,000+ pixels wide and 3–8 MB. Upload it as your homepage hero and every visitor downloads all of it — even though a phone screen only needs an image around 800 pixels wide, which can weigh 80–150 KB in a modern format. That's a 20–50x difference on a single file, and most homepages have five to ten images.

On a strong LTE connection, an extra 5 MB might cost a couple of seconds. On weak cell data during a storm — when towers are congested because everyone in the zip code is doing the same thing — it can be ten seconds or more. Your homeowner left at three.

The fix:

1. Resize every image to the largest size it'll actually display. Hero images rarely need to be wider than 1,600–2,000 pixels; team photos and gallery thumbnails far less.
2. Convert to WebP (or AVIF), which typically cuts file size 25–35% versus JPEG at the same visual quality.
3. Compress. Free tools like Squoosh do this in a browser; WordPress plugins can batch it.
4. Lazy-load anything below the first screen so the phone downloads images only as the visitor scrolls to them.

Effort: an afternoon. Payoff: usually the single biggest speed gain available on a small-business site.

Culprit #2: Page-builder and theme bloat

If your site was built with a drag-and-drop page builder on top of a "does-everything" theme, it's likely shipping a lot of code your pages never use — sliders, animation libraries, icon packs, three different font families, a dozen plugins each adding their own scripts and stylesheets.

Every one of those files has to be downloaded, and worse, the JavaScript has to be executed — and phone processors are far weaker than laptops. A page that "loads" in two seconds on your desktop can take three times as long to become tappable on a mid-range Android, which is what a lot of your customers actually carry. Google's Core Web Vitals measure exactly this (interactivity, not just load), and they factor into how you rank.

The fix, in order of effort:

1. Deactivate and delete plugins you don't use. Every plugin is a suspect. (An hour.)
2. Cut to one font family, two weights. Fonts are a sneaky-heavy download. (An hour.)
3. Add a caching/optimization plugin that minifies and defers scripts. (A half day, with testing.)
4. Rebuild on a lighter foundation. For sites drowning in builder bloat, a rebuild on a lean theme or a modern static setup is sometimes cheaper than fighting the old stack — and the speed difference is night and day. (A real project, but often the right one.)

Culprit #3: Cheap shared hosting

That $5/month hosting plan puts your site on a server shared with hundreds — sometimes thousands — of other websites. Before your page even starts sending, the server has to wake up and respond. On oversold shared hosting, that first response (time to first byte) alone can eat one to two seconds of your three-second budget. Nothing you do to images or plugins fixes that; it's upstream of everything.

There's a traffic-spike angle here too: whatever drives your busiest hours — a cold snap, a burst pipe, a big local event — cheap hosting is exactly the kind that buckles under a spike. The busiest, most valuable hour of your month is exactly when your site is slowest.

The fix: move to decent managed hosting or a modern hosting platform with a CDN (a network that serves your site from a location near the visitor). Realistic cost is $20–40/month instead of $5. Migration is a few hours of work for someone who's done it before. For most local businesses this is the best $30 a month spends anywhere in the marketing budget.

The order of operations

If you do nothing else, do these, in this order:

1. Compress and resize your images — biggest payoff, lowest effort.
2. Delete unused plugins and extra fonts — quick, free, meaningful.
3. Upgrade off bottom-tier hosting — small monthly cost, fixes the part you can't optimize around.
4. Add caching and lazy loading — moderate effort, compounding benefit.
5. Consider a rebuild only if the numbers are still bad after 1–4 — then it's the honest answer, not an upsell.

Test before and after with Google's free PageSpeed Insights (pagespeed.web.dev) — look at the mobile score, not desktop, and pay attention to Largest Contentful Paint. Under 2.5 seconds is Google's "good" threshold.

How West Fork approaches this

Speed is the first thing we audit on any site we take on, because it's usually the highest-ROI fix available. We run mobile-first performance tests, fix images and hosting before proposing anything bigger, and we'll tell you plainly if your current site just needs a tune-up rather than a rebuild. Every site we build is tested on real phone connections, not just an office desktop, before it goes live.