4 sec in total
157 ms
3.3 sec
583 ms
Click here to check amazing Uswest content for United States. Otherwise, check out these important facts you probably never knew about uswest.com
Discover CenturyLink residential home internet services. Find high-speed internet, local and long distance home phone services, TV, and special bundle offers.
Visit uswest.comWe analyzed Uswest.com page load time and found that the first response time was 157 ms and then it took 3.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
uswest.com performance score
name
value
score
weighting
Value3.5 s
33/100
10%
Value12.8 s
0/100
25%
Value10.6 s
7/100
10%
Value5,260 ms
0/100
30%
Value0.537
14/100
15%
Value28.8 s
0/100
10%
157 ms
284 ms
106 ms
172 ms
247 ms
Our browser made a total of 151 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Uswest.com, 38% (58 requests) were made to Centurylink.com and 4% (6 requests) were made to Assets.adobedtm.com. The less responsive or slowest element that took the longest time to load (2.3 sec) relates to the external source Centurylink.com.
Page size can be reduced by 1.4 MB (32%)
4.4 MB
3.0 MB
In fact, the total size of Uswest.com main page is 4.4 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. 60% of websites need less resources to load. Images take 2.6 MB which makes up the majority of the site volume.
Potential reduce by 125.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 125.5 kB or 77% of the original size.
Potential reduce by 73.2 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. Uswest images are well optimized though.
Potential reduce by 901.3 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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 901.3 kB or 73% of the original size.
Potential reduce by 316.4 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. Uswest.com needs all CSS files to be minified and compressed as it can save up to 316.4 kB or 82% of the original size.
Number of requests can be reduced by 98 (74%)
133
35
The browser has sent 133 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Uswest. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 49 to 1 for JavaScripts and from 13 to 1 for CSS and as a result speed up the page load time.
uswest.com
157 ms
www.centurylink.com
284 ms
reset.css
106 ms
require2.js
172 ms
jquery.min.js
247 ms
jquery.qwest-core.js
315 ms
mp_linkcode.js
104 ms
jqModal.css
209 ms
jquery-ui-1.8.11.custom.css
307 ms
qwest.jquery-ui-0.0.1.css
205 ms
new-global.css
312 ms
template_a.css
310 ms
qwest.jquery-ui-autocomplete-0.0.1.css
311 ms
modals.css
351 ms
homepage.css
367 ms
ctlButtons.css
365 ms
swfobject.js
406 ms
mtagconfig.js
369 ms
satelliteLib-203dbecd4d364d7db40bdcdebb64d13058915546.js
223 ms
embeddedGeoContentController.js
314 ms
homepage-banner-block.css
352 ms
spdemo.js
382 ms
oo_style.css
397 ms
oo_engine.5.9.0.js
432 ms
oo_conf_inline.5.9.0.js
429 ms
mpel.js
66 ms
qwest_logo.png
172 ms
ctl_logo.png
183 ms
interstitial-circles.gif
203 ms
jquery.autozam.js
202 ms
jquery-ui.min.js
441 ms
cookies2.js
284 ms
template_link_matrix.js
350 ms
locator.js
283 ms
US7112-HP-GAPCLOSURE-AZ.png
378 ms
oo_icon.gif
248 ms
homepage_sprite.png
2334 ms
dap_sprite.png
889 ms
satellite-563112f564746d662300261a.js
88 ms
satellite-541c73c9583b03c2ae0000be.js
106 ms
satellite-53fba157ff659973bb00048f.js
63 ms
analytics.js
6 ms
linkid.js
8 ms
target.js
86 ms
ajax
34 ms
collect
6 ms
collect
73 ms
mm-engine.min.js
51 ms
mm-control.php
27 ms
standard
34 ms
global_nav_sprite.png
79 ms
global_nav_sprite_bg.png
109 ms
US8684-HP-PURE_Background.png
415 ms
959x313_homepage_background_bundle.png
161 ms
959x313_homepage_background_tv_dtv.png
204 ms
959x313_homepage_background_tv_prism.png
160 ms
speed-demo.png
288 ms
jquery.cookie.js
282 ms
RZ5V1h4dE-0
107 ms
ui-bg_flat_75_ffffff_40x100.png
252 ms
template.png
1563 ms
jqModal.js
303 ms
geoamapi.js
344 ms
jquery.watermark.js
506 ms
com-centurylink.netmng.com
55 ms
satellite-541332ce09c7a707dc000152.js
46 ms
mpel_storage.html
166 ms
jquery.ctlHome.js
452 ms
www-embed-player-vflfNyN_r.css
49 ms
www-embed-player.js
104 ms
base.js
321 ms
nan.netmng.com
25 ms
ClickTracking.aspx
66 ms
27 ms
activityi;src=4529201;type=homep01;cat=ctlho0;ord=850710970
64 ms
activityi;src=4529201;type=homep01;cat=residhp1;ord=1164065403
65 ms
com-centurylink.netmng.com
15 ms
com-centurylink.netmng.com
11 ms
nan.netmng.com
57 ms
39 ms
spp.pl
237 ms
ILogger.aspx
163 ms
lb
162 ms
119 ms
ep
365 ms
activity;src=4485138;type=invmedia;cat=6mpsy105;ord=1
234 ms
tre
134 ms
spp.pl
231 ms
fbevents.js
229 ms
lb
195 ms
activityi;src=4575664;type=invmedia;cat=iyc0kz3e;ord=8792200770694.763
180 ms
sp.js
109 ms
pixel
106 ms
rtset
107 ms
Pug
107 ms
rum
105 ms
13209
102 ms
274 ms
match.aspx
142 ms
42 ms
activityi;src=4575664;type=invmedia;cat=iyc0kz3e;ord=9592379105743.021
166 ms
mpel
85 ms
u.php
1269 ms
Pug
257 ms
tap.php
17 ms
40 ms
sd
75 ms
iu3
116 ms
sync
74 ms
382706.gif
73 ms
merge
74 ms
mapuser
75 ms
activity;src=4366032;type=invmedia;cat=z7boli2p;ord=1
233 ms
rum
88 ms
mpel_ssd.js
189 ms
i
164 ms
i
154 ms
www.centurylink.com
163 ms
modal_bg1.png
1153 ms
lr.gif
140 ms
Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js
92 ms
ad_status.js
97 ms
centurycore.shortcuts.js
137 ms
1033 ms
1050 ms
pixel.gif
63 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
76 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
79 ms
i
27 ms
ecc
1037 ms
dlxdata.netmng.com
1044 ms
mpel_storage.html
56 ms
65 ms
914 ms
goat.php
53 ms
interstitial-circles1.bmp
109 ms
interstitial-circles2.bmp
116 ms
interstitial-circles3.bmp
79 ms
interstitial-circles4.bmp
77 ms
interstitial-circles5.bmp
121 ms
interstitial-circles6.bmp
151 ms
pixel
40 ms
cm
93 ms
yahoo.ashx
189 ms
epx.gif
91 ms
s47805705426726
83 ms
pixel
15 ms
adex.ashx
191 ms
1
65 ms
deploy2.asp
52 ms
satellite-541b397277c309730b000206.js
35 ms
uswest.com accessibility score
Names and labels
These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
<frame> or <iframe> elements do not have a title
Links do not have a discernible name
uswest.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
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
uswest.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
N/A
ISO-8859-1
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Uswest.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Uswest.com main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
uswest.com
Open Graph description is not detected on the main page of Uswest. 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: