What Is Round-Trip Time? – Definition and How It Works
Learn what RTT is, why it multiplies through handshakes, and how it sets a floor on request time regardless of bandwidth.
Round-trip time is how long a signal takes to reach a destination and return. It is the unit that protocol costs are counted in, and it is largely fixed by distance.
1. Why RTT Rather Than One-Way Time
Almost every network operation requires a response: an acknowledgement, a handshake reply, an HTTP response. So the meaningful unit is the round trip, and protocol design is largely a matter of minimising how many are needed.
2. Round Trips Multiply
A single HTTPS request on a fresh connection:
| Step | Round trips |
|---|---|
| DNS resolution | 1 (if not cached) |
| TCP handshake | 1 |
| TLS 1.3 handshake | 1 |
| HTTP request and response | 1 |
| Total | ~4 |
At 20 ms RTT that is roughly 80 ms before any content transfers. At 200 ms — an intercontinental path — it is about 800 ms.
The important consequence: on a distant connection, most of the time for a small response is spent on round trips, not on transferring data. Bandwidth is irrelevant there.
3. Distance Sets the Floor
Light in fibre travels roughly 200 km per millisecond, and a round trip covers the distance twice. Add routing that is never a straight line, and 100–200 ms intercontinental RTT is physics plus reality, not misconfiguration.
No optimisation reduces it. Only moving closer does.
4. Reducing Round Trips
Since RTT is fixed, the lever is how many round trips you need:
- Reuse connections. Keep-alive removes the TCP and TLS handshakes from every request after the first — the single largest saving available.
- Cache DNS. Removes one round trip per new hostname.
- TLS session resumption, reducing the handshake cost on reconnection.
- HTTP/2 or HTTP/3 multiplexing, so many requests share one connection.
- QUIC, which combines transport and TLS into a single handshake.
- Fewer requests — one API call returning fifty records instead of fifty calls.
Point 1 dominates. A client that opens a fresh connection per request pays three extra round trips every time, and fixing it is a one-line change.
5. Proxy Hops Add Round Trips
Each intermediary is another leg. A request through a proxy in another region travels client → proxy → target and back, so the total path can be far longer than the direct one.
For a residential proxy, the exit is a consumer connection with its own latency characteristics, which adds more still.
This is why proxy location should be chosen by proximity to the target, not merely by which country is permitted. A permitted-but-distant exit can double request time.
6. Measuring It
ping -c 20 example.com # ICMP RTT, if not filtered
curl -o /dev/null -s -w 'connect=%{time_connect} tls=%{time_appconnect} ttfb=%{time_starttransfer}\n' https://example.com
time_connect approximates one RTT, so it is the cleanest available estimate when ICMP is blocked. The gap between time_appconnect and time_starttransfer is the server's own processing plus one more round trip — useful for separating network cost from server cost.
7. Where RTT Matters Most
Many small requests. Dominated entirely by round trips. Batch them.
Serial dependent requests. Each waits for the last, so RTT multiplies by chain length — the classic waterfall.
Browser page loads. A page fetching many resources sequentially pays RTT repeatedly, which is why resource blocking helps latency as well as bandwidth.
Rendering waits. Waiting for network idle means waiting for the slowest of many round trips.
Large single transfers, by contrast, are bandwidth-bound and barely care about RTT.
8. Summary
Round-trip time is the time for a signal to reach a destination and return, it is largely fixed by distance, and protocol costs are counted in it — a fresh HTTPS request needs around four round trips before any content arrives.
Since RTT cannot be reduced, reduce the number of round trips: reuse connections, cache DNS, resume TLS sessions, multiplex, and batch requests — and choose proxy exits near the target, because every hop adds a full leg to the path.