The Almost-Complete Guide to Cumulative Layout Shift

CLS Beyond the Scoreboard

Most of us know Cumulative Layout Shift by the annoyance it causes: you’re about to tap a link, an ad slides in, and you end up somewhere else entirely. It’s the page moving under your cursor, or losing your spot mid-article. Google’s Core Web Vitals metric tries to put a number on that feeling — but as Jess B. Peck explains, it’s a proxy, not a perfect measure.

CLS is essentially a three-dimensional equation tracking how often elements shift and by how much, all to approximate a user’s perception of instability. It’s useful for flagging problem areas, not for quantifying exactly how irritating a page is. Peck’s point is that the metric is more diagnostic than judgmental — it tells developers where users might be suffering, not precisely how much. Even a site as polished as Google can trip over it; she describes tapping an element just as it appeared, which sent her to the wrong page.

That gap between measurement and reality is why some in the community warn against treating CLS as a target to be optimized at all costs. Chris Coyier has worried that focusing on the numbers might lead to “tricky strategies” that game the metric while slightly degrading the actual experience. Harry Roberts echoed the concern, suggesting that chasing the score can pull attention away from what truly matters.

What we’re really after, as web developers, is less misery for the people using our sites. CLS is a helpful indicator, but it’s not the whole story. Jeremy Keith put it succinctly: the numbers are a proxy for user experience, and pain or frustration are not easily reducible to a score. The map is not the territory.

That doesn’t mean the metric is useless — just that it shouldn’t be obsessed over in isolation. A page with a perfect CLS score can still feel broken if other factors are off, and a page with a slightly imperfect score might still be a joy to use. The point is to fix the underlying instability, not to polish the measurement. And while some may try to work the system for SEO, the responsibility of honest developers is to keep the focus on the actual experience, not just the numbers that approximate it.