Cache headers, CDNs, and stale-while-revalidate
One header turns a cold cache into an instant page for roughly a third of visits, and it costs nothing to ship. What it does, and where it quietly breaks.
Long reads that follow one mechanism all the way down. Slower to write, and the ones people still link to two years later.
One header turns a cold cache into an instant page for roughly a third of visits, and it costs nothing to ship. What it does, and where it quietly breaks.
Width is time and depth is the call stack. Once those two facts land, most of a trace reads itself.
Sixteen milliseconds, and everything that has to fit inside them before the screen updates.
Invalidation, not repainting. The interesting work is in deciding how little to redo.
Memory cache, disk cache, service worker, CDN, origin. Five places a response can come from, and they disagree more often than you would like.
Download, parse, match, shape, raster. The stage that surprises people is shaping, and it is the one you cannot skip.
The last stage of the pipeline, running on its own thread, which is exactly why transform animations survive a busy main thread.
The bug report says "it gets slow after a few hours". That is a leak, and the heap snapshot will name it.