tupi.fm

Readiness by lane

Green: tupi.fm. Thin bar: Audio & Music Streaming peer median.

Priority fixes for tupi.fm

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

1. Priority 1 · Accelerate

   No render-blocking scripts in <head>

   Observed: The homepage <head> loaded 2 external scripts without async or defer.

   Why it matters: A plain <script src> in the head stops the browser from showing anything until that file has downloaded and run.

   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 WordPress: Since WordPress 6.3, scripts can be registered with a defer or async loading strategy.

   57% 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: Control Third-Party Scripts Before They Control Your Page

2. Priority 2 · 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.

   18% of Audio & Music Streaming peers do this.

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

3. Priority 3 · Harden

   security.txt published

   Observed: No valid /.well-known/security.txt with a Contact field was returned.

   What to do: Publish /.well-known/security.txt with at least Contact and Expires fields, as RFC 9116 requires, and review it before it expires.

   On Cloudflare: Cloudflare Security Center can serve a security.txt file for the zone.

   10% of Audio & Music Streaming peers do this.

   Guide: A Practical Website Health Check for Owners

4. Priority 4 · Harden

   DNSSEC signed

   Observed: No DS record was found for tupi.fm at its parent zone, so its DNS answers are not DNSSEC-signed.

   What to do: Enable DNSSEC at your DNS provider, then add the DS record at your registrar. Plan provider moves carefully: a stale DS record can make the domain fail to resolve.

   On Cloudflare: Enable DNSSEC in DNS > Settings and add the DS record at the registrar.

   6.1% of Audio & Music Streaming peers do this.

   Guide: Website Uptime Readiness: Prepare Before Traffic Arrives

What tupi.fm already does well

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

• CAA records limit who can issue certificatesCAA limits issuance to amazon.com, amazontrust.com, comodoca.com and others.13% 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://www.tupi.fm/

Homepage response

HTTP 200

TLS

TLSv1.3, HTTP/2

Certificate

Google Trust Services, 90-day validity, expiring 2027-01-08

CDN or edge

Cloudflare

Platform or framework

WordPress

DNS operators

Cloudflare

HSTS

max-age 365 days, includeSubDomains, preload

DMARC policy

p=quarantine

Homepage HTML

393 KB, br

Images on homepage

225 (jpg 339, png 80, avif 46, webp 22, svg 5)

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

• canliradyodinle.fm82
• epidemicsound.com84
• looperman.com88
• songsterr.com84
• tamilchristiansongs.in88

Audio & Music Streaming readiness benchmark