What you're about to take part in is the result of my two-year journey towards making sense of what latency actually is in the context of a web application, with careful consideration to each vector that contributes to delays on the front end that surface while profiling an application, and also what a front end developer both does and does not have control over when addressing every known factor of latency.
Much of what follows here has been adapted from a live talk that I gave a handful of times throughout 2022 (most notably at All Things Open).
Herein there’s no seasoned experience required of you, the reader, in order to have a meaningful engagement with this multipart series of graphic articles – however a general familiarity with web app development, front end profiling, Observability, and JavaScript will make your forthcoming engagement more comprehensible and enjoyable.
Let's begin.
Part one: redefining latency's scope
Note: Please use the arrow keys, or swipe left and right to advance each frame in the view below:
