aemet.es

Readiness by lane

Green: aemet.es. Thin bar: Weather Forecast peer median.

Priority fixes for aemet.es

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

1. Priority 1 · Accelerate

   HTML compressed

   Observed: The homepage HTML (66 KB) was delivered without gzip, Brotli or zstd compression.

   Why it matters: Compression usually shrinks HTML several times over, so the first bytes of the page arrive sooner on slow connections.

   What to do: Enable Brotli or gzip for text responses (HTML, CSS, JavaScript, JSON, SVG) at the CDN or origin.

   On Amazon CloudFront: Enable Compress objects automatically on the cache behaviour.

   95% of Weather Forecast peers do this. Limit: Read from the homepage response only; other pages or regions may send different headers.

   Guide: How to Set a Website Performance Budget That Teams Can Keep

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.

   On Amazon CloudFront: Attach a response headers policy with Strict-Transport-Security to each distribution.

   39% of Weather Forecast peers do this.

   Guide: HTTPS and TLS Guide for Website Owners

3. Priority 3 · Accelerate

   Static files cached for 30 days or more

   Observed: A same-site stylesheet or script was cacheable for 1 hours, 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

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

What aemet.es already does well

Practices fewer than half of Weather Forecast peers use.

• DNSSEC signedDNSSEC delegation (DS record) present.12% of peers
• DMARC policy enforces quarantine or rejectDMARC policy p=quarantine.31% of peers
• Reachable over IPv6IPv6 address published.48% of peers

What we saw

Homepage checked

https://www.aemet.es/

Homepage response

HTTP 200, after 1 redirect

TLS

TLSv1.3, HTTP/2

Certificate

DigiCert, 198-day validity, expiring 2027-01-17

CDN or edge

Amazon CloudFront

DNS operators

1 self-run or other nameserver domain

DMARC policy

p=quarantine

Homepage HTML

66 KB, uncompressed

Images on homepage

52 (svg 30, jpg 11, gif 9, png 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 Weather Forecast sites

• aqicn.org45
• hidmet.gov.rs42
• lamma.toscana.it43
• metservice.com46
• vremea.net46

Weather Forecast readiness benchmark