Skip to tool
Visual stability diagnostics

CLS Checker and Layout Shift Finder

Run a CLS test on mobile, tablet, and desktop. Check the Cumulative Layout Shift score, replay each shift, and find the elements that moved.

  • Frame-by-frame timeline
  • Viewport-specific shifts
  • Visual element evidence

Element-level CLS diagnostics

Find the elements causing Cumulative Layout Shift

Move beyond a single CLS score and see when content moved, which element shifted, and what changed on screen.
01

Replay every unexpected layout shift

CLS Finder converts a lab test into an interactive layout shift timeline. Scrub through captured frames to see the page before and after each movement, then inspect the CSS selector and bounding box of the affected element. This visual evidence helps separate genuine instability from an element that simply appeared later in the loading process.

Each shift card includes its individual contribution to the cumulative score. Start with the largest shift, open the visual comparison, and trace the responsible element back to its image, embed, font, banner, component, or injected content.

02

Compare mobile, tablet, and desktop CLS

Responsive layouts can produce different shift clusters at different breakpoints. A navigation bar may wrap on a narrow screen, an advertisement may use a different slot, or a desktop hero may become a mobile carousel. The tool tests mobile, tablet, and desktop viewports independently so device-specific instability is not hidden inside one result.

Compare the score, shift count, screenshots, and affected selectors for every viewport. If you also need to identify the largest painted element at each screen size, run the LCP Finder.

CLS optimization

How to fix layout shifts and improve visual stability

Use the affected selector and the timing of the shift to choose a fix that removes the underlying cause.
01

Reserve space for images, ads, and embeds

Images, videos, iframes, advertisements, and widgets can push nearby content when their final dimensions were not known during the initial layout. Add intrinsic width and height attributes, use CSS aspect-ratio, or provide a stable placeholder so the browser reserves the correct space before the resource arrives.

Dynamic slots should have a minimum height that matches the likely content. If a slot can collapse, reserve space only while it is expected to load and avoid removing that space while the visitor is reading nearby content.

02

Control font swaps and injected content

Web fonts can reflow a heading or paragraph when the fallback and final typefaces have different metrics. Preload genuinely critical fonts, reduce unnecessary font variants, and use font metric overrides such as size-adjust when appropriate. These techniques make the fallback occupy dimensions closer to the final font.

Cookie notices, consent managers, recommendations, and personalization should not be inserted above existing content without reserved space. Prefer overlays for temporary notices or render stable containers before asynchronous data arrives.

Testing workflow

Turn a CLS report into a reliable regression test

Combine focused lab diagnostics with real-user data, then retest the same viewports after every change.
01

Use lab and field data together

CLS Finder is designed for diagnosis. It gives you a reproducible page load, captured frames, and element-level evidence that is difficult to obtain from an aggregate field score. Real-user data from the Chrome UX Report shows whether visitors experience a broader visual stability problem across different devices, networks, sessions, and page states.

Check the URL with the Core Web Vitals Checker to review field CLS, use this timeline to locate likely causes, apply the fix, and run the same test again. A good lab result does not guarantee that every real-user path is stable, but it provides a clear baseline for preventing regressions.

Frequently Asked Questions