Website readiness profile · Snapshot 23 October 2026
djmwanga.com
djmwanga.com's public homepage, certificate and DNS checked against 31 practices and compared with 277 Audio & Music Streaming sites.
- Readiness index
- 68/100
- Ahead of
- 55%
- Practices observed
- 19/31
- Popularity band
- Top 10K
Audio & Music Streaming median 66
of measured Audio & Music Streaming sites
0 of 31 could not be measured
Chrome UX Report top-sites list
Readiness by lane
Green: djmwanga.com. Thin bar: Audio & Music Streaming peer median.
Enable
92/100
Peers 84
Harden
43/100
Peers 55
Accelerate
90/100
Peers 64
Recover
0/100
Peers 8
Priority fixes for djmwanga.com
Ordered by impact and by how common each practice is among peers.
Priority 1 · Harden
HSTS kept for at least a year
Observed: The homepage response did not include a Strict-Transport-Security header.
Why it matters: HSTS tells browsers to use HTTPS for your host on every later visit, which removes the window where a first HTTP request can be intercepted.
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.
On Cloudflare: Enable HSTS under SSL/TLS > Edge Certificates > HTTP Strict Transport Security and raise max-age gradually.
33% of Audio & Music Streaming peers do this. Limit: Read from the homepage response only; other pages or regions may send different headers.
Priority 2 · Harden
DMARC policy enforces quarantine or reject
Observed: The DMARC policy for djmwanga.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.
Priority 3 · Accelerate
Offscreen images lazy-loaded
Observed: The homepage had 38 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.
On WordPress: WordPress has added loading="lazy" to images by default since 5.5; check that your theme or a plugin has not removed it.
53% of Audio & Music Streaming peers do this.
Priority 4 · Harden
Framing restricted
Observed: The homepage did not send frame-ancestors or X-Frame-Options, so other sites may frame it.
What to do: Send Content-Security-Policy: frame-ancestors 'self' (or a list of trusted origins). X-Frame-Options: SAMEORIGIN covers older browsers.
On Cloudflare: Add the header with a response header transform rule.
42% of Audio & Music Streaming peers do this.
What djmwanga.com already does well
Practices fewer than half of Audio & Music Streaming peers use.
- HTTP/3 advertisedHTTP/3 advertised.31% of peers
- Modern image formats in useWebP or AVIF images detected.34% of peers
- Reachable over IPv6IPv6 address published.41% of peers
What we saw
- Homepage checked
- https://djmwanga.com/
- Homepage response
- HTTP 200
- TLS
- TLSv1.3, HTTP/2
- Certificate
- Google Trust Services, 90-day validity, expiring 2026-11-27
- CDN or edge
- Cloudflare
- Platform or framework
- WordPress
- DNS operators
- Cloudflare
- DMARC policy
- p=none
- Homepage HTML
- 221 KB, br
- Images on homepage
- 38 (jpg 182, webp 6, avif 3, png 3)
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 12
- HSTS kept for at least a year
- CAA records limit who can issue certificates
- DNSSEC signed
- security.txt published
- DMARC policy enforces quarantine or reject
- X-Content-Type-Options: nosniff
- Framing restricted
- Content Security Policy present
- Referrer-Policy set
- Offscreen images lazy-loaded
- Social preview image set
- Nameservers spread across providers
Observed 19
- HTTP requests move to HTTPS
- TLS 1.3 negotiated
- Certificate has more than 14 days left
- Certificate lifetime of 100 days or less
- HTTP/2 negotiated
- HTTP/3 advertised
- HTML compressed
- Static files cached for 30 days or more
- Modern image formats in use
- No render-blocking scripts in <head>
- robots.txt published
- XML sitemap discoverable
- Reachable over IPv6
- Canonical URL declared
- Meta description written
- Mobile viewport configured
- Structured data present
- Page language declared
- At most one redirect to the homepage
Own djmwanga.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: djmwanga.com. This profile covers configuration only.