tempo.pt

Readiness by lane

Green: tempo.pt. Thin bar: Weather Forecast peer median.

Priority fixes for tempo.pt

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

1. Priority 1 · Harden

   HSTS kept for at least a year

   Observed: The homepage response did not include a Strict-Transport-Security header.

   Why it matters: HSTS tells browsers to use HTTPS for your host on every later visit, which removes the window where a first HTTP request can be intercepted.

   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 Cloudflare: Enable HSTS under SSL/TLS > Edge Certificates > HTTP Strict Transport Security and raise max-age gradually.

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

   Guide: HTTPS and TLS 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 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.

   On Cloudflare: Use Cache Rules to set edge and browser TTLs for static file paths.

   48% of Weather Forecast peers do this.

   Guide: Browser Caching Guide for Website Owners

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

4. Priority 4 · Harden

   DMARC policy enforces quarantine or reject

   Observed: No DMARC record was found at _dmarc.tempo.pt.

   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 tempo.pt already does well

Practices fewer than half of Weather Forecast peers use.

• HTTP/3 advertisedHTTP/3 advertised.28% of peers
• Structured data presentJSON-LD structured data found.39% of peers
• X-Content-Type-Options: nosniffnosniff header present.46% of peers

What we saw

Homepage checked

https://www.tempo.pt/

Homepage response

HTTP 200

TLS

TLSv1.3, HTTP/2

Certificate

Google Trust Services, 90-day validity, expiring 2026-12-18

CDN or edge

Cloudflare

DNS operators

Cloudflare

Homepage HTML

112 KB, br

Images on homepage

68 (png 34, jpg 23, svg 11)

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

• gismeteo.kz59
• inumet.gub.uy61
• knmi.nl60
• sinoptik.bg60
• weatherzone.com60

Weather Forecast readiness benchmark