Skip to content
https://att.com

Lighthouse Mobile

· 0 checks — Mobile Lighthouse audit -- Performance, Accessibility, Best Practices, and SEO category breakdown.
SCORE
0
GRADE
FIX
0
REVIEW
0
PASS
0
INFO
0

Detailed Report

Audit breakdown by category with detailed findings.

29

Performance

Insights

Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Polyfills and transforms enable older browsers to use new JavaScript features. However, many aren't necessary for modern browsers. Consider modifying your JavaScript build process to not transpile Baseline features, unless you know you must support older browsers. Learn why most sites can deploy ES6+ code without transpiling

Why this matters

Performance issues directly impact user engagement and conversion rates.

3rd party code can significantly impact load performance. Reduce and defer loading of 3rd party code to prioritize your page's content.

Why this matters

Performance issues directly impact user engagement and conversion rates.

A long cache lifetime can speed up repeat visits to your page. Learn more about caching.

Why this matters

Performance issues directly impact user engagement and conversion rates.

RequestCache TTLTransfer Size
www.att.com/chat/vendor.3bead717194d1db70967.js0.0 ms1.4 MiB
www.att.com/chat/main.2f20a27ebbd2c708b679.js0.0 ms481.1 KiB
cdn.quantummetric.com/qscripts/quantum-att.js300.0 s224.9 KiB
/enkelF6GShZjrsdHKwEMJHpQ6yQ/9wEOVzJaY1iYXkQO3p/MigqcywGT...21600.0 s182.2 KiB
/enkelF6GShZjrsdHKwEMJHpQ6yQ/9wEOVzJaY1iYXkQO3p/MigqcywGT...21600.0 s182.1 KiB
/signals/config/263973384029222?v=2.9.269&r=stable&domain...1200.0 s118.7 KiB
www.att.com/marketing/_next/static/chunks/267.7b34b28dad4a2ea0.js86400.0 s186.7 KiB
www.att.com/marketing/_next/static/chunks/91.12480f890e44bdeb.js86400.0 s139.1 KiB
www.att.com/auto-static-pages/nav/component.js?ct=a3943cc900.0 s50.2 KiB
www.att.com/marketing/_next/static/chunks/256-5c16d630bb9fe017.js86400.0 s89.8 KiB
www.att.com/scripts/adobe/prod/mbox-contents-v2.js3600.0 s44.9 KiB
assets.adobedtm.com/784fdfb70d09/eda645f0abc0/launch-05d1e3f92bae.min.js3600.0 s43.9 KiB
www.att.com/marketing/_next/static/chunks/196.fd5ee18b3fd65790.js86400.0 s81.2 KiB
www.att.com/marketing/_next/static/chunks/main-df5c36a2e9e7e18d.js86400.0 s77.8 KiB
www.att.com/MEG/chatserver/js/jsPlugin.js0.0 ms28.2 KiB
www.att.com/scripts/ssaf_universal_client/prod/ssaf-uc.js3600.0 s33.4 KiB
www.att.com/marketing/_next/static/chunks/905.d2a428f87753318f.js86400.0 s52.3 KiB
www.att.com/marketing/_next/static/chunks/pages/_page-e23d986491f3717f.js86400.0 s47.1 KiB
www.att.com/marketing/_next/static/chunks/145.e588f977467d4e17.js86400.0 s43.6 KiB
www.att.com/marketing/_next/static/chunks/739.93cb783417708fe7.js86400.0 s42.5 KiB
www.att.com/scripts/adobe/prod/visitor.js3600.0 s20.9 KiB
/signals/config/427667220899227?v=2.9.269&r=stable&domain...1200.0 s14.7 KiB
www.att.com/marketing/_next/static/chunks/330.f5cca9824c1866c4.js86400.0 s31.7 KiB
www.att.com/auto-static-pages/nav/header.js?ct=a3943cc900.0 s13.6 KiB
scripts.clarity.ms/0.8.59/clarity.js86400.0 s26.2 KiB
www.att.com/marketing/_next/static/chunks/522-0ef319cd8268ba7b.js86400.0 s26.1 KiB
ucm-us.verint-cdn.com/files/sites/att/live/sdk.js86400.0 s19.6 KiB
www.att.com/marketing/_next/static/chunks/pages/_app-d1b14e4c5b4e6aa3.js86400.0 s18.1 KiB
www.att.com/scripts/adobe/prod/gpi.js3600.0 s8.6 KiB
www.att.com/auto-static-pages/nav/service.js?ct=a3943cc900.0 s7.3 KiB
www.att.com/akam/13/3f17e21b21600.0 s9.4 KiB
s2.go-mpulse.net/boomerang/WPDUB-APVCN-LTNDE-ZPC3E-YKMHC604800.0 s57.7 KiB
www.att.com/scripts/adobe/prod/cobrowse_main.min.js3600.0 s5.4 KiB
www.att.com/chat/runtime.6404741a5640753c7d59.js0.0 ms3.9 KiB
www.att.com/scripts/adobe/prod/datp-mvp.js3600.0 s3.8 KiB
www.att.com/marketing/_next/static/chunks/888-9455b47a42377797.js86400.0 s7.5 KiB
www.att.com/scripts/adobe/prod/smart-banner.js3600.0 s3.7 KiB
ucm-us.verint-cdn.com/files/sites/att/live/customcode.js86400.0 s4.6 KiB
www.att.com/marketing/_next/static/chunks/706-1bd809abfdd7e573.js86400.0 s3.5 KiB
signin.att.com/static/ciam/en/common/js/keepAlive.js0.0 ms1.0 KiB
www.att.com/marketing/_next/static/chunks/webpack-c7874e330a91c4d5.js86400.0 s2.4 KiB
www.att.com/scripts/adobe/prod/adobeLaunch-abs.js3600.0 s816 B
www.att.com/scripts/adobe/prod/ssaf-mvp-loader.js3600.0 s575 B
insight.adsrvr.org/track/pxl/?adv=texq94s&ct=0:0rsar66&fmt=30.0 ms149 B
www.att.com/marketing/_next/static/1776109432743/_buildManifest.js2535621.0 s1.1 KiB
www.att.com/marketing/_next/static/1776109432743/_ssgManifest.js2535621.0 s815 B
/tr/?id=263973384029222&ev=PageView&dl=https%3A%2F%2Fwww....0.0 ms19 B
/tr/?id=427667220899227&ev=PageView&dl=https%3A%2F%2Fwww....0.0 ms16 B
/a?v=3&t=l&pid=168417233&rv=64h1&tag_exp=0~115616986~1159...0.0 ms11 B
cdn.quantummetric.com/qscripts/quantum-att.js300.0 s0 B
s2.go-mpulse.net/boomerang/WPDUB-APVCN-LTNDE-ZPC3E-YKMHC604800.0 s0 B

