tnstc.in

Readiness by lane

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

Priority fixes for tnstc.in

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 · 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

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

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 tnstc.in already does well

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

• DMARC policy enforces quarantine or rejectDMARC policy p=quarantine.40% of peers
• HSTS kept for at least a yearHSTS with a 365-day max-age.41% of peers

What we saw

Homepage checked

https://www.tnstc.in/

Homepage response

HTTP 200, after 2 redirects

TLS

TLSv1.3, http/1.1

Certificate

GoDaddy, 368-day validity, expiring 2027-01-05

DNS operators

GoDaddy DNS

HSTS

max-age 365 days

DMARC policy

p=quarantine

Homepage HTML

95 KB, gzip

Images on homepage

22 (png 15, jpg 6, gif 1)

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

• cotralspa.it40
• ctabustracker.com40
• indianrail.gov.in41
• kuruken.jp41
• lefrecce.it41

Trains & Public Transport readiness benchmark