Introduction
When a website is slow, most people focus on:
- Theme
- Plugins
- Images
- Cache plugin
But in the real world, the majority of performance comes from the hosting infrastructure. In this article we examine, numerically and technically, which part of performance is in your hands and which part lies on the hosting side.
1. What Makes Up Website Performance? (Real Breakdown)
A page's load time is roughly composed of the following components:
| Component | Control |
|---|---|
| TTFB (Server response) | Hosting |
| Database response | Hosting |
| CPU processing | Hosting |
| Disk I/O | Hosting |
| Network latency | Hosting |
| HTML/CSS/JS size | You |
| Images | You |
| Frontend render | User device |
Critical reality: Most performance problems originate not from the frontend but from server response (TTFB).
2. TTFB: The Clearest Indicator of Hosting Quality
To measure TTFB:
curl -o /dev/null -s -w "TTFB: %{time_starttransfer}\n" https://siteadresi.comRealistic TTFB Comparison
| Hosting Type | Average TTFB |
|---|---|
| Shared hosting | 600–1200 ms |
| Quality shared | 400–700 ms |
| VPS | 150–300 ms |
| Dedicated | 80–180 ms |
Difference: 800 ms
This means:
800 ms × 20 requests = 16 seconds of pure server waitingThat is why simply installing a cache plugin cannot speed up a site.
3. CPU Limit: The Biggest Invisible Bottleneck
In shared hosting environments, typically:
| Plan | CPU Limit |
|---|---|
| Entry | 25% CPU |
| Mid | 50% CPU |
| Good | 1 CPU |
| VPS | 2–8 CPU |
What happens when the CPU limit is reached?
- Site slows down
- Admin panel slows down
- Adding to cart is delayed
- Checkout slows down
- Sometimes 508 Resource Limit error
Real-World Scenario
On a WooCommerce site:
| Condition | Page Load |
|---|---|
| With CPU throttling | 4.8 s |
| Without CPU throttling | 1.9 s |
60% speed difference due to CPU alone.
4. Disk I/O: The Silent Killer of WordPress Sites
WordPress reads from disk constantly:
- PHP files
- Logs
- Cache
- Sessions
- Uploads
- Database
Disk Speed Comparison
| Disk | IOPS |
|---|---|
| HDD | 100 |
| SATA SSD | 500–1000 |
| NVMe SSD | 3000–6000 |
WordPress can perform ~200–400 disk operations per page load.
Calculation:
| Disk | Duration |
|---|---|
| HDD | 3–4 s |
| SSD | 0.8 s |
| NVMe | 0.2 s |
Disk alone can make a 3-second difference.
5. PHP Worker Count: Concurrent User Limit
PHP Worker = How many people can use the site simultaneously.
| PHP Workers | Concurrent Users |
|---|---|
| 1 | 5–10 |
| 2 | 10–20 |
| 4 | 20–40 |
| 8 | 40–80 |
What happens when workers run out?
- Site queues requests
- TTFB increases
- Site slows down but CPU appears idle
This is very frequently misdiagnosed.
6. Simple Load Test (Real Test Scenario)
Test with Apache Benchmark:
ab -n 1000 -c 20 https://siteadresi.com/This test measures:
- 20 concurrent users
- 1000 total requests
- Average response time
- Requests per second
Example Results
| Hosting | Response Time | Req/sec |
|---|---|---|
| Shared | 1200 ms | 16 |
| VPS | 320 ms | 62 |
| Dedicated | 140 ms | 140 |
This difference is created not just by optimization but by infrastructure.
7. Performance Control Distribution (The Most Important Table)
| Performance Factor | Impact | Who Controls It |
|---|---|---|
| TTFB | 30% | Hosting |
| CPU | 20% | Hosting |
| Disk I/O | 15% | Hosting |
| Network | 10% | Hosting |
| Database | 10% | Hosting |
| Cache | 10% | You |
| Images | 5% | You |
CONCLUSION:
~75% of performance is hosting infrastructure.
That is why:
- Changing the theme does not fix it
- A cache plugin alone does not fix it
- Compressing images alone does not fix it
If the infrastructure is poor, the site will be slow.
8. Shared vs VPS vs Dedicated (Real Comparison)
| Feature | Shared | VPS | Dedicated |
|---|---|---|---|
| CPU | Shared | Dedicated | Dedicated |
| RAM | Shared | Dedicated | Dedicated |
| Disk | Shared | Usually Dedicated | Dedicated |
| PHP Workers | Limited | More | Many |
| TTFB | High | Medium | Low |
| Traffic handling | Low | Medium | High |
9. When Should You Upgrade Your Hosting?
If the following conditions exist, the problem is 80% hosting:
- TTFB > 500 ms
- CPU limit warning
- Admin panel is slow
- Site slows down as traffic increases
- Adding to cart is slow
- Checkout is slow
- Cache is active but site is still slow
10. Summary: What Are You Actually Controlling?
| Area | You | Hosting |
|---|---|---|
| Theme | ✓ | |
| Plugin | ✓ | |
| Images | ✓ | |
| Cache | ✓ | |
| CPU | ✓ | |
| RAM | ✓ | |
| Disk | ✓ | |
| Network | ✓ | |
| TTFB | ✓ |
In other words, the majority of your site's speed is controlled by your hosting, not by you.
Performance Optimization Order (The Correct Order)
- Hosting infrastructure
- Server cache
- PHP version
- Database
- Theme & plugins
- Images
Most people do this in reverse.
CONCLUSION
If your website is slow, ask yourself:
"Is my site slow, or is my server slow?"
In most cases the answer is: The server is slow.
CTA
Further guides on this topic:
- VPS vs Shared Hosting Performance Comparison
- How to Reduce TTFB?
- LiteSpeed vs Nginx Performance Test
- What Is a PHP Worker?