att.net website review

Not measured in this review.

• Real-user TTFB: 1.3 s

  1.3 s

  Real visitors wait 1.3 s for your server to start answering (75th percentile). Good is under 800 ms.

• Tap response (INP) held steady for real visitors

  +6%

  Over the last 25 four-week periods to 2026-10-03, real Chrome visitors' tap response (inp) went from 172 ms to 184 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

• Largest content (LCP) held steady for real visitors

  0%

  Over the last 25 four-week periods to 2026-10-03, real Chrome visitors' largest content (lcp) went from 1.9 s to 1.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

• Page weight: 10.3 MB

  10.3 MB

  Your homepage downloads 10.3 MB on a phone, 6.8 MB of it images (66%). Under 2 MB keeps phones on slow connections fast.

• An image on the first screen is lazy-loaded

  https://d29szjachogqwa.cloudfront.net/images/user-uploaded/9 is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

  Elements (2)

• About 2.9 g of CO₂ per visit

  2.91 g

  By the Sustainable Web Design model, a visit to your homepage emits about 2.91 g of CO₂e: 349.4 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

• Hidden but focusable

  3 elements hidden from screen readers can still receive keyboard focus.

  Elements (3)

• 3 text elements with low contrast

  3 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

  Elements (3)

• Page should contain a level-one heading (1 element)

  Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

  Elements (1)

• 14 links without text

  14 visible links have no text or label, so screen readers cannot say where they go.

  Elements (1)

• ARIA role should be appropriate for the element (1 element)

  ARIA role should be appropriate for the element: 1 element on the page fails this check, rated minor by axe-core.

  Elements (1)

• No H1 headline

  There is no <h1>, so neither visitors nor Google get a clear main headline.

• No structured data

  No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

• No social preview image

  No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

• No XML sitemap

  No XML sitemap at https://currently.att.yahoo.com/sitemap.xml, so Google discovers your pages only by following links.

• No X (Twitter) card tag

  No twitter:card tag. X falls back to Open Graph, which is incomplete here.

• 21 internal links, 20 external

  The homepage links to 21 pages on att.net and 20 external pages.

• robots.txt blocks 2 AI answer engine crawlers

  2 of 6

  Your robots.txt shuts out ChatGPT (ChatGPT-User) and Perplexity (PerplexityBot). These fetch pages to answer people's questions and cite the source, so your site can't be quoted or linked in those answers.

• No Organization structured data

  There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

• No llms.txt

  There is no /llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.

• Opted out of AI training for 4 crawlers

  robots.txt blocks GPTBot, ClaudeBot, Google-Extended and CCBot, which collect pages to train models. That's a legitimate choice and doesn't by itself stop the site appearing in AI answers.

• 15 internal pages checked

  We fetched 15 pages linked from your homepage (of 17 found) and read each the way a search engine does.

• 1 broken image

  1 image failed to load on a phone, for example https://api.reg.yahoo.com/issueIUCookie?signature=EAfp78mgbiDAcNv1Ses4G4VOLbPYfgqcAd1GFAbr5JQ=&partner=sbc&ts=1791766013.

• 13 small tap targets

  13 of 48 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

• 3 JavaScript errors while loading

  3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_SOCKET_NOT_CONNECTED”.

• 2 redirects before the homepage

  Opening https://att.net goes through 2 redirects before the homepage loads.

• 3 links through redirect chains

  3 links go through two or more redirects, for example https://mail.yahoo.com/?.intl=us&.partner=sbc&.lang=en-US.

• No Permissions-Policy

  No Permissions-Policy header to switch off camera, microphone and location for embedded content.

• DNSSEC is off

  yahoo.com's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.

• No call to action on the first screen

  On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

• No calls to action

  We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

• Local business without LocalBusiness data

  Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

• No phone number on the homepage

  A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

• No analytics detected

  No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

• No direct contact details

  No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

• No opening hours

  The homepage shows no opening hours. If customers visit or call, show when.

• No map or directions link

  There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

• No risk reducer

  No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

• About 631 words of copy

  The homepage carries about 631 words of visible text.

• No DMARC policy

  att.net has no DMARC record, so nothing tells receivers what to do with mail that fails SPF or DKIM. Gmail and Yahoo require DMARC from bulk senders.

• No SPF record

  att.net has no SPF record, so mail servers can't tell which servers may send email as you. Your mail lands in spam more often, and anyone can send mail pretending to be you.

• No DKIM key on the usual selectors

  We found no DKIM key on the selectors the big email providers use. If you send through one of them, turning on DKIM signing improves delivery.

• Email authentication score: 0/100

  Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

• 8 trackers load before any consent

  8

  Before a visitor clicks anything, the page loads Comscore, Criteo, Google Ads, Google Analytics and Google Tag Manager and 3 mores (measured from a US location before any click). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.

• 26 cookies set on arrival

  26

  Opening the homepage sets 26 cookies, 2 of them by other companies (measured from a US location before any click).

• No consent tool detected

  No known cookie consent tool loads with the page. Some sites build their own banner, and some only show one to visitors from the EU.

• 48 other companies contacted

  Loading the homepage contacts 48 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.