runnet.jp

Readiness by lane

Green: runnet.jp. Thin bar: Fitness & Health peer median.

Priority fixes for runnet.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.

   89% of Fitness & Health 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 · 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.

   78% of Fitness & Health peers do this.

   Guide: XML Sitemap Guide: Include Only URLs You Stand Behind

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.

   56% of Fitness & Health peers do this.

   Guide: Browser Caching Guide for Website Owners

4. Priority 4 · Accelerate

   Modern image formats in use

   Observed: The homepage had 150 images and none used WebP or AVIF.

   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.

   45% of Fitness & Health peers do this.

   Guide: AVIF, WebP, JPEG, and PNG: Choose the Right Image Format

What runnet.jp already does well

Practices fewer than half of Fitness & Health peers use.

• Reachable over IPv6IPv6 address published.36% of peers
• Content Security Policy presentContent-Security-Policy present.38% of peers
• HSTS kept for at least a yearHSTS with a 3650-day max-age.43% of peers

What we saw

Homepage checked

https://runnet.jp/

Homepage response

HTTP 200

TLS

TLSv1.2, HTTP/2

Certificate

GlobalSign, 396-day validity, expiring 2027-01-26

DNS operators

Amazon Route 53

HSTS

max-age 3,650 days

DMARC policy

p=quarantine

Homepage HTML

224 KB, gzip

Images on homepage

150 (jpg 94, png 40, svg 16)

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 Fitness & Health sites

• 111.nhs.uk54
• myuncchart.org54
• novantmychart.org54
• s-re.jp54
• shafadoc.ir54

Fitness & Health readiness benchmark