att.net

Readiness by lane

Green: att.net. Thin bar: Webmail & Message Inboxes peer median.

Priority fixes for att.net

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 Webmail & Message Inboxes 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 · Accelerate

   Modern image formats in use

   Observed: The homepage had 37 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.

   On Next.js: The next/image component serves optimized formats automatically.

   41% of Webmail & Message Inboxes peers do this.

   Guide: AVIF, WebP, JPEG, and PNG: Choose the Right Image Format

3. Priority 3 · Enable

   At most one redirect to the homepage

   Observed: The homepage was reached after 2 redirects.

   What to do: Point every alternate address (http, www or apex, old paths) straight to the final URL in a single redirect.

   85% of Webmail & Message Inboxes peers do this.

   Guide: Technical SEO Audit: A Practical Owner’s Guide

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.

   30% of Webmail & Message Inboxes peers do this.

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

What att.net already does well

Practices fewer than half of Webmail & Message Inboxes peers use.

• Social preview image setog:image present.36% of peers
• Content Security Policy presentContent-Security-Policy present.42% of peers
• Referrer-Policy setReferrer-Policy present.42% of peers

What we saw

Homepage checked

https://www.att.net/

Homepage response

HTTP 200, after 2 redirects

TLS

TLSv1.3, http/1.1

Certificate

DigiCert, 198-day validity, expiring 2027-03-21

Platform or framework

Next.js

DNS operators

1 self-run or other nameserver domain

HSTS

max-age 365 days

DMARC policy

p=quarantine

Homepage HTML

480 KB, gzip

Images on homepage

37 (jpg 19, png 11)

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 Webmail & Message Inboxes sites

• generator.email70
• laposte.net68
• libero.it67
• privateemail.com70
• web.de71

Webmail & Message Inboxes readiness benchmark