3.3 sec in total
71 ms
2.7 sec
527 ms
Welcome to embarqmail.com homepage info - get ready to check Embarqmail best content right away, or after learning these important things about embarqmail.com
Login to CenturyLink Email, Browse Local and National News | CenturyLink
Visit embarqmail.comWe analyzed Embarqmail.com page load time and found that the first response time was 71 ms and then it took 3.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
embarqmail.com performance score
name
value
score
weighting
Value7.0 s
1/100
10%
Value15.5 s
0/100
25%
Value13.3 s
2/100
10%
Value2,030 ms
7/100
30%
Value0.187
65/100
15%
Value23.8 s
1/100
10%
71 ms
77 ms
1065 ms
88 ms
126 ms
Our browser made a total of 136 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Embarqmail.com, 22% (30 requests) were made to Da4pli3l5vc0d.cloudfront.net and 15% (21 requests) were made to Static.peridot.synacor.com. The less responsive or slowest element that took the longest time to load (1.1 sec) relates to the external source Centurylink.net.
Page size can be reduced by 1.8 MB (39%)
4.6 MB
2.8 MB
In fact, the total size of Embarqmail.com main page is 4.6 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 2.5 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 92% of the original size.
Potential reduce by 125.1 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. Embarqmail images are well optimized though.
Potential reduce by 534.7 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 534.7 kB or 63% of the original size.
Number of requests can be reduced by 44 (37%)
120
76
The browser has sent 120 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Embarqmail. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 35 to 1 for JavaScripts and as a result speed up the page load time.
embarqmail.com
71 ms
www.centurylink.net
77 ms
centurylink.net
1065 ms
res.php
88 ms
res.php
126 ms
res.php
46 ms
satelliteLib-2ac5be31d865383e58438363c86dd3409ef4ce17.js
5 ms
res.php
46 ms
amzn_ads.js
225 ms
13344.js
92 ms
showads.js
95 ms
track.gif
39 ms
mbox-contents-9afb00cdd4676c759c023f17fc251ccfcacafe05.js
4 ms
json
82 ms
loader.js
42 ms
synacor.js
98 ms
client_logo_light_lg.png
63 ms
century-tel.png
62 ms
embarq_pms.png
72 ms
q-cmykMag.png
72 ms
enhanced_by_google.png
61 ms
ebay.png
60 ms
amazon.png
61 ms
adchoices_icon.png
69 ms
sync
51 ms
load.js
88 ms
impl.271-68-RELEASE.js
26 ms
beacon.js
28 ms
pmk-201725013.3.js
6 ms
active_arrow.png
29 ms
symbolset-custom.woff
24 ms
144 ms
sourcesanspro-light.svgz
37 ms
sourcesanspro-light.woff
46 ms
sourcesanspro-regular.svgz
37 ms
sourcesanspro-regular.woff
46 ms
70 ms
71 ms
75 ms
76 ms
sourcesanspro-semibold.svgz
24 ms
sourcesanspro-semibold.woff
46 ms
sourcesanspro-bold.woff
23 ms
weathericons-regular-webfont.woff
46 ms
4 ms
9 ms
5 ms
7 ms
5 ms
6 ms
4 ms
5 ms
5 ms
6 ms
5 ms
5 ms
25 ms
23 ms
4 ms
4 ms
160 ms
157 ms
156 ms
153 ms
27 ms
6 ms
5 ms
newsroom.js
10 ms
6 ms
4 ms
16 ms
oo_float_icon.gif
30 ms
318 ms
analytics.js
21 ms
jpt
35 ms
jpt
37 ms
cygnus
361 ms
publishertag.js
32 ms
jpt
33 ms
jpt
34 ms
jpt
35 ms
jpt
60 ms
jpt
43 ms
jpt
91 ms
gshowad.js
25 ms
bid
43 ms
;cfp=1;rndc=1504653447;noperf=1;alias=;cmd=bid;cors=yes
133 ms
get-action
38 ms
;cfp=1;rndc=1504653447;noperf=1;alias=;cmd=bid;cors=yes
337 ms
;cfp=1;rndc=1504653448;noperf=1;alias=;cmd=bid;cors=yes
92 ms
;cfp=1;rndc=1504653447;noperf=1;alias=;cmd=bid;cors=yes
333 ms
;cfp=1;rndc=1504653447;noperf=1;alias=;cmd=bid;cors=yes
92 ms
;cfp=1;rndc=1504653448;noperf=1;alias=;cmd=bid;cors=yes
276 ms
AdCallAggregator
261 ms
fastlane.json
303 ms
fastlane.json
84 ms
fastlane.json
303 ms
fastlane.json
303 ms
fastlane.json
80 ms
fastlane.json
78 ms
gemini-synacor.js
50 ms
track.gif
42 ms
json
84 ms
iframe.html
41 ms
track.gif
28 ms
track.gif
29 ms
track.gif
43 ms
g-d-min.js
7 ms
ssi
429 ms
postmessage.min.js
185 ms
bk-coretag.js
23 ms
generic
135 ms
pixel
192 ms
utsync.ashx
145 ms
cse
302 ms
3aadbb71016ecd7a194bbe2791777e9a.png
141 ms
generic
61 ms
0f5b9800b8b7803f79a0156b5c214ed6.png
31 ms
9f47710340456ec9fcfead286e9ad261.jpg
27 ms
ea3edadd3006c70f1b5c20b99f730e29.jpg
26 ms
635c3a7bad527851abda3e72f46aef7d.jpg
29 ms
%3Fapp%3Dportal%26sig%3D48add57365ba639191586c902db821d28579a8ebe483ba48027c34b5f221fa94
28 ms
%3Fapp%3Dportal%26sig%3D48add57365ba639191586c902db821d28579a8ebe483ba48027c34b5f221fa94
28 ms
%3Fapp%3Dportal%26sig%3D48add57365ba639191586c902db821d28579a8ebe483ba48027c34b5f221fa94
29 ms
%3Fapp%3Dportal%26sig%3D48add57365ba639191586c902db821d28579a8ebe483ba48027c34b5f221fa94
30 ms
7b9315f5b22a9f4ceafb3da02b6bf880.jpg
31 ms
91d93108-35ee-4e91-9cee-54e2ddd9659b.jpeg
30 ms
8634213c2959eeb0ed2d7be6ded00415.jpg
31 ms
pixel
26 ms
32441
21 ms
52154.gif
6 ms
generic
5 ms
rtb-h
17 ms
s95085671420674
81 ms
receive
12 ms
rtb-h
18 ms
embarqmail.com 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.
embarqmail.com 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
embarqmail.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
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 Embarqmail.com 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 Embarqmail.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.
embarqmail.com
Open Graph description is not detected on the main page of Embarqmail. 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: