STATUS IS UPREADINESS PROFILE

Website readiness profile · Snapshot 23 October 2026

vodafone.cz

vodafone.cz's public homepage, certificate and DNS checked against 31 practices and compared with 285 Telecommunications & Internet sites.

Readiness index
68/100

Telecommunications & Internet median 67

Ahead of
51%

of measured Telecommunications & Internet sites

Practices observed
19/31

0 of 31 could not be measured

Popularity band
Top 50K

Chrome UX Report top-sites list

Measured 2026-10-23 11:56:08 UTC from one location. How we measure

Readiness by lane

Green: vodafone.cz. Thin bar: Telecommunications & Internet peer median.

Enable

95/100

Peers 82

Harden

57/100

Peers 61

Accelerate

63/100

Peers 57

Recover

0/100

Peers 16

Priority fixes for vodafone.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: 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.

    54% of Telecommunications & Internet peers do this. Limit: Read from the homepage response only; other pages or regions may send different headers.

  2. Priority 2 · Accelerate

    Static files cached for 30 days or more

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

    41% of Telecommunications & Internet peers do this.

  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.

    68% of Telecommunications & Internet peers do this.

  4. Priority 4 · Accelerate

    No render-blocking scripts in <head>

    Observed: The homepage <head> loaded 4 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.

    37% of Telecommunications & Internet peers do this.

What vodafone.cz already does well

Practices fewer than half of Telecommunications & Internet peers use.

  • DNSSEC signedDNSSEC delegation (DS record) present.13% of peers
  • Certificate lifetime of 100 days or lessShort-lived 90-day certificate from GlobalSign nv-sa, already inside the 2027 limit.28% of peers

What we saw

Homepage checked
https://www.vodafone.cz/
Homepage response
HTTP 200
TLS
TLSv1.3, HTTP/2
Certificate
GlobalSign, 90-day validity, expiring 2027-01-19
CDN or edge
Imperva
DNS operators
1 self-run or other nameserver domain
DMARC policy
p=quarantine
Homepage HTML
199 KB, gzip
Images on homepage
36 (webp 51, png 7)

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

Observed 19

  • HTTP requests move to HTTPS
  • TLS 1.3 negotiated
  • Certificate has more than 14 days left
  • Certificate lifetime of 100 days or less
  • DNSSEC signed
  • DMARC policy enforces quarantine or reject
  • HTTP/2 negotiated
  • HTML compressed
  • Modern image formats in use
  • Offscreen images lazy-loaded
  • robots.txt published
  • XML sitemap discoverable
  • Canonical URL declared
  • Meta description written
  • Mobile viewport configured
  • Structured data present
  • Social preview image set
  • Page language declared
  • At most one redirect to the homepage

Own vodafone.cz?

Re-run the checks after a change, or verify the site in a free workspace to save reports with history, compare against similar sites and competitors, and track a private action plan. What owners get.

Live status for this site: Status Is Down: vodafone.cz. This profile covers configuration only.

Compare with other Telecommunications & Internet sites