Jump to
Sep 01, 2026
VPS vs shared hosting_ when the cheap plan starts costing money
Most sites do not outgrow shared hosting on a tuesday afternoon with a warning email. they outgrow it slowly, and the first symptom is not downtime, it is a checkout that takes four seconds instead of one. the honest answer to the VPS vs shared hosting question is that shared hosting is fine for a large number of sites, and expensive for a specific kind of site. this article gives you the thresholds. studio ubique is a web design and SEO agency from Zwolle, active since 2012, building custom websites, webshops and applications for dutch smes and international clients.
Shared hosting is not slow. It is unpredictable, and unpredictability is the thing that quietly eats your conversion rate while every graph still looks green.
What shared hosting and a VPS actually are
Shared hosting means your site sits on one physical server alongside dozens or hundreds of other sites, sharing processor time, memory and disk. A VPS, virtual private server, carves that same machine into isolated slices with guaranteed resources of their own. Same hardware, different rules about who gets what.
The practical difference is not raw power. It is predictability. On shared hosting, someone else’s badly written import script can consume the processor for ninety seconds and your homepage waits its turn. This is called the noisy neighbour effect, and it is the reason your site is fast in the morning and sluggish at four in the afternoon for no reason you can find in your own logs.
Studio Ubique works from Zwolle since 2012. In that time the hosting question has changed shape twice: first everyone wanted the cheapest plan, then everyone wanted cloud, and now most people just want to know which one stops the phone ringing. Studio Ubique builds custom websites in WordPress, Vue.js, Node.js, Next.js, NestJS and Laravel, and the hosting answer differs per stack. A brochure site in WordPress with six pages and two plugins genuinely does not need a VPS. A Node.js application needs one by definition, because shared hosting rarely runs persistent processes at all.
Performance: where shared hosting quietly falls over
Shared hosting fails on concurrency, not on speed. A single visitor loading a single page gets a perfectly acceptable response. Twenty simultaneous visitors, each triggering database queries, is where the limits show. Most shared plans cap the number of PHP processes that can run at once, and when that cap is hit, requests queue.
You see this in TTFB, time to first byte, meaning how long the server takes before sending anything at all. Under load, TTFB on a crowded shared plan can drift from 200 milliseconds to well over a second, which pushes LCP, largest contentful paint, past the 2.5 second threshold Google treats as good in Core Web Vitals (web.dev, 2024). The page did not get heavier. The server just got busier.
Studio Ubique projects target Lighthouse 90+ on mobile. Reaching that score on a quiet shared server is straightforward. Holding it during a Friday afternoon campaign is where the plan matters. That is the tell.
Caching hides a lot of this, and honestly caching is underrated. A static page served from cache does not care what plan you are on. But logged-in users, cart pages and checkout bypass cache by design, which is exactly why webshops feel the pinch first while their marketing pages still score beautifully.
Decision box
- Best if: your site handles carts, logins, bookings or search, gets more than roughly 25.000 monthly visits, or runs anything that needs a persistent process
- Not ideal if: you run a small content site with heavy caching, stable traffic and nobody internally who wants to think about servers
- Likely overkill when: you have a five page brochure site, fewer than 3.000 visits a month, and your only complaint is that a plugin is slow
Security: isolation is the real difference
A VPS is not automatically more secure. It is more isolated, which is a different thing, and the distinction matters because isolation protects you from other people’s mistakes while doing nothing about your own.
On shared hosting, the risk that gets underestimated is cross-site contamination, where malware on one account on the server spreads to neighbouring accounts through shared directories or weak permissions. Sucuri’s website threat research has reported for years that a meaningful share of reinfections trace back to other sites on the same server rather than the site being cleaned. A VPS removes that entire category of problem. It does not remove outdated plugins, reused passwords or an admin account that belonged to a freelancer in 2019.
Here is where reputable shared hosting has genuinely improved: account isolation, automatic core updates and managed firewalls are standard now at the better providers. Meanwhile an unmanaged VPS with a default SSH configuration and no automatic patching is measurably worse than a decent shared plan. You bought a private room and left the door open.
Studio Ubique offers 99.9 percent uptime across hosted sites, and most of the work behind that number is boring: patch schedules, backup verification, and checking that the restore actually restores.
Scalability: what changes when traffic grows
Scaling on shared hosting means switching to a bigger shared plan, which usually means the same constraint with a higher number attached. Scaling on a VPS means adding processor cores or memory, and often keeping the same server while you do it.
What actually changes when a site gets busier is who has to make decisions. On shared hosting nobody does, until support emails you about resource limits. On a VPS somebody has to look at graphs and choose. That someone is either you, an internal developer, or an agency. If the answer is “nobody”, a VPS will not help you.
Three situations reliably break shared hosting: a newsletter to 20.000 subscribers landing at once, a product launch picked up by a large account on LinkedIn, and a background import running while normal traffic continues. All three involve concurrency, not volume. A site can serve 80.000 monthly visits comfortably and fall over at 400 concurrent visitors on a single evening.
The unpopular part: most sites that migrate to a VPS were never resource-constrained. They were plugin-constrained. Moving a bloated WordPress install to a bigger server buys maybe 30 percent and costs you a monthly bill forever, when deleting four plugins and fixing the database would have bought more for nothing. Upgrade the hosting after you have cleaned the site, not instead of it.
Cost, effort and who does the server work
Shared hosting runs roughly 5 to 15 euro per month. A VPS starts around 10 to 20 euro unmanaged, and 40 to 120 euro managed. The number that catches people out is not the server, it is the hours.
An unmanaged VPS is a small system administration job. Security updates, firewall rules, PHP version upgrades, mail delivery, backups, monitoring. None of it is difficult, all of it is regular, and it is the kind of work that gets skipped in a busy quarter and remembered during an incident. Studio Ubique rates are 60 to 65 euro per hour, so it takes very few emergency hours to make a managed plan look reasonable in hindsight.
This is where Managed web hosting sits: the server is a VPS, but the patching, backups and monitoring are somebody’s actual job rather than an unassigned intention. Studio Ubique works with care, growth and partnership models, not SLAs, which mostly means the conversation is about what the site needs rather than about response time clauses.
One project sticks in memory: a WooCommerce shop moved to a VPS after months of complaints about slow order pages. The VPS helped a little. What actually fixed it was discovering an abandoned cart plugin writing a row to the database on every single page view, including bot traffic. Two years of that. The server was never the problem, it was just the thing that got blamed.
How to migrate without breaking things
Migration goes wrong in three predictable places: DNS timing, email, and something hardcoded in the database that nobody remembered. Plan around those and the rest is mechanical.
Lower your DNS TTL, time to live, to five minutes at least 24 hours before the move, so the switch propagates quickly instead of over two days. Copy files and database to the new server, run the site on a temporary address, test checkout or forms with a real transaction, then switch DNS during your quietest hour. Keep the old server running for a week. Not for a day. A week.
Email is the sneaky one. If mail runs on the same host, moving the site can move the mail records with it, and nobody notices until an invoice bounces. Check the MX records separately, before anything else.
What to monitor monthly
- Server memory and processor usage at peak hour, not average across the month
- TTFB on one cached page and one uncached page, so you can tell cache from server
- Backup restore test on a staging copy, at least once a quarter but check the backups exist monthly
- Security patch status for PHP, the operating system and WordPress core
- Uptime, with an alert that reaches a human, not an inbox nobody reads
Shared hosting limits show up as concurrency problems rather than raw slowness, with time to first byte rising under load and pushing largest contentful paint past the 2.5 second threshold Google treats as good (web.dev, 2024). A VPS provides isolated resources and predictable behaviour, but only pays off when the site is genuinely resource-constrained. Studio Ubique advises cleaning plugin and database bloat before upgrading hosting.
FAQs
Is a VPS always faster than shared hosting?
No. A well-cached site on a good shared plan can outperform a badly configured VPS, because speed comes from what the server has to do per request, not from how much hardware sits behind it, and a VPS only wins clearly once concurrency is the bottleneck.
How many visitors before i need a VPS?
There is no clean number, but as a rough guide, sites above roughly 25.000 monthly visits with dynamic content, or any site with carts, logins and search running uncached, tend to hit shared hosting limits before that traffic level feels impressive.
What is the difference between managed and unmanaged VPS hosting?
Unmanaged means you handle updates, firewall, backups and monitoring yourself, while managed VPS hosting means a provider or agency does that work, which usually costs 30 to 100 euro more per month and saves considerably more than that during an incident.
Can i move from shared hosting to a VPS without downtime?
Practically yes, if you lower your DNS TTL beforehand, run the site on a temporary address until it is verified, switch during a quiet hour and keep the old server live for a week so anything still resolving to it keeps working.
Does a VPS help with Google rankings?
Indirectly. Faster and more stable server response improves Core Web Vitals, which is a ranking signal, but if your slowness comes from unoptimised images or heavy plugins rather than server load, the VPS will change your bill more than your rankings.
The unnoticed slowdown
Shared hosting rarely announces the moment it stops being enough, so most sites carry a slow checkout for a year before anyone measures it. That year has a price, and it is not on your hosting invoice.
