indianrailways.gov.in

Readiness by lane

Green: indianrailways.gov.in. Thin bar: Trains & Public Transport peer median.

Priority fixes for indianrailways.gov.in

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

1. Priority 1 · Accelerate

   HTML compressed

   Observed: The homepage HTML (109 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 · 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

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

What indianrailways.gov.in already does well

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

• CAA records limit who can issue certificatesCAA limits issuance to emsign.com, letsencrypt.org.8.9% of peers
• Nameservers spread across providersNameservers spread across more than one operator.15% of peers
• Content Security Policy presentContent-Security-Policy present.34% of peers

What we saw

Homepage checked

https://indianrailways.gov.in/

Homepage response

HTTP 200

TLS

TLSv1.2

Certificate

eMudhra Technologies Limited, 70-day validity, expiring 2026-12-01

DNS operators

3 self-run or other nameserver domains

DMARC policy

p=quarantine

Homepage HTML

109 KB, uncompressed

Images on homepage

56 (png 24, svg 18, jpg 1)

Limits: homepage only, one location, one moment. Header checks reflect the homepage response; other pages may differ.

All 31 checks

Select a gap for the method and fix. How each check works

Compare with other Trains & Public Transport sites

• cp.sk50
• ctpcj.ro49
• hankyu.co.jp42
• portalpasazera.pl51
• smart-ex.jp44

Trains & Public Transport readiness benchmark