We value your privacy

We use essential cookies to run this site, and analytics and marketing cookies only with your consent. Nothing non-essential loads until you agree. See our cookie policy.

RogueLogic
What we doSEOAEOPPC and paid AIGoogle AdsMeta AdsBing AdsDigital PRAI and automationWeb designCompetitor ReconAnswer monitoringVisibility modelWho we helpManufacturingProfessional servicesEngineeringSaaSLegalHealthcareThinkingInsightsCase notesFAQ hubPricingAbout0117 000 0000
Glossary

What is Cumulative Layout Shift (CLS)?

Cumulative Layout Shift (CLS) is a Core Web Vitals metric that measures how much the visible content of a page moves around unexpectedly as it loads. It scores the visual stability of a page: high CLS means elements jump as images, fonts or injected content load, often causing a visitor to tap the wrong thing. A good CLS is 0.1 or less, measured on real-world field data.

In depth

Cumulative Layout Shift (CLS), explained properly.

CLS measures how much a page's visible content moves around unexpectedly as it loads.
High CLS causes mis-taps and broken trust: buttons and text that jump as images, fonts or banners load.
A good score is 0.1 or less, measured on real-user field data across the page's whole lifespan.
It is a Core Web Vital and a ranking signal, and it matters for AI agents that can only act on stable elements.
It is usually fixable: reserve space for media and embeds, load fonts without reflow, and avoid injecting content above the fold.

What CLS actually measures

CLS quantifies unexpected movement. As a page loads, an image without reserved space can push text down, a late-loading font can reflow a paragraph, or an injected banner can shove a button just as someone goes to tap it. CLS adds up these shifts into a single score, weighted by how much of the screen moved and how far. It is deliberately about unexpected shifts, movement a user did not cause, because those are the ones that break trust and cause mis-taps. It is measured on real users across the whole life of the page.

Why CLS matters

Layout shift is the most viscerally annoying performance problem: the button that moves the instant before you tap it, the article that jumps as you start reading. It is a Core Web Vital and a ranking signal, and it matters even more for AI agents that now browse the web, because an agent can only act reliably on an element that stays put. Unlike loading speed, CLS problems often persist well after the initial load, which is why they are measured across the page's whole lifespan rather than just the first moment.

How CLS is improved

CLS is usually very fixable once diagnosed. The standard causes are images and embeds without dimensions or reserved space, web fonts that reflow text when they swap in, and content injected above existing content, such as banners or ads. The fixes are to reserve space for media and embeds, load fonts so they do not cause a reflow, and avoid inserting content above what a user is already looking at. We trace each shift to its cause and fix it, so buttons and forms stay where a visitor, or an agent, expects them.

How Rogue Logic helps
Core Web Vitals and page speedFast websitesTechnical SEOCore Web Vitals, defined
Common questions

Cumulative Layout Shift (CLS): common questions.

What is a good CLS score?

0.1 or less is good, 0.1 to 0.25 needs improvement, and over 0.25 is poor, measured on real-user field data across the whole life of the page, not just the first load.

What causes layout shift?

Usually images or embeds without reserved space, web fonts that reflow text when they load, and content injected above what is already on screen, such as banners or ads.

Why does CLS matter for AI browsing?

AI agents that browse the web can only reliably act on an element that stays put. A page that shifts under an agent mid-task causes errors, so low CLS helps agents as well as human visitors.

More terms
Core Web VitalsDigital PRE-E-A-TInteraction to Next Paint (INP)Largest Contentful Paint (LCP)Schema markupTechnical SEOTime to First Byte (TTFB)

Want this done properly, not just defined?