CLS too high: reduce layout shifts

The shifting element is not always the cause

If a heel jumps down, an image reloaded over it can be responsible without a reserved space. Therefore, observe the time of the shift and which elements appear immediately before it or change their size. Also reloaded fonts and hidden hints can move the layout.

Example: Recognizing the Result

Illustrative example: When loading an advertising space, the article slides downwards. The shifted text element is measured, but the missing space reservation is on the banner above it.

Limit cause and implement correction

Reserve the required space in the layout and test with slow network and empty cache. A fixed height must not cut off longer texts. In addition, control interactions and later loading phases; a quiet screenshot immediately after launch does not prove a stable page.

What makes you recognize a suitable correction

Track the layout shift recording up to the triggering element. Reserve space in advance and also test consent banners, fonts and reloaded content.

Classification and boundaries

When is this indication not a clear error?

A single laboratory measurement does not describe all user states. Classify targeted user interactions and late shifts separately.

Further documentation

web.dev: Optimizing CLS

CLS too high after CMS and cause

Many audit messages can be resolved faster if they are grouped by system, page type and technical cause. CMS indentations are only linked where CLS has a clearly own cause or fixed route in the respective system.

CLS too high in WordPressCheck theme, SEO plugin, page builder, cache plugin and media library. CLS too high in TYPO3Target TypoScript, Site Config, Fluid Templates, Extensions, Language Tree and Caches. CLS too high in ShopwareExamine experience worlds, category templates, product data, variants, sales channels and SEO URLs. CLS too high in ShopifyTarget theme, collections, products, apps, metafields, markets and robots rules. CLS too high in WooCommerceCheck WooCommerce templates, WordPress theme, SEO plugin, product data and cache specifically. CLS too high in MagentoCheck catalog rules, layered navigation, product variants, store views, extensions and cache/indexer. CLS too high in WixTarget SEO panel, dynamic pages, apps, redirects, and automatically generated sitemaps. CLS too high in webflowExamine collections, templates, designer settings, redirects, custom code and sitemap settings.

Frequent causes of this error

JavaScript and performance budgetToo much JavaScript, blocking resources or client-side rendering worsen crawlability and core web vitals. Cache and CDN RulesCaching, CDN, edge rules or minification deliver old, blocked or technically modified pages. Media and image processesImage sizes, alt texts, lazy loading or media URLs are not maintained consistently or technically delivered incorrectly. Theme and page builder outputVisual builders, theme snippets, or design components generate HTML that is incomplete or contradictory to search engines.

Related SEO Errors

Images without dimensionsMissing image dimensions can cause layout shifts LCP too slowA Slow Largest Visible Element Degrades User Experience and Core Web Vitals GZIP is missingUncompressed text resources make pages unnecessarily difficult HTTP/2 is missingModern protocols improve parallel transmission and technical basis

Appropriate Seitenreport checks

This error should not be checked in isolation. The following tools and clusters help to narrow down the cause faster and to cleanly prioritize the affected URL groups.

Image SEO CheckerCheck images, alt texts, lazy loading and file sizes.Open the check -> Performance toolsControl core web hospitals and load time signals.Open the check -> Accessibility toolsCheck alt texts, contrast, forms and usability.Open the check ->

CLS too high: Reduce layout shifts