ratbv.ro

Readiness by lane

Green: ratbv.ro. Thin bar: Trains & Public Transport peer median.

Priority fixes for ratbv.ro

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

1. Priority 1 · Accelerate

   HTML compressed

   Observed: The homepage HTML (11 KB) was delivered without gzip, Brotli or zstd compression.

   Why it matters: Compression usually shrinks HTML several times over, so the first bytes of the page arrive sooner on slow connections.

   What to do: Enable Brotli or gzip for text responses (HTML, CSS, JavaScript, JSON, SVG) at the CDN or origin.

   86% of Trains & Public Transport peers do this. Limit: Read from the homepage response only; other pages or regions may send different headers.

   Guide: How to Set a Website Performance Budget That Teams Can Keep

2. Priority 2 · Accelerate

   HTTP/2 negotiated

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

   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.

   Guide: CDN 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 · 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

What ratbv.ro already does well

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

• No render-blocking scripts in <head>Head scripts load without blocking.43% of peers
• Certificate lifetime of 100 days or lessShort-lived 89-day certificate from Let's Encrypt, already inside the 2027 limit.43% of peers

What we saw

Homepage checked

https://www.ratbv.ro/

Homepage response

HTTP 200

TLS

TLSv1.3, http/1.1

Certificate

Let's Encrypt, 89-day validity, expiring 2027-01-10

DNS operators

1 self-run or other nameserver domain

DMARC policy

p=none

Homepage HTML

11 KB, uncompressed

Images on homepage

11 (svg 9, jpg 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

• bus.com.ua32
• imhd.sk36
• korail.com37
• mu-kgt.ru36
• tobus.jp29

Trains & Public Transport readiness benchmark