3.1 sec in total
140 ms
2.8 sec
145 ms
Welcome to qwest.com homepage info - get ready to check Qwest best content for United States right away, or after learning these important things about qwest.com
Discover CenturyLink residential home internet services. Find high-speed internet, local and long distance home phone services, TV, and special bundle offers.
Visit qwest.comWe analyzed Qwest.com page load time and found that the first response time was 140 ms and then it took 2.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
qwest.com performance score
name
value
score
weighting
Value5.6 s
6/100
10%
Value13.2 s
0/100
25%
Value11.4 s
5/100
10%
Value19,130 ms
0/100
30%
Value0.537
14/100
15%
Value37.2 s
0/100
10%
140 ms
289 ms
98 ms
178 ms
242 ms
Our browser made a total of 164 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Qwest.com, 21% (34 requests) were made to Centurylink.com and 9% (14 requests) were made to Google.com. The less responsive or slowest element that took the longest time to load (1.1 sec) relates to the external source Centurylink.com.
Page size can be reduced by 2.1 MB (36%)
5.7 MB
3.7 MB
In fact, the total size of Qwest.com main page is 5.7 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. 65% of websites need less resources to load. Images take 3.2 MB which makes up the majority of the site volume.
Potential reduce by 93.8 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 93.8 kB or 77% of the original size.
Potential reduce by 175.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. Qwest images are well optimized though.
Potential reduce by 1.4 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 1.4 MB or 71% of the original size.
Potential reduce by 435.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. Qwest.com needs all CSS files to be minified and compressed as it can save up to 435.3 kB or 82% of the original size.
Number of requests can be reduced by 110 (83%)
133
23
The browser has sent 133 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Qwest. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 59 to 1 for JavaScripts and from 10 to 1 for CSS and as a result speed up the page load time.
qwest.com
140 ms
www.centurylink.com
289 ms
reset.css
98 ms
require2.js
178 ms
jquery.min.js
242 ms
jquery.qwest-core.js
202 ms
satelliteLib-203dbecd4d364d7db40bdcdebb64d13058915546.js
6 ms
mp_linkcode.js
100 ms
jqModal.css
152 ms
jquery-ui-1.8.11.custom.css
231 ms
qwest.jquery-ui-0.0.1.css
154 ms
new-global.css
273 ms
template_a.css
272 ms
qwest.jquery-ui-autocomplete-0.0.1.css
225 ms
modals.css
344 ms
udp.css
318 ms
ctlButtons.css
319 ms
mpel.js
18 ms
satellite-563112f564746d662300261a.js
4 ms
satellite-5919f73664746d20c6005ac1.js
12 ms
satellite-59a7238564746d6e40007a67.js
15 ms
target.js
22 ms
ajax
27 ms
satellite-587f0e4464746d47ca00b4c4.js
85 ms
qwest_logo.png
129 ms
ctl_logo.png
128 ms
jquery.autozam.js
53 ms
jquery-ui.min.js
187 ms
cookies2.js
164 ms
template_link_matrix.js
177 ms
locator.js
143 ms
munchkin.js
167 ms
standard
11 ms
standard
9 ms
dap_sprite.png
1107 ms
ui-bg_flat_75_ffffff_40x100.png
96 ms
satellite-5841c48f64746d5573006633.html
14 ms
activityi;src=4529201;type=rmkty0;cat=centu00;dc_lat=;dc_rdid=;tag_for_child_directed_treatment=;ord=4278918937779.963
59 ms
satellite-589cbb0464746d11630075c6.js
9 ms
conversion.js
37 ms
satellite-541b397277c309730b000206.js
8 ms
mpel_storage.html
26 ms
com-centurylink.netmng.com
150 ms
mpel
20 ms
33 ms
satellite-541332ce09c7a707dc000152.js
17 ms
satellite-572900af64746d356b00270f.js
7 ms
mpel_ssd.js
4 ms
31c5892c-0834-4705-9963-6ce6c5f92ca2.js
142 ms
mpel_storage.html
3 ms
el3.gif
184 ms
47 ms
jqModal.js
115 ms
geoamapi.js
157 ms
munchkin.js
40 ms
visitWebPage
110 ms
nan.netmng.com
82 ms
com-centurylink.netmng.com
24 ms
sp.js
121 ms
ClickTracking.aspx
103 ms
104 ms
activityi;src=4529201;type=homep01;cat=ctlho0;ord=1650918959
70 ms
activityi;src=4529201;type=homep01;cat=residhp1;ord=1531143354
150 ms
31c5892c-0834-4705-9963-6ce6c5f92ca2.js
44 ms
WR-latest.js
95 ms
i.cid
1051 ms
activity;xsp=265376;ord=4874786378350.108
730 ms
727 ms
727 ms
726 ms
lb
870 ms
ytc.js
957 ms
fbevents.js
831 ms
spp.pl
829 ms
activity;src=4485138;type=invmedia;cat=6mpsy105;ord=1
799 ms
tre
892 ms
718 ms
718 ms
719 ms
activity;xsp=229016;ord=1
714 ms
spp.pl
859 ms
nan.netmng.com
60 ms
62 ms
centurycore.shortcuts.js
83 ms
ChangeMonitor-latest.js
723 ms
i
655 ms
fbevents.js
641 ms
lb
795 ms
634 ms
activityi;src=4575664;type=invmedia;cat=iyc0kz3e;ord=689104364719.2418
709 ms
rhvwwbce9.js
762 ms
pixel
629 ms
rtset
706 ms
Pug
673 ms
rum
628 ms
mapuser
625 ms
lb
707 ms
iui3
664 ms
iu3
683 ms
382706.gif
646 ms
goat.php
164 ms
186 ms
272 ms
rum
108 ms
267 ms
modal_bg1.png
163 ms
interstitial-circles1.bmp
115 ms
interstitial-circles2.bmp
139 ms
interstitial-circles3.bmp
138 ms
interstitial-circles4.bmp
138 ms
interstitial-circles5.bmp
158 ms
interstitial-circles6.bmp
239 ms
sd
102 ms
conv
234 ms
px
96 ms
djsg.js
240 ms
i
87 ms
838625782841135
66 ms
217 ms
286 ms
216 ms
212 ms
tap.php
55 ms
13209
182 ms
merge
52 ms
169 ms
906937512708326
35 ms
814021002077465
52 ms
controltag.js.1c86c30cac854ccdacab6e3099f5b9ee
36 ms
95 ms
UserMatch.ashx
117 ms
144 ms
90 ms
tre
189 ms
proxy.3d2100fd7107262ecb55ce6847f01fa5.html
37 ms
82 ms
56 ms
22 ms
36 ms
45 ms
42 ms
rhvwwbce9.js
9 ms
s51981287307571
88 ms
32 ms
46 ms
64 ms
46 ms
12 ms
21 ms
21 ms
11 ms
18 ms
activity;src=4366032;type=invmedia;cat=z7boli2p;ord=1
47 ms
pixel
28 ms
i.match
401 ms
satellite-595521a064746d0b95004bf4.js
30 ms
satellite-595521a064746d0b95004bf5.js
28 ms
optout_check
17 ms
get
49 ms
%7B%7B814021002077465%7D%7D
16 ms
kc
60 ms
tag.js
101 ms
ecc
55 ms
.jsonp
12 ms
qwest.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
qwest.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
qwest.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
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Qwest.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 Qwest.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.
qwest.com
Open Graph description is not detected on the main page of Qwest. 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: