1.7 sec in total
184 ms
1.4 sec
123 ms
Welcome to sorry.centurylink.com homepage info - get ready to check Sorry Century Link best content for United States right away, or after learning these important things about sorry.centurylink.com
Copyright © 2011 CenturyLink. All rights reserved. Permission is given to view, copy, print, and distribute material on this Web site subject to the following conditions:
Visit sorry.centurylink.comWe analyzed Sorry.centurylink.com page load time and found that the first response time was 184 ms and then it took 1.5 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 30% of websites can load faster.
sorry.centurylink.com performance score
name
value
score
weighting
Value3.4 s
36/100
10%
Value3.5 s
63/100
25%
Value10.9 s
6/100
10%
Value2,710 ms
3/100
30%
Value0
100/100
15%
Value27.4 s
0/100
10%
184 ms
89 ms
173 ms
142 ms
138 ms
Our browser made a total of 72 requests to load all elements on the main page. We found that 44% of them (32 requests) were addressed to the original Sorry.centurylink.com, 4% (3 requests) were made to Nan.netmng.com and 4% (3 requests) were made to Centurylink.dc.ignitionone.com. The less responsive or slowest element that took the longest time to load (809 ms) belongs to the original domain Sorry.centurylink.com.
Page size can be reduced by 1.2 MB (78%)
1.5 MB
331.7 kB
In fact, the total size of Sorry.centurylink.com main page is 1.5 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. 35% of websites need less resources to load. Javascripts take 1.4 MB which makes up the majority of the site volume.
Potential reduce by 26.1 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. This page needs HTML code to be minified as it can gain 4.6 kB, which is 14% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 26.1 kB or 78% of the original size.
Potential reduce by 7.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. Obviously, Sorry Century Link needs image optimization as it can save up to 7.2 kB or 13% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 1.1 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.1 MB or 81% of the original size.
Potential reduce by 43.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. Sorry.centurylink.com needs all CSS files to be minified and compressed as it can save up to 43.5 kB or 80% of the original size.
Number of requests can be reduced by 55 (83%)
66
11
The browser has sent 66 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Sorry 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 27 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
sorry.centurylink.com
184 ms
reset.css
89 ms
global.css
173 ms
sorry.css
142 ms
selectordie.css
138 ms
jquery.jscrollpane.css
98 ms
statmapsvg.css
126 ms
ctl-liveperson-mtagconfig.js
139 ms
s_code.js
315 ms
jquery.min.js
308 ms
jquery-ui-min.js
485 ms
require2.js
266 ms
oo_style.css
236 ms
oo_engine.5.9.0.js
309 ms
oo_conf_inline.5.9.0.js
280 ms
jquery.min.js
487 ms
rgbcolor.js
305 ms
canvg.js
416 ms
statmapsvg.js
415 ms
mbox.js
330 ms
selectordie.js
427 ms
jquery.mousewheel.js
374 ms
jScrollPane.js
492 ms
svg_fix.js
809 ms
cookies2.js
479 ms
jquery.qwest-core.js
596 ms
svg_custom.js
503 ms
css
24 ms
s1595870886463
83 ms
oo_icon.gif
60 ms
standard
11 ms
global-header.png
67 ms
sorry-page-sprite.png
67 ms
global_nav_sprite.png
269 ms
dropdown_bg.png
47 ms
com-centurylink.netmng.com
30 ms
usa-with-labels.svg
228 ms
nan.netmng.com
31 ms
ClickTracking.aspx
32 ms
15 ms
com-centurylink.netmng.com
11 ms
com-centurylink.netmng.com
11 ms
17 ms
nan.netmng.com
27 ms
sp.js
48 ms
pixel
31 ms
rtset
49 ms
Pug
48 ms
rum
16 ms
13209
68 ms
19 ms
match.aspx
67 ms
4 ms
sync
15 ms
u.php
95 ms
tap.php
56 ms
rum
61 ms
dlxdata.netmng.com
105 ms
merge
54 ms
49 ms
mapuser
49 ms
sd
47 ms
382706.gif
32 ms
i
28 ms
i
25 ms
lr.gif
12 ms
24 ms
pixel.gif
9 ms
i
7 ms
21 ms
18 ms
deploy2.asp
87 ms
sorry.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
Buttons do not have an accessible name
<frame> or <iframe> elements do not have a title
Links do not have a discernible name
<object> elements do not have alternate text
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
[id] attributes on active, focusable elements are not unique
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
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
List items (<li>) are not contained within <ul> or <ol> parent elements.
sorry.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
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
sorry.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
Page is blocked from indexing
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 Sorry.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 Sorry.centurylink.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.
sorry.centurylink.com
Open Graph description is not detected on the main page of Sorry 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: