Website readiness profile · Snapshot 23 October 2026
city.nagoya.jp
city.nagoya.jp's public homepage, certificate and DNS checked against 31 practices and compared with 954 Government Services sites.
- Readiness index
- 55/100
- Ahead of
- 53%
- Practices observed
- 15/31
- Popularity band
- Top 50K
Government Services median 53
of measured Government Services sites
0 of 31 could not be measured
Chrome UX Report top-sites list
Readiness by lane
Green: city.nagoya.jp. Thin bar: Government Services peer median.
Enable
72/100
Peers 59
Harden
69/100
Peers 59
Accelerate
18/100
Peers 41
Recover
0/100
Peers 25
Priority fixes for city.nagoya.jp
Ordered by impact and by how common each practice is among peers.
Priority 1 · Accelerate
HTML compressed
Observed: The homepage HTML (186 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 Amazon CloudFront: Enable Compress objects automatically on the cache behaviour.
74% of Government Services 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
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.
30% of Government Services peers do this.
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.
42% of Government Services peers do this.
Guide: XML Sitemap Guide: Include Only URLs You Stand Behind
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.
Guide: Control Third-Party Scripts Before They Control Your Page
What city.nagoya.jp already does well
Practices fewer than half of Government Services peers use.
- Structured data presentJSON-LD structured data found.15% of peers
- Social preview image setog:image present.36% of peers
What we saw
- Homepage checked
- https://www.city.nagoya.jp/
- Homepage response
- HTTP 200
- TLS
- TLSv1.3, HTTP/2
- Certificate
- Amazon, 197-day validity, expiring 2027-03-11
- CDN or edge
- Amazon CloudFront
- DNS operators
- Amazon Route 53
- HSTS
- max-age 365 days
- DMARC policy
- p=reject
- Homepage HTML
- 186 KB, uncompressed
- Images on homepage
- 225 (svg 108, png 67, jpg 36, gif 14)
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
Not observed 16
- Certificate lifetime of 100 days or less
- CAA records limit who can issue certificates
- DNSSEC signed
- security.txt published
- Content Security Policy present
- Referrer-Policy set
- HTTP/3 advertised
- HTML compressed
- Static files cached for 30 days or more
- Modern image formats in use
- Offscreen images lazy-loaded
- No render-blocking scripts in <head>
- XML sitemap discoverable
- Reachable over IPv6
- Canonical URL declared
- Nameservers spread across providers
Observed 15
- HTTP requests move to HTTPS
- HSTS kept for at least a year
- TLS 1.3 negotiated
- Certificate has more than 14 days left
- DMARC policy enforces quarantine or reject
- X-Content-Type-Options: nosniff
- Framing restricted
- HTTP/2 negotiated
- robots.txt published
- Meta description written
- Mobile viewport configured
- Structured data present
- Social preview image set
- Page language declared
- At most one redirect to the homepage
Own city.nagoya.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.nagoya.jp. This profile covers configuration only.