Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →Use when auditing slow page loads, heavy assets, or rendering delays related to Minimize cumulative layout shift. Verify the actual bottleneck in DevTools, Lighthouse, or field data before recommending changes.
| Test case | Without → With | Effect | Δ tokens | Δ turns |
|---|---|---|---|---|
| case-02 | ✓→✓ | ＝ Same ✓ | -12% | 0% |
| case-03 | ✓→✓ | ＝ Same ✓ | -8% | 0% |
| case-04 | ✓→✓ | ＝ Same ✓ | -13% | 0% |
| case-05 | ✓→✓ | ＝ Same ✓ | -7% | 0% |
| case-06 | ✓→✓ | ＝ Same ✓ | -13% | 0% |
Layout shifts cause accidental clicks, reading disruption, and user frustration—a good CLS score ensures content stays where users expect it.
Measure CLS using Lighthouse or PageSpeed Insights. Verify score is below 0.1 for good visual stability.
Reserve space for images/embeds with dimensions, use font-display strategies, and avoid injecting content above existing content.
Explain how CLS measures visual stability and why unexpected layout shifts frustrate users and cause accidental clicks.
Review the routes, assets, and loading behavior that affect Minimize cumulative layout shift. Flag exact files, requests, or rendering steps that add unnecessary network, CPU, or layout cost, and describe the measurement method used to confirm the issue.
For full implementation details, code examples, and framework-specific guidance, see references/rule.md.
Rule page: https://frontendchecklist.io/en/rules/performance/cumulative-layout-shift
Other measured skills in the registry, with their headline benchmark lift.