megatiempo.cl

Readiness by lane

Green: megatiempo.cl. Thin bar: Weather Forecast peer median.

Priority fixes for megatiempo.cl

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

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

2. Priority 2 · Accelerate

   Static files cached for 30 days or more

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

3. Priority 3 · Harden

   DMARC policy enforces quarantine or reject

   Observed: No DMARC record was found at _dmarc.megatiempo.cl.

   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

4. Priority 4 · Accelerate

   Offscreen images lazy-loaded

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

   50% of Weather Forecast peers do this.

   Guide: Lazy Loading Without Broken Pages

What megatiempo.cl already does well

Practices fewer than half of Weather Forecast peers use.

• Content Security Policy presentContent-Security-Policy present.22% of peers
• Modern image formats in useWebP or AVIF images detected.23% of peers
• Referrer-Policy setReferrer-Policy present.27% of peers

What we saw

Homepage checked

https://www.megatiempo.cl/

Homepage response

HTTP 200

TLS

TLSv1.3

Certificate

Sectigo, 386-day validity, expiring 2026-11-26

DNS operators

1 self-run or other nameserver domain

HSTS

max-age 365 days, includeSubDomains

Homepage HTML

115 KB, gzip

Images on homepage

29 (jpg 15, gif 8, png 3, webp 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

Compare with other Weather Forecast sites

• foreca.com69
• tempo.com70
• tiempo3.com69
• weawow.com70
• windfinder.com69

Weather Forecast readiness benchmark