The 3 pound hosting plan that costs thousands
Search "cheap web hosting" and you will find dozens of providers offering plans for 2 to 5 pounds per month. Unlimited bandwidth. Unlimited storage. Free SSL. Free domain. It sounds like an incredible deal.
It is not. Those plans rely on overselling — placing far more websites on a single server than the hardware can comfortably support. The provider bets that most sites will be quiet most of the time. When that assumption holds, everyone gets acceptable performance. When it does not — when your site gets a burst of traffic, when a neighbouring site gets attacked, when the server runs maintenance during your peak hours — your site slows to a crawl or goes down entirely.
The hosting provider does not alert you. There is no email saying "your site was slow for 45 minutes today." There is no dashboard warning. The slowdown happens, visitors leave, and you never know. That is the hidden cost.
How overselling actually works
A physical server might have 64GB of RAM, 16 CPU cores, and 2TB of SSD storage. A budget hosting provider places 500 to 1,000 accounts on that server. Each account is "allocated" resources that, if summed, exceed the server capacity by 10 to 20 times.
This is not fraud — it is standard practice. The hosting industry calls it resource allocation based on statistical usage patterns. Most websites use a tiny fraction of their allocated resources most of the time. A personal blog getting 50 visitors a day uses almost nothing.
The problem emerges when multiple sites on the same server need resources simultaneously. During business hours, when traffic peaks across time zones, the server runs hot. CPU usage climbs. RAM fills up. Disk I/O becomes a bottleneck. The hosting provider's resource management software — typically CloudLinux — starts throttling accounts that use the most.
Your site might be one of them. Or you might be fine today but throttled tomorrow because a different site on the server changed. You have no visibility into this. You have no control over it. The only thing you control is whether you know it is happening — and that requires external monitoring.
The five hidden costs of cheap hosting
1. Lost revenue during invisible downtime
Your site loads in 2 seconds normally. During a throttling episode, it loads in 12. Or it returns a 503 error intermittently. Visitors arrive, wait, and leave. If you run an ecommerce store, those are lost sales. If you run a service business, those are lost leads. If you run a SaaS, those are potential customers who will never come back.
According to Cloudflare research, 53% of mobile visitors abandon a page that takes longer than 3 seconds to load. Every second of additional load time reduces conversions by up to 7%. On cheap hosting, you are haemorrhaging conversions during every throttling episode — and you have no idea.
2. SEO damage that takes months to recover
Google measures page speed. Specifically, Google uses Core Web Vitals — including Largest Contentful Paint and Time to First Byte — as ranking signals. When your hosting throttles your site, TTFB spikes. LCP follows. Your Core Web Vitals fail.
Google does not penalise you immediately for one slow day. But consistent poor performance — the kind that cheap hosting delivers during peak hours every day — gradually pushes you down in search results. The site that was ranking on page one slowly drops to page two. Traffic declines. Revenue follows.
Recovering SEO rankings after persistent speed issues takes weeks to months. The 3 pounds per month you saved on hosting costs you far more in lost organic traffic.
3. Customer trust damage you cannot measure
A visitor arrives at your site and it takes 10 seconds to load. They do not think "the hosting provider must be throttling CPU." They think "this business cannot even keep their website running properly." That impression sticks. They go to a competitor whose site loaded in 1.5 seconds. They never come back to you.
You cannot measure this. There is no metric for "visitors who formed a negative impression of your business because your site was slow." But it happens every single time your hosting degrades your performance.
4. Support costs and wasted time
When your site slows down, you troubleshoot. You check your plugins. You clear your cache. You contact your hosting provider and wait 4 hours for a response that says "we do not see any issues on our end." You spend half a day investigating a problem that was caused by someone else's site on the same server.
This happens repeatedly. Every throttling episode triggers another round of investigation. Your time — or your developer's time — has a cost. A few hours of troubleshooting each month quickly exceeds the cost of better hosting.
5. The renewal price trap
That 2.99 per month introductory price? It renews at 12.99. The hosting provider buries this in the terms. The first year is subsidised to get you in. The second year is the real price. By the time you discover it, your site is set up, your DNS points there, and migrating feels like too much work. So you pay the inflated renewal price for hosting that was not good enough at 2.99.
The noisy neighbour problem
Imagine renting a flat in a building where 500 other tenants share a single water supply. Most of the time, water pressure is fine. But every morning when everyone showers at the same time, the pressure drops. Some mornings, the tenant in flat 247 decides to fill a swimming pool and everyone else gets a trickle.
That is shared hosting. Your neighbours — the other sites on the same server — affect your performance. A site running a broken cron job that loops infinitely, a WordPress installation hit by a brute force attack, an ecommerce store running a flash sale — any of these can consume enough server resources to slow down every other site on the machine.
You cannot see your neighbours. You cannot control them. You cannot ask them to stop. All you can do is detect when their activity affects your site — and that requires monitoring.
What cheap hosting providers will not tell you
Hosting providers are not lying when they say "unlimited bandwidth" and "99.9% uptime guarantee." They are being technically accurate in a way that is practically meaningless.
"Unlimited bandwidth" means they will not charge you extra for data transfer. It does not mean your site can handle unlimited traffic. The CPU and memory limits — the things that actually matter — are buried in the acceptable use policy.
"99.9% uptime guarantee" means about 8.7 hours of downtime per year is within the guarantee. And the guarantee typically only applies to complete server outages — not throttling, not slow performance, not the 503 errors your visitors see during peak hours. If your site loads in 15 seconds, that counts as "up."
The hosting provider also will not tell you when they throttle your account. There is no email. No notification. No dashboard alert. The throttling happens silently and lifts silently. Without external monitoring, you will never know.
How to stop losing money to bad hosting
Step 1: Find out if your hosting is throttling you
Set up Uptrue's HTTP monitoringon your site. It checks every 60 seconds and records the response time on each check. Within a few days, you will have a clear picture of your site's real performance — including the throttling episodes your hosting provider never tells you about.
- Sign up at uptrue.io/signup (free plan available)
- Add an HTTP monitor for your homepage
- Set a response time threshold of 3 seconds
- Configure alerts via Slack, email, or Microsoft Teams
- Wait 48 hours and review the response time data
Step 2: Quantify the damage
Look at the data. How many times per day does your response time exceed 3 seconds? During which hours? For how long? Cross-reference with your analytics — is there a correlation between slow response times and higher bounce rates? Calculate the revenue impact.
Step 3: Make the business case for better hosting
A managed WordPress host or VPS typically costs 10 to 30 pounds per month. Compare that to the revenue you are losing during throttling episodes. For most business sites, the upgrade pays for itself within the first month.
Step 4: Monitor after migration
After moving to better hosting, keep monitoring. Verify that response times improved. Track them over time. Better hosting reduces throttling but does not eliminate all performance issues — plugin conflicts, database bloat, and traffic spikes still need attention.
Find out if your hosting is costing you money
Instant health score across uptime, SSL, DNS, security headers, and performance. See your real response times — not what your hosting provider claims.
Check Your Website ScoreWhen cheap hosting is actually fine
To be fair, cheap hosting works for some use cases. A personal blog with 100 visitors a month. A portfolio site you update once a year. A hobby project with no revenue attached. If the site going down for a few hours does not cost you anything — no lost sales, no lost leads, no reputation damage — then cheap hosting is perfectly reasonable.
But the moment your site represents your business — the moment visitors becoming customers matters — the calculus changes entirely. The cheapest hosting plan is the most expensive choice you can make.
Stop guessing. Start monitoring.
Your hosting provider will never tell you when they throttle your site. Your uptime monitor says 100% while visitors see 15-second load times. The only way to know what your visitors actually experience is to measure it — every 60 seconds, from outside your hosting environment.
Uptrue monitors response time on every check, alerts you when performance degrades, and gives you the data you need to make informed decisions about your hosting. Whether you stay on cheap hosting or upgrade, at least you will know what it is actually costing you.
See what your hosting is really doing to your site
Free plan available. HTTP monitoring with response time tracking. Alerts via Slack, email, and Teams. No credit card required.
Frequently asked questions
Why is cheap shared hosting so unreliable?
Cheap shared hosting providers oversell their servers — placing hundreds or thousands of websites on a single machine. Each site shares CPU, RAM, and disk I/O. When any site on the server spikes in traffic or resource usage, every other site suffers. The provider profits by selling more accounts than the hardware can comfortably support, betting that most sites will be low-traffic. When that bet fails, your site pays the price.
What does overselling mean in web hosting?
Overselling means the hosting provider sells more resources than the server physically has. A server with 64GB of RAM might host 500 accounts each "allocated" 1GB — totalling 500GB on a 64GB machine. This works because most accounts use very little at any given time. But during peak hours, when many sites are active simultaneously, there is not enough resource to go around. The provider throttles accounts, queues requests, or suspends sites entirely.
How much does website downtime actually cost?
The cost depends on your business. An ecommerce site making 10,000 pounds per month loses roughly 14 pounds per hour of downtime. But the real cost is higher — lost customer trust, abandoned carts that never return, negative reviews, and Google ranking drops that take weeks to recover. A Gartner study estimated the average cost of IT downtime at 5,600 dollars per minute for enterprises. For small businesses, even a few hours of downtime during a promotion can wipe out the profit margin for the month.
What are noisy neighbours in shared hosting?
Noisy neighbours are other websites on the same physical server as yours. When a neighbouring site gets a traffic spike, runs a badly coded plugin, gets hit by a bot attack, or executes heavy database queries, it consumes shared server resources. Your site slows down or becomes unreachable because someone else on the same server is using more than their fair share. You cannot see who they are, what they are doing, or when they will stop.
How does CPU throttling work on shared hosting?
Hosting providers use software like CloudLinux to enforce resource limits on each account. When your site exceeds its allocated CPU seconds per hour, the provider throttles your PHP processes — slowing them down or queuing them. Your pages still load, but they take 10 to 20 seconds instead of 2. The server returns a 200 status code, so basic uptime monitors say your site is fine. But visitors experience a site that feels broken.
Is the cheapest hosting plan always a bad idea?
Not always — but usually. A personal blog with 100 visitors a month can run fine on cheap hosting. The problem is when a business-critical site relies on it. If your site generates revenue, captures leads, or represents your brand to customers, the risk of throttling, downtime, and slow performance is not worth the 3 to 5 pounds per month you save. The first hour of downtime during a sales promotion costs more than a year of better hosting.
How can I tell if my hosting is throttling my site?
Your hosting provider will not tell you. The only reliable way is external monitoring. Set up an HTTP monitor that tracks response time on every check. When your host throttles your CPU, response times spike from under 2 seconds to 5, 10, or 20+ seconds. Uptrue records response times on every check and alerts you when they exceed your threshold — so you see throttling the moment it starts, not after visitors have already left.
What hosting should I use instead of cheap shared hosting?
For business sites, managed WordPress hosting or a VPS provides dedicated resources that no other site can consume. Managed hosts like Cloudways, Kinsta, or RunCloud handle server optimisation for you. A VPS from providers like DigitalOcean, Linode, or Vultr gives you guaranteed CPU and RAM starting around 5 to 12 pounds per month — barely more than cheap shared hosting but with dramatically better reliability and performance.