Preview unavailable[CATEGORY / ARCHIVE]
Uncategorized.
Performance culture, browser folklore, and the small details that make a site feel fast.
We Benchmarked Our Own Site and It Was Humbling
We build shirts about performance culture. It would be a little rich to do that and never actually check our […]
Read the full dispatch[ARCHIVE_INDEX]
MORE FROM THE
WORKBENCH.
What Your Favorite HTTP Status Code Says About You
You don’t choose your favorite HTTP status code. It chooses you, usually during a formative debugging session sometime in your […]
Read articleAn Oral History of the Loading Spinner
Nobody agrees on who invented the loading spinner, and everybody agrees it has ruled their life since roughly the dial-up […]
Read articleTTFB: A Love Story
Time To First Byte is not a glamorous metric. It doesn’t have the visual drama of a layout shift or […]
Read articleThe Five Stages of Waiting for a Lighthouse Score
There is a very specific kind of silence that happens in the seconds between clicking “Analyze page load” and the […]
Read articleWhy We Made a Shirt About Cache Misses
We didn’t set out to start a merch brand. We set out to fix a website that loaded like it […]
Read article[WATCH_LIST / CHROME DEVELOPERS / 2020]
A useful hour
with the waterfall.
Core Web Vitals can turn into a wall of acronyms fast. This Chrome Developers talk with Addy Osmani is a grounded starting point: watch it with a page open beside you, then follow one problem through its request, render, and interaction path.
Three notes to keep
- Measure a real page before deciding which change matters.
- Give the browser enough information to make a stable layout.
- Fix the work a visitor actually waits on before polishing the rest.
A 2020 Chrome Developers session with Addy Osmani.









