Website Loading Speed and Bandwidth Requirements
Calculate how page weight affects loading time at different bandwidths. Optimize asset sizes to meet Core Web Vitals targets for LCP and FCP.
Detailed Explanation
Website Loading Speed vs Bandwidth
Page load time is a direct function of page weight and available bandwidth. Understanding this relationship is critical for web performance optimization and meeting Core Web Vitals targets.
Page Weight Benchmarks
| Page Type | Median Size | 90th Percentile |
|---|---|---|
| Simple blog | 1.5 MB | 3 MB |
| News site | 3 MB | 6 MB |
| E-commerce PDP | 4 MB | 8 MB |
| SPA (React/Next.js) | 2 MB | 5 MB |
| Image-heavy portfolio | 5 MB | 15 MB |
Load Time by Bandwidth
For a 3 MB page:
Slow 3G (0.4 Mbps): 3 * 8 / 0.4 = 60 seconds
Fast 3G (1.5 Mbps): 3 * 8 / 1.5 = 16 seconds
4G (20 Mbps): 3 * 8 / 20 = 1.2 seconds
WiFi (50 Mbps): 3 * 8 / 50 = 0.48 seconds
Fiber (1 Gbps): 3 * 8 / 1000 = 0.024 seconds
Note: Real page loads involve multiple round trips (DNS, TCP, TLS, HTTP), so actual times are higher than raw bandwidth calculations suggest.
Core Web Vitals Targets
| Metric | Good | Needs Improvement | Poor |
|---|---|---|---|
| LCP | < 2.5s | < 4.0s | > 4.0s |
| FID/INP | < 100ms | < 300ms | > 300ms |
| CLS | < 0.1 | < 0.25 | > 0.25 |
To achieve LCP < 2.5s on a 4G connection (20 Mbps average):
Max LCP resource size: 20 Mbps * 2.5s / 8 = 6.25 MB
Minus overhead (DNS, TCP, TLS): ~0.5s
Effective budget: 20 * 2.0 / 8 = 5 MB for LCP resource
Optimization Impact
| Technique | Typical Savings |
|---|---|
| WebP/AVIF images | 30-50% of image bytes |
| Brotli compression | 15-25% of text bytes |
| Code splitting | 40-60% of initial JS |
| Lazy loading | 50-80% of below-fold assets |
| CDN (reduce latency) | 100-300ms per round trip |
Budget Planning
For targeting 3G users (emerging markets):
Target load time: 5 seconds
Bandwidth: 1.5 Mbps
Round trips overhead: 2 seconds
Data budget: 1.5 * 3 / 8 = 0.56 MB = 562 KB total page weight
This is extremely tight, requiring aggressive optimization.
Use Case
Frontend developers optimizing Core Web Vitals scores, performance engineers setting page weight budgets, product managers understanding the impact of page size on mobile users, and SEO specialists improving search rankings through performance optimization.