Cumulative Layout Shift is the metric that makes clients say the page “jumps.” Monitoring CLS without budgets turns into a vibes debate in Slack.
Common CLS sources on client sites
Late webfonts, ads and embeds without reserved space, images without dimensions, banners injected after first paint, and carousels that reflow when slides initialise. Agencies see the same list across stacks; the fix owners differ. A diagnostic run shows the shift. A schedule shows whether last week’s “fix” held.
Budgets and alerts that people honour
Set a CLS budget per template class (home vs article vs checkout). Alert when a monitored lab run crosses the budget, and include the URL and timestamp in the notification. Avoid alerting on every minor flicker if your team will mute the channel; a budget you ignore is worse than a slightly looser budget you respect.
Field CLS from CrUX can disagree with lab CLS. Show both when you have them. Do not average them into one vanity number.
Where GTmetrix still helps
When CLS trips an alert, a filmstrip or careful visual pass in a diagnostic tool still helps you name the element. Scheduled monitoring tells you which release window broke the budget. Use both instead of pretending one screenshot is a monitoring programme.