← All posts

Why Your Website Is Slow (and What It’s Costing You)

You already know it’s slow. Here’s what “slow” actually means, what it’s costing you in calls you never got, and the handful of ordinary things causing it.

You already know your site is slow. You’ve pulled it up on your phone sitting in the truck, watched the white screen sit there, and thought huh, that takes a minute. Then a call came in and you forgot about it.

That’s the thing about a slow website. It never sends you a bill. It just quietly costs you, one visitor at a time, and you never find out which customers you lost — because the people who leave don’t call to tell you why.

So let’s put real numbers on it. What “slow” means, what it costs, why it’s happening, and what actually fixes it.


1. First, what “slow” actually means

“Slow” isn’t a feeling. Google put a number on it years ago, and those numbers are what your search ranking gets graded against. They’re called Core Web Vitals, and there are three of them:

  • Does the main thing on the page show up within 2.5 seconds? Not the whole page — the biggest visible piece. Your headline, your hero photo, whatever the visitor is actually waiting on.
  • Does the page respond within 200 milliseconds when someone taps something? That’s the lag between a tap and anything happening. It’s the reason people tap a button three times.
  • Does the page hold still while it loads? You know the one — you go to tap “Call Now,” an ad or an image finally loads above it, everything jumps, and you’ve tapped something else entirely.

Here’s the part most people miss. Google doesn’t grade you on your average visitor. It grades you at the 75th percentile — meaning your slowest quarter of visitors has to hit those numbers too. So the guy standing in a gravel lot outside Gettysburg on two bars of cell service counts just as much as the person on fiber at home.

The takeaway: Your site isn’t fast because it feels fast on your laptop at your desk. It’s fast when it’s under 2.5 seconds for the customer with a bad signal and an older phone.


2. What it’s costing you

This is where it stops being a technical conversation.

The clearest study I’ve seen on this comes from Portent, which looked at 100 million page views across e-commerce and lead-generation sites. For lead-gen sites — which is most local service businesses, the ones where the goal is a form or a phone call — a site that loads in 1 second converts about three times better than one that loads in 5 seconds. Not three percent better. Three times.

Google and Deloitte ran a different study across 37 brands and 30 million sessions, and found that improving mobile load time by a tenth of a second lifted retail conversions 8.4% and form submissions on lead-gen sites by 21.6%. A tenth of a second. And Google’s own mobile research found that as load time goes from 1 second to 10, the odds a mobile visitor bounces go up 123%.

Put that in local terms. Say 300 people land on your site in a month from Google, and 5% of them call you. That’s 15 calls. If your site is a 5-second site instead of a 1-second site, you’re not looking at 15 calls — you’re looking at something closer to 5, and you never see the other 10. They’re not angry. They just hit back and tapped the next contractor down the list.

Whatever a job is worth to you, multiply it by those missing calls. That’s the number.

The takeaway: Speed isn’t a technical score. It’s the difference between someone calling you and someone calling the next guy, and it repeats every single day.


3. Why it’s slow — the honest list

In 25 years of this work I have almost never found an exotic cause. It’s nearly always the same four or five things, and none of them are your fault.

Your images are enormous. This is the number one culprit, every time. The median mobile page on the internet is about 2.1 megabytes, and images are the single biggest slice of it. That happens because someone took a photo on a phone — a 4,000-pixel-wide, four-megabyte photo — and uploaded it straight to the site, where it gets displayed at 800 pixels wide. The visitor downloads the whole four megabytes anyway. Ten photos like that on your homepage, and you’ve built a site that only works on good WiFi.

You’re paying for plugins in load time. Every plugin — the booking widget, the review slider, the popup, the page builder itself — brings its own code along. The median page now pulls in twenty-odd separate scripts. Each one is another thing the browser has to fetch and run before your visitor sees anything. Nobody adds ten plugins at once. You add one a year for six years, and then one day the site takes eight seconds.

Third-party scripts you’ve forgotten about. The chat widget you tried for a month. The tracking pixel from the ad campaign that ended in 2023. The social feed embed. These load from somebody else’s server, which means your site is only as fast as their server on a bad day.

Your hosting. Cheap shared hosting means your site sits on a machine with a few hundred other sites. Before a single byte reaches your visitor, the server has to wake up and think about it. That’s a second gone before anything has even started loading.

Nothing is cached. On a lot of small-business sites, every visitor causes the page to be rebuilt from scratch — database queries and all — even though the page hasn’t changed since March. Caching means building it once and handing out copies. It’s often the single biggest win available.

The takeaway: Slow sites are almost never mysterious. They’re oversized photos, accumulated plugins, forgotten scripts, cheap hosting, and no caching — in that order.


4. How to check yours in five minutes

You don’t need me for this part, and you shouldn’t take anyone’s word for it, including mine.

  • Run PageSpeed Insights. It’s free, it’s from Google, and you just paste in your URL. Look at the mobile tab, not desktop. If there’s a section with real-world visitor data, read that one first — that’s your actual customers, not a simulation.
  • Test the page people actually land on. Most visitors from Google arrive on a service page, not your homepage. Test the pages that matter.
  • Try it on your own phone, off WiFi. Turn WiFi off, load your site on cell data, and count. That’s the real experience for a good share of your customers.

If it’s under two seconds, you’re in good shape and you can spend your money elsewhere. If it’s over four, you have a fixable problem that’s costing you work right now.


5. What actually fixes it — in order

Here’s the part where a lot of agencies would tell you that you need a full rebuild. Sometimes that’s true. Often it isn’t, and I’d rather tell you the cheap fixes first.

  • Compress and resize the images. Cheapest fix in the business, and usually the biggest single improvement. A photo that looks identical to a human can be a tenth the size.
  • Turn off what you’re not using. Every plugin and script you no longer need is free speed sitting on the table.
  • Turn on caching and a CDN. A CDN keeps copies of your site on servers around the country so it doesn’t have to travel as far. On most small sites this is an afternoon of work, not a project.
  • Move to better hosting. Modern hosting for a small business site costs less than most people expect, and it can take a full second off before you change anything else.
  • Then, if it’s still slow, rebuild. When a site is a decade of plugins stacked on a page builder, there’s a point where you’re maintaining the problem instead of fixing it. But that’s the last resort, not the opening pitch.

This is also the reason we build on lean, static code here instead of stacking a template full of plugins. It’s not purism. It’s that a site with less in it has less to be slow about, and it stays that way three years from now when nobody’s watching.

The takeaway: Start with images and caching. Most slow small-business sites get most of the way back with a day of work and no redesign at all.


What it comes down to

A slow website isn’t a technical problem you can put off until things quiet down. It’s a leak. Every day it runs, some number of people who were looking for exactly what you do decide you’re not worth the wait, and you never hear about it.

The good news is that it’s one of the few problems in this business with clear numbers, known causes, and fixes that mostly cost hours instead of thousands. You can measure it in five minutes and you can usually fix most of it in a day.

So go run the test. If the number comes back ugly, I’m happy to look at it with you and tell you straight whether it’s a two-hour fix or a real project.

Free 30-minute consultation. No obligation. Just an honest look at what your site needs.

Or call/text: (717) 677-2502

Sources consulted: Google’s Core Web Vitals thresholds and field-data guidance (web.dev); the HTTP Archive Web Almanac 2025 page weight report; Portent’s site speed and conversion rate research (2022); Google, 55, and Deloitte, “Milliseconds Make Millions”; and Google/SOASTA mobile page speed benchmark research.