meteo.cat

Readiness by lane

Green: meteo.cat. Thin bar: Weather Forecast peer median.

Priority fixes for meteo.cat

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

1. Priority 1 · Accelerate

   HTML compressed

   Observed: The homepage HTML (473 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 Fastly: Enable compression for text content types.

   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

   TLS 1.3 negotiated

   Observed: The TLS connection negotiated TLSv1.2.

   What to do: Enable TLS 1.3 on your CDN or server. Keep TLS 1.2 available for older clients unless you have checked your audience.

   88% 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 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.

   On WordPress: Caching plugins or your host can set long browser cache lifetimes for theme and plugin assets.

   48% of Weather Forecast peers do this.

   Guide: Browser Caching Guide for Website Owners

4. Priority 4 · Accelerate

   No render-blocking scripts in <head>

   Observed: The homepage <head> loaded 2 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.

   On WordPress: Since WordPress 6.3, scripts can be registered with a defer or async loading strategy.

   56% of Weather Forecast peers do this.

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

What meteo.cat already does well

Practices fewer than half of Weather Forecast peers use.

• DNSSEC signedDNSSEC delegation (DS record) present.12% of peers
• HSTS kept for at least a yearHSTS with a 365-day max-age.39% of peers

What we saw

Homepage checked

https://www.meteo.cat/

Homepage response

HTTP 200

TLS

TLSv1.2, HTTP/2

Certificate

Sectigo, 365-day validity, expiring 2027-01-12

CDN or edge

Fastly

Platform or framework

WordPress

DNS operators

Amazon Route 53

HSTS

max-age 365 days

DMARC policy

p=none

Homepage HTML

473 KB, uncompressed

Images on homepage

13 (png 10, gif 2, jpg 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

• amindi.ge47
• meteoam.it46
• shmu.sk49
• weathernews.jp49
• xn--lodgobmh.com49

Weather Forecast readiness benchmark