What a fast site actually means to someone using it
A perfect performance score and a site that feels slow are entirely compatible. Here is the gap between them.
/ In this article:
Performance scores measure a synthetic load on a simulated device. A customer measures the wait between deciding to read something and being able to.
The number that matters
Time to readable content, on the median device your analytics actually reports — not the flagship phone in the room where the decision is being made.
Optimising for the score rather than the wait is how sites end up fast in the report and slow in the hand.
/ TITANMATTER
Where the time usually goes
- Fonts that block text for hundreds of milliseconds.
- Hero images sized for a desktop retina display, served to a phone.
- Third-party tags, loaded synchronously, that nobody remembers adding.
- Client-side rendering of content that never changes.
What we do about it
Server-render anything static, ship the smallest font subset that covers the copy, and put a budget on third-party scripts that someone has to argue against to exceed.
