How to get cumulative layout shift right
We end up explaining this on discovery calls often enough that it deserved writing down. The short answer to cumulative layout shift is that it is mostly a sequence of small decisions, not one big one.
Real-world numbers from actual visitors matter more than a score produced on a fast laptop. It is worth deciding this deliberately rather than inheriting whatever the last person set up.
Why this earns attention
Content jumping around is one of the most irritating experiences. This is the sort of thing that compounds, quietly, in both directions. Anything you cannot measure here, you are deciding by taste, which is fine as long as everyone knows it.
The steps
- Establish what you have today before changing anything
- Set explicit dimensions on images and embeds
- Late-loading banners are a common cause
- Write down the decision so the next person does not re-litigate it
Late-loading banners are a common cause. None of that requires a large budget, only a decision and someone to own it. The failure mode is not doing it wrong, it is doing it once and assuming it stays done.
Where to go from here
In practice
Speed is a feature people notice only in its absence, and then they leave rather than complain. Three things worth confirming about cumulative layout shift before you move on:
- Someone can say what the current setup is without going to look
- Late-loading banners are a common cause — and you know whether that is true here
- There is a way to tell whether the last change to this helped
Worth checking on your own setup before it becomes someone else's problem to fix.