ctpcj.ro

Readiness by lane

Green: ctpcj.ro. Thin bar: Trains & Public Transport peer median.

Priority fixes for ctpcj.ro

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

1. Priority 1 · Harden

   HSTS kept for at least a year

   Observed: The homepage response did not include a Strict-Transport-Security header.

   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.

   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

   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

   Modern image formats in use

   Observed: The homepage had 18 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 20 external scripts 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 ctpcj.ro already does well

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

• DMARC policy enforces quarantine or rejectDMARC policy p=quarantine.40% of peers

What we saw

Homepage checked

https://ctpcj.ro/

Homepage response

HTTP 200, after 1 redirect

TLS

TLSv1.3, HTTP/2

Certificate

Asseco Data Systems S.A., 198-day validity, expiring 2027-04-26

Platform or framework

Joomla

DNS operators

1 self-run or other nameserver domain

DMARC policy

p=quarantine

Homepage HTML

85 KB, br

Images on homepage

18 (png 13, gif 5)

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

• cp.sk50
• indianrailways.gov.in47
• mavcsoport.hu51
• portalpasazera.pl51
• smart-ex.jp44

Trains & Public Transport readiness benchmark