Learning on Web Dev Open is free for all.

Systems Thinking > Proving it worksLatency Budget
Phase 03Proving it works173 of 434

Latency Budget

Spend a fixed millisecond budget across a request waterfall and find out how quickly a sequential await eats all of it.

Drill22 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

  • Estimate the cost of a dependency chain before writing it
  • Identify which requests can overlap and which genuinely cannot
Ask the community

Loading…

← PreviousBisecting a bug instead of staring at itProving it worksNext →What a module actually isShip something other people install