Black FridayCyber Monday 2026
15Days
19Hrs
16Mins
58Secs
Flat20% OFF

Our biggest sale of the year20% off the first payment on all maintenance plans. Code BF2026

Grab the deal
WordPress

Cumulative Layout Shift (CLS) in WordPress: Causes and Fixes

When a page jumps while it loads, visitors misclick and Google notices. Learn what CLS is and how to fix the images, fonts, embeds and banners behind it.

wpallsolution Updated 7 min read

Cumulative layout shift in WordPress is what you notice when a page jumps while it loads: you start to tap a button and the text moves, because an image, an ad or a banner appeared above it. Google measures this as CLS, one of the Core Web Vitals, and it is also a real usability problem, since people click the wrong thing. This guide explains what CLS measures, what a good score is, and how to find and fix the usual causes on a WordPress site.

Quick answer

According to web.dev, CLS measures how much visible content moves unexpectedly, and a good score is 0.1 or less at the 75th percentile of page loads. The common causes are images and videos without set dimensions, late-loading ads and embeds, web fonts that change the text size, and banners or popups inserted above existing content. Fix them by reserving space: set image dimensions, give embeds a fixed area, load fonts carefully, and overlay notices instead of pushing content down.

How this guide was prepared: it is research-based. We used the web.dev articles on CLS and on optimising it, and the WordPress source, listed under Sources and checked on October 23, 2026. We did not test your site, and a lab score from one test can differ from what real visitors experience.

What CLS measures

A layout shift happens when a visible element changes its start position between two frames. web.dev defines CLS as the largest burst of layout shift scores during a visit. Each shift score is the impact fraction (how much of the viewport the unstable elements affect) multiplied by the distance fraction (how far they moved). The thresholds, measured at the 75th percentile of page loads and split by mobile and desktop, are: good at 0.1 or less, needs improvement above 0.1 up to 0.25, and poor above 0.25. Field data (real visitors) matters most, while lab tests help you find causes.

The decision tree: what is making your page jump?

Flowchart for cumulative layout shift in WordPress: five questions about the score, image dimensions, embeds, fonts and banners
Five questions point to what is moving your layout.
  1. CLS above 0.1 in field or lab data? Find the shifting elements (Step 1).
  2. Images or video without dimensions? Add width and height or an aspect ratio (Step 2).
  3. Ads, embeds or iframes appear late? Reserve space (Step 3).
  4. Text changes size when the font loads? Tune the font loading (Step 4).
  5. Banners or popups push content down? Overlay or reserve space (Step 5).

Symptoms and likely causes

What you seeLikely causeStart with
Content jumps down when an image loadsThe image has no width, height or aspect ratioStep 2
A video or map pushes text down lateAn embed has no reserved spaceStep 3
Headings change size or wrap differently after a momentA web font replaces a fallback with different metricsStep 4
A cookie notice or promo bar shoves the page downIt is inserted into the flow instead of overlaidStep 5
Elements move during an animationThe animation changes layout propertiesStep 5 and the animation note below

5 steps to reduce cumulative layout shift in WordPress

Step 1: Measure and find what moves

Run PageSpeed Insights and read the field data for CLS if your site has enough visitors, then the lab diagnostics for “avoid large layout shifts”, which name the elements that moved. Chrome DevTools can also highlight layout shifts in the Performance panel. Fix one cause at a time and test again. If your slowest part is the main content, see our guide to Largest Contentful Paint in WordPress.

Step 2: Give images and video dimensions

web.dev recommends width and height attributes on images and video, or a CSS aspect-ratio when attributes are not practical, so the browser can reserve the space before the file loads. WordPress core adds dimension attributes to images it outputs, and in its code images need those attributes before it adds loading and priority hints, so the common problems come from theme templates, page builder widgets, CSS backgrounds and custom HTML that leave them out. Check the images that shift and add dimensions or an aspect ratio. Our guide on keeping Elementor sites fast covers builder-specific points.

Step 3: Reserve space for ads, embeds and iframes

Give maps, videos, social embeds, ad slots and forms a fixed height with min-height or aspect-ratio, sized for the smallest expected content. web.dev also notes that keeping a placeholder when no ad is returned avoids a shift from collapsing the space, and that content which arrives late should sit lower on the page.

Step 4: Handle web fonts carefully

When a custom font replaces a fallback, text can change size and move other content. web.dev suggests choosing a suitable font-display value (for example optional), specifying a generic fallback, matching the fallback’s metrics with properties such as size-adjust, and preloading important fonts. Self-hosting only the weights you use also reduces loading work.

Step 5: Do not push content down with banners, popups and notices

Cookie notices, promo bars and popups inserted above content shift everything below them. Either overlay them with fixed positioning, which takes them out of the page flow so they do not push anything, or reserve their space from the start, which also works for a sticky bar because a sticky element keeps its place in the flow. For animations, web.dev advises using transform rather than changing properties such as top or left. If the problem started after an update, check Elementor update broke your website or look for a plugin change with how to find the plugin that broke your site.

Version and hosting differences

  • Page builders and themes decide how much of the markup you can change, so some fixes happen in the builder settings and some in the theme.
  • Caching and optimisation plugins can change when scripts and styles load, which can create or remove shifts, so test after changing them.
  • Mobile and desktop are scored separately; check both.

How to verify the fix

  • Lab tests show a lower CLS and no flagged elements.
  • Field data improves over the following weeks, since it is a 28 day style average.
  • You can load the page on a slow connection without anything jumping.

How to prevent it from happening again

  • Set dimensions for every new image, embed and ad slot.
  • Test new banners, popups and widgets before they go live.
  • Check CLS after theme, builder or plugin updates; see how to update WordPress plugins safely.

Frequently asked questions

What is a good CLS score?

web.dev says 0.1 or less at the 75th percentile of page loads is good, above 0.25 is poor.

Does CLS affect SEO?

CLS is part of the Core Web Vitals, which Google uses as signals, but it is one factor among many. We cannot promise ranking changes.

Why is my lab score different from field data?

Lab tests run once under fixed conditions; field data comes from real visitors, devices and networks.

Can a plugin fix CLS by itself?

Some optimisation plugins help, but reserving space for each element is usually a design and template task.

Related guide: Optimize Images in WordPress: WebP, AVIF, Sizes and Lazy Loading

Related guide: Interaction to Next Paint (INP) in WordPress: What It Is and How to Improve It

What to do next

Find the moving element, reserve its space and test again. If your theme or builder makes this hard, wpallsolution offers WordPress development and WordPress maintenance packages. We cannot promise a score or ranking.

Sources and official documentation

Keep reading

More guides

Need a hand with this?

Tell us what is happening. We reply with honest next steps.

Talk to us