Why Is Your Website Slow — And Is It Costing You Kansas City Customers?

How slow is your website, really?

You don't have to guess — you can measure it in about a minute, for free.

Go to pagespeed.web.dev, paste in your web address, and hit Analyze. Look at the Mobile tab — that's the one that matters, because most of your customers are on phones. You'll get a Performance score from 0 to 100. Under 50 is a real problem. 50 to 89 is "needs work." 90 and up is where you want to live.

Most small-business sites I test come back somewhere in the 30s and 40s on mobile. If that's you, you're not alone — and you're also quietly losing people every single day.

Want to see the other end of the scale? Run workhorsecrs.com through the same tool. That's a site I hand-coded for a court reporter here in the metro, and on mobile it scores a perfect 100 — Performance, Accessibility, Best Practices, and SEO, all the way across. Same test you just ran on yours. I'm not telling you it's fast — go check it yourself. That's the whole point of this article: this stuff is measurable, so nobody has to take anybody's word for it.

What is a slow website actually costing you?

More than you'd think — in customers you never hear about and rankings you never earned.

The numbers are brutal. Around 53% of people on a phone leave a site that takes longer than three seconds to load. Every extra second drops your conversions by roughly 7%. And these aren't people who complain — they just leave, tap your competitor, and you never know they were there. It's the most expensive kind of lost sale: the silent one.

Then there's Google. Site speed isn't just a nicety — it's a confirmed ranking factor. Google measures how fast your pages load and feel (they call it Core Web Vitals), and slow sites get pushed down the results. So a slow site is a double hit: the people who find you leave, and fewer people find you in the first place.

Put it together and a slow website is a leak you can't see. You're paying for it whether you notice or not.

Why are most Kansas City small business sites slow?

Usually it's one or more of six things — and most of them trace back to how the site was built. Here are the usual suspects, in the order I find them:

Giant images. The single most common one. You upload a beautiful 4MB photo straight off your phone, it looks fine to you, and now every visitor — including the person on cell data in a parking lot — downloads the full thing. One oversized image can add two or three seconds by itself.

Cheap hosting. That $5-a-month plan puts your site on a server shared with hundreds of others. When their traffic spikes, yours crawls.

Too many plugins. If your site's on WordPress, every plugin adds code the browser has to load. Most small-business WordPress sites run 15 to 30 of them, plenty loading on every page whether they're needed there or not.

A bloated theme. Pre-built themes carry thousands of lines of code for features you'll never use. Your barbershop is loading e-commerce checkout code it doesn't even have.

No caching. Without it, the server rebuilds your entire page from scratch for every single visitor instead of handing them a ready-made copy.

And the one nobody wants to say out loud: the way it was built. Which brings us to the part your current web guy probably won't bring up on his own.

What can you fix yourself this week?

A few of these you can knock out today, for free, and they genuinely move the needle. I'd rather you have a faster site than a sales call, so here's what you can actually do without hiring anyone:

Compress your images. Run your photos through a free tool like TinyPNG before you upload them, and don't serve a 4000-pixel-wide image where a 1600-wide one looks identical. On an image-heavy page this alone can cut load time in half.

Add Cloudflare (it's free). It copies your site to servers around the world and serves each visitor from the closest one, and it handles some caching automatically. Setup is mostly pointing your domain at it.

Delete plugins you're not using. Every one you remove is code the browser stops having to load. Be honest about which ones actually earn their keep.

Then run the PageSpeed test again and watch the number move after each change. That feedback loop is oddly satisfying, and it tells you exactly what's working.

Do those and a genuinely slow site will get meaningfully faster. Sometimes that's enough. Sometimes it isn't — and it's worth knowing why.

When fixing isn't enough — it's the architecture

Sometimes you can optimize all day and still hit a wall, because the problem isn't the settings. It's the foundation.

Here's the honest version most speed articles won't give you, because they're written by people who build on the exact platforms they'd have to criticize. Optimization has a ceiling. Compress the images, add caching, upgrade the hosting, and you can drag a slow site from, say, a 40 up to maybe a 65. That's real improvement — but you're still tuning an engine that was heavy to begin with.

The sites that score in the 90s and 100s usually aren't "better-optimized WordPress." They're built differently from the ground up — hand-coded, no bloated theme, no pile of plugins, nothing the browser has to wade through. That's not a tweak. It's a different foundation.

And this is the part a lot of developers will dodge: admitting a rebuild would fix it means admitting the first build was on the wrong foundation. So you'll hear "it's fine" or "that's just how websites are." It isn't. (If you want to know how to tell whether your web guy is being straight with you about this kind of thing, I wrote a whole piece on it.)

How fast can a hand-coded site actually be?

Fast enough that you can go verify it yourself right now.

Back to workhorsecrs.com — the court reporting site I mentioned. A perfect 100 on mobile, across the board. No WordPress, no theme, no plugins. Just hand-written code and nothing the browser doesn't need.

That's not a magic trick, and it's not me being a genius. It's just what happens when a site is built to be fast instead of optimized to be less slow after the fact. Every site I build is meant to hit those marks, because on a phone, in a local market, speed is the difference between the customer calling you and calling the next result down.

So don't take my word for any of it. Run your site. Run Workhorse. Run your competitors. The scores don't lie — and now you know what they mean.