iett.istanbul

Readiness by lane

Green: iett.istanbul. Thin bar: Trains & Public Transport peer median.

Priority fixes for iett.istanbul

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

1. Priority 1 · Accelerate

   HTML compressed

   Observed: The homepage HTML (99 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 · 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 iett.istanbul already does well

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

• DMARC policy enforces quarantine or rejectDMARC policy p=reject.40% of peers
• HSTS kept for at least a yearHSTS with a 365-day max-age.41% of peers
• No render-blocking scripts in <head>Head scripts load without blocking.43% of peers

What we saw

Homepage checked

https://iett.istanbul/

Homepage response

HTTP 200

TLS

TLSv1.2

Certificate

Sectigo, 372-day validity, expiring 2027-01-27

DNS operators

1 self-run or other nameserver domain

HSTS

max-age 365 days

DMARC policy

p=reject

Homepage HTML

99 KB, uncompressed

Images on homepage

86 (svg 56, jpg 15, png 13)

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

• delhimetrorail.info56
• grandtrain.ru56
• kudikina.ru55
• onlineksrtcswift.com55
• renfe.com57

Trains & Public Transport readiness benchmark