tenki.jp

Readiness by lane

Green: tenki.jp. Thin bar: Weather Forecast peer median.

Priority fixes for tenki.jp

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

1. Priority 1 · Enable

   Mobile viewport configured

   Observed: The homepage had no viewport meta tag, so phones may render it zoomed out.

   Why it matters: Without it, phones render the page at desktop width and shrink it, which makes text tiny and hard to use.

   What to do: Add <meta name="viewport" content="width=device-width, initial-scale=1"> and check the layout on small screens.

   91% of Weather Forecast peers do this. Limit: Based on the homepage HTML delivered to an automated client; scripts that run later were not executed.

   Guide: Responsive Web Design Checklist for Real Devices

2. Priority 2 · Harden

   HSTS kept for at least a year

   Observed: Strict-Transport-Security was sent with a max-age of 0 days, below the one-year benchmark.

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

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.

   56% of Weather Forecast peers do this.

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

What tenki.jp already does well

Practices fewer than half of Weather Forecast peers use.

• CAA records limit who can issue certificatesCAA limits issuance to amazon.com, digicert.com, globalsign.com and others.8.9% 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://tenki.jp/

Homepage response

HTTP 200

TLS

TLSv1.3, HTTP/2

Certificate

Amazon, 394-day validity, expiring 2027-02-10

CDN or edge

Amazon CloudFront

DNS operators

Amazon Route 53

HSTS

max-age 0 days, preload

DMARC policy

p=none

Homepage HTML

181 KB, gzip

Images on homepage

64 (jpg 40, png 38, svg 6, webp 2)

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

• climaeradar.com.br63
• climatempo.com.br65
• meteo.it64
• meteoprog.com65
• world-weather.ru64

Weather Forecast readiness benchmark