Network Latency Budget Calculator
Set a target response time, add up the latency each stage consumes (DNS, connect, server, transfer, render) and see how much of the budget is left.
How it works
Remaining = target − (DNS + connect + server + transfer + render)
A latency budget is a top-down design tool: pick the response time users should feel (say 200 ms) and then allocate it across every stage a request passes through. Adding the stages up and subtracting from the target tells you at a glance whether the design fits and which stage is eating the budget. It turns vague "make it faster" goals into a concrete per-component target you can hold each layer to.
Worked example
With a 200 ms target and stages of 20 (DNS) + 40 (connect) + 60 (server) + 30 (transfer) + 20 (render) = 170 ms, you have 30 ms of headroom (15% of the budget spare). If server processing rose to 100 ms, total would be 210 ms — 10 ms over budget, flagging the server as the stage to optimise.
Frequently asked questions
What is a good total latency target?
Interfaces feel instant under about 100 ms and still responsive up to ~200–300 ms for a full request. Beyond a second, users perceive a clear wait. The right target depends on the action, so set it from the experience you want, then budget backwards.
Why budget latency per stage instead of measuring the total?
A single total tells you whether you passed or failed but not why. Allocating a budget to each stage turns performance into an accountable target per component, so a regression points straight at the layer that overspent.
Related calculators
This calculator is for educational purposes. Double-check important results before acting on them.