Learning on Web Dev Open is free for all.

System Design & Performance > Where the milliseconds goLatency Budget
Phase 06Where the milliseconds go302 of 434

Latency Budget

Rounds against the clock: spend a millisecond budget across a request path and see what your allocation actually delivers.

Drill20 minAI off

Latency Budget

Split 200ms across DNS, TLS, TTFB, download and render without cheating physics.

Play Latency Budget

You should now be able to

  • Allocate a latency budget across a request path
  • Predict the effect of a change before measuring it
Ask the community

Loading…

← PreviousCold starts, regions, and the round trip you forgotWhere the milliseconds goNext →Core Web Vitals as a budget, not a scoreWhere the milliseconds go