Website readiness profile · Snapshot 23 October 2026
orange.pl
orange.pl's public homepage, certificate and DNS checked against 31 practices and compared with 285 Telecommunications & Internet sites.
- Readiness index
- 54/100
- Ahead of
- 18%
- Practices observed
- 14/30
- Popularity band
- Top 50K
Telecommunications & Internet median 67
of measured Telecommunications & Internet sites
1 of 31 could not be measured
Chrome UX Report top-sites list
Readiness by lane
Green: orange.pl. Thin bar: Telecommunications & Internet peer median.
Enable
95/100
Peers 82
Harden
38/100
Peers 61
Accelerate
42/100
Peers 57
Recover
0/100
Peers 16
Priority fixes for orange.pl
Ordered by impact and by how common each practice is among peers.
Priority 1 · 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.
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 Next.js: Add the header in the headers() option of next.config.js for all routes.
54% of Telecommunications & Internet peers do this. Limit: Read from the homepage response only; other pages or regions may send different headers.
Priority 2 · Harden
DMARC policy enforces quarantine or reject
Observed: The DMARC policy for orange.pl was p=none, which asks receivers to take no action on failing mail.
What to do: Publish DMARC with p=none and a reporting address first, fix any legitimate senders that fail SPF or DKIM alignment, then move to quarantine and finally reject.
59% of Telecommunications & Internet peers do this.
Priority 3 · Accelerate
Modern image formats in use
Observed: The homepage had 5 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.
On Next.js: The next/image component serves optimized formats automatically.
52% of Telecommunications & Internet peers do this.
Guide: AVIF, WebP, JPEG, and PNG: Choose the Right Image Format
Priority 4 · 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.
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.
What we saw
- Homepage checked
- https://www.orange.pl/
- Homepage response
- HTTP 200
- TLS
- TLSv1.3, HTTP/2
- Certificate
- DigiCert, 198-day validity, expiring 2026-12-17
- Platform or framework
- Next.js
- DNS operators
- 1 self-run or other nameserver domain
- HSTS
- max-age 186 days, includeSubDomains, preload
- DMARC policy
- p=none
- Homepage HTML
- 301 KB, gzip
- Images on homepage
- 5 (svg 3, png 3)
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
Not observed 16
- HSTS kept for at least a year
- Certificate lifetime of 100 days or less
- CAA records limit who can issue certificates
- DNSSEC signed
- security.txt published
- DMARC policy enforces quarantine or reject
- X-Content-Type-Options: nosniff
- Framing restricted
- Content Security Policy present
- Referrer-Policy set
- HTTP/3 advertised
- Static files cached for 30 days or more
- Modern image formats in use
- No render-blocking scripts in <head>
- Reachable over IPv6
- Nameservers spread across providers
Observed 14
- HTTP requests move to HTTPS
- TLS 1.3 negotiated
- Certificate has more than 14 days left
- HTTP/2 negotiated
- HTML compressed
- 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
Not measured 1
- Offscreen images lazy-loaded
Own orange.pl?
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: orange.pl. This profile covers configuration only.