Your first network request is the most important. Reduce its latency by avoiding redirects, ensuring a fast server response, and enabling text compression.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Consider setting font-display to swap or optional to ensure text is consistently visible. swap can be further optimized to mitigate layout shifts with font metric overrides.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Optimize LCP by making the LCP image discoverable from the HTML immediately, and avoiding lazy-loading

Why this matters

Performance issues directly impact user engagement and conversion rates.

lhId: page-0-DIV
nodeLabel: div > div.jsx-2913604578 > div.max-width-background > div#background-background
path: 1,HTML,2,BODY,1,DIV,1,DIV,3,DIV,0,DIV,1,DIV
selector: div > div.jsx-2913604578 > div.max-width-background > div#background-background
snippet: <div class="absolute-fill bg-no-repeat zoomable" id="background-background">

Avoid chaining critical requests by reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.

Why this matters

Performance issues directly impact user engagement and conversion rates.

More than 4 preconnect connections were found. These should be used sparingly and only to the most important origins.
description: [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints help the browser establish a connection earlier in the page load, saving time when the first request for that origin is made. The following are the origins that the page preconnected to.
title: Preconnected origins
description: Add [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints to your most important origins, but try to use no more than 4.
title: Preconnect candidates
value: No additional origins are good candidates for preconnecting

Requests are blocking the page's initial render, which may delay LCP. Deferring or inlining can move these network requests out of the critical path.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Reducing the download time of images can improve the perceived load time of the page and LCP. Learn more about optimizing image size

Why this matters

Performance issues directly impact user engagement and conversion rates.

URLResource SizeEst Savings
div > div.max-width-background > div.jsx-1049057036 > div#heropanel_HP-0-background div > div.max-width-background > div.jsx-1049057036 > div#heropanel_HP-0-background
/scmsassets/upper_funnel/internet/7110800-base-hero-150ff...148.1 KiB23.9 KiB

These insights are also available in the Chrome DevTools Performance Panel - record a trace to view more detailed information.

Time to Interactive is the amount of time it takes for the page to become fully interactive. Learn more about the Time to Interactive metric.

Why this matters

Performance issues directly impact user engagement and conversion rates.

TTI

The maximum potential First Input Delay that your users could experience is the duration of the longest task. Learn more about the Maximum Potential First Input Delay metric.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 1.3 s
URLTime Spent
att.com/1.3 s
www.att.com/0.0 ms

Keep the server response time for the main document short because all other requests depend on it. Learn more about the Time to First Byte metric.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 839 ms
URLTime Spent
www.att.com/939 ms

Diagnostics

Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity. Learn how to reduce unused CSS.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 1.1 s 1.9 MiB
URLTransfer SizeEst Savings
www.att.com/chat/vendor.3bead717194d1db70967.js1.4 MiB578.1 KiB
www.att.com/chat/main.2f20a27ebbd2c708b679.js480.4 KiB167.4 KiB
www.att.com/marketing/_next/static/chunks/267.7b34b28dad4a2ea0.js185.9 KiB131.2 KiB
www.att.com/marketing/_next/static/chunks/91.12480f890e44bdeb.js138.4 KiB111.9 KiB
www.att.com/marketing/_next/static/chunks/196.fd5ee18b3fd65790.js80.5 KiB71.4 KiB
www.att.com/scripts/adobe/prod/marketing.min.js128.2 KiB65.7 KiB
www.googletagmanager.com/gtag/js?id=AW-1036745755&cx=c&gtm=4e64h1136.5 KiB61.3 KiB
www.googletagmanager.com/gtag/js?id=DC-6143919&cx=c&gtm=4e64h1130.9 KiB60.7 KiB
www.googletagmanager.com/gtm.js?id=GTM-PQ6DMZSB158.7 KiB58.6 KiB
www.att.com/marketing/_next/static/chunks/256-5c16d630bb9fe017.js89.1 KiB57.6 KiB
www.att.com/chat/130.7 KiB51.3 KiB
www.att.com/marketing/_next/static/chunks/905.d2a428f87753318f.js51.6 KiB50.1 KiB
www.googletagmanager.com/gtag/js?id=AW-1049001539&cx=c&gtm=4e5bc1150.0 KiB48.5 KiB
cdn.quantummetric.com/qscripts/quantum-att.js224.3 KiB46.9 KiB
cdn.quantummetric.com/qscripts/quantum-att.js224.3 KiB45.7 KiB
www.att.com/marketing/_next/static/chunks/145.e588f977467d4e17.js42.9 KiB40.0 KiB
/enkelF6GShZjrsdHKwEMJHpQ6yQ/9wEOVzJaY1iYXkQO3p/MigqcywGT...181.0 KiB38.4 KiB
/enkelF6GShZjrsdHKwEMJHpQ6yQ/9wEOVzJaY1iYXkQO3p/MigqcywGT...181.0 KiB38.2 KiB
/signals/config/263973384029222?v=2.9.269&r=stable&domain...118.6 KiB35.5 KiB
www.att.com/auto-static-pages/nav/component.js?ct=a3943cc49.9 KiB35.1 KiB
www.att.com/scripts/adobe/prod/facebook.js86.4 KiB32.9 KiB
www.att.com/marketing/_next/static/chunks/739.93cb783417708fe7.js41.7 KiB31.9 KiB
www.att.com/81.9 KiB31.7 KiB
www.att.com/marketing/_next/static/chunks/main-df5c36a2e9e7e18d.js77.1 KiB31.1 KiB
www.att.com/marketing/_next/static/chunks/pages/_page-e23d986491f3717f.js46.3 KiB30.0 KiB
s2.go-mpulse.net/boomerang/WPDUB-APVCN-LTNDE-ZPC3E-YKMHC57.6 KiB20.1 KiB

Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to reduce Javascript execution time.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URLTotal CPU TimeScript EvaluationScript Parse
www.att.com/8.6 s5.3 s96 ms
Unattributable3.9 s649 ms0.0 ms
www.att.com/chat/vendor.3bead717194d1db70967.js1.8 s1.7 s33 ms
s2.go-mpulse.net/boomerang/WPDUB-APVCN-LTNDE-ZPC3E-YKMHC1.8 s1.5 s35 ms
cdn.quantummetric.com/qscripts/quantum-att.js1.6 s1.3 s165 ms
/enkelF6GShZjrsdHKwEMJHpQ6yQ/9wEOVzJaY1iYXkQO3p/MigqcywGT...1.5 s1.3 s103 ms
www.att.com/chat/801 ms653 ms95 ms
www.googletagmanager.com/gtm.js?id=GTM-PQ6DMZSB751 ms688 ms51 ms
ucm-us.verint-cdn.com/files/modules/unified-websdk/3.7.0/visitor.js603 ms587 ms2.9 ms
www.att.com/marketing/_next/static/chunks/pages/_page-e23d986491f3717f.js508 ms491 ms16 ms
ucm-us.verint-cdn.com/files/modules/unified-websdk/3.7.0/rules-engine.js463 ms441 ms3.3 ms
www.att.com/marketing/_next/static/chunks/main-df5c36a2e9e7e18d.js432 ms375 ms20 ms
/signals/config/263973384029222?v=2.9.269&r=stable&domain...369 ms337 ms29 ms
www.googletagmanager.com/gtag/js?id=AW-1036745755&cx=c&gtm=4e64h1366 ms262 ms36 ms
www.googletagmanager.com/gtag/js?id=AW-1049001539&cx=c&gtm=4e5bc1334 ms297 ms36 ms
www.att.com/scripts/adobe/prod/marketing.min.js215 ms174 ms41 ms
scripts.clarity.ms/0.8.59/clarity.js205 ms192 ms10 ms
www.att.com/chat/main.2f20a27ebbd2c708b679.js202 ms172 ms9.7 ms
www.googletagmanager.com/gtag/js?id=DC-6143919&cx=c&gtm=4e64h1180 ms146 ms33 ms
www.att.com/akam/13/3f17e21b169 ms156 ms5.0 ms
www.att.com/scripts/adobe/prod/mbox-contents-v2.js161 ms137 ms18 ms
www.att.com/auto-static-pages/nav/component.js?ct=a3943cc144 ms104 ms0.8 ms
www.att.com/scripts/adobe/prod/visitor.js143 ms127 ms6.0 ms
www.att.com/scripts/adobe/prod/facebook.js115 ms85 ms29 ms
assets.adobedtm.com/784fdfb70d09/eda645f0abc0/launch-05d1e3f92bae.min.js113 ms81 ms29 ms
www.att.com/MEG/chatserver/js/jsPlugin.js104 ms82 ms14 ms
/infy/acs/account/uiiyot1djz/js/business/analytics-produc...92 ms84 ms2.9 ms
www.att.com/marketing/_next/static/chunks/267.7b34b28dad4a2ea0.js70 ms1.2 ms66 ms
www.att.com/auto-static-pages/nav/header.js?ct=a3943cc66 ms10 ms0.2 ms
/signals/config/427667220899227?v=2.9.269&r=stable&domain...66 ms53 ms5.3 ms
www.att.com/scripts/adobe/prod/engage.min.js64 ms54 ms7.6 ms
ucm-us.verint-cdn.com/files/modules/unified-websdk/3.7.0/database.js62 ms60 ms0.6 ms
www.clarity.ms/tag/uet/18003891?conversions=1&insights=151 ms49 ms0.4 ms
www.att.com/scripts/adobe/prod/gpi.js50 ms33 ms5.0 ms

Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to minimize main-thread work

Why this matters

Performance issues directly impact user engagement and conversion rates.

CategoryTime Spent
Script Evaluation18.3 s
Other6.4 s
Script Parsing & Compilation1.2 s
Garbage Collection522 ms
Style & Layout243 ms
Rendering162 ms
Parse HTML & CSS144 ms

Minifying JavaScript files can reduce payload sizes and script parse time. Learn how to minify JavaScript.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 0.0 ms 602.7 KiB

More information about the performance of your application. These numbers don't directly affect the Performance score.

Layout shift culprits
Optimize DOM size
Forced reflow
LCP breakdown
Modern HTTP
Optimize viewport for mobile
User Timing marks and measures 143 user timings
Avoid long main-thread tasks 20 long tasks found
Image elements have explicit `width` and `height`
Page didn't prevent back/forward cache restoration
Network Requests
Network Round Trip Times 170 ms
Server Backend Latencies 360 ms
Tasks
Diagnostics
Metrics
Screenshot Thumbnails
Final Screenshot
Script Treemap Data
Resources Summary
Avoid large layout shifts 1 layout shift found
INP breakdown
Avoid non-composited animations
98

Accessibility

These checks highlight opportunities to improve the accessibility of your web app. Automatic detection can only detect a subset of issues and does not guarantee the accessibility of your web app, so manual testing is also encouraged.

Best practices

One main landmark helps screen reader users navigate a web page. Learn more about landmarks.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html.theme-att-2022 html.theme-att-2022

These items highlight common accessibility best practices.

Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
ORDER NOW body > div#__next > div > a#link-:R26j6:
Shop now div > div.type-base > strong > a
See offer details div.jsx-2874297542 > div.microbanner-pad > div#legalId_Legal > button.btn-reset
See offer details div.jsx-2114025360 > div.jsx-2114025360 > div#card-40-legal_Legal > button.btn-reset
Shop now div.jsx-2114025360 > div.jsx-2114025360 > div.cta-container > a#button-:R456kij6H1:
See offer details div.jsx-4241832964 > div.jsx-4241832964 > div#card-41-legal_Legal > button.btn-reset
Shop now div.jsx-4241832964 > div.jsx-4241832964 > div.cta-container > a#button-:Rc5akij6H1:
See offer details div.row > div.flex-self-center > div#heropanel_HP-3_Legal > button.btn-reset
Interactive controls are keyboard focusable
Interactive elements indicate their purpose and state
The page has a logical tab order
Visual order on the page follows DOM order
User focus is not accidentally trapped in a region
The user's focus is directed to new content added to the page
HTML5 landmark elements are used to improve navigation
Offscreen content is hidden from assistive technology
Custom controls have associated labels
Custom controls have ARIA roles
`[aria-*]` attributes match their roles
`[aria-hidden="true"]` is not present on the document `<body>`
`[role]`s have all required `[aria-*]` attributes
`[role]` values are valid
`[aria-*]` attributes have valid values
`[aria-*]` attributes are valid and not misspelled
Buttons have an accessible name
`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
`button`, `link`, and `menuitem` elements have accessible names
ARIA attributes are used as specified for the element's role
`[aria-hidden="true"]` elements do not contain focusable descendents
Elements use only permitted ARIA attributes
Background and foreground colors have a sufficient contrast ratio
Document has a `<title>` element
`<frame>` or `<iframe>` elements have a title
`<html>` element has a `[lang]` attribute
`<html>` element has a valid value for its `[lang]` attribute
Links are distinguishable without relying on color.
Links have a discernible name
Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
No element has a `[tabindex]` value greater than 0
Touch targets have sufficient size and spacing.
Heading elements appear in a sequentially-descending order
Deprecated ARIA roles were not used
`[accesskey]` values are unique
Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
ARIA input fields have accessible names
ARIA `meter` elements have accessible names
ARIA `progressbar` elements have accessible names
Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
`[role]`s are contained by their required parent element
Elements with the `role=text` attribute do not have focusable descendents.
ARIA toggle fields have accessible names
ARIA `tooltip` elements have accessible names
ARIA `treeitem` elements have accessible names
The page contains a heading, skip link, or landmark region
`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
Definition list items are wrapped in `<dl>` elements
ARIA IDs are unique
No form fields have multiple labels
`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.
Image elements have `[alt]` attributes
Input buttons have discernible text.
`<input type="image">` elements have `[alt]` text
Form elements have associated labels
The document does not use `<meta http-equiv="refresh">`
`<object>` elements have alternate text
Select elements have associated label elements.
Skip links are focusable.
Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
`[lang]` attributes have a valid value
`<video>` elements contain a `<track>` element with `[kind="captions"]`
Tables have different content in the summary attribute and `<caption>`.
All heading elements contain content.
Uses ARIA roles only on compatible elements
Image elements do not have `[alt]` attributes that are redundant text.
Identical links have the same purpose.
Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.
`<td>` elements in a large `<table>` have one or more table headers.
77

Best Practices

General

Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Deprecation / WarningSource
AttributionReporting

Errors logged to the console indicate unresolved problems. They can come from network request failures and other browser concerns. Learn more about this errors in console diagnostic audit

Why this matters

Performance issues directly impact user engagement and conversion rates.

SourceDescription
Access to XMLHttpRequest at 'https://fid.agkn.com/f?apiKey=2676946699&1pc=18789812083435352743657027715098502178&i4==141.227.188.220' from origin 'https://www.att.com' has been blocked by CORS policy: The value of the 'Access-Control-Allow-Origin' header in the response must not be the wildcard '*' when the request's credentials mode is 'include'. The credentials mode of requests initiated by the XMLHttpRequest is controlled by the withCredentials attribute.
Access to XMLHttpRequest at 'https://fid.agkn.com/f?apiKey=2797353676&1pc=18789812083435352743657027715098502178&i4==141.227.188.220' from origin 'https://www.att.com' has been blocked by CORS policy: The value of the 'Access-Control-Allow-Origin' header in the response must not be the wildcard '*' when the request's credentials mode is 'include'. The credentials mode of requests initiated by the XMLHttpRequest is controlled by the withCredentials attribute.
ChunkLoadError: Loading chunk node_modules_pnpm_web-vitals_3_5_2_node_modules_web-vitals_dist_web-vitals_js failed. (error: https://www.att.com/enkelF6GShZjrsdHKwEMJHpQ6yQ/9wEOVzJaY1iYXkQO3p/MigqcywGTg/SnU/node_modules_pnpm_web-vitals_3_5_2_node_modules_web-vitals_dist_web-vitals_js.3b28ec967b2cf282eaf1.js) at __webpack_require__.f.j (https://www.att.com/chat/runtime.6404741a5640753c7d59.js:262:29) at https://www.att.com/chat/runtime.6404741a5640753c7d59.js:105:40 at Array.reduce (<anonymous>) at __webpack_require__.e (https://www.att.com/chat/runtime.6404741a5640753c7d59.js:104:67) at reportWebVitals (https://www.att.com/chat/main.2f20a27ebbd2c708b679.js:51639:29) at 93107 (https://www.att.com/chat/main.2f20a27ebbd2c708b679.js:51714:1) at __webpack_require__ (https://www.att.com/chat/runtime.6404741a5640753c7d59.js:29:42) at __webpack_exec__ (https://www.att.com/chat/main.2f20a27ebbd2c708b679.js:52564:48) at https://www.att.com/chat/main.2f20a27ebbd2c708b679.js:52565:54 at __webpack_require__.O (https://www.att.com/chat/runtime.6404741a5640753c7d59.js:66:23)
www.att.com/ line 1223, col 0
Error: <svg> attribute height: Expected length, "inherit".
www.att.com/ line 1223, col 0
Error: <svg> attribute width: Expected length, "inherit".
Failed to load resource: net::ERR_FAILED
Failed to load resource: net::ERR_FAILED
Failed to load resource: the server responded with a status of 404 ()
ReferenceError: index is not defined at toLoadAdvertisement (https://www.att.com/scripts/adobe/prod/visitor.js:2:68514) at HTMLScriptElement.onLoad (https://www.att.com/marketing/_next/static/chunks/pages/_app-d1b14e4c5b4e6aa3.js:1:54047) at HTMLScriptElement.<anonymous> (https://www.att.com/marketing/_next/static/chunks/main-df5c36a2e9e7e18d.js:1:33285)
www.att.com/chat/ line 418, col 352
Warning: ReactDOM.render is no longer supported in React 18. Use createRoot instead. Until you switch to the new API, your app will behave as if it's running React 17. Learn more: https://reactjs.org/link/switch-to-createroot

Source maps translate minified code to the original source code. This helps developers debug in production. In addition, Lighthouse is able to provide further insights. Consider deploying source maps to take advantage of these benefits. Learn more about source maps.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Uses HTTPS
Avoids third-party cookies
Allows users to paste into input fields
Avoids requesting the geolocation permission on page load
Avoids requesting the notification permission on page load
Displays images with correct aspect ratio
Serves images with appropriate resolution
Page has the HTML doctype
Properly defines charset
No issues in the `Issues` panel in Chrome Devtools
Ensure CSP is effective against XSS attacks
Use a strong HSTS policy
Ensure proper origin isolation with COOP
Mitigate DOM-based XSS with Trusted Types
Detected JavaScript libraries
Redirects HTTP traffic to HTTPS
Mitigate clickjacking with XFO or CSP
83

SEO

These checks ensure that your page is following basic search engine optimization advice. There are many additional factors Lighthouse does not score here that may affect your search ranking, including performance on Core Web Vitals. Learn more about Google Search Essentials.

Crawling and Indexing

Search engines may use `href` attributes on links to crawl websites. Ensure that the `href` attribute of anchor elements links to an appropriate destination, so more pages of the site can be discovered. Learn how to make links crawlable

Why this matters

Performance issues directly impact user engagement and conversion rates.

Uncrawlable Link
Ver en español div.mega-universal-nav-row > div.container > div.flex > a.link-text
Ver en español div.flex-1 > ul.font-bold > li > a.flex

If your robots.txt file is malformed, crawlers may not be able to understand how you want your website to be crawled or indexed. Learn more about robots.txt.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Line #ContentError
102Disallow: https://pre-www.att.com/home-phone/lifeline/Pattern should either be empty, start with "/" or "*"
326Disallow: https://pre-www.att.com/home-phone/lifeline/Pattern should either be empty, start with "/" or "*"

To appear in search results, crawlers need access to your app.

Structured data is valid
Page isn’t blocked from indexing
Document has a `<title>` element
Document has a meta description
Page has successful HTTP status code
Links have descriptive text
Document has a valid `hreflang`
Document has a valid `rel=canonical`
Image elements have `[alt]` attributes

Send Feedback