movistar.es

Readiness by lane

Green: movistar.es. Thin bar: Telecommunications & Internet peer median.

Priority fixes for movistar.es

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

   TLS 1.3 negotiated

   Observed: The TLS connection negotiated TLSv1.2.

   What to do: Enable TLS 1.3 on your CDN or server. Keep TLS 1.2 available for older clients unless you have checked your audience.

   81% of Telecommunications & Internet peers do this.

   Guide: HTTPS and TLS Guide for Website Owners

3. Priority 3 · Harden

   CAA records limit who can issue certificates

   Observed: No CAA record was found for movistar.es, so any public certificate authority may issue for it.

   What to do: Publish CAA records naming every CA you actually use, including the CAs your CDN uses for managed certificates. Add an iodef contact if you want reports.

   15% of Telecommunications & Internet peers do this.

   Guide: HTTPS and TLS Guide for Website Owners

4. Priority 4 · Harden

   security.txt published

   Observed: No valid /.well-known/security.txt with a Contact field was returned.

   What to do: Publish /.well-known/security.txt with at least Contact and Expires fields, as RFC 9116 requires, and review it before it expires.

   13% of Telecommunications & Internet peers do this.

   Guide: A Practical Website Health Check for Owners

What movistar.es already does well

Practices fewer than half of Telecommunications & Internet peers use.

• HTTP/3 advertisedHTTP/3 advertised.13% of peers
• Referrer-Policy setReferrer-Policy present.33% of peers
• No render-blocking scripts in <head>Head scripts load without blocking.37% of peers

What we saw

Homepage checked

https://www.movistar.es/

Homepage response

HTTP 200

TLS

TLSv1.2, http/1.1

Certificate

DigiCert, 198-day validity, expiring 2026-11-11

CDN or edge

Google edge

Platform or framework

WordPress, Next.js, Adobe Experience Manager

DNS operators

1 self-run or other nameserver domain

HSTS

max-age 365 days, includeSubDomains

DMARC policy

p=reject

Homepage HTML

222 KB, gzip

Images on homepage

40 (jpg 63, avif 60, webp 60, png 7)

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

• bouyguestelecom.fr79
• lowi.es79
• meo.pt80
• sky.com79
• telekom.de79

Telecommunications & Internet readiness benchmark