1.6 sec in total
58 ms
1.1 sec
455 ms
Visit my.att.net now to see the best up-to-date My AT T content for United States and also check out these interesting facts you probably never knew about my.att.net
Get the latest in news, entertainment, sports, weather and more on Currently.com. Sign up for free email service with AT&T Yahoo Mail.
Visit my.att.netWe analyzed My.att.net page load time and found that the first response time was 58 ms and then it took 1.5 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 30% of websites can load faster.
my.att.net performance score
name
value
score
weighting
Value3.7 s
28/100
10%
Value6.0 s
13/100
25%
Value8.1 s
21/100
10%
Value2,640 ms
4/100
30%
Value0
100/100
15%
Value16.9 s
5/100
10%
58 ms
422 ms
80 ms
73 ms
72 ms
Our browser made a total of 86 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original My.att.net, 2% (2 requests) were made to Currently.att.yahoo.com and 2% (2 requests) were made to Edge-mcdn.secure.yahoo.com. The less responsive or slowest element that took the longest time to load (422 ms) relates to the external source Currently.att.yahoo.com.
Page size can be reduced by 909.0 kB (43%)
2.1 MB
1.2 MB
In fact, the total size of My.att.net main page is 2.1 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. 70% of websites need less resources to load. HTML takes 1.1 MB which makes up the majority of the site volume.
Potential reduce by 901.5 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 901.5 kB or 80% of the original size.
Potential reduce by 3.4 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. My AT T images are well optimized though.
Potential reduce by 4.0 kB
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. This website has mostly compressed JavaScripts.
Potential reduce by 37 B
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. My.att.net has all CSS files already compressed.
Number of requests can be reduced by 36 (46%)
79
43
The browser has sent 79 CSS, Javascripts, AJAX and image requests in order to completely render the main page of My 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 37 to 1 for JavaScripts and as a result speed up the page load time.
currently.att.yahoo.com
58 ms
currently.att.yahoo.com
422 ms
cmp.js
80 ms
tdv2-wafer-utils.customErrorHandler.bcda778b736c3a054af62f437b536e78.js
73 ms
fpDesktop.2e8440661542e9dfceb3228f597ec875.js
72 ms
benji-2.1.39.js
74 ms
wf-caas-1.36.5.js
71 ms
wf-toggle-1.15.4.js
71 ms
react-wafer-featurebar.custom.default.95a7979b4c06295e22960043d003fb49.js
78 ms
wf-clipboard-copy-1.0.2.js
76 ms
wf-video-3.1.2.js
76 ms
wf-bind-1.1.3.js
75 ms
wf-text-1.2.0.js
76 ms
wf-fetch-1.19.1.js
76 ms
wf-benji-1.1.4.js
80 ms
wf-scrollview-2.22.6.js
80 ms
wf-beacon-1.3.4.js
79 ms
wf-action-1.8.1.js
79 ms
wf-template-1.4.3.js
81 ms
wf-menu-1.3.0.js
81 ms
wf-countdown-1.2.5.js
82 ms
wf-form-1.34.5.js
82 ms
wf-lightbox-1.10.6.js
83 ms
wf-native-da-1.0.5.js
82 ms
wf-image-1.4.0.js
85 ms
wf-rapid-1.10.8.js
83 ms
react-wafer-stream.custom.default.34fba140d46159f80d116c63459e57e7.js
85 ms
f59534f.caas-news_web.min.js
93 ms
cerebro_min.js
30 ms
att_homepage_en-US_s_f_p_bestfit_homepage.png
52 ms
header_1x-1479864976616.min.png
51 ms
spritify-sprite-light-fd484ded-e3dce7a4.png
41 ms
Medium.woff
51 ms
Regular.woff
51 ms
Light.woff
45 ms
ExtraLight.woff
64 ms
Semibold.woff
50 ms
f56668f0-02cf-11ef-94fa-d6ef9256a0d6.cf.jpg
21 ms
d7795030-0e02-11ef-a35b-84d3abaff420.cf.jpg
22 ms
c8d793c0-0df3-11ef-ad56-7ee0b5184342.cf.jpg
11 ms
46fdb9e0-0d9b-11ef-bcfc-66a51cc884f0.cf.jpg
11 ms
11cb69d0-0d90-11ef-956f-31256fc971f0.cf.jpg
11 ms
92763460-0dfa-11ef-affb-41edf5f0a298.cf.jpg
19 ms
cafdfe23cbd301f00b75275506b08c2e.cf.jpg
20 ms
trendingNow.yhome-atomic.c16f97f81be530fa2b48a1ffeffd4678.min.css
8 ms
trendingNow-flameIcon.yhome-variable.a2368adb8251677d29ac1399a6f34c43.min.css
10 ms
analytics-3.54.3.js
27 ms
wf-core-1.65.1.js
30 ms
safe.min.js
29 ms
advertisement_0.0.19.js
30 ms
fb7c1f5690db56750c8772181e75c2da.cf.jpg
210 ms
ae5b0e3d76fa33146f87380f3409f5c5.cf.jpg
31 ms
cc5da7872050d80238fcb0b7a7c4aef9.cf.jpg
30 ms
7755ad4663351d31c1a585a8d5d5804e.cf.jpg
210 ms
a146f0183582db4b7f0d22d7d8e1237a.cf.jpg
211 ms
149537df4495ab5079508dd290d21563.cf.jpg
214 ms
40880dd11a7c5a14dfde7f929c173229.cf.jpg
208 ms
5ae688fb0aec52dbbaccbca64d8a6977.cf.jpg
207 ms
c8c4594b304806b181771ac2de0d8c04.cf.jpg
211 ms
50f88e528bb6540429be5ff4027169fa.cf.jpg
212 ms
83d4a629a6fbc65bdad819be25f3b57f.cf.jpg
216 ms
3e1159f8cc264e0a8bb41849b8889c75.cf.jpg
213 ms
b836fe404659555e034a5de885209e1c.cf.jpg
214 ms
28d36bea8f826b9e56ada03d3b911ca4.cf.jpg
214 ms
bda610ce372197f903106f7266e2e450.cf.jpg
225 ms
11d646364701220e6e09034259e93b78.cf.jpg
220 ms
5d2f0e9ef268f3eec750033a06cb1577.cf.jpg
218 ms
e4680a1873890984c8d7c88ec4e7894b.cf.jpg
216 ms
cc3dc531ad48d08ff35b87b44f3e0f34.cf.jpg
215 ms
fca15ce333d731d3beef3b9358266307.cf.jpg
218 ms
528cf820-fb80-11ee-bff1-95bb1220b2b5.cf.jpg
216 ms
e25a246798a266138373e478f5001754.cf.jpg
218 ms
73f1a76e108367611fe6d1ab82b78329.cf.jpg
224 ms
54d4c550c74f78f908d33ce4324b8944.cf.jpg
224 ms
c72a6a30-0c99-11ef-bdb7-3975c7604b18.cf.jpg
220 ms
e2b3992b0342a9d664511c57596f018a.cf.jpg
225 ms
aa723403edff11e629cb7269030f9bbb.cf.jpg
226 ms
7125fc70-0c95-11ef-ad5f-b06ab14ba4b3.cf.jpg
224 ms
d6bc4c1bf5428c7ad643e9ec9f5fdbf6.cf.jpg
227 ms
gateway.min.js
215 ms
cs_1.6.0.js
171 ms
exp.json
62 ms
perf-vitals_3.2.0.js
59 ms
fs.utils.js
8 ms
fs.sanitize.js
5 ms
fs.compress.js
4 ms
my.att.net accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
my.att.net best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
my.att.net SEO score
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
![]()
EN
![]()
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise My.att.net 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 My.att.net 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.
my.att.net
Open Graph data is detected on the main page of My AT T. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: