kosokubus.com

Readiness by lane

Green: kosokubus.com. Thin bar: Trains & Public Transport peer median.

Priority fixes for kosokubus.com

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

1. Priority 1 · Accelerate

   HTTP/2 negotiated

   Observed: The TLS handshake selected http/1.1 instead of HTTP/2.

   Why it matters: HTTP/2 sends many files over one connection, which speeds up pages with lots of images, styles and scripts.

   What to do: Enable HTTP/2 on your CDN or server. Most CDNs do this by default.

   77% of Trains & Public Transport peers do this. Limit: Certificate and protocol were observed from one vantage point; CDNs can present different certificates by region.

   Guide: CDN Guide for Website Owners

2. Priority 2 · 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.

   41% of Trains & Public Transport peers do this.

   Guide: HTTPS and TLS Guide for Website Owners

3. Priority 3 · Harden

   DMARC policy enforces quarantine or reject

   Observed: The DMARC policy for kosokubus.com 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.

   40% of Trains & Public Transport peers do this.

   Guide: A Practical Website Health Check for Owners

4. Priority 4 · 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.

   38% of Trains & Public Transport peers do this.

   Guide: Browser Caching Guide for Website Owners

What kosokubus.com already does well

Practices fewer than half of Trains & Public Transport peers use.

• Modern image formats in useWebP or AVIF images detected.28% of peers
• Referrer-Policy setReferrer-Policy present.29% of peers
• Structured data presentJSON-LD structured data found.33% of peers

What we saw

Homepage checked

https://www.kosokubus.com/

Homepage response

HTTP 200

TLS

TLSv1.3, http/1.1

Certificate

Let's Encrypt, 89-day validity, expiring 2026-12-15

DNS operators

1 self-run or other nameserver domain

DMARC policy

p=none

Homepage HTML

248 KB, gzip

Images on homepage

95 (png 75, webp 21, jpg 9, svg 8, gif 2)

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 Trains & Public Transport sites

• emtmadrid.es62
• obilet.com62
• pinskap.by61
• plataforma10.com.ar61
• trenitalia.com62

Trains & Public Transport readiness benchmark