“They’re probably just busy.”
That’s what you’ve been telling yourself for six months. Every ticket that sits for a week, every email you have to send twice to get a one-line answer — some part of you fills in the excuse on their behalf.
Maybe they are busy. Or maybe your hosting company isn’t responding because you’ve quietly become a low-priority account at a company that stopped thinking about you the day your payment cleared. The problem is you can’t tell the difference from where you’re sitting. From the inside, both look exactly like waiting.
So stop guessing. Here’s how to tell whether you have a responsiveness problem or a relationship problem — with numbers instead of vibes.
What’s a reasonable response time?
When you send your hosting company a request, there are two things to measure: how fast they respond, and how fast they fix it. Those are separate promises. A response is “we got it, here’s what happens next.” A fix is the work actually getting done. Plenty of providers are fine at one and hopeless at the other — quick to reply, slow to deliver, or the reverse.
So what’s reasonable? A response the same business day. Non-urgent fixes done within two to five business days. And real emergencies — site down, checkout broken, contact form swallowing leads — handled in hours, not days.
If those numbers sound generous compared to what you’re getting, you already have your answer.
This is also what a service agreement is for, and why “we’ll get to it” isn’t one. A real one puts a number next to a promise. If nobody has ever told you what your provider’s response times are supposed to be, that’s not an oversight.
The five tells
You follow up more than they respond. The ratio has flipped. You’re the one keeping the relationship alive, and you’re doing it on your own time.
“Quick questions” go unanswered until they turn into billable projects. The favor that took five minutes last year is somehow a scoped engagement this year.
You’ve stopped asking for things. Not because you don’t need them — because it’s not worth the friction. This is the one people miss, because it doesn’t feel like a red flag. It feels like maturity. It isn’t. It’s you managing around a vendor you’re paying.
Things change on your site and your website company never mentions it. Work happens, occasionally. You find out by noticing, not by being informed. Nothing is documented, nothing is explained, and you couldn’t reconstruct what was done if you had to.
You’re paying for strategy and getting odd jobs. One client came to us paying over $1,000 a month to their SEO team. And work was happening — kind of. A text change here, a tweak to a page there. But going back through six months of the account, we couldn’t find anything that resembled actual SEO: no strategy, no content plan, nothing built to move rankings or traffic. They weren’t being ignored, exactly. They were being kept busy — small visible tasks standing in for the work they were actually paying for. If your monthly reports are a list of little edits and you can’t point to what any of it was for, that’s this.
Two or three of these land? You’re not imagining it.
Why hosting companies go unresponsive
Here’s the part that might make you feel marginally better about them, if not about your situation: it’s usually not personal. It’s arithmetic.
If you’re on a bundled retainer — the one where a couple thousand a month covers social, web work, SEO, content, and a monthly call — the money got divided before it ever reached your ticket. Spread across five service lines, each one gets a few hundred dollars of real attention. There isn’t a budget line for answering you quickly, because responsiveness isn’t one of the five things you’re buying. It’s the thing that quietly gets funded out of whatever’s left.
Same math applies to headcount. A shop carrying fifty accounts with two people doing the work isn’t staffed to give anyone real attention. Everybody gets a thin slice, everybody pays full price, and the slow response you’re experiencing isn’t a failure of the system — it’s the system working as designed.
And this isn’t a big-shop or small-shop thing. We took over a site for an institution that had been with an established web company for years — real company, real staff — and slow, unhelpful support was one of their core complaints. Size doesn’t fix it. Structure does.
The useful question isn’t “are these people bad at their job.” It’s “how many other accounts am I sharing a queue with, and where in that queue do I land.”
Run the test
You don’t have to keep guessing about any of this. Give it thirty days.
Send one normal-priority request. Nothing urgent, nothing dramatic — a real task you actually want done. Write down two times: when they responded, and when it was actually finished. Hold both against the benchmarks above.
Then, separately, send one question:
“Can you confirm where my domain is registered and that I have administrator access to my site?”
Watch the answer, but watch the clock harder. A provider with nothing to hide answers that in a day, in one paragraph, without asking why you want to know. A provider who’s been quietly holding your keys gets vague, or slow, or curious about your motives. That hesitation tells you something a response-time log can’t.
Fair warning: that question is also the first item on the checklist for leaving. If the answer comes back wrong, you’ll want the rest of it.
But wouldn’t leaving cost more?
This is the thing that keeps people parked with an unresponsive hosting company a year longer than they should be. The devil you know is at least a devil with your login credentials.
Sometimes leaving costs more. Often it doesn’t, because slow and expensive tend to travel together — you’re not paying a premium for excellent work, you’re paying retail for a spot near the back of a queue.
The library I mentioned was paying premium-tier prices for hosting and support that had gone quiet, right as an accessibility deadline closed in. What they needed wasn’t more money into the same relationship. They got a rebuilt, compliant site from a provider who answers the phone, and their monthly cost went down.
Slow and expensive isn’t a package deal. Usually it’s two symptoms of the same problem.
If the test confirmed what you already suspected, don’t open with the breakup email. Open with a quiet audit of what you actually control — here’s the full checklist.
Or skip the DIY version. Get a free rescue assessment and we’ll tell you honestly whether you’ve got a responsiveness problem or a relationship problem — and what it’d take to fix it. Get a Free Rescue Assessment
