35.2 sec in total
222 ms
29.2 sec
5.8 sec
Visit centurylink.com now to see the best up-to-date Century Link content for United States and also check out these interesting facts you probably never knew about centurylink.com
Discover CenturyLink residential home internet services. Find high-speed internet, local and long distance home phone services, TV, and special bundle offers.
Visit centurylink.comWe analyzed Centurylink.com page load time and found that the first response time was 222 ms and then it took 35 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster.
centurylink.com performance score
name
value
score
weighting
Value3.7 s
28/100
10%
Value9.5 s
0/100
25%
Value9.0 s
15/100
10%
Value8,680 ms
0/100
30%
Value0
100/100
15%
Value29.4 s
0/100
10%
222 ms
304 ms
199 ms
329 ms
815 ms
Our browser made a total of 143 requests to load all elements on the main page. We found that 27% of them (38 requests) were addressed to the original Centurylink.com, 10% (14 requests) were made to Google.com and 7% (10 requests) were made to Assets.adobedtm.com. The less responsive or slowest element that took the longest time to load (9.2 sec) relates to the external source Secure.leadback.advertising.com.
Page size can be reduced by 1.7 MB (33%)
5.3 MB
3.5 MB
In fact, the total size of Centurylink.com main page is 5.3 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. 75% 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. Images take 3.0 MB which makes up the majority of the site volume.
Potential reduce by 93.6 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.6 kB or 77% of the original size.
Potential reduce by 103.7 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. Century Link images are well optimized though.
Potential reduce by 1.2 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.2 MB or 71% of the original size.
Potential reduce by 319.5 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. Centurylink.com needs all CSS files to be minified and compressed as it can save up to 319.5 kB or 82% of the original size.
Number of requests can be reduced by 106 (80%)
132
26
The browser has sent 132 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Century Link. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 54 to 1 for JavaScripts and from 10 to 1 for CSS and as a result speed up the page load time.
centurylink.com
222 ms
www.centurylink.com
304 ms
reset.css
199 ms
require2.js
329 ms
jquery.min.js
815 ms
jquery.qwest-core.js
813 ms
satelliteLib-203dbecd4d364d7db40bdcdebb64d13058915546.js
169 ms
mp_linkcode.js
237 ms
jqModal.css
235 ms
jquery-ui-1.8.11.custom.css
298 ms
qwest.jquery-ui-0.0.1.css
295 ms
new-global.css
781 ms
template_a.css
780 ms
qwest.jquery-ui-autocomplete-0.0.1.css
539 ms
modals.css
1798 ms
udp.css
1692 ms
ctlButtons.css
1692 ms
mpel.js
27 ms
satellite-563112f564746d662300261a.js
227 ms
satellite-5919f73664746d20c6005ac1.js
286 ms
satellite-59a7238564746d6e40007a67.js
285 ms
target.js
131 ms
ajax
852 ms
satellite-587f0e4464746d47ca00b4c4.js
409 ms
munchkin.js
1425 ms
qwest_logo.png
844 ms
ctl_logo.png
536 ms
jquery.autozam.js
47 ms
munchkin.js
236 ms
jquery-ui.min.js
394 ms
cookies2.js
265 ms
template_link_matrix.js
357 ms
locator.js
252 ms
standard
198 ms
standard
1088 ms
visitWebPage
1206 ms
jqModal.js
810 ms
geoamapi.js
766 ms
dap_sprite.png
659 ms
ui-bg_flat_75_ffffff_40x100.png
600 ms
ui-bg_flat_0_aaaaaa_40x100.png
1942 ms
satellite-5841c48f64746d5573006633.html
608 ms
activityi;src=4529201;type=rmkty0;cat=centu00;dc_lat=;dc_rdid=;tag_for_child_directed_treatment=;ord=3493561134673.6553
694 ms
satellite-589cbb0464746d11630075c6.js
440 ms
conversion.js
242 ms
satellite-541b397277c309730b000206.js
240 ms
modal_sprite.png
1082 ms
ui-icons_222222_256x240.png
484 ms
mpel_storage.html
955 ms
2735 ms
centurycore.shortcuts.js
791 ms
com-centurylink.netmng.com
2178 ms
satellite-541332ce09c7a707dc000152.js
2000 ms
satellite-572900af64746d356b00270f.js
2000 ms
mpel
2118 ms
modal_bg1.png
2021 ms
goat.php
842 ms
interstitial-circles1.bmp
840 ms
interstitial-circles2.bmp
840 ms
interstitial-circles3.bmp
839 ms
interstitial-circles4.bmp
837 ms
interstitial-circles5.bmp
820 ms
interstitial-circles6.bmp
615 ms
946 ms
s76434412049129
598 ms
nan.netmng.com
478 ms
com-centurylink.netmng.com
411 ms
31c5892c-0834-4705-9963-6ce6c5f92ca2.js
477 ms
mpel_ssd.js
98 ms
mpel_storage.html
118 ms
el3.gif
405 ms
sp.js
288 ms
ClickTracking.aspx
1088 ms
240 ms
activityi;src=4529201;type=homep01;cat=ctlho0;ord=736288681
1805 ms
activityi;src=4529201;type=homep01;cat=residhp1;ord=1336321972
472 ms
nan.netmng.com
1254 ms
31c5892c-0834-4705-9963-6ce6c5f92ca2.js
309 ms
WR-latest.js
1632 ms
848 ms
ytc.js
3143 ms
fbevents.js
4458 ms
lb
9229 ms
i
5154 ms
activity;xsp=265376;ord=9437115460168.57
7276 ms
spp.pl
7907 ms
activity;src=4485138;type=invmedia;cat=6mpsy105;ord=1
6661 ms
activity;xsp=229016;ord=1
6808 ms
spp.pl
7877 ms
lb
7876 ms
activityi;src=4575664;type=invmedia;cat=iyc0kz3e;ord=5928015345707.536
6115 ms
rhvwwbce9.js
7692 ms
rtset
4713 ms
Pug
5410 ms
ChangeMonitor-latest.js
2910 ms
lb
4397 ms
5343 ms
4974 ms
4972 ms
5234 ms
fbevents.js
5900 ms
838625782841135
2001 ms
djsg.js
3640 ms
i
1735 ms
3654 ms
2056 ms
3705 ms
3940 ms
906937512708326
1447 ms
13209
1963 ms
merge
1904 ms
px
1903 ms
rum
1654 ms
sd
1564 ms
sync
1564 ms
iu3
1880 ms
tap.php
1564 ms
382706.gif
1509 ms
iui3
1826 ms
1822 ms
4727 ms
1535 ms
680 ms
881 ms
conv
4472 ms
3769 ms
pixel
4171 ms
controltag.js.1c86c30cac854ccdacab6e3099f5b9ee
1051 ms
814021002077465
896 ms
4024 ms
3597 ms
863 ms
3838 ms
2738 ms
2682 ms
2991 ms
2977 ms
3022 ms
proxy.3d2100fd7107262ecb55ce6847f01fa5.html
1221 ms
activity;src=4366032;type=invmedia;cat=z7boli2p;ord=1
712 ms
624 ms
rhvwwbce9.js
64 ms
i.match
578 ms
centurylink.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
centurylink.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
Displays images with incorrect aspect ratio
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
centurylink.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 Centurylink.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 Centurylink.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.
centurylink.com
Open Graph description is not detected on the main page of Century Link. 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: