Add up a TLS certificate chain in bytes, count the records it spans and see the handshake bandwidth it costs at scale.
The TLS Certificate message carries every certificate except the trusted root, each with a 3-byte length prefix. Once the chain exceeds the initial congestion window of about 14.6 kB, the server must wait for an ACK mid-handshake, adding a full round trip to every new connection. Certificate bytes are paid on every full handshake, so a chain with a needless root and an RSA-4096 leaf can add tens of milliseconds to first-byte latency and terabytes of monthly egress at CDN scale.
Certificate Chain Size
chain bytes = leaf + (intermediates × average size) + optional root + OCSP staple + 3 bytes of length prefix per certificate.
Cold-start round trips
extra round trips = ⌈chain ÷ (10 × 1460 bytes)⌉ − 1, using the default initial congestion window.
chain bytes = leaf + (intermediates × average size) + optional root + OCSP staple + 3 bytes of length prefix per certificate. The TLS Certificate message carries every certificate except the trusted root, each with a 3-byte length prefix. Once the chain exceeds the initial congestion window of about 14.6 kB, the server must wait for an ACK mid-handshake, adding a full round trip to every new connection.
Certificate bytes are paid on every full handshake, so a chain with a needless root and an RSA-4096 leaf can add tens of milliseconds to first-byte latency and terabytes of monthly egress at CDN scale.
This calculator takes 6 inputs: Leaf certificate size, Average intermediate size, Intermediate CAs in the chain, Send the root certificate too, Stapled OCSP response, TLS full handshakes per day. The pre-filled defaults are a realistic starting point — replace them with figures from your own environment for a result you can act on.
No. Clients only trust a root they already have in their store, so transmitting it wastes 1–2 kB per handshake and gains nothing. Send the leaf plus the intermediates that bridge to a widely trusted root.