The 600ms Tax: Why Every TCP Connection Starts with a State Negotiation

TL;DR: A TCP handshake is a mandatory three-step negotiation—SYN, SYN-ACK, and ACK—required to synchronize sequence numbers and reserve memory buffers before data transfer. This protocol overhead adds a minimum of 1.5 round-trips of latency, making persistent connection reuse a critical optimization for reducing time-to-first-byte (TTFB). Fetching a file from a remote server isn't just a matter of bandwidth; it’s a battle against the physics of the network. If your round-trip time (RTT) to a server is 200ms, you aren't waiting 200ms for your data. You’re likely waiting 600ms before the first byte even arrives. This delay isn't a limitation of your fiber line—it’s the intentional cost of establishing a reliable state between two machines over an unreliable infrastructure. I look at this as a "resource reservation tax." Before a single packet of your HTML or JSON is sent, both the client and the server have to agree on exactly how they will track the data. This negotiation is what we cal