Website readiness profile · Snapshot 23 October 2026

weather.gc.ca

weather.gc.ca's public homepage, certificate and DNS checked against 31 practices and compared with 190 Weather Forecast sites.

Readiness index: 51/100
Ahead of: 21%
Practices observed: 13/30
Popularity band: Top 10K

Measured 2026-10-23 12:19:04 UTC from one location. How we measure

Readiness by lane

Green: weather.gc.ca. Thin bar: Weather Forecast peer median.

Enable

56/100

Peers 76

Harden

55/100

Peers 54

Accelerate

36/100

Peers 59

Recover

100/100

Peers 14

Priority fixes for weather.gc.ca

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

Priority 1 · Accelerate
HTTP/2 negotiated
Observed: The TLS handshake selected http/1.1 instead of HTTP/2.
Why it matters: HTTP/2 sends many files over one connection, which speeds up pages with lots of images, styles and scripts.
What to do: Enable HTTP/2 on your CDN or server. Most CDNs do this by default.
84% of Weather Forecast peers do this. Limit: Certificate and protocol were observed from one vantage point; CDNs can present different certificates by region.
Guide: CDN Guide for Website Owners
Priority 2 · Accelerate
Static files cached for 30 days or more
Observed: A same-site stylesheet or script was cacheable for no max-age, short of the 30-day benchmark.
What to do: Give versioned (fingerprinted) CSS, JavaScript, fonts and images Cache-Control: public, max-age=31536000, immutable, and change the file name whenever the content changes.
48% of Weather Forecast peers do this.
Guide: Browser Caching Guide for Website Owners
Priority 3 · Enable
XML sitemap discoverable
Observed: No sitemap was listed in robots.txt or found at /sitemap.xml.
What to do: Generate an XML sitemap of canonical URLs, reference it in robots.txt and submit it in Google Search Console.
66% of Weather Forecast peers do this.
Guide: XML Sitemap Guide: Include Only URLs You Stand Behind
Priority 4 · Harden
DMARC policy enforces quarantine or reject
Observed: The DMARC policy for weather.gc.ca 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.
31% of Weather Forecast peers do this.
Guide: A Practical Website Health Check for Owners

What weather.gc.ca already does well

Practices fewer than half of Weather Forecast peers use.

security.txt publishedsecurity.txt with a contact found.3.2% of peers
Nameservers spread across providersNameservers spread across more than one operator.14% of peers
HSTS kept for at least a yearHSTS with a 730-day max-age.39% of peers

What we saw

Homepage checked: https://weather.gc.ca/
Homepage response: HTTP 200
TLS: TLSv1.3, http/1.1
Certificate: Entrust Limited, 198-day validity, expiring 2026-11-14
DNS operators: 2 self-run or other nameserver domains
HSTS: max-age 730 days, preload
DMARC policy: p=none
Homepage HTML: 744 KB, gzip
Images on homepage: 3 (svg 2, jpg 1)

Limits: homepage only, one location, one moment. Header checks reflect the homepage response; other pages may differ.

All 31 checks

Select a gap for the method and fix. How each check works

Not observed 17

Observed 13

HTTP requests move to HTTPS
HSTS kept for at least a year
TLS 1.3 negotiated
Certificate has more than 14 days left
security.txt published
HTML compressed
No render-blocking scripts in <head>
robots.txt published
Meta description written
Mobile viewport configured
Page language declared
At most one redirect to the homepage
Nameservers spread across providers

Not measured 1

Offscreen images lazy-loaded

Own weather.gc.ca?

Re-run the checks after a change, keep a private action plan in a free workspace, or report a mistake.

Re-check weather.gc.ca now Add to owner workspace Request a correction or removal

Live status for this site: Status Is Down: weather.gc.ca. This profile covers configuration only.

Compare with other Weather Forecast sites

Weather Forecast readiness benchmark