GoogleChrome / GoogleChrome/lighthouse
Lighthouse flagging HLS video chunks as text content
- 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://hls-js.netlify.app/demo/?src=https://hls.enniscdn.net/ded3f0fb-0721-49bb-b761-2123d7be9ed7/master.m3u8&demoConfig=eyJlbmFibGVTdHJlYW1pbmciOnRydWUsImF1dG9SZWNvdmVyRXJyb3IiOnRydWUsInN0b3BPblN0YWxsIjpmYWxzZSwiZHVtcGZNUDQiOmZhbHNlLCJsZXZlbENhcHBpbmciOi0xLCJsaW1pdE1ldHJpY3MiOi0xfQ==
### What happened?
When running Lighthouse on a page with an embedded HLS video, the video chunks are incorrectly flagged as "text content". This seems false, especially as the chunks come back with `Content-Type: application/octet-stream`.

They're also flagged as "enormous payloads". Are there any docs pointing to how best to chunk up video for playback? HLS/DASH seems best practise at the moment.
### What did you expect?
For Lighthouse not to interpret video chunks as text content.
### What have you tried?
_No response_
### How were you running Lighthouse?
Chrome DevTools
### Lighthouse Version
9.6.1
### Chrome Version
Chromium: 103.0.5060.114 (arm64)
### Node Version
_No response_
### OS
macOS
### Relevant log output
_No response_
Contributor guide
Assessment
This issue has not been assessed yet.