Understanding TLS 1.3 Session Resumption

By Marcus Hale · July 14, 2026 · Security

TLS 1.3 collapsed the handshake to a single round trip, but the real latency win for repeat visitors comes from resumption. A client presenting a valid pre-shared key can skip straight to encrypted application data, which on mobile networks can be the difference between a page that feels instant and one that feels broken.

The trade-off lives in forward secrecy. Tickets encrypted with a long-lived server key mean captured traffic can be decrypted later if that key leaks. Operators who care rotate ticket keys on a strict cadence - daily is common, hourly is not crazy - and accept the small CPU cost of more full handshakes.

If you terminate TLS at a load balancer, check whether ticket keys are shared across the pool. A surprise fail-open here silently breaks resumption for half your fleet and shows up only as a mysterious latency regression in percentiles.