STATUS IS UPREADINESS PROFILE

Website readiness profile · Snapshot 23 October 2026

verizon.com

verizon.com's public homepage, certificate and DNS checked against 31 practices and compared with 285 Telecommunications & Internet sites.

Readiness index
79/100

Telecommunications & Internet median 67

Ahead of
85%

of measured Telecommunications & Internet sites

Practices observed
22/31

0 of 31 could not be measured

Popularity band
Top 5K

Chrome UX Report top-sites list

Measured 2026-10-23 11:26:07 UTC from one location. How we measure

Readiness by lane

Green: verizon.com. Thin bar: Telecommunications & Internet peer median.

Enable

79/100

Peers 82

Harden

85/100

Peers 61

Accelerate

75/100

Peers 57

Recover

0/100

Peers 16

Priority fixes for verizon.com

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

  1. Priority 1 · 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.

    Why it matters: Returning visitors and later page views reuse cached files instead of downloading them again.

    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. Limit: Read from the homepage response only; other pages or regions may send different headers.

  2. Priority 2 · Enable

    Social preview image set

    Observed: The homepage had no og:image, so shared links may show without a preview image.

    What to do: Add Open Graph tags, including og:image with a 1200 x 630 image.

    59% of Telecommunications & Internet peers do this.

  3. Priority 3 · Enable

    Structured data present

    Observed: The homepage had no JSON-LD structured data.

    What to do: Add JSON-LD for your organization and main content types, then test it with Google's Rich Results Test.

    51% of Telecommunications & Internet peers do this.

  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.

What verizon.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, digicert.com, letsencrypt.org.15% 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.verizon.com/
Homepage response
HTTP 200
TLS
TLSv1.3, HTTP/2
Certificate
DigiCert, 364-day validity, expiring 2026-12-08
CDN or edge
Akamai
Platform or framework
Adobe Experience Manager
DNS operators
Akamai Edge DNS
HSTS
max-age 365 days, includeSubDomains, preload
DMARC policy
p=reject
Homepage HTML
115 KB, gzip
Images on homepage
12

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

Observed 22

  • 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
  • DMARC policy enforces quarantine or reject
  • X-Content-Type-Options: nosniff
  • Framing restricted
  • Content Security Policy present
  • Referrer-Policy set
  • HTTP/2 negotiated
  • HTML compressed
  • Modern image formats in use
  • Offscreen images lazy-loaded
  • No render-blocking scripts in <head>
  • robots.txt published
  • XML sitemap discoverable
  • Canonical URL declared
  • Meta description written
  • Mobile viewport configured
  • Page language declared
  • At most one redirect to the homepage

Own verizon.com?

Re-run the checks after a change, keep a private action plan in a free workspace, or report a mistake.

Live status for this site: Status Is Down: verizon.com. This profile covers configuration only.

Compare with other Telecommunications & Internet sites