FREE The web stack LESSON · The web stack
Deliver the experience as a budget
Accessibility, resilience, observability, and evolution
The web experience is the result of many budgets spent together.
Latency, JavaScript, memory, network transfer, layout stability, accessibility, privacy, and failure recovery all compete for engineering attention. A fast server cannot rescue an unusable keyboard flow; a small bundle cannot rescue a serial dependency chain. Define user-critical journeys, allocate budgets at boundaries, and test on constrained devices and networks.
Optimize the user’s complete task, not a component’s favorite metric.
Hydration can turn delivered HTML into delayed interactivity.
Server rendering may show content before client code has loaded and attached behavior. Large bundles, main-thread work, mismatched markup, and third-party scripts can create an interface that appears ready but is not. Measure real interaction latency, ship less client code, preserve native browser behavior, and progressively enhance critical actions.
Pixels on screen are not proof that the task can be completed.