Break an end-to-end response-time target into network, edge processing, origin, and client-rendering components. This calculator shows how much latency remains, whether the target is exceeded, and which entered component consumes the largest share of the budget.
Budget utilization is the component total divided by the target.
A positive margin indicates room within the stated target; a negative margin indicates the response path exceeds it by that amount.
Use comparable percentiles for every component—mixing averages with p95 or p99 timings produces a misleading budget.
A 200 ms target with 45 ms network, 20 ms edge, 70 ms origin, and 40 ms client time uses 175 ms. The result is 25 ms remaining, or 87.5% of the budget used.
It uses the inputs, formula, units, and independence assumptions shown on this page. Change the inputs to match your own system or experiment.
Use representative averages for planning, preserve headroom where applicable, and test multiple plausible scenarios instead of relying on one point estimate.
No. The result is a planning estimate. Validate it with measured data, monitoring, load tests, or an experiment-design review as appropriate.
The calculator checks values required by the formula and displays an error instead of returning NaN or Infinity. Valid zero values remain available where they are meaningful.
Tools may use different statistical approximations, unit conventions, rounding rules, priors, confidence definitions, or operational headroom assumptions.
| Variable | Unit | Meaning |
|---|---|---|
| Target | ms | Maximum end-to-end response time |
| Components | ms | Non-overlapping parts of the response path |
| Margin | ms | Target minus total component time |