transportnsw.info

Readiness by lane

Green: transportnsw.info. Thin bar: Trains & Public Transport peer median.

Priority fixes for transportnsw.info

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

1. Priority 1 · Accelerate

   HTML compressed

   Observed: The homepage HTML (237 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.

   On Amazon CloudFront: Enable Compress objects automatically on the cache behaviour.

   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

   Static files cached for 30 days or more

   Observed: A same-site stylesheet or script was cacheable for 14 days, 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

3. Priority 3 · Accelerate

   Modern image formats in use

   Observed: The homepage had 11 images and none used WebP or AVIF.

   What to do: Serve WebP or AVIF with a JPEG or PNG fallback, either through an image CDN or by generating both formats at build time.

   28% of Trains & Public Transport peers do this.

   Guide: AVIF, WebP, JPEG, and PNG: Choose the Right Image Format

4. Priority 4 · Accelerate

   Offscreen images lazy-loaded

   Observed: The homepage had 11 images and none used loading="lazy".

   What to do: Add loading="lazy" to images below the fold. Do not lazy-load the main hero image, because that delays the largest visible element.

   43% of Trains & Public Transport peers do this.

   Guide: Lazy Loading Without Broken Pages

What transportnsw.info already does well

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

• Referrer-Policy setReferrer-Policy present.29% of peers
• Content Security Policy presentContent-Security-Policy present.34% of peers
• DMARC policy enforces quarantine or rejectDMARC policy p=reject.40% of peers

What we saw

Homepage checked

https://transportnsw.info/

Homepage response

HTTP 200

TLS

TLSv1.3, HTTP/2

Certificate

Amazon, 197-day validity, expiring 2027-04-17

CDN or edge

Amazon CloudFront

Platform or framework

Drupal

DNS operators

Amazon Route 53

HSTS

max-age 365 days, includeSubDomains, preload

DMARC policy

p=reject

Homepage HTML

237 KB, uncompressed

Images on homepage

11 (jpg 30, png 3)

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.com63
• efe.cl63
• oebb.at64
• ouigo.com64
• tfl.gov.uk64

Trains & Public Transport readiness benchmark