You’re on a plumber’s website on your phone, about to tap the “Call Now” button. Right as your thumb lands, an ad banner pops in from the top and shoves everything down. You end up tapping something else entirely. Frustrated, you hit back and call the next result instead. That’s Cumulative Layout Shift — and it doesn’t just annoy your visitors, it costs you calls and Google ranking points at the same time.
Cumulative Layout Shift (CLS) is one of Google’s three Core Web Vitals — the speed metrics that directly feed into search rankings. It measures how much your page moves around while it’s loading. Every time an element jumps, shifts, or pops in unexpectedly, it adds to your CLS score. A score of 0 means nothing moved. A score above 0.25 is considered poor, and Google treats it as a negative ranking signal.
Unlike load speed, which you can feel as a user, layout shift is sneaky. Your site might look fine when you preview it on a fast desktop connection, but on a slower mobile connection where resources arrive in a different order, the same page jumps all over the place.
Layout shift creates two separate problems. First, it directly frustrates visitors — especially on mobile, where tap targets are small and a shifted button is easy to miss. Frustrated visitors leave without calling. Second, Google measures CLS at scale using real Chrome browser data from actual visitors. If enough real users experience bad layout shift on your site, Google logs it and adjusts your rankings accordingly. You don’t get to protest; the data speaks for itself.
Go to pagespeed.web.dev, run your site, and look at the CLS score in the “Core Web Vitals” section:
The diagnostic section below the scores will flag specific elements causing layout shift. Look for warnings about “images without explicit width and height” or “content jumping in from late-loading resources.”
The fundamental solution to CLS is telling the browser how much space each element needs before it arrives — so the page layout is locked in from the start and nothing pushes anything else around. For images, this means always specifying width and height attributes. For fonts, it means using font-display strategies that don’t cause jarring swaps. For third-party scripts, it means loading them in ways that don’t inject content into the main flow.
This is architectural work — the kind of thing that should be baked into how a site is built, not bolted on afterward. A well-built contractor site handles CLS correctly by default, so you’re not constantly patching layout problems every time you add new content or a new plugin.
If you manage your own WordPress site, go into any page builder and check that every image you add has width and height values set. Even rough values are better than nothing. Remove any third-party chat widgets or pop-up tools you don’t actively use — each one is a potential layout shift waiting to happen. Small steps like these won’t solve a deep CLS problem, but they’ll reduce it.
When visitors land on a page that doesn’t jump around, they trust it more. And a page Google sees as stable and well-built is a page Google is more willing to rank.
We build service businesses 500+ page, fast, SEO-ready websites — for $249/month, with a live dashboard so you can watch it climb.
See How It Works →