Before a single byte of HTTP data can flow, TCP demands tribute: one full round trip solely to establish state.
The Sequence
Transmission Control Protocol (TCP) requires both client and server to synchronize sequence numbers and acknowledge connection readiness. This ensures reliable, ordered delivery, but at a strict latency cost.
The Cost of Physics
If a user in Sydney connects to a server in Virginia (RTT ~200ms), the handshake alone consumes 200ms before the TLS handshake even begins. The speed of light in fiber is roughly 200,000 km/s. This physical limitation is why edge CDN termination is non-negotiable for global performance.
| Geographic Path | Fiber RTT (Theoretical) | TCP Handshake (Actual) |
|---|---|---|
| New York to London | ~55ms | ~75ms |
| Tokyo to Los Angeles | ~88ms | ~110ms |
| Sydney to US East | ~160ms | ~210ms |
Mitigation Strategies
- TCP Fast Open (TFO): Allows data to be sent in the initial SYN packet, but suffers from middlebox interference and limited deployment.
- Connection Pooling: Keep connections alive to avoid repeating the handshake.
- Move to QUIC: HTTP/3 abandons TCP entirely, moving transport logic to UDP to allow 0-RTT connection resumption.