Latency is a budget, not a number

2026-08-02

People quote latency as if it were a property of a link. It is closer to a budget you spend across a page load: DNS, connection setup, TLS, first byte, then a dozen round trips for assets. Spending 200 ms in the wrong place is invisible in a ping test and obvious to a user.

Where the time goes

On a cold load, name resolution and the handshake usually cost more than the transfer itself. That is why connection reuse, sane DNS TTLs, and a single round-trip handshake matter more than shaving a millisecond off a warm request.

A useful habit

Before adding capacity, sketch the request timeline. If the same connection serves every asset, the budget belongs to the first request only. If not, you are paying setup cost over and over and no amount of bandwidth fixes it.

Filed under: performance.