128.5 sec in total
808 ms
102 sec
25.6 sec
Click here to check amazing Century Link content for United States. Otherwise, check out these important facts you probably never knew about centurylink.net
Login to CenturyLink Email, Browse Local and National News | CenturyLink
Visit centurylink.netWe analyzed Centurylink.net page load time and found that the first response time was 808 ms and then it took 127.6 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.net performance score
name
value
score
weighting
Value6.7 s
2/100
10%
Value16.1 s
0/100
25%
Value13.6 s
2/100
10%
Value3,020 ms
2/100
30%
Value0.189
65/100
15%
Value25.7 s
0/100
10%
808 ms
696 ms
689 ms
664 ms
203 ms
Our browser made a total of 167 requests to load all elements on the main page. We found that 11% of them (18 requests) were addressed to the original Centurylink.net, 20% (33 requests) were made to Da4pli3l5vc0d.cloudfront.net and 13% (21 requests) were made to Static.peridot.synacor.com. The less responsive or slowest element that took the longest time to load (9.1 sec) relates to the external source Da4pli3l5vc0d.cloudfront.net.
Page size can be reduced by 2.9 MB (37%)
7.7 MB
4.9 MB
In fact, the total size of Centurylink.net main page is 7.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. 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. Images take 4.2 MB which makes up the majority of the site volume.
Potential reduce by 1.1 MB
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 1.1 MB or 91% of the original size.
Potential reduce by 130.6 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.6 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.6 MB or 71% of the original size.
Potential reduce by 3.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. Centurylink.net needs all CSS files to be minified and compressed as it can save up to 3.3 kB or 77% of the original size.
Number of requests can be reduced by 68 (45%)
150
82
The browser has sent 150 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 43 to 1 for JavaScripts and as a result speed up the page load time.
centurylink.net
808 ms
res.php
696 ms
res.php
689 ms
res.php
664 ms
satelliteLib-2ac5be31d865383e58438363c86dd3409ef4ce17.js
203 ms
res.php
4770 ms
amzn_ads.js
6807 ms
13344.js
6221 ms
showads.js
4786 ms
track.gif
1625 ms
mbox-contents-9afb00cdd4676c759c023f17fc251ccfcacafe05.js
34 ms
json
1281 ms
loader.js
233 ms
synacor.js
760 ms
load.js
1033 ms
impl.271-68-RELEASE.js
509 ms
beacon.js
1032 ms
client_logo_light_lg.png
409 ms
century-tel.png
409 ms
embarq_pms.png
932 ms
q-cmykMag.png
932 ms
enhanced_by_google.png
932 ms
ebay.png
931 ms
amazon.png
864 ms
adchoices_icon.png
863 ms
sync
2843 ms
pmk-201725013.3.js
142 ms
active_arrow.png
146 ms
symbolset-custom.woff
73 ms
474 ms
sourcesanspro-light.svgz
87 ms
sourcesanspro-light.woff
86 ms
weathericons-regular-webfont.woff
1953 ms
sourcesanspro-regular.svgz
1933 ms
sourcesanspro-regular.woff
1933 ms
1286 ms
sourcesanspro-semibold.svgz
404 ms
sourcesanspro-semibold.woff
335 ms
sourcesanspro-bold.woff
334 ms
1122 ms
1121 ms
1121 ms
79 ms
80 ms
79 ms
80 ms
45 ms
178 ms
54 ms
192 ms
86 ms
96 ms
83 ms
94 ms
51 ms
67 ms
94 ms
65 ms
85 ms
233 ms
70 ms
186 ms
9063 ms
json
156 ms
generic
418 ms
pixel
486 ms
utsync.ashx
645 ms
cse
2741 ms
generic
2426 ms
pixel
2355 ms
3aadbb71016ecd7a194bbe2791777e9a.png
788 ms
32441
824 ms
liveramp_sync.xgi
1321 ms
generic
830 ms
rtb-h
1873 ms
receive
1599 ms
liveramp_sync.xgi
1632 ms
rtb-h
728 ms
8b37adf20608eaa44e31b4208a3fae90.jpg
611 ms
0f5b9800b8b7803f79a0156b5c214ed6.png
98 ms
4c9b164c167531ebf08624d34b161d83.jpg
264 ms
c0e181fc8ca8c69ddd6ee2c3fd5e70ad.jpg
295 ms
%3Fapp%3Dportal%26sig%3D48add57365ba639191586c902db821d28579a8ebe483ba48027c34b5f221fa94
312 ms
%3Fapp%3Dportal%26sig%3D48add57365ba639191586c902db821d28579a8ebe483ba48027c34b5f221fa94
293 ms
%3Fapp%3Dportal%26sig%3D48add57365ba639191586c902db821d28579a8ebe483ba48027c34b5f221fa94
294 ms
%3Fapp%3Dportal%26sig%3D37b7c5982a55a90f5d6ae0eee39551fe5a6f51770cd66694ce349517479c28b7
1337 ms
327 ms
1819 ms
1674 ms
384 ms
newsroom.js
59 ms
get-action
48 ms
json
350 ms
147 ms
151 ms
fb1a0ac544a55ca8fd4b6aacd0089c78.png
70 ms
oo_float_icon.gif
376 ms
ea3edadd3006c70f1b5c20b99f730e29.jpg
206 ms
91d93108-35ee-4e91-9cee-54e2ddd9659b.jpeg
2536 ms
602 ms
analytics.js
561 ms
jpt
716 ms
jpt
892 ms
jpt
892 ms
jpt
1523 ms
jpt
714 ms
jpt
1523 ms
gshowad.js
1478 ms
publishertag.js
1477 ms
cygnus
1628 ms
jpt
1425 ms
jpt
1424 ms
jpt
1283 ms
bid
1483 ms
;cfp=1;rndc=1504623364;noperf=1;alias=;cmd=bid;cors=yes
2091 ms
;cfp=1;rndc=1504623364;noperf=1;alias=;cmd=bid;cors=yes
1850 ms
;cfp=1;rndc=1504623364;noperf=1;alias=;cmd=bid;cors=yes
1885 ms
;cfp=1;rndc=1504623363;noperf=1;alias=;cmd=bid;cors=yes
1829 ms
;cfp=1;rndc=1504623364;noperf=1;alias=;cmd=bid;cors=yes
1829 ms
;cfp=1;rndc=1504623364;noperf=1;alias=;cmd=bid;cors=yes
1910 ms
fastlane.json
1187 ms
fastlane.json
1165 ms
fastlane.json
1203 ms
fastlane.json
1101 ms
fastlane.json
695 ms
fastlane.json
1197 ms
gemini-synacor.js
2319 ms
1362 ms
AdCallAggregator
142 ms
gpt.js
572 ms
g-d-min.js
450 ms
ssi
913 ms
pubads_impl_147.js
790 ms
showad.js
3134 ms
show_companion_ad.js
726 ms
container.html
675 ms
PugMaster
1535 ms
track.gif
1302 ms
iframe.html
1314 ms
receive
883 ms
pixel
990 ms
generic
917 ms
track.gif
1004 ms
track.gif
1099 ms
track.gif
1004 ms
track.gif
1066 ms
track.gif
1065 ms
track.gif
1066 ms
track.gif
1052 ms
postmessage.min.js
1129 ms
bk-coretag.js
1126 ms
Pug
3083 ms
demconf.jpg
3029 ms
Pug
3086 ms
Pug
2959 ms
Pug
2979 ms
Pug
3268 ms
track.gif
2980 ms
2932 ms
ads
1657 ms
Pug
956 ms
Pug
1062 ms
s64562127920798
1775 ms
track.gif
1893 ms
track.gif
63 ms
click
3123 ms
osd.js
3235 ms
centurylink.net accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
[aria-hidden="true"] elements contain focusable descendents
[role]s do not have all required [aria-*] attributes
[aria-*] attributes do not have valid values
[aria-*] attributes are not valid or misspelled
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
Buttons do not have an accessible name
Image elements do not have [alt] attributes
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Definition list items are not wrapped in <dl> elements
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.
centurylink.net best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
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
centurylink.net 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
Image elements do not have [alt] attributes
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 Centurylink.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 Centurylink.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.
centurylink.net
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: