qobuz.com

Readiness by lane

Green: qobuz.com. Thin bar: Audio & Music Streaming peer median.

Priority fixes for qobuz.com

Ordered by impact and by how common each practice is among peers.

1. Priority 1 · Accelerate

   Static files cached for 30 days or more

   Observed: A same-site stylesheet or script was cacheable for 1 hours, short of the 30-day benchmark.

   Why it matters: Returning visitors and later page views reuse cached files instead of downloading them again.

   What to do: Give versioned (fingerprinted) CSS, JavaScript, fonts and images Cache-Control: public, max-age=31536000, immutable, and change the file name whenever the content changes.

   56% of Audio & Music Streaming peers do this. Limit: Read from the homepage response only; other pages or regions may send different headers.

   Guide: Browser Caching Guide for Website Owners

2. Priority 2 · Harden

   HSTS kept for at least a year

   Observed: The homepage response did not include a Strict-Transport-Security header.

   What to do: Send Strict-Transport-Security on HTTPS responses. Start with a short max-age (for example 300 seconds), confirm every subdomain works over HTTPS, then raise it in steps to 31536000. Add includeSubDomains only when all subdomains are HTTPS. HSTS preload is optional and hard to undo; hstspreload.org itself does not recommend it by default.

   33% of Audio & Music Streaming peers do this.

   Guide: HTTPS and TLS Guide for Website Owners

3. Priority 3 · Harden

   DMARC policy enforces quarantine or reject

   Observed: The DMARC policy for qobuz.com was p=none, which asks receivers to take no action on failing mail.

   What to do: Publish DMARC with p=none and a reporting address first, fix any legitimate senders that fail SPF or DKIM alignment, then move to quarantine and finally reject.

   38% of Audio & Music Streaming peers do this.

   Guide: A Practical Website Health Check for Owners

4. Priority 4 · Harden

   Certificate lifetime of 100 days or less

   Observed: The certificate from Gandi SAS had a 198-day validity period, longer than the 100-day maximum that applies from March 2027.

   What to do: Move to automated issuance and renewal now, while you still have time to test it.

   69% of Audio & Music Streaming peers do this.

   Guide: HTTPS and TLS Guide for Website Owners

What qobuz.com already does well

Practices fewer than half of Audio & Music Streaming peers use.

• Content Security Policy presentContent-Security-Policy present.18% of peers
• Referrer-Policy setReferrer-Policy present.27% of peers
• HTTP/3 advertisedHTTP/3 advertised.31% of peers

What we saw

Homepage checked

https://www.qobuz.com/

Homepage response

HTTP 200, after 1 redirect

TLS

TLSv1.3, HTTP/2

Certificate

Gandi SAS, 198-day validity, expiring 2027-03-11

CDN or edge

Akamai

DNS operators

Amazon Route 53

DMARC policy

p=none

Homepage HTML

140 KB, gzip

Images on homepage

24 (jpg 18, png 12, webp 6)

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

Compare with other Audio & Music Streaming sites

• citimuzik.com75
• joysound.com74
• nporadio1.nl75
• pocketfm.com75
• radiofm.rs75

Audio & Music Streaming readiness benchmark