orange.fr

Readiness by lane

Green: orange.fr. Thin bar: Telecommunications & Internet peer median.

Priority fixes for orange.fr

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 · Enable

   Meta description written

   Observed: The homepage had no meta description.

   What to do: Write a short, specific description of the page for people, not a list of keywords.

   91% of Telecommunications & Internet peers do this.

   Guide: Meta Titles and Descriptions That Match Search Intent

3. Priority 3 · Enable

   Canonical URL declared

   Observed: The homepage did not declare a canonical URL.

   What to do: Add a self-referencing canonical link to every indexable page, using the final https:// URL.

   76% of Telecommunications & Internet peers do this.

   Guide: Canonical Tags: A Decision Guide for Duplicate URLs

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

What orange.fr 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
• No render-blocking scripts in <head>Head scripts load without blocking.37% of peers

What we saw

Homepage checked

https://www.orange.fr/

Homepage response

HTTP 200, after 1 redirect

TLS

TLSv1.3

Certificate

DigiCert, 198-day validity, expiring 2027-01-09

DNS operators

1 self-run or other nameserver domain

HSTS

max-age 365 days

DMARC policy

p=quarantine

Homepage HTML

1 KB, gzip

Images on homepage

0

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

• astrasms.com65
• connect.net.pk64
• o2online.es65
• red-by-sfr.fr65
• yettel.hu66

Telecommunications & Internet readiness benchmark