STATUS IS UPREADINESS PROFILE

Website readiness profile · Snapshot 23 October 2026

jma.go.jp

jma.go.jp's public homepage, certificate and DNS checked against 31 practices and compared with 190 Weather Forecast sites.

Readiness index
53/100

Weather Forecast median 63

Ahead of
25%

of measured Weather Forecast sites

Practices observed
14/31

0 of 31 could not be measured

Popularity band
Top 5K

Chrome UX Report top-sites list

Measured 2026-10-23 11:51:41 UTC from one location. How we measure

Readiness by lane

Green: jma.go.jp. Thin bar: Weather Forecast peer median.

Enable

44/100

Peers 76

Harden

69/100

Peers 54

Accelerate

38/100

Peers 59

Recover

0/100

Peers 14

Priority fixes for jma.go.jp

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

  1. Priority 1 · Enable

    robots.txt published

    Observed: No robots.txt file was returned at the site root.

    Why it matters: robots.txt is where crawlers look first for crawl rules and sitemap locations. Without it, they assume everything is open.

    What to do: Publish /robots.txt with any crawl rules you need and a Sitemap: line pointing to your XML sitemap.

    90% of Weather Forecast peers do this. Limit: Only the standard location was requested, once, at the time of the check.

  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.

  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.

  4. Priority 4 · Accelerate

    No render-blocking scripts in <head>

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

What jma.go.jp already does well

Practices fewer than half of Weather Forecast peers use.

  • Content Security Policy presentContent-Security-Policy present.22% of peers
  • Referrer-Policy setReferrer-Policy present.27% of peers
  • Framing restrictedFraming controls present.38% of peers

What we saw

Homepage checked
https://www.jma.go.jp/
Homepage response
HTTP 200, after 1 redirect
TLS
TLSv1.3, HTTP/2
Certificate
GlobalSign, 199-day validity, expiring 2027-03-05
CDN or edge
Amazon CloudFront
DNS operators
Amazon Route 53
HSTS
max-age 365 days, preload
DMARC policy
p=none
Homepage HTML
15 KB, gzip
Images on homepage
22 (png 11, jpg 5, svg 5, gif 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

Observed 14

  • HTTP requests move to HTTPS
  • HSTS kept for at least a year
  • TLS 1.3 negotiated
  • Certificate has more than 14 days left
  • X-Content-Type-Options: nosniff
  • Framing restricted
  • Content Security Policy present
  • Referrer-Policy set
  • HTTP/2 negotiated
  • HTML compressed
  • Meta description written
  • Mobile viewport configured
  • Page language declared
  • At most one redirect to the homepage

Own jma.go.jp?

Re-run the checks after a change, keep a private action plan in a free workspace, or report a mistake.

Live status for this site: Status Is Down: jma.go.jp. This profile covers configuration only.

Compare with other Weather Forecast sites