GoogleChrome / GoogleChrome/lighthouse

PageSpeed Insights seemingly cannot download MP4s - negatively affecting score

Open
#17,216 1 comment 0 reactions 0 assignees View on GitHub
bug
Dominant language
JavaScript
Stars
30.8k
Forks
9.8k
Avg merge
1d 14h
Merged PRs (30d)
20

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.raumgut.com

### What happened?

The mp4 video on the page results in:

Failed to load resource: net::ERR_CONNECTION_FAILED

This reduces the "Best Practices" score :-(

Image

### What did you expect?

Either download the video properly or at the very least not mark this as a violation of best practices - it's a normal video.

### What have you tried?

_No response_

### How were you running Lighthouse?

PageSpeed Insights

### Lighthouse Version

(PSI, current version)

### Chrome Version

(PSI)

### Node Version

_No response_

### OS

_No response_

### Relevant log output

```sh

```

Contributor guide

Open the contributing guide

Research direction

Start by reproducing https://www.raumgut.com through PageSpeed Insights and inspect the failed MP4 request alongside the Best Practices result. Determine whether the video download failure is expected or incorrectly treated as a violation; done means the video is handled properly or no longer produces a false violation.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
performance
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.