myradioonline.ro

Readiness by lane

Green: myradioonline.ro. Thin bar: Audio & Music Streaming peer median.

Priority fixes for myradioonline.ro

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

1. 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.

   Guide: HTTPS and TLS Guide for Website Owners

2. Priority 2 · Accelerate

   Offscreen images lazy-loaded

   Observed: The homepage had 55 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.

   Guide: Lazy Loading Without Broken Pages

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

   Guide: Structured Data Basics for Website Owners

4. Priority 4 · Harden

   CAA records limit who can issue certificates

   Observed: No CAA record was found for myradioonline.ro, so any public certificate authority may issue for it.

   What to do: Publish CAA records naming every CA you actually use, including the CAs your CDN uses for managed certificates. Add an iodef contact if you want reports.

   On Cloudflare: Cloudflare documents which CAs its managed certificates need; include them in your CAA records.

   13% of Audio & Music Streaming peers do this.

   Guide: HTTPS and TLS Guide for Website Owners

What myradioonline.ro already does well

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

• Content Security Policy presentContent-Security-Policy present.18% of peers
• HTTP/3 advertisedHTTP/3 advertised.31% of peers
• Modern image formats in useWebP or AVIF images detected.34% of peers

What we saw

Homepage checked

https://myradioonline.ro/

Homepage response

HTTP 200

TLS

TLSv1.3, HTTP/2

Certificate

Let's Encrypt, 89-day validity, expiring 2027-01-05

CDN or edge

Cloudflare

DNS operators

Cloudflare

DMARC policy

p=quarantine

Homepage HTML

73 KB, br

Images on homepage

55 (png 54, webp 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

• bandlab.com80
• ecouterradioenligne.com79
• myradioonline.pl80
• spotify.com81
• ultimate-guitar.com80

Audio & Music Streaming readiness benchmark