swisscom.ch

Readiness by lane

Green: swisscom.ch. Thin bar: Telecommunications & Internet peer median.

Priority fixes for swisscom.ch

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.

   72% of Telecommunications & Internet 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

   HSTS kept for at least a year

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

   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.

   Guide: HTTPS and TLS Guide for Website Owners

3. Priority 3 · Accelerate

   Modern image formats in use

   Observed: The homepage had 11 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.

   52% of Telecommunications & Internet peers do this.

   Guide: AVIF, WebP, JPEG, and PNG: Choose the Right Image Format

4. Priority 4 · Accelerate

   Static files cached for 30 days or more

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

   Guide: Browser Caching Guide for Website Owners

What swisscom.ch already does well

Practices fewer than half of Telecommunications & Internet peers use.

• security.txt publishedsecurity.txt with a contact found.13% of peers
• Reachable over IPv6IPv6 address published.33% of peers
• Referrer-Policy setReferrer-Policy present.33% of peers

What we saw

Homepage checked

https://www.swisscom.ch/

Homepage response

HTTP 200, after 1 redirect

TLS

TLSv1.3

Certificate

SwissSign AG, 198-day validity, expiring 2027-01-06

Platform or framework

Adobe Experience Manager

DNS operators

1 self-run or other nameserver domain

HSTS

max-age 186 days, includeSubDomains

DMARC policy

p=reject

Homepage HTML

490 KB, gzip

Images on homepage

11 (png 16)

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

• koodomobile.com63
• superonline.net63
• totalwireless.com63
• tuenti.com.ar64
• yousee.dk63

Telecommunications & Internet readiness benchmark