oebb.at

Readiness by lane

Green: oebb.at. Thin bar: Trains & Public Transport peer median.

Priority fixes for oebb.at

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

   TLS 1.3 negotiated

   Observed: The TLS connection negotiated TLSv1.2.

   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.

   85% of Trains & Public Transport peers do this.

   Guide: HTTPS and TLS Guide for Website Owners

3. Priority 3 · Enable

   robots.txt published

   Observed: No robots.txt file was returned at the site root.

   What to do: Publish /robots.txt with any crawl rules you need and a Sitemap: line pointing to your XML sitemap.

   81% of Trains & Public Transport peers do this.

   Guide: Robots.txt Guide: Control Crawling Without Hiding Mistakes

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

   66% of Trains & Public Transport peers do this.

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

What oebb.at already does well

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

• security.txt publishedsecurity.txt with a contact found.9.5% of peers
• Nameservers spread across providersNameservers spread across more than one operator.15% of peers
• Modern image formats in useWebP or AVIF images detected.28% of peers

What we saw

Homepage checked

https://www.oebb.at/

Homepage response

HTTP 200

TLS

TLSv1.2, http/1.1

Certificate

DigiCert, 384-day validity, expiring 2026-12-08

DNS operators

2 self-run or other nameserver domains

HSTS

max-age 365 days

DMARC policy

p=none

Homepage HTML

175 KB, gzip

Images on homepage

82 (jpg 120, svg 16, png 12)

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

• autogari.ro64
• greyhound.com64
• mbta.com64
• ouigo.com64
• tfl.gov.uk64

Trains & Public Transport readiness benchmark