Why font loading matters more than it looks
We end up explaining this on discovery calls often enough that it deserved writing down. Font loading is easy to treat as a detail, and that is exactly why it is worth a few minutes of attention.
Speed is a feature people notice only in its absence, and then they leave rather than complain. It rarely shows up as a line item, which is exactly why it slips.
What is actually at stake
Custom fonts commonly block the first paint. In practice this is a scheduling problem more than a technical one. The teams that stay on top of it are the ones who put it on a calendar rather than a wish list.
Self-hosting removes a third-party round trip. There is a version of this that is over-engineered, and it is worth avoiding. Doing this properly once is usually cheaper than doing it approximately three times.
Common failure modes
A sensible fallback prevents invisible text. None of that requires a large budget, only a decision and someone to own it. If two people in the business would answer this differently, that gap is the actual problem.
In practice
Real-world numbers from actual visitors matter more than a score produced on a fast laptop. Three things worth confirming about font loading before you move on:
- Someone can say what the current setup is without going to look
- A sensible fallback prevents invisible text — and you know whether that is true here
- There is a way to tell whether the last change to this helped
The point is not perfection, it is knowing which of these you have consciously chosen to skip.