A tradesperson launches a brochure site: ten pages, a contact form, a few hundred visits a month. A freelance developer recommends a €15/month VPS "to stay safe". The web agency offers €5 shared hosting. Who is right?
The answer rarely depends on technology prestige. It depends on the next credible incident: a plugin crash, a traffic spike after a viral post, or a simple missed backup. For most small sites at launch, shared hosting remains the most rational entry point — not because it is "worse", but because it outsources tasks nobody will do at the start.
Three months later, nobody tested backup restore. Six months later, the site gained twenty plugins and a mini-shop. Shared hosting was not a day-1 mistake — it can become a constraint if nobody set a switch threshold.
What shared hosting actually does for a small site
On shared hosting you share a server with other customers. The provider runs the OS, baseline security patches, the web server and often SSL certificates. You deploy your site — WordPress, static pages, a tiny shop — in a limited but sufficient space.
| Typical need | Shared hosting fits? | Why |
|---|---|---|
| Brochure site, blog, portfolio | Yes | Low load, little server customisation |
| WordPress with 5–10 common plugins | Yes, with care | Watch plugin weight and caching |
| Small WooCommerce shop (< 50 orders/month) | Sometimes | Depends on theme, cache and cron |
| Custom app (Laravel, Node) | No | Needs process control, versions, deploy flow |
| Steady traffic > 50,000 visits/month | Rarely | Noisy neighbours or I/O caps |
Shared hosting is not a "cheap VPS". It is an operating model: you trade flexibility for simplicity and predictable cost.
The trap is not starting on shared hosting. It is staying on shared hosting after the site has changed nature and nobody noticed.
When shared hosting is the right first choice
Three profiles that fit a shared start:
1. No sysadmin available. Nobody to patch an OS, configure a firewall or restore a snapshot at 3 a.m. Paying for a VPS without skills to run it often recreates a badly configured shared account — at higher cost.
2. Budget and timeline are tight. Going live matters more than perfect architecture. A serious European shared plan with SSL and documented backups covers most initial needs.
3. The site is predictable. No imminent media campaign, no 50,000-product catalogue, no heavy server-side processing. Load is readable.
In those cases, saving €10/month on a VPS "just in case" makes sense — if you document what is not included: backup restore, PHP version, SSH, reliable cron.
Limits that show up sooner than expected
Shared hosting becomes a bottleneck when neighbours or contractual caps clash with your site:
- Shared CPU: an automatic backup or WooCommerce import can temporarily saturate resources. Symptom: global slowness with no code change.
- Fixed versions: PHP 7.4 locked while your CMS needs 8.1. Migration impossible without changing product tier.
- Unreliable cron: scheduled tasks late, WooCommerce queues backing up.
- No integrated staging: every update is tested in production by default.
- Limited support: "your site uses too many resources" with no application diagnosis.
These signals do not mean "bad host". They mean product / need mismatch.
Shared vs VPS for a small site: the real switch criterion
Moving to a VPS is not about raw traffic. Compare instead:
| Criterion | Stay on shared | Consider a VPS |
|---|---|---|
| Sysadmin skill | None or occasional | At least one technical owner |
| Server customisation | Not needed | PHP extensions, Redis, workers |
| Isolation | Acceptable | Required (neighbours, compliance) |
| Total cost | < €10/month enough | €15–30 budget + admin time |
| Recurring incident | No | Yes (CPU caps, cron, versions) |
A €5 VPS does not really exist: add hardening time, backups and monitoring. For a small site with no ops team, managed shared or dedicated WordPress often beats a neglected bare VPS.
The summit: shared hosting is not a mandatory step — it is a simplicity contract
Many projects overbuild on day one out of technical pride. Others underbuild by staying two years on shared hosting that no longer matches a running shop. Both mistakes come from the same blind spot: good hosting follows real usage, not the logo on the slide.
Decide and move forward without blind spots
List three plausible incidents in the next six months — WordPress update, traffic spike, form spam — and check how your shared plan actually handles them. Ask backup policy: frequency, retention, restore included or paid, turnaround time. Note PHP version and limits before signing, then set a switch threshold — e.g. if response time stays above 800 ms with no app cause for two weeks. Compare providers via our host directory and comparison tool; for the next step, read Your first VPS: when shared hosting becomes a limitation.
Frequently asked questions
Is shared hosting enough for a small business WordPress site?
Yes, while traffic stays modest, plugins are under control and you accept shared neighbours. Once caching is no longer enough or updates keep breaking production, a VPS or managed WordPress plan is more rational.
What signals mean shared hosting no longer fits?
Variable response times without an app cause, CPU limits during backups, inability to pick PHP version, or need for SSH that is not offered.
Should you avoid shared hosting for sensitive data?
Shared hosting is not banned by GDPR, but it offers less isolation control. For strict contractual requirements, a documented VPS or cloud is easier to defend.
How do you compare two shared plans?
On the same scenario: PHP version, backups, I/O limits, incident support, real cost after year one.
A small site does not need the most powerful server. It needs the product that absorbs the next incident without turning your Monday into a sysadmin course.