CLS measures unexpected movement. The usual causes are images without dimensions, late-loading fonts, injected banners and content that appears above existing content after a network response.
Key takeaways
- Target: CLS ≤ 0.1 at the 75th percentile.
- Measure field data before choosing a fix.
- Change one bottleneck at a time and re-measure on a mid-range phone.
- A fast lab score is not a substitute for real-user data.
What Cumulative Layout Shift measures
The browser scores layout shifts by the size of the affected area and the distance it moved. Only unexpected shifts count; a shift caused by a user interaction within 500ms is excluded.
The fixes that usually move the number
- Set width and height (or aspect ratio) on every image and video.
- Reserve space for ads, cookie banners, embeds and async content.
- Use font fallbacks and
font-displayso text does not jump when the web font loads. - Avoid inserting content above the viewport after load.
- Use transform animations instead of animating layout properties.
Symptom, cause and fix
| Symptom | Likely cause | What to do |
|---|---|---|
| Images jump on load | Missing dimensions | Set width/height or an aspect-ratio container |
| Text reflows after fonts load | Web font swap without a metric-compatible fallback | Tune the fallback and preload the font |
| Banner pushes content down | Late consent or promotion script | Reserve a fixed slot before the script runs |
| Page shifts on navigation | Skeleton has a different height | Match the skeleton to the final layout |
How to measure it properly
- Find the shift. Use the Performance panel's Layout Shift regions or WebPageTest filmstrip.
- Check the cause. Inspect the element that moved and the resource that arrived late.
- Test on a slow connection. Throttle the network and CPU to expose late-loading content.
- Fix the space, not the symptom. Reserve dimensions rather than hiding the element.
- Monitor field CLS. Alert on regressions after a design or marketing change.
A practical example
<div style={{ aspectRatio: "16 / 9" }}>
<Image
src="/chart.webp"
alt="Revenue chart"
fill
sizes="(max-width: 768px) 100vw, 800px"
/>
</div>
Common mistakes
- Using
height: autowithout an intrinsic size. - Injecting a cookie banner above the header after hydration.
- Animating
top,left,widthorheightinstead oftransform. - Assuming a good desktop CLS covers mobile.
A 30-day improvement plan
- Week 1. Collect field data and pick the worst route. Write down the baseline.
- Week 2. Fix the largest bottleneck and deploy behind a normal release.
- Week 3. Test on a mid-range phone and a throttled connection; fix regressions.
- Week 4. Compare field data, document the change and add a monitor or budget.
Field data vs lab data
| Source | What it tells you | How to use it |
|---|---|---|
| Field data | What real users experienced | The source of truth for the metric |
| Lab test | A reproducible diagnosis | Find the cause and test a fix |
| Synthetic monitoring | Availability and regressions over time | Alert on a budget breach |
| RUM segmentation | Device, country and route differences | Target the worst segment |
| Server timing | Database, cache and render time | Separate backend from frontend |
Set a performance budget
| Budget | Example starting point | Why |
|---|---|---|
| LCP | 2.5s or less at p75 | The main content must appear quickly |
| INP | 200ms or less at p75 | Interactions must feel responsive |
| CLS | 0.1 or less at p75 | Layout movement erodes trust |
| JavaScript | A route-level KB budget | Prevents bundle creep |
| Images | Responsive sizes and modern formats | The largest common payload |
| Third-party scripts | A named owner and a cap | Uncontrolled tags are a common regression |
Third-party script policy
- Every script needs an owner, a purpose and a review date.
- Load analytics and marketing tags after consent and after the main content.
- Prefer server-side events where they reduce client JavaScript.
- Test the checkout and sign-up with the full tag set enabled.
- Remove tags that no longer answer a business question.
Frequently asked questions
The target is CLS ≤ 0.1 at the 75th percentile. A single fast test is not enough; use the 75th percentile of real page views and segment by mobile and desktop.
No. Start with the routes that matter to revenue or support: checkout, pricing, sign-up, the main product page and the most-read blog template. A fast homepage with a slow checkout is not a fast site.
It depends on traffic. Low-traffic sites can take weeks to accumulate enough data. Use lab tools for immediate feedback, but keep the field metric as the source of truth.
Often yes. Image dimensions, priority, bundle splits, caching and third-party scripts usually deliver more than a visual refresh. Redesign only after the measurement shows the layout itself is the bottleneck.
Sources and further reading
- Fix layout shifts (web.dev)
- Web Vitals (web.dev)
- Next.js image optimisation (nextjs.org)
Related reading
Need a performance audit?
Send the URL and the metric that matters. I will identify the bottleneck, the likely fix and the cheapest way to prove it worked.
How to cite this guide: Nur Hossain Repon, “CLS optimization guide for Next.js and React apps”, Nhrepon Portfolio, reviewed October 2026, https://nhrepon.com/posts/cls-optimization-guide-for-next-js-and-react-apps.





Comments
No comments yet.