ee.co.uk

Readiness by lane

Green: ee.co.uk. Thin bar: Telecommunications & Internet peer median.

Priority fixes for ee.co.uk

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

1. Priority 1 · Harden

   HSTS kept for at least a year

   Observed: Strict-Transport-Security was sent with a max-age of 0 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.

   Guide: HTTPS and TLS Guide for Website Owners

2. Priority 2 · Accelerate

   Static files cached for 30 days or more

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

3. Priority 3 · Accelerate

   Offscreen images lazy-loaded

   Observed: The homepage had 40 images and none used loading="lazy".

   What to do: Add loading="lazy" to images below the fold. Do not lazy-load the main hero image, because that delays the largest visible element.

   66% of Telecommunications & Internet peers do this.

   Guide: Lazy Loading Without Broken Pages

4. Priority 4 · Accelerate

   No render-blocking scripts in <head>

   Observed: The homepage <head> loaded 1 external script 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.

   On Next.js: Use the next/script component with an appropriate loading strategy.

   37% of Telecommunications & Internet peers do this.

   Guide: Control Third-Party Scripts Before They Control Your Page

What ee.co.uk already does well

Practices fewer than half of Telecommunications & Internet peers use.

• security.txt publishedsecurity.txt with a contact found.13% of peers
• CAA records limit who can issue certificatesCAA limits issuance to amazon.com, geotrust.com, globalsign.com and others.15% of peers
• Content Security Policy presentContent-Security-Policy present.48% of peers

What we saw

Homepage checked

https://ee.co.uk/

Homepage response

HTTP 200

TLS

TLSv1.3, HTTP/2

Certificate

DigiCert, 393-day validity, expiring 2026-11-20

CDN or edge

Imperva

Platform or framework

Next.js, Adobe Experience Manager

DNS operators

Amazon Route 53

HSTS

max-age 0 days

DMARC policy

p=reject

Homepage HTML

219 KB, gzip

Images on homepage

40 (webp 38, png 2)

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

• airtelkenya.com70
• klarmobil.de70
• odido.nl70
• vodacom.co.za71
• vodafone.es71

Telecommunications & Internet readiness benchmark