Website readiness profile · Snapshot 23 October 2026
telmex.com
telmex.com's public homepage, certificate and DNS checked against 31 practices and compared with 285 Telecommunications & Internet sites.
- Readiness index
- 59/100
- Ahead of
- 27%
- Practices observed
- 15/31
- Popularity band
- Top 50K
Telecommunications & Internet median 67
of measured Telecommunications & Internet sites
0 of 31 could not be measured
Chrome UX Report top-sites list
Readiness by lane
Green: telmex.com. Thin bar: Telecommunications & Internet peer median.
Enable
59/100
Peers 82
Harden
66/100
Peers 61
Accelerate
50/100
Peers 57
Recover
0/100
Peers 16
Priority fixes for telmex.com
Ordered by impact and by how common each practice is among peers.
Priority 1 · Harden
DMARC policy enforces quarantine or reject
Observed: The DMARC policy for telmex.com was p=none, which asks receivers to take no action on failing mail.
Why it matters: An enforcing DMARC policy helps receiving mail systems reject email that falsely claims to come from your domain, a common route for phishing your customers.
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. Limit: Read from public DNS at the time of the check; records may have changed since.
Priority 2 · Accelerate
Modern image formats in use
Observed: The homepage had 52 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.
52% of Telecommunications & Internet peers do this.
Guide: AVIF, WebP, JPEG, and PNG: Choose the Right Image Format
Priority 3 · 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
Priority 4 · Accelerate
Static files cached for 30 days or more
Observed: A same-site stylesheet or script was cacheable for 1 days, 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 telmex.com already does well
Practices fewer than half of Telecommunications & Internet peers use.
- CAA records limit who can issue certificatesCAA limits issuance to amazon.com, comodoca.com, digicert.com and others.15% of peers
- No render-blocking scripts in <head>Head scripts load without blocking.37% of peers
- Content Security Policy presentContent-Security-Policy present.48% of peers
What we saw
- Homepage checked
- https://telmex.com/
- Homepage response
- HTTP 200
- TLS
- TLSv1.3, HTTP/2
- Certificate
- DigiCert, 198-day validity, expiring 2027-04-18
- DNS operators
- 1 self-run or other nameserver domain
- HSTS
- max-age 365 days, includeSubDomains
- DMARC policy
- p=none
- Homepage HTML
- 335 KB, gzip
- Images on homepage
- 52 (jpg 26, png 13)
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
- Certificate lifetime of 100 days or less
- DNSSEC signed
- security.txt published
- DMARC policy enforces quarantine or reject
- Framing restricted
- Referrer-Policy set
- HTTP/3 advertised
- Static files cached for 30 days or more
- Modern image formats in use
- Offscreen images lazy-loaded
- Reachable over IPv6
- Canonical URL declared
- Meta description written
- Structured data present
- Social preview image set
- Nameservers spread across providers
Observed 15
- HTTP requests move to HTTPS
- HSTS kept for at least a year
- TLS 1.3 negotiated
- Certificate has more than 14 days left
- CAA records limit who can issue certificates
- X-Content-Type-Options: nosniff
- Content Security Policy present
- HTTP/2 negotiated
- HTML compressed
- No render-blocking scripts in <head>
- robots.txt published
- XML sitemap discoverable
- Mobile viewport configured
- Page language declared
- At most one redirect to the homepage
Own telmex.com?
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: telmex.com. This profile covers configuration only.
Compare with other Telecommunications & Internet sites
- a1.hr58
- im3.id59
- myt.mu58
- softbank.jp59
- te.eg59