movistar.com.pe

Readiness by lane

Green: movistar.com.pe. Thin bar: Telecommunications & Internet peer median.

Priority fixes for movistar.com.pe

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

1. Priority 1 · Harden

   HTTP requests move to HTTPS

   Observed: A request to http://www.movistar.com.pe/ was not redirected to HTTPS.

   Why it matters: Visitors who type the address or follow an old link start on unencrypted HTTP. A redirect moves them to the encrypted site before any cookies or form data are sent.

   What to do: Add a permanent (301 or 308) redirect from every http:// URL to the same https:// URL at your CDN, load balancer or web server.

   On WordPress: Set both WordPress Address and Site Address to https:// in Settings > General, then add the server or CDN redirect.

   94% of Telecommunications & Internet peers do this. Limit: Measured for the homepage only, from one location, at the time of the check.

   Guide: HTTPS and TLS Guide for Website Owners

2. Priority 2 · Harden

   HSTS kept for at least a year

   Observed: The homepage response did not include a Strict-Transport-Security header.

   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 Azure Front Door/CDN: Add a response header action in a Front Door rule set.

   54% of Telecommunications & Internet peers do this.

   Guide: HTTPS and TLS Guide for Website Owners

3. Priority 3 · Harden

   DMARC policy enforces quarantine or reject

   Observed: The DMARC policy for movistar.com.pe 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.

   Guide: A Practical Website Health Check for Owners

4. Priority 4 · Accelerate

   Static files cached for 30 days or more

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

   On WordPress: Caching plugins or your host can set long browser cache lifetimes for theme and plugin assets.

   41% of Telecommunications & Internet peers do this.

   Guide: Browser Caching Guide for Website Owners

What movistar.com.pe already does well

Practices fewer than half of Telecommunications & Internet peers use.

• Reachable over IPv6IPv6 address published.33% of peers

What we saw

Homepage checked

https://www.movistar.com.pe/

Homepage response

HTTP 200

TLS

TLSv1.3, HTTP/2

Certificate

DigiCert, 183-day validity, expiring 2026-12-12

CDN or edge

Azure Front Door/CDN

Platform or framework

WordPress

DNS operators

1 self-run or other nameserver domain

DMARC policy

p=none

Homepage HTML

605 KB, br

Images on homepage

239 (svg 192, webp 98, 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

Compare with other Telecommunications & Internet sites

• kolbi.cr55
• movistar.com.ar55
• orange.pl54
• spectrum.net55
• tim.com.br54

Telecommunications & Internet readiness benchmark