Website readiness profile · Snapshot 23 October 2026
spotify.com
spotify.com's public homepage, certificate and DNS checked against 31 practices and compared with 277 Audio & Music Streaming sites.
- Readiness index
- 81/100
- Ahead of
- 95%
- Practices observed
- 23/30
- Popularity band
- Top 1K
Audio & Music Streaming median 66
of measured Audio & Music Streaming sites
1 of 31 could not be measured
Chrome UX Report top-sites list
Readiness by lane
Green: spotify.com. Thin bar: Audio & Music Streaming peer median.
Enable
92/100
Peers 84
Harden
86/100
Peers 55
Accelerate
59/100
Peers 64
Recover
100/100
Peers 8
Priority fixes for spotify.com
Ordered by impact and by how common each practice is among peers.
Priority 1 · Accelerate
Modern image formats in use
Observed: The homepage had 84 images and none used WebP or AVIF.
Why it matters: WebP and AVIF are typically much smaller than JPEG or PNG at similar quality, and images are often the heaviest part of a page.
What to do: Serve WebP or AVIF with a JPEG or PNG fallback, either through an image CDN or by generating both formats at build time.
34% of Audio & Music Streaming peers do this. Limit: Based on the homepage HTML delivered to an automated client; scripts that run later were not executed.
Guide: AVIF, WebP, JPEG, and PNG: Choose the Right Image Format
Priority 2 · Accelerate
Offscreen images lazy-loaded
Observed: The homepage had 84 images and none used loading="lazy".
What to do: Add loading="lazy" to images below the fold. Do not lazy-load the main hero image, because that delays the largest visible element.
53% of Audio & Music Streaming peers do this.
Priority 3 · Accelerate
HTTP/3 advertised
Observed: The homepage did not advertise HTTP/3 through an Alt-Svc header.
What to do: Turn on HTTP/3 at your CDN. Browsers fall back to HTTP/2 automatically, so the risk is low.
31% of Audio & Music Streaming peers do this.
Priority 4 · Enable
Structured data present
Observed: The homepage had no JSON-LD structured data.
What to do: Add JSON-LD for your organization and main content types, then test it with Google's Rich Results Test.
52% of Audio & Music Streaming peers do this.
What spotify.com already does well
Practices fewer than half of Audio & Music Streaming peers use.
- Nameservers spread across providersNameservers spread across Google Cloud DNS and NS1.7.6% of peers
- security.txt publishedsecurity.txt with a contact found.10% of peers
- Content Security Policy presentContent-Security-Policy present.18% of peers
What we saw
- Homepage checked
- https://www.spotify.com/
- Homepage response
- HTTP 200, after 1 redirect
- TLS
- TLSv1.3, HTTP/2
- Certificate
- Let's Encrypt, 89-day validity, expiring 2026-12-30
- CDN or edge
- Fastly, Google edge
- DNS operators
- Google Cloud DNS, NS1
- HSTS
- max-age 365 days
- DMARC policy
- p=reject
- Homepage HTML
- 305 KB, gzip
- Images on homepage
- 84 (jpg 4)
Limits: homepage only, one location, one moment. Header checks reflect the homepage response; other pages may differ.
Stack and providers
Seen in the homepage response, certificate and DNS. Provider pages compare how their customers configure the same checks.
All 31 checks
Select a gap for the method and fix. How each check works
Not observed 7
Observed 23
- HTTP requests move to HTTPS
- HSTS kept for at least a year
- TLS 1.3 negotiated
- Certificate has more than 14 days left
- Certificate lifetime of 100 days or less
- security.txt published
- DMARC policy enforces quarantine or reject
- X-Content-Type-Options: nosniff
- Framing restricted
- Content Security Policy present
- HTTP/2 negotiated
- HTML compressed
- No render-blocking scripts in <head>
- robots.txt published
- XML sitemap discoverable
- Reachable over IPv6
- Canonical URL declared
- Meta description written
- Mobile viewport configured
- Social preview image set
- Page language declared
- At most one redirect to the homepage
- Nameservers spread across providers
Not measured 1
- Static files cached for 30 days or more
Own spotify.com?
Re-run the checks after a change, keep a private action plan in a free workspace, or report a mistake.
Live status for this site: Status Is Down: spotify.com. This profile covers configuration only.