jisin.jp

Readiness by lane

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

Priority fixes for jisin.jp

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

1. Priority 1 · Harden

   HSTS kept for at least a year

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

   Why it matters: HSTS tells browsers to use HTTPS for your host on every later visit, which removes the window where a first HTTP request can be intercepted.

   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. Limit: Read from the homepage response only; other pages or regions may send different headers.

   Guide: HTTPS and TLS Guide for Website Owners

2. Priority 2 · Enable

   Canonical URL declared

   Observed: The homepage did not declare a canonical URL.

   What to do: Add a self-referencing canonical link to every indexable page, using the final https:// URL.

   89% of News & Media peers do this.

   Guide: Canonical Tags: A Decision Guide for Duplicate URLs

3. Priority 3 · Harden

   DMARC policy enforces quarantine or reject

   Observed: The DMARC policy for jisin.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 News & Media peers do this.

   Guide: A Practical Website Health Check for Owners

4. Priority 4 · Accelerate

   Offscreen images lazy-loaded

   Observed: The homepage had 126 images and none used loading="lazy".

   What to do: Add loading="lazy" to images below the fold. Do not lazy-load the main hero image, because that delays the largest visible element.

   On WordPress: WordPress has added loading="lazy" to images by default since 5.5; check that your theme or a plugin has not removed it.

   72% of News & Media peers do this.

   Guide: Lazy Loading Without Broken Pages

What jisin.jp already does well

Practices fewer than half of News & Media peers use.

• X-Content-Type-Options: nosniffnosniff header present.42% of peers
• Framing restrictedFraming controls present.42% of peers
• Modern image formats in useWebP or AVIF images detected.44% of peers

What we saw

Homepage checked

https://jisin.jp/

Homepage response

HTTP 200

TLS

TLSv1.3, HTTP/2

Certificate

Amazon, 197-day validity, expiring 2027-02-19

CDN or edge

Amazon CloudFront

Platform or framework

WordPress

DNS operators

Amazon Route 53

DMARC policy

p=none

Homepage HTML

136 KB, gzip

Images on homepage

126 (jpg 84, webp 34, png 7, svg 1)

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

Compare with other News & Media sites

• ilna.ir63
• ipit.in63
• ithardware.pl63
• kompas.com63
• kurier.at63

News & Media readiness benchmark