invia.cz

Readiness by lane

Green: invia.cz. Thin bar: Travel Bookings & Trip Planning peer median.

Priority fixes for invia.cz

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

1. Priority 1 · Harden

   HSTS kept for at least a year

   Observed: Strict-Transport-Security was sent with a max-age of 14 days, below the one-year benchmark.

   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.

   On Amazon CloudFront: Attach a response headers policy with Strict-Transport-Security to each distribution.

   46% of Travel Bookings & Trip Planning 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 · Accelerate

   Static files cached for 30 days or more

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

   49% of Travel Bookings & Trip Planning peers do this.

   Guide: Browser Caching Guide for Website Owners

3. Priority 3 · Harden

   Framing restricted

   Observed: The homepage did not send frame-ancestors or X-Frame-Options, so other sites may frame it.

   What to do: Send Content-Security-Policy: frame-ancestors 'self' (or a list of trusted origins). X-Frame-Options: SAMEORIGIN covers older browsers.

   On Amazon CloudFront: Set frame options in a response headers policy.

   56% of Travel Bookings & Trip Planning peers do this.

   Guide: A Practical Website Health Check for Owners

4. Priority 4 · Accelerate

   HTTP/3 advertised

   Observed: The homepage did not advertise HTTP/3 through an Alt-Svc header.

   What to do: Turn on HTTP/3 at your CDN. Browsers fall back to HTTP/2 automatically, so the risk is low.

   On Amazon CloudFront: Select HTTP/3 in the distribution's supported HTTP versions.

   33% of Travel Bookings & Trip Planning peers do this.

   Guide: CDN Guide for Website Owners

What invia.cz already does well

Practices fewer than half of Travel Bookings & Trip Planning peers use.

• Modern image formats in useWebP or AVIF images detected.41% of peers
• No render-blocking scripts in <head>Head scripts load without blocking.44% of peers

What we saw

Homepage checked

https://www.invia.cz/

Homepage response

HTTP 200

TLS

TLSv1.3, HTTP/2

Certificate

Amazon, 197-day validity, expiring 2027-01-15

CDN or edge

Amazon CloudFront

DNS operators

Azure DNS

HSTS

max-age 14 days, includeSubDomains

DMARC policy

p=reject

Homepage HTML

479 KB, gzip

Images on homepage

61 (jpg 108, svg 18, avif 4, webp 4)

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 Travel Bookings & Trip Planning sites

• aena.es69
• budget.com69
• cozycozy.com69
• islands.com69
• meinschiff.com69

Travel Bookings & Trip Planning readiness benchmark