There is a clear difference between knowing what polices auto-hébergées is and knowing what to do about it on a Monday morning, facing a real site with three years of history. This article covers the second case.
The mistakes we see most often
Three mistakes recur with surprising regularity: applying a recommendation without checking it fits the context, changing several parameters at once which makes measurement impossible, and giving up after six weeks because nothing moved.
The third is the most expensive. Effects are rarely visible before a full recrawl and re-evaluation cycle, which often takes two to three months on a mid-sized site.
Measure in the field, not the lab
A score obtained on a fibre-connected development machine says nothing about real experience. Field data, collected from actual visits, often reveals a considerable gap.
This is especially true on mobile, where network and CPU variability make averages misleading: look at the 75th percentile, not the mean.
Check before moving on
- Check the rendered source, not just the display
- Measure before, not after
- Automate every repetitive check
- Document the decision, not just the action
- Remove before adding
Visual stability, the detail that irritates
Content jumping during load causes frustration out of all proportion to its technical cause, often trivial: an undeclared image dimension, a badly calibrated fallback font.
These are the cheapest fixes in all of web performance, and among the most perceptible to users.
A budget, or nothing
Without an explicit ceiling, a page grows with every change. Setting a budget — in weight, requests and render time — turns performance into a design constraint rather than an occasional project.
The budget must be checked automatically, otherwise it becomes a polite intention nobody consults.
Weight is not the only culprit
Cutting kilobytes helps, but load order often matters more. A lightweight render-blocking resource costs more than a heavy lazily-loaded image.
Start by identifying what blocks, then what weighs — in that order. The reverse leads to lengthy optimisation of elements with no perceptible effect.
Read next
Going further
This deserves a review every six months: engines change, your content ages, and a setup that was correct last year may now be counterproductive. Schedule the review rather than enduring it.
