pocketfm.com

Readiness by lane

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

Priority fixes for pocketfm.com

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

1. Priority 1 · Harden

   HTTP requests move to HTTPS

   Observed: A request to http://pocketfm.com/ was not redirected to HTTPS.

   Why it matters: Visitors who type the address or follow an old link start on unencrypted HTTP. A redirect moves them to the encrypted site before any cookies or form data are sent.

   What to do: Add a permanent (301 or 308) redirect from every http:// URL to the same https:// URL at your CDN, load balancer or web server.

   On Amazon CloudFront: Set the viewer protocol policy of each cache behaviour to Redirect HTTP to HTTPS.

   92% of Audio & Music Streaming peers do this. Limit: Measured for the homepage only, from one location, at the time of the check.

   Guide: HTTPS and TLS Guide for Website Owners

2. Priority 2 · Accelerate

   No render-blocking scripts in <head>

   Observed: The homepage <head> loaded 1 external script without async or defer.

   What to do: Add defer to scripts that need the DOM, async to independent ones such as analytics, or move them to the end of the body.

   On Next.js: Use the next/script component with an appropriate loading strategy.

   57% of Audio & Music Streaming peers do this.

   Guide: Control Third-Party Scripts Before They Control Your Page

3. Priority 3 · Harden

   Certificate lifetime of 100 days or less

   Observed: The certificate from Amazon had a 197-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

4. Priority 4 · Harden

   Content Security Policy present

   Observed: The homepage response did not include a Content-Security-Policy header.

   What to do: Start with Content-Security-Policy-Report-Only to see what would break, tighten the policy over a few weeks, then enforce it.

   On Next.js: Next.js documents nonce-based CSP with middleware.

   18% of Audio & Music Streaming peers do this.

   Guide: Payment Security and PCI DSS: What Website Owners Need to Know

What pocketfm.com already does well

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

• Referrer-Policy setReferrer-Policy present.27% of peers
• HTTP/3 advertisedHTTP/3 advertised.31% of peers
• HSTS kept for at least a yearHSTS with a 365-day max-age covering subdomains.33% of peers

What we saw

Homepage checked

https://pocketfm.com/

Homepage response

HTTP 200

TLS

TLSv1.3, HTTP/2

Certificate

Amazon, 197-day validity, expiring 2027-05-07

CDN or edge

Amazon CloudFront

Platform or framework

Next.js

DNS operators

Amazon Route 53

HSTS

max-age 365 days, includeSubDomains, preload

DMARC policy

p=reject

Homepage HTML

196 KB, gzip

Images on homepage

64 (webp 48, jpg 9, svg 6, png 1)

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

• ceenaija.com75
• citimuzik.com75
• nporadio1.nl75
• qobuz.com75
• radiofm.rs75

Audio & Music Streaming readiness benchmark