Packery results in significant cumulative shift score
Open
- Dominant language
- JavaScript
- Stars
- 4.3k
- Forks
- 324
- PR merge metrics
- No merged PRs in 30d
Description
Perhaps unavoidably so, Packery drags my site down with a significant cumulative shift (CLS) score during Lighthouse tests. Has anyone found a way around this?
Contributor guide
Research direction
Start by reproducing the reported Packery layout in a Lighthouse test and measure its cumulative layout shift. No files or tests are named; done means identifying whether Packery causes the significant CLS and documenting or implementing a verified way around it.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend, performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100