Network Packet Journey
Follow a packet through the entire network stack - from browser to database and back!
Pro tip: Use keyboard shortcuts - Space to play/pause, R to reset, Esc to close details
Scenario:
Basic HTTP
HTTPS
HTTPS + CDN
HTTPS + CDN (Cached)
Mode:
Live Journey
Ready to Begin!
Press Space or click "Start Journey" below
Pending
Active
Complete
Failed
Journey Stages
1
Browser
10ms
2
DNS Resolution
50ms
3
TCP Handshake
30ms
4
TLS Handshake
100ms
5
CDN / Edge
20ms
6
Load Balancer
5ms
7
Web Server
10ms
8
Application
50ms
9
Database
30ms
9
Network Hops
305ms
Total Latency
610ms
Round-Trip Time
Scenario Comparison
See how different configurations affect performance
| Scenario | Stages | One-Way | Round-Trip | Best For |
|---|---|---|---|---|
Basic HTTP Simple unencrypted HTTP request | 7 | 185ms | 370ms | Development, testing |
HTTPS Encrypted HTTPS with TLS | 8 | 285ms | 570ms | Production, secure data |
HTTPS + CDN With CDN edge server | 9 | 305ms | 610ms | Global users, static content |
HTTPS + CDN (Cached) CDN cache hit - fastest! | 5 | 210ms | 420ms | Repeated requests, optimal speed |
💡 Insight: The CDN cached scenario is 31% faster than the full CDN journey! This is why caching is crucial for performance.
Did You Know?
Speed of Light: Even at the speed of light, a packet takes ~30ms to travel from New York to London (3,500 miles). Network latency is bound by physics!
CDN Magic: Content Delivery Networks cache data at edge servers close to users, reducing latency from 200ms+ to under 20ms!
DNS Caching: Your browser caches DNS lookups for hours, so subsequent requests to the same domain skip the DNS resolution step entirely!
HTTP/3: The latest HTTP protocol uses QUIC (UDP-based) to establish connections faster, combining TCP + TLS handshakes into one step!