Who is this for?
This guide is for freelancers, agencies, or businesses managing multiple client sites, especially those moving up from shared hosting or managing clustered websites on a single server.
If you’re exploring VPS hosting, chances are you're trying to consolidate your websites into a more powerful, cost-efficient hosting setup. Maybe you’re frustrated with shared hosting limits or bill shock from hyperscaler clouds like AWS.
Either way, you want a straight answer:
“How many websites can I actually run on a VPS without it slowing to a crawl?”
Let’s break it down.
VPS resources: what determines capacity?
Every VPS plan comes with a specific allocation of CPU cores, RAM, storage, and bandwidth. How far these stretch depends on:
| Capacity driver | What to measure |
|---|---|
| CPU | Peak and sustained CPU, run queue, throttling, and per-request time |
| Memory | Working set, cache behavior, swap, out-of-memory events, and process limits |
| Storage | Database and file I/O latency, IOPS, throughput, growth, and free-space headroom |
| Network | Requests, transfer, connection count, TLS cost, upstream latency, and provider policy |
| Application | Dynamic-page ratio, plugins, jobs, database queries, caching, and error rate |
| Recovery | Backup window, restore time, rollback, monitoring, and acceptable downtime |
Real Virtarix plans, real examples
Here’s how our VPS packages stack up in real-world deployments:
| Virtarix plan | Listed compute profile | Validation before consolidation |
|---|---|---|
| S | 3 vCores, 6 GB RAM | Replay representative traffic and verify CPU, memory, storage, transfer, and recovery headroom |
| M | 6 vCores, 16 GB RAM | Run the same test and document the safe operating threshold |
| L | 8 vCores, 32 GB RAM | Include database, cache, background jobs, backup, and failure testing |
| XL | 12 vCores, 64 GB RAM | Validate tenant boundaries, monitoring, restore time, and blast radius |
| XXL | 16 vCores, 128 GB RAM | Compare consolidation with multiple instances and a scaled architecture before production |
What affects website load on a VPS?
Before you install 20 WordPress sites on a single server, consider these factors:
Site type and traffic
- A static HTML site might use 20MB RAM at idle.
- A WooCommerce store with plugins might spike to 300MB+ per user session.
Stack efficiency
- Apache + cPanel? Heavy.
- Nginx + PHP-FPM + MariaDB? Butter-smooth.
Caching strategy
- Use full-page caching (e.g., with FastCGI or LSCache), object caching (Redis), and CDN like Cloudflare to offload requests.
Database tuning
- Slow MySQL queries and poor indexing can choke performance with just 5 websites. Use query caching, cron cleanups, and separate database users.
Final answer: how many websites can you host?
If you're using a modern stack with caching, CDN, and efficient plugins:
- M plan: 20–30 sites
- L plan: 40–50 sites
- XL plan: 75+ sites
- XXL plan: 100+ sites with high availability setup
Your mileage will vary based on site type, plugins, and tuning — but these are solid ballparks.
Ready to move website performance onto Virtarix VPS?
Compare VPS sizes for websites that need dedicated resources, NVMe storage, root access, snapshots, backups, and traffic headroom.
VPS S
For small WordPress sites
- ✓ 3 cores
- ✓ 6 GB
- ✓ 50 GB NVMe
- ✓ Unlimited
VPS M
For growing WooCommerce or blogs
- ✓ 6 cores
- ✓ 16 GB
- ✓ 100 GB NVMe
- ✓ Unlimited