mavcsoport.hu

Readiness by lane

Green: mavcsoport.hu. Thin bar: Trains & Public Transport peer median.

Priority fixes for mavcsoport.hu

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

1. Priority 1 · Accelerate

   HTTP/2 negotiated

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

   Why it matters: HTTP/2 sends many files over one connection, which speeds up pages with lots of images, styles and scripts.

   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. Limit: Certificate and protocol were observed from one vantage point; CDNs can present different certificates by region.

   Guide: CDN Guide for Website Owners

2. Priority 2 · Harden

   TLS 1.3 negotiated

   Observed: The TLS connection negotiated TLSv1.2.

   What to do: Enable TLS 1.3 on your CDN or server. Keep TLS 1.2 available for older clients unless you have checked your audience.

   85% of Trains & Public Transport peers do this.

   Guide: HTTPS and TLS Guide for Website Owners

3. Priority 3 · Harden

   HSTS kept for at least a year

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

   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.

   Guide: HTTPS and TLS Guide for Website Owners

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

What mavcsoport.hu already does well

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

• CAA records limit who can issue certificatesCAA limits issuance to e-szigno.hu, letsencrypt.org.8.9% of peers
• Nameservers spread across providersNameservers spread across more than one operator.15% of peers
• Content Security Policy presentContent-Security-Policy present.34% of peers

What we saw

Homepage checked

https://www.mavcsoport.hu/

Homepage response

HTTP 200

TLS

TLSv1.2

Certificate

Microsec Ltd., 395-day validity, expiring 2027-02-20

Platform or framework

Drupal

DNS operators

2 self-run or other nameserver domains

DMARC policy

p=reject

Homepage HTML

80 KB, gzip

Images on homepage

38 (png 25, jpg 12)

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
• highwaybus.com51
• idos.cz51
• portalpasazera.pl51
• railway.gov.tw52

Trains & Public Transport readiness benchmark