Website readiness profile · Snapshot 23 October 2026
prtimes.jp
prtimes.jp's public homepage, certificate and DNS checked against 31 practices and compared with 87 SEO & Email Marketing sites.
- Readiness index
- 73/100
- Ahead of
- 67%
- Practices observed
- 20/31
- Popularity band
- Top 5K
SEO & Email Marketing median 62
of measured SEO & Email Marketing sites
0 of 31 could not be measured
Chrome UX Report top-sites list
Readiness by lane
Green: prtimes.jp. Thin bar: SEO & Email Marketing peer median.
Enable
95/100
Peers 77
Harden
55/100
Peers 55
Accelerate
85/100
Peers 66
Recover
0/100
Peers 3
Priority fixes for prtimes.jp
Ordered by impact and by how common each practice is among peers.
Priority 1 · Accelerate
Modern image formats in use
Observed: The homepage had 51 images and none used WebP or AVIF.
Why it matters: WebP and AVIF are typically much smaller than JPEG or PNG at similar quality, and images are often the heaviest part of a page.
What to do: Serve WebP or AVIF with a JPEG or PNG fallback, either through an image CDN or by generating both formats at build time.
41% of SEO & Email Marketing peers do this. Limit: Based on the homepage HTML delivered to an automated client; scripts that run later were not executed.
Guide: AVIF, WebP, JPEG, and PNG: Choose the Right Image Format
Priority 2 · Harden
DMARC policy enforces quarantine or reject
Observed: The DMARC policy for prtimes.jp was p=none, which asks receivers to take no action on failing mail.
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.
37% of SEO & Email Marketing peers do this.
Priority 3 · Harden
Certificate lifetime of 100 days or less
Observed: The certificate from GlobalSign nv-sa had a 198-day validity period, longer than the 100-day maximum that applies from March 2027.
What to do: Move to automated issuance and renewal now, while you still have time to test it.
85% of SEO & Email Marketing peers do this.
Priority 4 · Harden
Content Security Policy present
Observed: The homepage response did not include a Content-Security-Policy header.
What to do: Start with Content-Security-Policy-Report-Only to see what would break, tighten the policy over a few weeks, then enforce it.
27% of SEO & Email Marketing peers do this.
Guide: Payment Security and PCI DSS: What Website Owners Need to Know
What prtimes.jp already does well
Practices fewer than half of SEO & Email Marketing peers use.
- HSTS kept for at least a yearHSTS with a 365-day max-age.36% of peers
- HTTP/3 advertisedHTTP/3 advertised.41% of peers
- Framing restrictedFraming controls present.48% of peers
What we saw
- Homepage checked
- https://prtimes.jp/
- Homepage response
- HTTP 200
- TLS
- TLSv1.3, HTTP/2
- Certificate
- GlobalSign, 198-day validity, expiring 2027-02-10
- CDN or edge
- Fastly
- DNS operators
- Amazon Route 53
- HSTS
- max-age 365 days
- DMARC policy
- p=none
- Homepage HTML
- 396 KB, gzip
- Images on homepage
- 51 (jpg 25, png 22, svg 4)
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 11
- 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
- Content Security Policy present
- Referrer-Policy set
- Modern image formats in use
- Reachable over IPv6
- Nameservers spread across providers
Observed 20
- HTTP requests move to HTTPS
- HSTS kept for at least a year
- TLS 1.3 negotiated
- Certificate has more than 14 days left
- Framing restricted
- HTTP/2 negotiated
- HTTP/3 advertised
- HTML compressed
- Static files cached for 30 days or more
- Offscreen images lazy-loaded
- No render-blocking scripts in <head>
- robots.txt published
- XML sitemap discoverable
- Canonical URL declared
- Meta description written
- Mobile viewport configured
- Structured data present
- Social preview image set
- Page language declared
- At most one redirect to the homepage
Own prtimes.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: prtimes.jp. This profile covers configuration only.