GoogleChrome / GoogleChrome/lighthouse
Treemap calculate amount bundle wrong for duplicated src
- 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/master/docs/variability.md) or [throttling](https://github.com/GoogleChrome/lighthouse/blob/master/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).
### URL
https://g3pfp.csb.app/
### What happened?
Treemap calculate amount bundle wrong when a page has a few elements with the same src. Network tab show only one request, not meter how many duplications you have, but Treemap adds all the numbers together.
[Example](https://g3pfp.csb.app/), [Report](https://googlechrome.github.io/lighthouse/treemap/?gzip=1#H4sIAAAAAAAAE71UuY7bMBD9FYNVAsjUfbkKgm1TOa6CLXiMbK4lkuGRjWH430PZXsRRtPFuk07km3lv3syIR9TvDFodkYHvHqwDvjE9WqGdc9qu4nib605jZikmWscoQp2QpL8TQzwXzo6slhmh3dIZgIHoJSeOjNeCh/Q5LEJOuB4Cuj6ji68XdPFwQTlcsoSSIWZjgS86ZRZXjkXQD0GWKRMopO/76+FBWN2TwxfFR2ohQ85AnPgBZ0pHRH+u1h30iE8qkiErwN+OSJIBbnyzESCSU/UTCxVrT3vBYmthuVNqb39/4a4qGpoWLC1ZVSQkLUhZ1mmak7ZNGW04frJByIBV3jD4fHCjYNpWSZNHyEsffF4v27pMmlN0rxbrgj0WP9mYEinBYApN3WZVOS+VN20zEcqzoowQ24meG5C39p+BasL2qzmapH4vTUyVctYZov/ma/NpVXWS35jHsTXsxeGcr6yp2glDVhbZ6fGG5IOXYdga+MeZAtI/Ql+a7aXebzFTQ2yAMPcprWM/8MsBa6O4Z+OG4kHI+bKypkkmdaVlVc4N9n9qvbpEz8RB+GPMfkm9c0GNQljOrsjpvGZYtalkW91Zp3/J8aKGlEOWvCKXT9dulHvjjMvyjTPGCc7e1/vQ5MfT6RR8K9mJ7RqcE3J7fmp6xcj5nQO53KxRiPoFX7oja4oFAAA=).
### What did you expect?
Network tab show only one request, not meter how many duplications you have, but Treemap adds all the numbers together. I expect that Treemap and Network tab have the same results.
### What have you tried?
_No response_
### How were you running Lighthouse?
Chrome DevTools
### Lighthouse Version
8.4.0
### Chrome Version
95.0.4638.54
### Node Version
_No response_
### OS
MacOS 11.6
### Relevant log output
_No response_
Contributor guide
Assessment
This issue has not been assessed yet.