Cumulative layout shift for small teams

This is one of those topics that looks small until it costs you something. Most advice about cumulative layout shift assumes a team that does not exist at your size. Here is the version that does not.

Performance work is mostly subtraction, which makes it unpopular and effective. Doing this properly once is usually cheaper than doing it approximately three times.

What to keep

Content jumping around is one of the most irritating experiences. Getting it slightly wrong is survivable. Ignoring it entirely is not. Assume whoever inherits this will have half your context and none of your patience.

What to drop

Process that exists to coordinate ten people is overhead when there are two of you. The cost of getting this wrong is rarely visible on the day it happens.

The practical version

Late-loading banners are a common cause. It is worth being explicit about, because assumptions differ quietly. The failure mode is not doing it wrong, it is doing it once and assuming it stays done.

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

If any of that sounds like a description of your current setup, it is fixable.