GoogleChrome / GoogleChrome/lighthouse

Inconsistent Media Resource Count Between resource-summary and network-requests Audits

Open
#16,113 1 comment 0 reactions 1 assignee Claimed by @connorjclark View on GitHub
docs P3
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

http://www.mercedes-benz.com/

### What happened?

The `resource-summary` and `network-requests` audits do not have the same number of items with `resourceType` set to Media. In `resource-summary`, there are 2 items, whereas in `network-requests`, there are actually 3 items with the media type. I noticed that there is an item with a `blob` URL in the network requests but couldn't find any documentation stating that this `blob` should not be counted in the `resource-summary`.

I have uploaded the report with the information here: https://gist.github.com/LarsFlieger/f6671b59bffdc768a6b4624aefc8f00c

### What did you expect?

I expected the number of items with `resourceType` Media to be consistent between the `resource-summary` and `network-requests` audits.

### What have you tried?

I have reviewed the audit details and checked the documentation but could not find any information explaining if `blob` URLs in network requests should not be counted in the `resource-summary`.

### How were you running Lighthouse?

PageSpeed Insights

### Lighthouse Version

12.0.0

### Chrome Version

125.0.6422.154

### Node Version

_No response_

### OS

_No response_

### Relevant log output

_No response_

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.