Tools & Wizards About Us
access.aetna.com screenshot

Report Summary

  • 44

    Performance

    Renders faster than
    63% of other websites

  • 73

    Accessibility

    Visual factors better than
    that of 38% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 75

    SEO

    Google-friendlier than
    32% of websites

access.aetna.com

NetScaler AAA

Page Load Speed

831 ms in total

First Response

87 ms

Resources Loaded

678 ms

Page Rendered

66 ms

access.aetna.com screenshot

About Website

Visit access.aetna.com now to see the best up-to-date Access Aetna content for United States and also check out these interesting facts you probably never knew about access.aetna.com

Visit access.aetna.com

Key Findings

We analyzed Access.aetna.com page load time and found that the first response time was 87 ms and then it took 744 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 15% of websites can load faster.

Performance Metrics

access.aetna.com performance score

44

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.1 s

3/100

10%

LCP (Largest Contentful Paint)

Value12.0 s

0/100

25%

SI (Speed Index)

Value6.6 s

37/100

10%

TBT (Total Blocking Time)

Value300 ms

79/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value11.8 s

17/100

10%

Network Requests Diagram

access.aetna.com

87 ms

tmindex.html

79 ms

jquery.min.js

60 ms

jquery-ui.min.js

121 ms

jquery.ui.touch-punch.min.js

47 ms

Our browser made a total of 21 requests to load all elements on the main page. We found that all of those requests were addressed to Access.aetna.com and no external sources were called. The less responsive or slowest element that took the longest time to load (135 ms) belongs to the original domain Access.aetna.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 38.7 kB (40%)

Content Size

97.1 kB

After Optimization

58.3 kB

  • HTML
  • Images

In fact, the total size of Access.aetna.com main page is 97.1 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 25% of websites need less resources to load. Images take 53.6 kB which makes up the majority of the site volume.

HTML Optimization

-87%

Potential reduce by 37.9 kB

  • Original 43.4 kB
  • After minification 31.9 kB
  • After compression 5.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. This page needs HTML code to be minified as it can gain 11.6 kB, which is 27% 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 37.9 kB or 87% of the original size.

Image Optimization

-2%

Potential reduce by 878 B

  • Original 53.6 kB
  • After minification 52.8 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. Access Aetna images are well optimized though.

Requests Breakdown

Number of requests can be reduced by 11 (58%)

Requests Now

19

After Optimization

8

  • Images
  • JavaScript
  • CSS

The browser has sent 19 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Access 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 12 to 1 for JavaScripts and as a result speed up the page load time.

Network Requests Diagram

access.aetna.com

access.aetna.com

87 ms

tmindex.html

tmindex.html

79 ms

jquery.min.js

jquery.min.js

60 ms

jquery-ui.min.js

jquery-ui.min.js

121 ms

jquery.ui.touch-punch.min.js

jquery.ui.touch-punch.min.js

47 ms

jquery-migrate.min.js

jquery-migrate.min.js

74 ms

init.js

init.js

75 ms

hammer.min.js

hammer.min.js

82 ms

jquery.dotdotdot.min.js

jquery.dotdotdot.min.js

76 ms

velocity.min.js

velocity.min.js

75 ms

slick.min.js

slick.min.js

92 ms

elliptic.min.js

elliptic.min.js

135 ms

ctxs.core.min.js

ctxs.core.min.js

65 ms

ctxs.webui.min.js

ctxs.webui.min.js

135 ms

ctxs.large-ui.min.css

ctxs.large-ui.min.css

128 ms

theme.css

theme.css

21 ms

style.css

style.css

21 ms

actionSprite.png

actionSprite.png

39 ms

folder_template.png

folder_template.png

38 ms

wspinner@2x.gif

wspinner@2x.gif

38 ms

ReceiverFullScreenBackground.jpg

ReceiverFullScreenBackground.jpg

38 ms

Accessibility Review

access.aetna.com accessibility score

73

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

access.aetna.com best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

access.aetna.com SEO score

75

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

High

robots.txt is not valid

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

High

Document uses legible font sizes

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Access.aetna.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 Access.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.

Social Sharing Optimization

access.aetna.com

Open Graph description is not detected on the main page of Access 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: