4.6 sec in total
271 ms
4 sec
325 ms
Welcome to m.att.com homepage info - get ready to check M AT T best content for United States right away, or after learning these important things about m.att.com
Shop deals on new phones, unlimited data plans, home internet with AT&T Fiber, and DIRECTV STREAM. Get 24/7 support, pay your bills & manage your account online.
Visit m.att.comWe analyzed M.att.com page load time and found that the first response time was 271 ms and then it took 4.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
m.att.com performance score
name
value
score
weighting
Value5.9 s
4/100
10%
Value9.4 s
0/100
25%
Value9.5 s
12/100
10%
Value5,300 ms
0/100
30%
Value0
100/100
15%
Value33.5 s
0/100
10%
271 ms
453 ms
56 ms
81 ms
97 ms
Our browser made a total of 77 requests to load all elements on the main page. We found that 61% of them (47 requests) were addressed to the original M.att.com, 17% (13 requests) were made to Att.com and 4% (3 requests) were made to Att.inq.com. The less responsive or slowest element that took the longest time to load (1.9 sec) belongs to the original domain M.att.com.
Page size can be reduced by 4.2 MB (72%)
5.8 MB
1.6 MB
In fact, the total size of M.att.com main page is 5.8 MB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 55% of websites need less resources to load. Javascripts take 5.1 MB which makes up the majority of the site volume.
Potential reduce by 64.7 kB
HTML content can be minified and compressed by a website’s server. The most efficient way is to compress content using GZIP which reduces data amount travelling through the network between server and browser. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 64.7 kB or 79% of the original size.
Potential reduce by 11.8 kB
Image size optimization can help to speed up a website loading time. The chart above shows the difference between the size before and after optimization. M AT T images are well optimized though.
Potential reduce by 4.1 MB
It’s better to minify JavaScript in order to improve website performance. The diagram shows the current total size of all JavaScript files against the prospective JavaScript size after its minification and compression. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 4.1 MB or 81% of the original size.
Potential reduce by 17.6 kB
CSS files minification is very important to reduce a web page rendering time. The faster CSS files can load, the earlier a page can be rendered. M.att.com needs all CSS files to be minified and compressed as it can save up to 17.6 kB or 63% of the original size.
Number of requests can be reduced by 38 (51%)
75
37
The browser has sent 75 CSS, Javascripts, AJAX and image requests in order to completely render the main page of M AT T. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 39 to 1 for JavaScripts and as a result speed up the page load time.
m.att.com
271 ms
m.att.com
453 ms
jquery.min.js
56 ms
utils.min.js
81 ms
granite.min.js
97 ms
jquery.min.js
95 ms
clientlib.min.css
268 ms
edmDataManager.js
93 ms
edmDataDefinition.js
92 ms
session.js
524 ms
clientlib.min.js
211 ms
clientlib.min.js
401 ms
GVP.js
330 ms
clientlib.min.js
173 ms
tealeaf.min.4.0.1607.shopmobile.js
170 ms
satelliteLib-bee1ce9b89e943a46b1dfd167adc564fe75eef37.js
328 ms
shared.min.js
223 ms
underscore.min.js
232 ms
kernel.min.js
260 ms
BrowserDetect.js
325 ms
mGlobalnav.js
407 ms
dcs_tag_DTM.js
143 ms
index.initsession.xhr.html
151 ms
index.userinfo.xhr.html
153 ms
mbox-contents-3fe7f1ac02f9f751c9c175021a5f0779a4287d23.js
31 ms
analytics.js
174 ms
target.js
244 ms
ajax
186 ms
18983
166 ms
rd
48 ms
id
853 ms
devicecategory.ajax.xhr.html
1924 ms
plancategory.ajax.xhr.html
894 ms
satellite-54d1307a3935650016830000.js
749 ms
s-code-contents-65778bc202aa3fe01113e6b6ea6d103eda099fe5.js
755 ms
_jcr_content.atgprofile.xhr.json
769 ms
retrievePersonalizationInfo
865 ms
fusion-sprite.png
429 ms
pixel-url.img
219 ms
index.json
162 ms
mGlobalnav.min.css
145 ms
oo_engine.min.js
322 ms
collect
706 ms
collect
838 ms
satellite-54fdfdc16637360016010200.js
222 ms
ajax
113 ms
ATT_Sprite_Retina_v3.2.2.png
266 ms
inqChatLaunch10004119.js
312 ms
dcs_tag_DTM.js
195 ms
oo_conf_mobile.js
119 ms
att-mob-sprite.png
98 ms
resolvePage
62 ms
_jcr_content.content.html
39 ms
inqChat.html
210 ms
JSAM_min.css
278 ms
oo_engine.min.js
235 ms
267447-m-mrq-iphone6se-buy-now-640x380-p.jpg
216 ms
266649-M-SS-BigTV-Deal-640.jpg
363 ms
265935-m-Switch-Score-350-Homepage-4-14-640x380-p.jpg
642 ms
263293-m-mrq-iphone6s-bogo-p.jpg
236 ms
267447-m-mrq-iphone6se-buy-now-960x300-l.jpg
249 ms
266649-M-SS-BigTV-Deal-960.jpg
296 ms
265935-m-Switch-Score-350-Homepage-4-13-960x300-l.jpg
329 ms
263293-m-mrq-iphone6s-bogo-l.jpg
305 ms
Omnes_ATTW02-Bold.woff
441 ms
Omnes_ATTW02-BoldItalic.woff
457 ms
Omnes_ATTW02-Italic.woff
639 ms
Omnes_ATTW02-Light.woff
641 ms
Omnes_ATTW02-LightItalic.woff
678 ms
Omnes_ATTW02-Medium.woff
714 ms
Omnes_ATTW02-MediumItalic.woff
741 ms
Omnes_ATTW02.woff
729 ms
site_10004119_default.js
325 ms
_jcr_content.content.html
368 ms
_jcr_content.content.html
391 ms
oo_engine.min.js
166 ms
oo_engine.min.js
156 ms
m.att.com accessibility score
m.att.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
m.att.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Mobile Friendly
Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).
Impact
Issue
Document uses legible font sizes
Tap targets are not sized appropriately
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise M.att.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that M.att.com main page’s claimed encoding is utf-8. Use of this encoding format is the best practice as the main page visitors from all over the world won’t have any issues with symbol transcription.
m.att.com
Open Graph data is detected on the main page of M AT T. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: