Why fast websites are a writing tool

Most performance advice is framed as engineering hygiene: compress this, defer that. But the reason to care is simpler. A page that arrives late is a page that is read less carefully, and the loss lands on the writing first.

The cost of waiting

Readers don’t experience milliseconds; they experience hesitation. When a headline appears before the body text, the eye starts and stops. When a font swaps mid-sentence, attention resets. Every reflow is a small interruption you didn’t intend to write.

• A 2.5s first paint costs roughly a third of mobile readers.
• Layout shift after paint is worse than a slower, stable paint.
• Images below the fold should never block the first sentence.

Perceived speed

The goal is not a benchmark score. It’s the impression that the page was already there. That impression comes from three things: stable layout, text before decoration, and no work happening after the reader begins.

Design the first 200 milliseconds and the rest of the page will forgive you.

Notes from a rebuild, 2024

A checklist that fits on a card

1. One typeface, two weights, preloaded.
2. Reserve space for every image with an aspect ratio.
3. Ship no JavaScript the article doesn’t need.

Fonts and layout shift

Webfonts are the most common cause of visible instability in a blog. The fix is unglamorous: fewer files, matched fallback metrics, and a size-adjust that keeps line breaks identical before and after the swap.

@font-face {
  font-family: "Geist";
  font-display: swap;
  size-adjust: 104%;
  src: url(geist.woff2) format("woff2");
}

What to cut first

If you only do one pass, sort every asset by bytes and ask what it adds to comprehension. The answer is usually “nothing”, and the table below is where most blogs find their first second.

None of this makes the writing better. It just makes sure the writing is what the reader meets first.