efe.cl

Readiness by lane

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

Priority fixes for efe.cl

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

1. Priority 1 · Enable

   XML sitemap discoverable

   Observed: No sitemap was listed in robots.txt or found at /sitemap.xml.

   Why it matters: A sitemap helps search engines find new and updated pages, especially on large or frequently updated sites.

   What to do: Generate an XML sitemap of canonical URLs, reference it in robots.txt and submit it in Google Search Console.

   On WordPress: WordPress has generated a basic sitemap at /wp-sitemap.xml since 5.5; SEO plugins can replace it.

   66% of Trains & Public Transport peers do this. Limit: Only the standard location was requested, once, at the time of the check.

   Guide: XML Sitemap Guide: Include Only URLs You Stand Behind

2. Priority 2 · Harden

   DMARC policy enforces quarantine or reject

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

   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.

   Guide: A Practical Website Health Check for Owners

3. Priority 3 · Accelerate

   Static files cached for 30 days or more

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

   On WordPress: Caching plugins or your host can set long browser cache lifetimes for theme and plugin assets.

   38% of Trains & Public Transport peers do this.

   Guide: Browser Caching Guide for Website Owners

4. Priority 4 · Accelerate

   Modern image formats in use

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

   On WordPress: WordPress has supported WebP uploads since 5.8 and AVIF since 6.5; image plugins or the host can convert existing images.

   28% of Trains & Public Transport peers do this.

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

What efe.cl 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
• HSTS kept for at least a yearHSTS with a 365-day max-age covering subdomains.41% of peers

What we saw

Homepage checked

https://www.efe.cl/

Homepage response

HTTP 200

TLS

TLSv1.3, HTTP/2

Certificate

Let's Encrypt, 89-day validity, expiring 2026-12-18

Platform or framework

WordPress

DNS operators

1 self-run or other nameserver domain

HSTS

max-age 365 days, includeSubDomains

DMARC policy

p=none

Homepage HTML

393 KB, br

Images on homepage

93 (jpg 86, png 72, svg 2)

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

• bushikaku.net62
• delhimetrorail.com63
• stib-mivb.be63
• tfl.gov.uk64
• transportnsw.info64

Trains & Public Transport readiness benchmark