telekom.si

Readiness by lane

Green: telekom.si. Thin bar: Telecommunications & Internet peer median.

Priority fixes for telekom.si

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

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

   Why it matters: Returning visitors and later page views reuse cached files instead of downloading them again.

   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. Limit: Read from the homepage response only; other pages or regions may send different headers.

   Guide: Browser Caching Guide for Website Owners

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

   Guide: A Practical Website Health Check for Owners

3. Priority 3 · Harden

   Content Security Policy present

   Observed: The homepage response did not include a Content-Security-Policy header.

   What to do: Start with Content-Security-Policy-Report-Only to see what would break, tighten the policy over a few weeks, then enforce it.

   48% of Telecommunications & Internet peers do this.

   Guide: Payment Security and PCI DSS: What Website Owners Need to Know

4. Priority 4 · Harden

   X-Content-Type-Options: nosniff

   Observed: The homepage response did not include X-Content-Type-Options: nosniff.

   What to do: Send X-Content-Type-Options: nosniff on all responses and make sure each file is served with the correct Content-Type.

   64% of Telecommunications & Internet peers do this.

   Guide: A Practical Website Health Check for Owners

What telekom.si already does well

Practices fewer than half of Telecommunications & Internet peers use.

• CAA records limit who can issue certificatesCAA limits issuance to digicert.com.15% of peers
• No render-blocking scripts in <head>Head scripts load without blocking.37% of peers

What we saw

Homepage checked

https://www.telekom.si/

Homepage response

HTTP 200

TLS

TLSv1.3, HTTP/2

Certificate

DigiCert, 198-day validity, expiring 2027-04-12

Platform or framework

Angular

DNS operators

1 self-run or other nameserver domain

HSTS

max-age 730 days, includeSubDomains, preload

DMARC policy

p=reject

Homepage HTML

1,573 KB, gzip

Images on homepage

28 (jpg 69, svg 7, png 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 Telecommunications & Internet sites

• au.com76
• claro.com.gt77
• cricketwireless.com76
• fizz.ca77
• jazztel.com77

Telecommunications & Internet readiness benchmark