Introduction
When most people think about Core Web Vitals optimization, they think of:
- Compress images
- Use lazy loading
- Minify CSS/JS
- Install a cache plugin
These are correct but incomplete. Because a significant portion of Core Web Vitals metrics is influenced by hosting infrastructure. In particular, the LCP and INP metrics are directly related to server performance.
In this article we will examine the relationship between Core Web Vitals and hosting numerically and technically.
1. What Are Core Web Vitals? (Quick Recap)
Core Web Vitals consist of 3 main metrics:
| Metric | What It Measures | Target |
|---|---|---|
| LCP | Largest Contentful Paint | < 2.5 s |
| INP | Interaction to Next Paint | < 200 ms |
| CLS | Layout Shift | < 0.1 |
These metrics are direct Google ranking factors.
2. How Does Hosting Affect Core Web Vitals?
The most important relationship:
| Metric | Hosting Effect |
|---|---|
| TTFB | Very high |
| LCP | High |
| INP | Medium |
| CLS | Low |
A page loads in this sequence:
DNS → TCP → SSL → TTFB → HTML → CSS → JS → Render → LCPIf TTFB is high, LCP is automatically loaded late.
3. TTFB → LCP Relationship (The Most Critical Point)
Simple model:
LCP = TTFB + Resource Load + Render DelayExample:
| Scenario | TTFB | Resource | Render | LCP |
|---|---|---|---|---|
| Shared hosting | 900 ms | 1.4 s | 0.8 s | 3.1 s |
| VPS | 250 ms | 1.2 s | 0.6 s | 2.05 s |
| VPS + CDN | 120 ms | 0.9 s | 0.4 s | 1.42 s |
Just by changing the hosting, LCP can go from 3.1 s → 2.0 s. That means passing Core Web Vitals.
4. Real Test Scenario (Before / After)
Test on a WordPress site:
| Infrastructure | TTFB | LCP | INP | PageSpeed |
|---|---|---|---|---|
| Shared | 820 ms | 3.8 s | 280 ms | 58 |
| VPS | 240 ms | 2.1 s | 190 ms | 82 |
| VPS + CDN | 110 ms | 1.5 s | 140 ms | 94 |
This change involved only:
- Hosting migration
- CDN
- Server cache
The frontend stays the same.
5. INP and CPU Relationship
INP = How quickly the page responds after a user interaction.
This depends on:
- CPU
- PHP execution
- Database response
- Server queue
- PHP worker
If CPU throttling is present on shared hosting:
| CPU Status | INP |
|---|---|
| CPU limit in place | 280–350 ms |
| No CPU limit | 120–180 ms |
This is why INP is not purely a JavaScript problem.
6. Core Web Vitals Measurement Tools
| Tool | What It Measures |
|---|---|
| PageSpeed Insights | Lab + Field data |
| Google Search Console | Real user data |
| WebPageTest | Detailed waterfall |
| GTmetrix | Performance analysis |
To measure TTFB:
curl -o /dev/null -s -w "TTFB: %{time_starttransfer}\n" https://site.com7. Core Web Vitals Impact by Hosting Type
| Hosting | TTFB | LCP | INP | CWV |
|---|---|---|---|---|
| Shared | High | Poor | Medium | Fail |
| VPS | Medium | Good | Good | Pass |
| Dedicated | Low | Very good | Very good | Pass |
| VPS + CDN | Very low | Very good | Very good | Pass |
8. The Biggest Misconception: Core Web Vitals = Frontend
Real breakdown of Core Web Vitals optimization:
| Optimization | Impact |
|---|---|
| Hosting / TTFB | 35% |
| CDN | 20% |
| Cache | 15% |
| Image optimization | 15% |
| CSS/JS | 10% |
| Font | 5% |
So more than 50% of Core Web Vitals is on the hosting + CDN side.
9. When Is Hosting the Core Web Vitals Problem?
If any of the following are present, the problem is most likely hosting:
- TTFB > 600 ms
- LCP is high but images are optimized
- INP is high but JS is minimal
- CWV deteriorates as traffic increases
- PageSpeed is low on mobile but good on desktop
- Cache is on but LCP is still high
CONCLUSION
Core Web Vitals is not just frontend optimization. If server response is slow, passing Core Web Vitals is very difficult.
Greatest impact order:
- Hosting (TTFB)
- CDN
- Cache
- Images
- CSS/JS
Most people start optimizing from the bottom.
CTA
To understand this topic better, the following guides are important:
- How to Lower TTFB?
- VPS vs Shared Hosting Performance
- What Is CDN and What Does It Do?
- LiteSpeed Cache Configuration Guide