grapee.jp

Readiness by lane

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

Priority fixes for grapee.jp

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

1. Priority 1 · Harden

   TLS 1.3 negotiated

   Observed: The TLS connection negotiated TLSv1.2.

   Why it matters: TLS 1.3 removes legacy cipher suites and completes the handshake in fewer round trips, so it is both safer and faster for new connections.

   What to do: Enable TLS 1.3 on your CDN or server. Keep TLS 1.2 available for older clients unless you have checked your audience.

   93% of News & Media peers do this. Limit: Certificate and protocol were observed from one vantage point; CDNs can present different certificates by region.

   Guide: HTTPS and TLS Guide for Website Owners

2. Priority 2 · Accelerate

   Static files cached for 30 days or more

   Observed: A same-site stylesheet or script was cacheable for 1 days, 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.

   On WordPress: Caching plugins or your host can set long browser cache lifetimes for theme and plugin assets.

   60% of News & Media peers do this.

   Guide: Browser Caching Guide for Website Owners

3. Priority 3 · Harden

   DMARC policy enforces quarantine or reject

   Observed: No DMARC record was found at _dmarc.grapee.jp.

   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 36 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 grapee.jp already does well

Practices fewer than half of News & Media peers use.

• HSTS kept for at least a yearHSTS with a 365-day max-age covering subdomains.35% 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://grapee.jp/

Homepage response

HTTP 200

TLS

TLSv1.2, HTTP/2

Certificate

Sectigo, 396-day validity, expiring 2027-03-20

Platform or framework

WordPress

DNS operators

1 self-run or other nameserver domain

HSTS

max-age 365 days, includeSubDomains, preload

Homepage HTML

65 KB, gzip

Images on homepage

36 (webp 53, 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

• gmconline.com.br62
• gong.bg62
• gp.se62
• grenzecho.net62
• heiliao.com62

News & Media readiness benchmark