STATUS IS UPREADINESS PROFILE

Website readiness profile · Snapshot 23 October 2026

city.chiba.jp

city.chiba.jp's public homepage, certificate and DNS checked against 31 practices and compared with 954 Government Services sites.

Readiness index
53/100

Government Services median 53

Ahead of
48%

of measured Government Services sites

Practices observed
14/31

0 of 31 could not be measured

Popularity band
Top 50K

Chrome UX Report top-sites list

Measured 2026-10-23 11:56:28 UTC from one location. How we measure

Readiness by lane

Green: city.chiba.jp. Thin bar: Government Services peer median.

Enable

77/100

Peers 59

Harden

60/100

Peers 59

Accelerate

20/100

Peers 41

Recover

0/100

Peers 25

Priority fixes for city.chiba.jp

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.

    55% of Government Services peers do this. Limit: Certificate and protocol were observed from one vantage point; CDNs can present different certificates by region.

  2. Priority 2 · Harden

    DMARC policy enforces quarantine or reject

    Observed: No DMARC record was found at _dmarc.city.chiba.jp.

    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.

    52% of Government Services peers do this.

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

    30% of Government Services peers do this.

  4. Priority 4 · Accelerate

    No render-blocking scripts in <head>

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

    39% of Government Services peers do this.

What city.chiba.jp already does well

Practices fewer than half of Government Services peers use.

  • Social preview image setog:image present.36% of peers
  • XML sitemap discoverableSitemap found.42% of peers

What we saw

Homepage checked
https://www.city.chiba.jp/
Homepage response
HTTP 200
TLS
TLSv1.3, http/1.1
Certificate
GlobalSign, 199-day validity, expiring 2027-02-11
DNS operators
Amazon Route 53
HSTS
max-age 365 days
Homepage HTML
55 KB, gzip
Images on homepage
114 (png 65, jpg 49)

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
  • HTML compressed
  • robots.txt published
  • XML sitemap discoverable
  • Meta description written
  • Mobile viewport configured
  • Social preview image set
  • Page language declared
  • At most one redirect to the homepage

Own city.chiba.jp?

Re-run the checks after a change, or verify the site in a free workspace to save reports with history, compare against similar sites and competitors, and track a private action plan. What owners get.

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

Compare with other Government Services sites