Round Trip Latency Budget
Calculator

It's the total time allowed for a request to travel from a client to a server and back, broken down into individual components like network transit time, server processing time, and any intermediate hops, so you can see where the time is actually being spent.

Data cannot travel faster than the speed of light through fiber optic cable, which imposes a hard physical floor on latency between distant locations regardless of bandwidth. This is why a server geographically closer to the user often responds faster than a more powerful server on the other side of the world.

Round-trip time (RTT) measures the time for a signal to travel to its destination and for the response to return, which is what most tools like ping actually measure. One-way latency is half of that in a symmetric network, though real networks aren't always perfectly symmetric in each direction.

Human perception research generally suggests that responses within 100 milliseconds feel instantaneous, while anything beyond roughly 1 second starts to feel like a noticeable delay that disrupts the user's flow. Budgeting individual components (DNS, TLS handshake, server processing, etc.) against that total helps identify where to optimize.

Common techniques include using a Content Delivery Network (CDN) to serve content from a location closer to the user, reducing the number of sequential network round trips a page or app requires, and optimizing server-side processing time so it consumes less of the overall budget.