That $3/month shared hosting plan seems like a great deal. It is $36 a year. It is also, very frequently, the reason a good business loses customers before it ever speaks to them.
The price is not dishonest — the hosting is genuinely cheap. What is dishonest is the implication that the cost of hosting is the cost of your website. It is not. Hosting is one line in a much larger account, and the most expensive line is the one that never appears on the invoice.
What you are actually buying
Shared hosting at that price means your site shares a CPU, memory and a database server with hundreds of other sites. When one of them is running a plugin that queries its database in a loop, your pages slow down even though nothing you own has changed.
Three things follow from that sharing, and all three cost you money:
- Speed. Your Time to First Byte depends on your neighbours' traffic, not your own.
- Uptime. An oversold server falls over under load. Usually at the worst possible moment.
- Attention. You cannot install a current PHP version, tune a cache, or move to a modern stack, because none of that is available at that price.
The number that matters
Slow sites lose visitors before they have a chance to evaluate anything else. Studies consistently show that a large majority of mobile visitors abandon a page that takes more than three seconds to load. On a slow shared host, a large share of your traffic hits that threshold during the first byte — before a single image or font is requested.
The cost of cheap hosting is not the £36. It is the enquiry you never received because the visitor left during the pause.
Now price it honestly. If your site receives enquiries worth, say, $500 each, and a slow host costs you five enquiries a month while a fast host recovers one, then cheap hosting is costing you roughly $2,500 a month. Nothing about that appears on the hosting invoice.
Performance is a ranking factor too
This is not only about conversion. Google measures Core Web Vitals — Largest Contentful Paint, Interaction to Next Paint and Cumulative Layout Shift — and they are explicit page experience signals. A slow origin server damages LCP directly, because LCP is dominated by how quickly the server responds and returns the HTML.
So cheap hosting quietly costs you twice: fewer visitors convert, and the visitors who do arrive are filtered by a ranking disadvantage you cannot see.
What we usually do instead
For most client sites the fix is not a bigger server. It is moving static delivery to a CDN, keeping dynamic work as small as possible, and adding a cache in front of everything. Migrating from budget hosts to setups using LiteSpeed and Cloudflare's CDN typically cuts load times by 60-80% without changing a line of site code — because the expensive part was never the application.
| Layer | What it does | Typical gain |
|---|---|---|
| CDN edge cache | Serves static files from a data centre near the visitor | Large — usually the single biggest win |
| Page cache | Serves whole generated pages without touching PHP | Large on content sites |
| Image optimisation | Modern formats, correct dimensions, lazy loading | Moderate, and compounds |
| Database tuning | Caching queries, adding indexes, cutting N+1 lookups | Varies — occasionally dramatic |
Notice that the first three are caching and delivery changes. They cost almost nothing and they do not require touching the application's logic. Most "we need a faster server" conversations are actually "we need a cache" conversations.
Signs your hosting is now the bottleneck
- Pages load quickly for you and slowly for everyone else — you are probably near the server.
- The site goes down during your busiest periods and comes back on its own.
- You cannot enable HTTPS without an add-on, or the certificate keeps expiring.
- Backups exist as a vague promise rather than a restore you have actually tested.
- Your email deliverability has quietly degraded — usually a shared-IP reputation problem.
- You know the price of hosting but not who operates the server.
That last one deserves emphasis. On cheap shared hosting you do not know who is physically responsible for the machine. During an incident that uncertainty costs hours — and incidents always happen when you are busiest.
What a proper migration looks like
- Measure first. Establish the current baseline so the improvement is provable rather than claimed.
- Move static assets to a CDN. Largest gain, lowest risk, reversible in minutes.
- Add a page cache. Test thoroughly — this is where dynamic content most often breaks.
- Optimise images. Modern formats, real dimensions, lazy loading below the fold.
- Move the origin to a capable host only if steps 2-4 have not been enough.
- Redirect everything. A full URL map so no inbound link, bookmark or ranking is lost.
- Verify, then keep verifying. Real-user monitoring, not just a one-off Lighthouse run.
Most sites that reach step 4 find they never need step 5, which is why the cheap plan they are on was never the problem in the way they assumed.
What good hosting should cost
For a small business site, a fair budget for hosting is not the smallest number available — it is the smallest number that includes managed TLS, tested backups, a real uptime record and someone who answers the phone when something breaks. That is usually somewhere in the low tens of dollars a month, and it is a rounding error compared to the traffic it protects.