Website readiness profile · Snapshot 23 October 2026
poinews.jp
poinews.jp's public homepage, certificate and DNS checked against 31 practices and compared with 3,856 News & Media sites.
- Readiness index
- 42/100
- Ahead of
- 1.5%
- Practices observed
- 11/31
- Popularity band
- Top 50K
News & Media median 68
of measured News & Media sites
0 of 31 could not be measured
Chrome UX Report top-sites list
Readiness by lane
Green: poinews.jp. Thin bar: News & Media peer median.
Enable
67/100
Peers 89
Harden
23/100
Peers 56
Accelerate
50/100
Peers 68
Recover
0/100
Peers 11
Priority fixes for poinews.jp
Ordered by impact and by how common each practice is among peers.
Priority 1 · Harden
HTTP requests move to HTTPS
Observed: A request to http://poinews.jp/ was not redirected to HTTPS.
Why it matters: Visitors who type the address or follow an old link start on unencrypted HTTP. A redirect moves them to the encrypted site before any cookies or form data are sent.
What to do: Add a permanent (301 or 308) redirect from every http:// URL to the same https:// URL at your CDN, load balancer or web server.
On Amazon CloudFront: Set the viewer protocol policy of each cache behaviour to Redirect HTTP to HTTPS.
96% of News & Media peers do this. Limit: Measured for the homepage only, from one location, at the time of the check.
Priority 2 · 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.
87% of News & Media peers do this.
Guide: XML Sitemap Guide: Include Only URLs You Stand Behind
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.
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.
On Amazon CloudFront: Attach a response headers policy with Strict-Transport-Security to each distribution.
35% of News & Media peers do this.
What poinews.jp already does well
Practices fewer than half of News & Media peers use.
- No render-blocking scripts in <head>Head scripts load without blocking.42% of peers
What we saw
- Homepage checked
- https://poinews.jp/
- Homepage response
- HTTP 200
- TLS
- TLSv1.3, HTTP/2
- Certificate
- Amazon, 197-day validity, expiring 2027-01-01
- CDN or edge
- Amazon CloudFront
- DNS operators
- Amazon Route 53
- DMARC policy
- p=none
- Homepage HTML
- 196 KB, gzip
- Images on homepage
- 22 (png 22)
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 20
- HTTP requests move to HTTPS
- HSTS kept for at least a year
- Certificate lifetime of 100 days or less
- CAA records limit who can issue certificates
- DNSSEC signed
- security.txt published
- DMARC policy enforces quarantine or reject
- X-Content-Type-Options: nosniff
- Framing restricted
- Content Security Policy present
- Referrer-Policy set
- HTTP/3 advertised
- Static files cached for 30 days or more
- Modern image formats in use
- Offscreen images lazy-loaded
- XML sitemap discoverable
- Reachable over IPv6
- Structured data present
- Social preview image set
- Nameservers spread across providers
Observed 11
- TLS 1.3 negotiated
- Certificate has more than 14 days left
- HTTP/2 negotiated
- HTML compressed
- No render-blocking scripts in <head>
- robots.txt published
- Canonical URL declared
- Meta description written
- Mobile viewport configured
- Page language declared
- At most one redirect to the homepage
Own poinews.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: poinews.jp. This profile covers configuration only.