The phone rings less than it should
You run a few ads, people search for you, and the traffic numbers in your analytics look fine. But the calls don't match. Somebody in Waldo or Overland Park is searching for an emergency plumber or a lunch spot before a Chiefs game, your site loads slow on their phone, and they back out before it finishes. They don't call to tell you. They just call the next name instead.
This is the part that's easy to miss because nothing looks broken. The site works. It just works too slowly for someone standing in a parking lot on 4G, trying to decide between you and three other results in about four seconds.
Why Kansas City traffic makes this worse
A lot of local searching happens in motion here, not at a desk. People check a contractor's site while sitting on 71 Highway traffic, or look up a vet's hours while driving back from the Plaza. Cell coverage in those stretches isn't always strong, and a page that's heavy with uncompressed photos or a video background just stalls out. On a fast home connection it might load in two seconds. On someone's phone near the Grandview Triangle it can take eight or ten.
Add in the seasonal swings. Summer storms knock out signal strength in pockets of the metro, and winter brings more people searching from inside, on home wifi, while also dealing with slower networks if a lot of neighbors are streaming at once during a snow day. A slow site doesn't fail the same way twice. It just fails more often than you'd guess.
More on this from Reading List What A Slow Page Costs A Kansas City Business In Calls.
What a few extra seconds actually costs
Local service businesses, HVAC, roofing, salons, auto shops, live or die on same-day calls. Someone with a furnace out in January isn't going to wait for your site to load. They're going to hit the back button and call whoever answers first. Every extra second of load time is a small tax on exactly the customers who are ready to act right now, which are the most valuable ones you have.
This shows up as missed calls you never see as missed. Nobody emails to say your site was slow. The lead just goes to a competitor three results down, and your numbers look the same as always, just a little short of where they should be.
What you can check yourself
Pull your site up on your own phone, not your office wifi, your actual phone data, standing outside. Time how long it takes to see something useful. If it's past four or five seconds, that's worth fixing. Look at your homepage for big photo galleries, autoplay videos, or anything that was added by a plugin and never removed. Those are usually the heaviest offenders and often the easiest to strip out.
Check how many images are on your most-visited pages and whether they're sized for print instead of web. A photo from a phone camera can be four or five megabytes. Resized properly, it should be a tenth of that and look identical on a screen. This part doesn't need a developer, just someone willing to spend an afternoon compressing images and deleting what isn't earning its place.
Where it stops being a DIY job
If the slowness is coming from the site's actual structure, the hosting it sits on, how it's coded, or a string of plugins all fighting each other, that's past what a business owner should be spending afternoons on. A site built years ago for a desktop-first world often needs real rebuilding work, not image compression, to get genuinely fast on mobile.
This is also the point where it's worth paying someone to run a real diagnostic rather than guessing. A professional can tell you whether the fix is a twenty-minute cleanup or a deeper rebuild, and whether your hosting itself is the bottleneck. For a business that depends on same-day local calls, that's not a vanity project. It's closer to fixing a storefront door that sticks: most people won't complain, they'll just try the next one.