Tools & Wizards About Us
auth.ehealth.com screenshot

Report Summary

  • 21

    Performance

    Renders faster than
    39% of other websites

  • 100

    Accessibility

    Visual factors better than
    that of 97% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 82

    SEO

    Google-friendlier than
    44% of websites

auth.ehealth.com

Medicare Information, Help, and Plan Enrollment - Medicare.com

Page Load Speed

1.8 sec in total

First Response

213 ms

Resources Loaded

1.3 sec

Page Rendered

289 ms

auth.ehealth.com screenshot

About Website

Welcome to auth.ehealth.com homepage info - get ready to check Auth Ehealth best content for United States right away, or after learning these important things about auth.ehealth.com

Looking for Medicare plans or ways to save money on Medicare? Get free information and comparison tools, plus live help from Medicare.com.

Visit auth.ehealth.com

Key Findings

We analyzed Auth.ehealth.com page load time and found that the first response time was 213 ms and then it took 1.6 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.

Performance Metrics

auth.ehealth.com performance score

21

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.1 s

47/100

10%

LCP (Largest Contentful Paint)

Value10.5 s

0/100

25%

SI (Speed Index)

Value5.6 s

52/100

10%

TBT (Total Blocking Time)

Value1,020 ms

26/100

30%

CLS (Cumulative Layout Shift)

Value0.585

11/100

15%

TTI (Time to Interactive)

Value13.0 s

13/100

10%

Network Requests Diagram

auth.ehealth.com

213 ms

medicare.com

203 ms

style.min.css

287 ms

critical.min.css

259 ms

font-awesome.css

237 ms

Our browser made a total of 37 requests to load all elements on the main page. We found that 3% of them (1 request) were addressed to the original Auth.ehealth.com, 46% (17 requests) were made to Medicare.com and 16% (6 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (530 ms) relates to the external source Medicare.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 280.1 kB (20%)

Content Size

1.4 MB

After Optimization

1.1 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Auth.ehealth.com main page is 1.4 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. 60% of websites need less resources to load. Images take 839.2 kB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 50.2 kB

  • Original 65.4 kB
  • After minification 58.1 kB
  • After compression 15.2 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 7.3 kB, which is 11% 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 50.2 kB or 77% of the original size.

Image Optimization

-6%

Potential reduce by 51.6 kB

  • Original 839.2 kB
  • After minification 787.5 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. Auth Ehealth images are well optimized though.

JavaScript Optimization

-23%

Potential reduce by 75.3 kB

  • Original 326.7 kB
  • After minification 326.4 kB
  • After compression 251.4 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 75.3 kB or 23% of the original size.

CSS Optimization

-56%

Potential reduce by 103.0 kB

  • Original 185.5 kB
  • After minification 185.3 kB
  • After compression 82.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. Auth.ehealth.com needs all CSS files to be minified and compressed as it can save up to 103.0 kB or 56% of the original size.

Requests Breakdown

Number of requests can be reduced by 20 (69%)

Requests Now

29

After Optimization

9

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 29 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Auth Ehealth. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 15 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

auth.ehealth.com

auth.ehealth.com

213 ms

medicare.com

medicare.com

203 ms

style.min.css

style.min.css

287 ms

critical.min.css

critical.min.css

259 ms

font-awesome.css

font-awesome.css

237 ms

homepage_header.min.js

homepage_header.min.js

283 ms

launch-084f0f418a76.min.js

launch-084f0f418a76.min.js

65 ms

jquery.min.js

jquery.min.js

337 ms

jquery-migrate.min.js

jquery-migrate.min.js

229 ms

css

css

30 ms

medicare-styles.min.css

medicare-styles.min.css

472 ms

main_home.min.js

main_home.min.js

530 ms

main_reco_home.min.js

main_reco_home.min.js

418 ms

main_recommendation_common.min.js

main_recommendation_common.min.js

418 ms

homepage-aep.min.css

homepage-aep.min.css

418 ms

id

id

59 ms

AppMeasurement.min.js

AppMeasurement.min.js

19 ms

AppMeasurement_Module_ActivityMap.min.js

AppMeasurement_Module_ActivityMap.min.js

103 ms

fbevents.js

fbevents.js

91 ms

full-color-logo.svg

full-color-logo.svg

108 ms

BBB.inline.svg

BBB.inline.svg

111 ms

soc.png

soc.png

115 ms

dest5.html

dest5.html

91 ms

seal.min.js

seal.min.js

294 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf

107 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVc.ttf

106 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf

221 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4gaVc.ttf

262 ms

print.css

print.css

119 ms

RC61e64c6d5bba4e6fa2eb9c9ccc683a13-source.min.js

RC61e64c6d5bba4e6fa2eb9c9ccc683a13-source.min.js

114 ms

RC45a9a4b55b4d480abe1cc123eae57f5c-source.min.js

RC45a9a4b55b4d480abe1cc123eae57f5c-source.min.js

70 ms

MDC_Desktop.png

MDC_Desktop.png

79 ms

Med40680

Med40680

169 ms

TK3_WkUHHAIjg75cFRf3bXL8LICs1_FvsUZiYA.ttf

TK3_WkUHHAIjg75cFRf3bXL8LICs1_FvsUZiYA.ttf

12 ms

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0RkxhjWVAexQ.ttf

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0RkxhjWVAexQ.ttf

11 ms

ibs:dpid=477&dpuuid=263f65feb0956e327885a99462347d9d36d299ffd30a04c7ad7353f6c32bdb43b0da87c991749652

ibs:dpid=477&dpuuid=263f65feb0956e327885a99462347d9d36d299ffd30a04c7ad7353f6c32bdb43b0da87c991749652

10 ms

pnapi_integration-latest.min.js

pnapi_integration-latest.min.js

19 ms

Accessibility Review

auth.ehealth.com accessibility score

100

Accessibility Issues

Best Practices

auth.ehealth.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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

auth.ehealth.com SEO score

82

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

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

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

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

auth.ehealth.com

Open Graph data is detected on the main page of Auth Ehealth. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: