cp.pt

Readiness by lane

Green: cp.pt. Thin bar: Trains & Public Transport peer median.

Priority fixes for cp.pt

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

1. Priority 1 · Accelerate

   HTML compressed

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

   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

   HTTP/2 negotiated

   Observed: The TLS handshake selected http/1.1 instead of HTTP/2.

   What to do: Enable HTTP/2 on your CDN or server. Most CDNs do this by default.

   77% of Trains & Public Transport peers do this.

   Guide: CDN Guide for Website Owners

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

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 cp.pt already does well

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

• DNSSEC signedDNSSEC delegation (DS record) present.13% of peers
• Referrer-Policy setReferrer-Policy present.29% of peers
• Content Security Policy presentContent-Security-Policy present.34% of peers

What we saw

Homepage checked

https://www.cp.pt/

Homepage response

HTTP 200, after 1 redirect

TLS

TLSv1.3, http/1.1

Certificate

Sectigo, 396-day validity, expiring 2027-01-23

DNS operators

1 self-run or other nameserver domain

HSTS

max-age 365 days, includeSubDomains, preload

DMARC policy

p=reject

Homepage HTML

3 KB, uncompressed

Images on homepage

0

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.info56
• doko-train.jp58
• itabus.it58
• renfe.com57
• trenes.com58

Trains & Public Transport readiness benchmark