GoogleChrome / GoogleChrome/lighthouse

Significant differences between CLS in PageSpeed Insights and Chrome DevTools

Open
#16,784 2 comments 0 reactions 0 assignees View on GitHub
bug
Dominant language
JavaScript
Stars
30.8k
Forks
9.8k
Avg merge
1d 20h
Merged PRs (30d)
19

Description

### FAQ

- [x] Yes, my issue is not about [variability](https://github.com/GoogleChrome/lighthouse/blob/main/docs/variability.md) or [throttling](https://github.com/GoogleChrome/lighthouse/blob/main/docs/throttling.md).
- [x] Yes, my issue is not about a specific accessibility audit (file with [axe-core](https://github.com/dequelabs/axe-core) instead).
- [x] Yes, my issue is not answered by [other FAQs](https://github.com/GoogleChrome/lighthouse#faq).

### URL

https://www.orchideen-wichmann.de/de/

### What happened?

PageSpeed Insights CLS: 0.807
Chrome DevTools Lighthouse CLS: 0.008

https://pagespeed.web.dev/analysis/https-www-orchideen-wichmann-de-de/n8hd7g4gh9?form_factor=desktop

Image

### What did you expect?

PageSpeed Insights CLS: 0.807
Chrome DevTools Lighthouse CLS: 0.807

I expected a similar result in Chrome DevTools so that the problem could be debugged more easily.

### What have you tried?

Critical CSS generation with help of npm package penthouse

### How were you running Lighthouse?

PageSpeed Insights AND Chrome DevTools

### Lighthouse Version

latest, I guess

### Chrome Version

_No response_

### Node Version

_No response_

### OS

_No response_

### Relevant log output

```sh

```

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.