STATUS IS UPREADINESS PROFILE

Website readiness profile · Snapshot 23 October 2026

amass.jp

amass.jp's public homepage, certificate and DNS checked against 31 practices and compared with 3,856 News & Media sites.

Readiness index
42/100

News & Media median 68

Ahead of
1.5%

of measured News & Media sites

Practices observed
12/31

0 of 31 could not be measured

Popularity band
Top 50K

Chrome UX Report top-sites list

Measured 2026-10-23 11:52:50 UTC from one location. How we measure

Readiness by lane

Green: amass.jp. Thin bar: News & Media peer median.

Enable

69/100

Peers 89

Harden

43/100

Peers 56

Accelerate

18/100

Peers 68

Recover

0/100

Peers 11

Priority fixes for amass.jp

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

  1. Priority 1 · Accelerate

    HTML compressed

    Observed: The homepage HTML (30 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.

    97% of News & Media peers do this. Limit: Read from the homepage response only; other pages or regions may send different headers.

  2. Priority 2 · Enable

    Mobile viewport configured

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

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

    98% of News & Media 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.

    60% of News & Media peers do this.

  4. Priority 4 · Harden

    HSTS kept for at least a year

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

    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.

    35% of News & Media peers do this.

What we saw

Homepage checked
https://amass.jp/
Homepage response
HTTP 200
TLS
TLSv1.3, HTTP/2
Certificate
Japan Registry Services Co., Ltd., 88-day validity, expiring 2026-12-15
DNS operators
1 self-run or other nameserver domain
DMARC policy
p=none
Homepage HTML
30 KB, uncompressed
Images on homepage
29 (jpg 29)

Limits: homepage only, one location, one moment. Header checks reflect the homepage response; other pages may differ.

All 31 checks

Select a gap for the method and fix. How each check works

Own amass.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: amass.jp. This profile covers configuration only.

Compare with other News & Media sites