ouigo.com

Readiness by lane

Green: ouigo.com. Thin bar: Trains & Public Transport peer median.

Priority fixes for ouigo.com

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

1. Priority 1 · Harden

   HSTS kept for at least a year

   Observed: Strict-Transport-Security was sent with a max-age of 180 days, below the one-year benchmark.

   Why it matters: HSTS tells browsers to use HTTPS for your host on every later visit, which removes the window where a first HTTP request can be intercepted.

   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.

   On Azure Front Door/CDN: Add a response header action in a Front Door rule set.

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

   Guide: HTTPS and TLS Guide for Website Owners

2. Priority 2 · Enable

   Meta description written

   Observed: The homepage had no meta description.

   What to do: Write a short, specific description of the page for people, not a list of keywords.

   82% of Trains & Public Transport peers do this.

   Guide: Meta Titles and Descriptions That Match Search Intent

3. Priority 3 · Accelerate

   Modern image formats in use

   Observed: The homepage had 33 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

   No render-blocking scripts in <head>

   Observed: The homepage <head> loaded 1 external script without async or defer.

   What to do: Add defer to scripts that need the DOM, async to independent ones such as analytics, or move them to the end of the body.

   43% of Trains & Public Transport peers do this.

   Guide: Control Third-Party Scripts Before They Control Your Page

What ouigo.com already does well

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

• Nameservers spread across providersNameservers spread across more than one operator.15% of peers
• Reachable over IPv6IPv6 address published.33% of peers
• Static files cached for 30 days or moreLong-lived caching on static files.38% of peers

What we saw

Homepage checked

https://www.ouigo.com/

Homepage response

HTTP 200

TLS

TLSv1.3, HTTP/2

Certificate

DigiCert, 182-day validity, expiring 2027-04-09

CDN or edge

Azure Front Door/CDN

Platform or framework

Drupal

DNS operators

5 self-run or other nameserver domains

HSTS

max-age 180 days, includeSubDomains

DMARC policy

p=reject

Homepage HTML

122 KB, gzip

Images on homepage

33 (png 22, svg 15)

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

• greyhound.com64
• mbta.com64
• oebb.at64
• tfl.gov.uk64
• transportnsw.info64

Trains & Public Transport readiness benchmark