At a glance the headline numbers for Media source
Where media files come from: same origin vs third party.
35.2% of media files stream from third parties.
The media source mix who uses what, and how fast each group loads
Media source. On the fleet: 64.8% self, 35.2% third party. 6.7% of sites use at least one self.
Self leads by count (64.8%) and by bytes (72.4%). computed
Passing INP per bucket every category and count level at once - color is the pass rate
Each row is a category, each column its own count bucket (few on the left, many on the right); the cell is the share of those sites passing INP.
No category moves the INP pass rate much, however many a site ships. computed
Few vs many - does quantity cost INP? the pass rate with few vs many of each category
Per category: the pass rate among pages with FEW of it (hollow ring) against pages with MANY (solid dot), worst trend first. Thin buckets are excluded from the endpoints.
Quantity barely moves INP here. The worst trend is Self, at 100 points. computed
Why this matters for the Core Web Vitals, and where to start fixing it
Video files are the biggest assets a page can carry, and the source decides who controls their delivery: the cache rules, the compression, the range requests that make seeking work. Third-party video also means another connection, usually for the largest download on the page.
For embedded players the source question disappears behind the iframe, and the facade pattern beats both options: a poster image until the visitor clicks. Host video yourself only with real video infrastructure behind it. Adaptive bitrates do not happen by accident.
How does this affect the Core Web Vitals?
The choice barely moves the LCP: 86% pass at best, 85% at worst. This signal does not separate passing sites from failing ones.
Chrome field data from 94,910 sites, representing millions of real page loads. How we measured.