8.7 sec in total
233 ms
7.9 sec
528 ms
Click here to check amazing Mobile content for India. Otherwise, check out these important facts you probably never knew about mobile.com
Shop deals on unlimited data plans, Internet service, and DIRECTV STREAM. Get 24/7 support, pay your bills & manage your account online.
Visit mobile.comWe analyzed Mobile.com page load time and found that the first response time was 233 ms and then it took 8.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
mobile.com performance score
name
value
score
weighting
Value4.1 s
21/100
10%
Value6.8 s
7/100
25%
Value8.3 s
19/100
10%
Value9,960 ms
0/100
30%
Value0
100/100
15%
Value28.2 s
0/100
10%
233 ms
1724 ms
48 ms
64 ms
74 ms
Our browser made a total of 175 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Mobile.com, 73% (128 requests) were made to Att.com and 7% (12 requests) were made to Att.inq.com. The less responsive or slowest element that took the longest time to load (1.7 sec) relates to the external source Att.com.
Page size can be reduced by 4.0 MB (78%)
5.2 MB
1.2 MB
In fact, the total size of Mobile.com main page is 5.2 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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Javascripts take 4.6 MB which makes up the majority of the site volume.
Potential reduce by 142.4 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 142.4 kB or 83% of the original size.
Potential reduce by 60.1 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. Obviously, Mobile needs image optimization as it can save up to 60.1 kB or 20% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 3.7 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 3.7 MB or 82% of the original size.
Potential reduce by 63.3 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. Mobile.com needs all CSS files to be minified and compressed as it can save up to 63.3 kB or 54% of the original size.
Number of requests can be reduced by 126 (74%)
171
45
The browser has sent 171 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Mobile. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 91 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.
mobile.com
233 ms
loginAction.olamexecute
1724 ms
global-styles.css
48 ms
nextGenGlobalStyles.css
64 ms
myatt-dashboard.css
74 ms
GVP.js
66 ms
mobilesiteRedirect.js
107 ms
jquery.min.js
80 ms
jquery.cookie.js
99 ms
tesla.scaffold.js
81 ms
global.js
80 ms
atgAjaxActions-min.js
108 ms
myatt-global-min.js
98 ms
TdataCombined.min.js
98 ms
prototype.js
118 ms
edmDataManager.js
148 ms
edmDataDefinition.js
104 ms
satelliteLib-bee1ce9b89e943a46b1dfd167adc564fe75eef37.js
222 ms
externalRedirectModal.js
148 ms
tealeaf.min.4.0.1607.OLAM.js
126 ms
mtagconfig_sso.js
147 ms
foresee-trigger-global.js
164 ms
BrowserDetect.js
143 ms
deleteCookies.js
158 ms
sniffer.js
164 ms
detectmobilebrowser.js
160 ms
jquery.iphone.password.js
165 ms
newLoginValidation.js
174 ms
BESTPing.js
180 ms
DSSLogout.js
174 ms
Prefetch.js
187 ms
jquery.poshytip.js
177 ms
myatt-gvp.js
196 ms
jquery.jcarousel.min.js
193 ms
myattConsoleLogger.js
210 ms
myAttRecommendationReporting.js
198 ms
dtmReporting.js
210 ms
dcs_tag.js
204 ms
myatt-common.css
194 ms
myatt-carousel.css
82 ms
myatt-common-parent.css
52 ms
edmDataManager.js
14 ms
edmDataDefinition.js
24 ms
tesla.theme.min.css
22 ms
background_left.jpg
593 ms
dcs_tag_DTM.js
454 ms
mbox-contents-3fe7f1ac02f9f751c9c175021a5f0779a4287d23.js
152 ms
satellite-52fe8aa99b6a7d521a00013b.js
127 ms
analytics.js
336 ms
dataMappingFramework.min.js
100 ms
tesla.theme.IRU.css
92 ms
background_right.jpg
154 ms
WirelessOLAM.jpg
183 ms
Uverse.jpg
182 ms
HomePhoneInternet.jpg
154 ms
Consolidated.jpg
154 ms
LoginOLAM.png
182 ms
login_arrow.png
182 ms
logoATTdotcom.png
144 ms
logoATTdotnet.png
139 ms
logoCTIA.png
151 ms
logoBBB.png
148 ms
logoTRUSTe.png
148 ms
logoOlympics.png
151 ms
tesla.zepto.min.js
149 ms
ATT_Sprite_Retina_v1.png
113 ms
ie-top-background.png
69 ms
ie-mid-background.png
73 ms
endLine.png
67 ms
rd
31 ms
mBXL5EOFcAyOVXgnEjN4hoAwBvoURjAAAAAAFT5AJVAAA=
7 ms
background_left.jpg
42 ms
id
116 ms
tesla.zepto.modules.js
80 ms
login-top-background.png
84 ms
login-mid-background.png
84 ms
grad-heading.gif
80 ms
dividerline-stokeSmall.png
81 ms
ActiveBar.png
88 ms
iconArrow.png
79 ms
LoginSelectAccBottomGradient.jpg
70 ms
login-bot-background-GreyNew.png
50 ms
input-right-login.png
49 ms
input-left-login.png
70 ms
sprite.png
50 ms
tesla.core.min.js
18 ms
NewcarouselBgH235.PNG
32 ms
tesla.modules.adobe.js
22 ms
tesla.modules.searchform.js
18 ms
tesla.modules.IRU.js
17 ms
img_prefooter.gif
21 ms
dotsitesPipe.gif
14 ms
ie-gr-bottom-background-nofat.png
302 ms
satellite-54d1307a3935650016830000.js
274 ms
s-code-contents-65778bc202aa3fe01113e6b6ea6d103eda099fe5.js
272 ms
jquery.poshytip.js
251 ms
jquery.colorbox.min.js
263 ms
jquery.uniform.min.js
280 ms
_gvp.min.js
219 ms
satellite-5668bfa964746d342a005ca3.js
179 ms
satellite-53500837715895f07a000221.js
149 ms
collect
237 ms
collect
238 ms
satellite-54fdfdc16637360016010200.js
133 ms
satellite-56094d0c3262301c8a0000bf.js
131 ms
navservlet
552 ms
background_right.jpg
150 ms
input-right-active-login.png
212 ms
input-left-active-login.png
211 ms
btn-Carousel-sprite_AA001471.gif
209 ms
ajaxLoader.gif
118 ms
inqChatLaunch10004119.js
233 ms
satellite-567046aa64746d071200822c.js
89 ms
satellite-567046aa64746d0712008241.js
36 ms
oo_engine.min.js
88 ms
tesla.modules.userinfo.js
99 ms
satellite-567046aa64746d0712008217.js
25 ms
tesla.modules.motionpoint.js
31 ms
GenericLayer.jsp
171 ms
s34513817841652
24 ms
tesla.modules.myatt.js
15 ms
resolvePage
93 ms
dcs.gif
433 ms
inqChat.html
48 ms
gvp_myATT-Help-With-Logging-In-B2C232082_4300384_110x62.jpg
338 ms
btn-play-sm-icon.png
15 ms
gvp_eSupport-Linking-Accounts-B2C187100_5000070_110x62.jpg
346 ms
gvp_SSO-06-Recover-ID-B2C227137_4300101_110x62.jpg
337 ms
gvp_SSO-07-Recover-Password-B2C227138_4300102_110x62.jpg
338 ms
print.css
25 ms
dcs.gif
373 ms
js
37 ms
site_10004119_default.js
191 ms
tcFramework.min.js
140 ms
satellite-55e9c2d86531310017000408.js
129 ms
satellite-55e9c2d86531310017000409.js
118 ms
satellite-55e9c2d8653131001700040a.js
118 ms
satellite-55e9c2d8653131001700040b.js
128 ms
satellite-55e9c2d8653131001700040c.js
127 ms
satellite-561bd2ba36336400140002c2.js
118 ms
satellite-53581859720846debf00042a.js
114 ms
satellite-54733ba335363100182b0200.js
108 ms
satellite-51faaeaa4c575cbda2000053.js
107 ms
satellite-566602d564746d43850048fa.js
107 ms
satellite-56940ca564746d5f90006d47.js
109 ms
satellite-567046aa64746d0712008254.js
25 ms
satellite-567046aa64746d0712008201.js
388 ms
postToServer.htm
70 ms
postToServer.js
132 ms
240 ms
oo_conf.js
124 ms
oo_style.js
121 ms
a.js;m=11022201015757;cache=0.8380894328001887
1021 ms
a.js;m=11022202051605;cache=0.7990860035642982
1352 ms
bk-coretag.js
272 ms
L21rdC81MzEvcGlkLzU3OTUyMTExL3QvMA
947 ms
img;p=11022200801116
1399 ms
6954.js
329 ms
oo_icon.gif
119 ms
newWindow.gif
137 ms
817 ms
initFramework
213 ms
img;m=11022202176866;cache=
1159 ms
jquery-1.11.1.min.js
980 ms
onEvent
225 ms
onEvent
443 ms
logdata
536 ms
s
553 ms
u
586 ms
resolveIpToHostName
250 ms
5675
60 ms
img;m=11022201015763
116 ms
adsct
224 ms
img;m=11022203137504;cache=
82 ms
cbc-min.js
191 ms
mobile.com accessibility score
mobile.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
mobile.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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Mobile.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 Mobile.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.
mobile.com
Open Graph description is not detected on the main page of Mobile. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: