emtmadrid.es

Readiness by lane

Green: emtmadrid.es. Thin bar: Trains & Public Transport peer median.

Priority fixes for emtmadrid.es

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

1. Priority 1 · Enable

   robots.txt published

   Observed: No robots.txt file was returned at the site root.

   Why it matters: robots.txt is where crawlers look first for crawl rules and sitemap locations. Without it, they assume everything is open.

   What to do: Publish /robots.txt with any crawl rules you need and a Sitemap: line pointing to your XML sitemap.

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

   Guide: Robots.txt Guide: Control Crawling Without Hiding Mistakes

2. Priority 2 · Enable

   XML sitemap discoverable

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

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

   66% of Trains & Public Transport peers do this.

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

3. Priority 3 · Accelerate

   Static files cached for 30 days or more

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

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

What emtmadrid.es 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
• Referrer-Policy setReferrer-Policy present.29% of peers
• Reachable over IPv6IPv6 address published.33% of peers

What we saw

Homepage checked

https://www.emtmadrid.es/

Homepage response

HTTP 200, after 1 redirect

TLS

TLSv1.3, HTTP/2

Certificate

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

DNS operators

2 self-run or other nameserver domains

HSTS

max-age 365 days, includeSubDomains

DMARC policy

p=quarantine

Homepage HTML

91 KB, gzip

Images on homepage

22 (gif 1)

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
• efe.cl63
• obilet.com62
• stib-mivb.be63
• trenitalia.com62

Trains & Public Transport readiness benchmark