Back to all writing

Performance is part of the reading experience

A fast page is not a benchmark in isolation. It is a page that lets the reader reach the idea without unnecessary waiting.

BY TIAGO BALABUCH
A page of reading lines beside a bright signal moving across a calm grid.

Performance numbers are useful, but a reader experiences something more direct: whether the page appears when they need it, whether text shifts while they are reading, and whether an interaction responds when they touch it.

That is why a content site should treat performance as part of its editorial design. A large cover image, a remote font, or an animation can all compete with the words for bandwidth and attention.

Spend work where it helps

For a mostly static article, the browser does not need a full application runtime just to display paragraphs. Generating the page ahead of time gives the reader useful HTML immediately. Interactivity can be added only to the parts that benefit from it.

Images deserve the same care:

  • Choose dimensions that match how the image is displayed.
  • Use descriptive alternative text when the image adds information.
  • Avoid loading below-the-fold images eagerly.
  • Keep decorative motion subtle and respect reduced-motion settings.

Measure the experience, not a trophy score

A score can point to a problem, but the purpose is to make the page more usable. Check the page on a real phone and a slower connection. Make sure the title is visible, the article is readable, and the controls respond without waiting for unnecessary code.

The best optimization is often the one a reader never has to think about.

Share this post