2.6 sec in total
84 ms
2.4 sec
153 ms
Visit landing.aetna.com now to see the best up-to-date Landing Aetna content for United States and also check out these interesting facts you probably never knew about landing.aetna.com
Learn the benefits of joining Aetna for individuals and families and learn about the benefits for employers, healthcare providers, and insurance producers.
Visit landing.aetna.comWe analyzed Landing.aetna.com page load time and found that the first response time was 84 ms and then it took 2.6 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.
landing.aetna.com performance score
84 ms
356 ms
203 ms
342 ms
238 ms
Our browser made a total of 54 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Landing.aetna.com, 4% (2 requests) were made to Assets.adobedtm.com and 4% (2 requests) were made to S7.addthis.com. The less responsive or slowest element that took the longest time to load (982 ms) relates to the external source Aetna.com.
Page size can be reduced by 1.2 MB (76%)
1.6 MB
377.0 kB
In fact, the total size of Landing.aetna.com main page is 1.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. 30% of websites need less resources to load. Javascripts take 1.1 MB which makes up the majority of the site volume.
Potential reduce by 155.0 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 45.4 kB, which is 26% 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 155.0 kB or 90% of the original size.
Potential reduce by 22.4 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, Landing Aetna needs image optimization as it can save up to 22.4 kB or 62% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 834.1 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 834.1 kB or 74% of the original size.
Potential reduce by 202.4 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. Landing.aetna.com needs all CSS files to be minified and compressed as it can save up to 202.4 kB or 81% of the original size.
Number of requests can be reduced by 37 (71%)
52
15
The browser has sent 52 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Landing Aetna. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 23 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
www.aetna.com
84 ms
www.aetna.com
356 ms
satelliteLib-abdd9c12e4282e18501b8ece2707c7bc44977a57.js
203 ms
common-clientlibs.min.css
342 ms
smart-homepage-clientlibs.min.css
238 ms
common-clientlibs.min.js
405 ms
smart-homepage-clientlibs.min.js
215 ms
foresee-trigger.js
252 ms
custom.js
293 ms
webtrends.js
290 ms
omniture.js
581 ms
jquery.min.js
527 ms
utils.min.js
433 ms
granite.min.js
401 ms
jquery.min.js
441 ms
shared.min.js
652 ms
underscore.min.js
627 ms
kernel.min.js
722 ms
browserDetect-clientlibs.min.css
660 ms
browserDetect-clientlibs.min.js
659 ms
s_code.js
662 ms
personalization-clientlibs.min.js
626 ms
onlineopinionV5-clientlibs.min.css
695 ms
onlineopinionV5-clientlibs.min.js
730 ms
mbox-contents-98e281172506d85bac5f2e870b543adfb20ceea8.js
97 ms
target.js
137 ms
ajax
46 ms
widget56.css
36 ms
logo.png
191 ms
green-spin.gif
323 ms
facebook_icon.png
259 ms
twitter_icon.png
293 ms
youtube_icon.png
297 ms
linkedin_icon.png
331 ms
tumblr-icon.png
455 ms
ico-down-blue.png
220 ms
ico-down-white.png
245 ms
global-desktop-sprite.png
241 ms
diagonalLinesBg.png
260 ms
6d747f1f-42ba-4b98-91b9-42d684cd2311.woff
968 ms
icn-arrowBlueSmall.png
288 ms
icn-arrowWhiteSmall.png
952 ms
icn-arrowGraySmall.png
954 ms
505b3d44-cc24-4e11-9b10-a4890cd63b22.woff
982 ms
wtid.js
267 ms
news_if.xml
843 ms
oo_tab.png
102 ms
oo_tab_icon.gif
105 ms
foresee-surveydef.js
162 ms
sh36.html
43 ms
dcs.gif
109 ms
s71899106462951
161 ms
foresee-dhtml.css
40 ms
s79890273502096
84 ms
landing.aetna.com SEO score
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Landing.aetna.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 Landing.aetna.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.
landing.aetna.com
Open Graph description is not detected on the main page of Landing Aetna. 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: