Your shared account lasted eighteen months. Then slowness returned with no visible theme change. Support says you "use too many resources" and offers an upgrade… that looks like the same shared product with a slightly higher cap. That is often what triggers a first VPS: not the urge to "level up", but the realisation that the product can no longer guarantee what the application requires.
Signals that shared hosting has hit its ceiling
Before buying a VPS, check the problem is not application-side — heavy plugin, SQL queries, no cache. If the code audit is clean and symptoms persist, these signals point to infrastructure limits:
| Symptom | Likely shared cause | What a VPS adds |
|---|---|---|
| Slowness at peak hours | Noisy CPU/RAM neighbours | Contractually dedicated resources |
| Late cron jobs | Shared load, priorities | Control of scheduled tasks |
| PHP version locked | Platform policy | Version and extension choice |
| Cannot install Redis | Closed plan | Custom cache / queue stack |
| Slow or paid restore | Standard shared process | Snapshots, owned procedure |
A VPS does not make a site fast. It removes a class of structural blocks shared hosting cannot fix.
What actually changes in your responsibility
On an unmanaged VPS you become co-administrator:
- Security: firewall, OS updates, SSH accounts, fail2ban.
- Services: nginx or Apache, PHP-FPM, database, TLS certificates.
- Backups: nobody will run them unless you configure them.
- Monitoring: disk space, load, expired certificates.
Many first VPS deployments fail here: the site migrates, nobody watches disk, the database fills, outage hits Friday night. The VPS was not "too small" — it was unoperated.
Sizing a first VPS without overbuying
For WordPress or a small PHP API, realistic baselines:
| Profile | Indicative RAM | Storage | Watch points |
|---|---|---|---|
| Optimised blog / brochure | 1–2 GB | 20–40 GB SSD | Page cache, auto OS updates |
| Active WooCommerce | 4 GB minimum | 40–80 GB | Redis or Memcached, dedicated cron |
| Several light sites | 2–4 GB | media-dependent | DB isolation, upload quotas |
| Node app / workers | 2–4 GB+ | log-dependent | Process manager, auto restart |
Start modest with snapshots enabled and a scale-up plan. Doubling RAM costs less than two days down mid-campaign.
Migrating without breaking production
A botched VPS migration costs more than the server:
- Clone first: restore a copy, test DNS via
/etc/hostsor a staging subdomain. - Sync files and database just before cutover; freeze writes if possible.
- Lower DNS TTL a week ahead to limit slow propagation.
- Check cron, outbound mail, certificates — three classic post-migration misses.
- Keep old shared hosting one week read-only while you validate.
The summit: a VPS is a transfer of control, not a promotion
Agencies sometimes sell VPS as aesthetic obviousness. Tech teams sometimes delay too long out of comfort. The right switch comes when the cost of staying (incidents, slowness, undeployable features) exceeds total cost of VPS + admin + backups.
Decide and move forward without blind spots
- Document three shared incidents from the last six months and how they were resolved.
- Calculate total VPS cost: instance + snapshots + monthly admin time.
- Choose managed or not based on who answers at 2 a.m.
- Test restore before shutting down old hosting.
Filter European VPS offers in our directory and cross-read Should a small website really start on shared hosting? to place your path.
Frequently asked questions
At what traffic level should you switch to a VPS?
Traffic alone is not enough. Switch when you need isolation, unavailable software versions, workers or reliable cron.
Is a €5 VPS enough for WordPress?
For a light site yes, with backups and monitoring. For WooCommerce, plan more RAM and object cache.
Should you pick managed VPS the first time?
If nobody has run Linux recently, a managed layer avoids expensive mistakes.
What is the difference between VPS and cloud for a first server?
VPS is fixed and predictable. Cloud is elastic and usage-billed — harder to budget initially.
Your first VPS marks the day when "the host handles it" is no longer a sufficient answer. Make sure you know who takes over.