recorrido.cl

Readiness by lane

Green: recorrido.cl. Thin bar: Trains & Public Transport peer median.

Priority fixes for recorrido.cl

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

1. Priority 1 · Harden

   DMARC policy enforces quarantine or reject

   Observed: The DMARC policy for recorrido.cl was p=none, which asks receivers to take no action on failing mail.

   Why it matters: An enforcing DMARC policy helps receiving mail systems reject email that falsely claims to come from your domain, a common route for phishing your customers.

   What to do: Publish DMARC with p=none and a reporting address first, fix any legitimate senders that fail SPF or DKIM alignment, then move to quarantine and finally reject.

   40% of Trains & Public Transport peers do this. Limit: Read from public DNS at the time of the check; records may have changed since.

   Guide: A Practical Website Health Check for Owners

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

3. Priority 3 · Harden

   Framing restricted

   Observed: The homepage did not send frame-ancestors or X-Frame-Options, so other sites may frame it.

   What to do: Send Content-Security-Policy: frame-ancestors 'self' (or a list of trusted origins). X-Frame-Options: SAMEORIGIN covers older browsers.

   55% of Trains & Public Transport peers do this.

   Guide: A Practical Website Health Check for Owners

4. Priority 4 · Accelerate

   Offscreen images lazy-loaded

   Observed: The homepage had 35 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 recorrido.cl already does well

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

• Modern image formats in useWebP or AVIF images detected.28% of peers
• Referrer-Policy setReferrer-Policy present.29% of peers
• Structured data presentJSON-LD structured data found.33% of peers

What we saw

Homepage checked

https://www.recorrido.cl/

Homepage response

HTTP 200, after 1 redirect

TLS

TLSv1.3, HTTP/2

Certificate

Amazon, 197-day validity, expiring 2027-03-18

DNS operators

Amazon Route 53

HSTS

max-age 730 days, includeSubDomains, preload

DMARC policy

p=none

Homepage HTML

312 KB, gzip

Images on homepage

35 (jpg 16, png 12, webp 4, svg 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

• 9292.nl72
• bcferries.com70
• horaires-de-trains.fr70
• kupos.cl73
• queropassagem.com.br71

Trains & Public Transport readiness benchmark