Spotify Core Web Vitals
How real Chrome users experience open.spotify.com, from Google's Chrome UX Report: the 75th percentile of visits on every device.
Spotify fails Core Web Vitals
Sep 26 – Oct 23, all devices
INP
455 ms
Needs improvement
LCP
5.9 s
Poor
CLS
0.57
Poor
FCP
4.2 s
Poor
TTFB
982 ms
Needs improvement
INP over time
Weekly p75. The dashed line is the 200 ms "good" threshold.
What the numbers say
- Spotify fails Core Web Vitals on Largest Contentful Paint (5.9 s, good is 2.5 s or less) and Cumulative Layout Shift (0.57, good is 0.10 or less) and Interaction to Next Paint (455 ms, good is 200 ms or less).
- Time to first byte is 982 ms, so most of the LCP time is spent after the first byte: loading the main image, fonts or scripts.
- Among 14 media and community sites we track, Spotify has the 14th fastest LCP.
- INP has held steady around 449 ms over the last 25 weeks.
Keep a site like this from getting slower
Real-user data shows a regression weeks after it ships. Vitalgate runs Lighthouse on every pull request and fails the check when a change breaks budgets like these: LCP ≤ 6.0 s, CLS ≤ 0.57, FCP ≤ 4.2 s.
Other media and community sites
| Site | Core Web Vitals | LCP | INP | CLS |
|---|---|---|---|---|
| YouTube | Fails | 4.7 s | 245 ms | 0.34 |
| Passes | 2.0 s | 144 ms | 0.01 | |
| X | Fails | 4.4 s | 334 ms | 0.07 |
| Fails | 2.5 s | 226 ms | 0.07 | |
| Medium | Passes | 2.4 s | 106 ms | 0.03 |
| Substack | Fails | 2.4 s | 203 ms | 0.02 |
| dev.to | Passes | 1.9 s | 82 ms | 0.00 |
| Hacker News | Passes | 554 ms | 44 ms | 0.00 |
| Product Hunt | Passes | 2.2 s | 195 ms | 0.07 |
| Wikipedia | Passes | 1.2 s | 81 ms | 0.00 |
| The Verge | Fails | 1.4 s | 130 ms | 0.16 |
| Twitch | Fails | 3.1 s | 303 ms | 0.23 |
| Netflix | Fails | 3.7 s | 208 ms | 0.03 |