rds.ca

Readiness by lane

Green: rds.ca. Thin bar: Sports Broadcast & Fantasy Games peer median.

Priority fixes for rds.ca

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

1. Priority 1 · Enable

   Meta description written

   Observed: The homepage had no meta description.

   Why it matters: Search engines often use it for the snippet under your link, so a clear description can improve click-through.

   What to do: Write a short, specific description of the page for people, not a list of keywords.

   91% of Sports Broadcast & Fantasy Games peers do this. Limit: Based on the homepage HTML delivered to an automated client; scripts that run later were not executed.

   Guide: Meta Titles and Descriptions That Match Search Intent

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.

   27% of Sports Broadcast & Fantasy Games peers do this.

   Guide: HTTPS and TLS Guide for Website Owners

3. Priority 3 · Accelerate

   Modern image formats in use

   Observed: The homepage had 4 images and none used WebP or AVIF.

   What to do: Serve WebP or AVIF with a JPEG or PNG fallback, either through an image CDN or by generating both formats at build time.

   35% of Sports Broadcast & Fantasy Games peers do this.

   Guide: AVIF, WebP, JPEG, and PNG: Choose the Right Image Format

4. Priority 4 · Accelerate

   No render-blocking scripts in <head>

   Observed: The homepage <head> loaded 3 external scripts 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.

   43% of Sports Broadcast & Fantasy Games peers do this.

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

What rds.ca already does well

Practices fewer than half of Sports Broadcast & Fantasy Games peers use.

• Content Security Policy presentContent-Security-Policy present.18% of peers
• DMARC policy enforces quarantine or rejectDMARC policy p=reject.32% of peers
• Reachable over IPv6IPv6 address published.43% of peers

What we saw

Homepage checked

https://www.rds.ca/

Homepage response

HTTP 200

TLS

TLSv1.3, HTTP/2

Certificate

Let's Encrypt, 89-day validity, expiring 2026-11-19

CDN or edge

Akamai

DNS operators

Vercara UltraDNS

DMARC policy

p=reject

Homepage HTML

243 KB, gzip

Images on homepage

4 (jpg 15)

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 Sports Broadcast & Fantasy Games sites

• liveticker.com66
• meridiano.net66
• mytischtennis.de66
• scoresinlive.com66
• si.com66

Sports Broadcast & Fantasy Games readiness benchmark