What Is WordPress Multisite?
WordPress Multisite is a feature that lets you manage multiple sites from a single WordPress installation.
Example use cases:
- Agencies (client sites)
- Universities (faculty sites)
- Franchise systems
- Blog networks
- SaaS platforms
How Does Multisite Work?
In a Multisite setup:
- All sites share a single database
- The same WordPress core is used
- Plugins and themes are shared
- Each site has its own content and users
This architecture requires careful attention to performance and security.
Difference Between Multisite and a Single Site
| Feature | Single Site | Multisite |
|---|---|---|
| Installation | 1 site | Multiple sites |
| Database | Single | Shared |
| Management | Simple | Complex |
| Resource usage | Low | High |
Factors Affecting Multisite Performance
Multisite performance depends on the following factors:
- Number of sites
- Traffic volume
- Number of plugins
- Database size
- Cache system
- Server capacity
Database performance in particular becomes critical.
Minimum Hosting Requirements for Multisite
Minimum recommendations for small Multisite projects:
| Resource | Minimum |
|---|---|
| CPU | 2 Cores |
| RAM | 4 GB |
| Disk | SSD |
| PHP | 8.0+ |
Performance issues may occur on hosting below this level.
Recommended Server Stack for Multisite
Recommended setup for high performance:
- Nginx or LiteSpeed
- PHP 8.2
- OPcache
- Redis Object Cache
- MariaDB
- HTTP/3
- NVMe disk
This stack significantly boosts Multisite performance.
Multisite Load Impact (Important)
Load in Multisite systems is not linear.
Example:
- 1 site = 1x load
- 5 sites = 3–4x load
- 10 sites = 6–8x load
- 20 sites = 12–15x load
Reasons:
- Shared database
- Shared CPU usage
- Increased query count
- Object cache demand
- Cron jobs
For this reason, in Multisite projects not only the number of sites but also the total traffic and database load must be calculated.
Is Shared Hosting Sufficient for Multisite?
Generally no.
On shared hosting:
- There are CPU limits
- RAM is shared
- There are I/O limits
- Neighbouring sites have an impact
For this reason, Multisite projects on shared hosting:
- Slow down
- Return 503 errors
- Have a slow admin panel
- Have increased site load times
Shared hosting is generally not recommended for Multisite.
VPS or Dedicated for Multisite?
| System | When |
|---|---|
| VPS | 2–20 sites |
| High-resource VPS | 20–100 sites |
| Dedicated | 100+ sites |
| Cloud Cluster | 200+ sites |
VPS is practically mandatory for growing Multisite projects.
Critical Optimizations for Multisite
What needs to be done for Multisite performance:
- Redis object cache must be used
- Database must be optimized
- OPcache must be active
- Unnecessary plugins must be removed
- CDN must be used
- Resource limits per site must be planned
- wp-cron must be disabled and server cron used instead
- Slow queries must be identified with Query Monitor
Scaling a Multisite without these optimizations leads to serious performance issues.
Conclusion: How to Choose the Right Hosting for Multisite
The most important factor in Multisite projects:
It is not the performance of a single site, but the total system load.
Correct hosting selection:
| Multisite Size | Recommended System |
|---|---|
| 2–5 sites | VPS |
| 5–20 sites | 8 GB RAM VPS |
| 20–50 sites | 16 GB RAM VPS |
| 50–100 sites | Dedicated |
| 100+ sites | Dedicated / Cloud |
Choosing the wrong hosting causes serious performance and downtime issues in Multisite projects.