Tools & Wizards About Us
help.heal.com screenshot

Report Summary

  • 40

    Performance

    Renders faster than
    59% of other websites

  • 98

    Accessibility

    Visual factors better than
    that of 94% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 85

    SEO

    Google-friendlier than
    55% of websites

help.heal.com

Primary Care Anywhere | Care Designed with Seniors in Mind

Page Load Speed

1.4 sec in total

First Response

23 ms

Resources Loaded

656 ms

Page Rendered

713 ms

help.heal.com screenshot

About Website

Visit help.heal.com now to see the best up-to-date Help Heal content for United States and also check out these interesting facts you probably never knew about help.heal.com

Visit help.heal.com

Key Findings

We analyzed Help.heal.com page load time and found that the first response time was 23 ms and then it took 1.4 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.

Performance Metrics

help.heal.com performance score

40

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.5 s

34/100

10%

LCP (Largest Contentful Paint)

Value7.8 s

3/100

25%

SI (Speed Index)

Value4.6 s

70/100

10%

TBT (Total Blocking Time)

Value690 ms

43/100

30%

CLS (Cumulative Layout Shift)

Value0.002

100/100

15%

TTI (Time to Interactive)

Value14.3 s

9/100

10%

Network Requests Diagram

help.heal.com

23 ms

primary-care-anywhere.html

92 ms

clientlib-base.min.ACSHASH76af1ae2d700b523a1118d3675e88a6d.css

6 ms

isk0brf.css

163 ms

CoveoFullSearch.min.css

33 ms

Our browser made a total of 39 requests to load all elements on the main page. We found that 3% of them (1 request) were addressed to the original Help.heal.com, 38% (15 requests) were made to Centerwellprimarycare.com and 33% (13 requests) were made to Assets.humana.com. The less responsive or slowest element that took the longest time to load (280 ms) relates to the external source Assets.humana.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 56.6 kB (4%)

Content Size

1.3 MB

After Optimization

1.2 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Help.heal.com main page is 1.3 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. 65% of websites need less resources to load. Images take 781.8 kB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 56.5 kB

  • Original 67.2 kB
  • After minification 58.9 kB
  • After compression 10.7 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 8.3 kB, which is 12% 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 56.5 kB or 84% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 781.8 kB
  • After minification 781.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. Help Heal images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 105 B

  • Original 369.7 kB
  • After minification 369.7 kB
  • After compression 369.6 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. This website has mostly compressed JavaScripts.

CSS Optimization

-0%

Potential reduce by 5 B

  • Original 48.1 kB
  • After minification 48.1 kB
  • After compression 48.1 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. Help.heal.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 14 (45%)

Requests Now

31

After Optimization

17

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

help.heal.com

help.heal.com

23 ms

primary-care-anywhere.html

primary-care-anywhere.html

92 ms

clientlib-base.min.ACSHASH76af1ae2d700b523a1118d3675e88a6d.css

clientlib-base.min.ACSHASH76af1ae2d700b523a1118d3675e88a6d.css

6 ms

isk0brf.css

isk0brf.css

163 ms

CoveoFullSearch.min.css

CoveoFullSearch.min.css

33 ms

CoveoJsSearch.Lazy.min.js

CoveoJsSearch.Lazy.min.js

45 ms

templates.js

templates.js

43 ms

clientlib-site.min.ACSHASHe60148507435efe280aeeab1c8fc0cb3.css

clientlib-site.min.ACSHASHe60148507435efe280aeeab1c8fc0cb3.css

31 ms

clientlib-dependencies.min.ACSHASHa9dcac4698709ca8e1cbc88363cf0793.js

clientlib-dependencies.min.ACSHASHa9dcac4698709ca8e1cbc88363cf0793.js

27 ms

clientlib-site.min.ACSHASH56285155e117d813a2534e7d1092dff5.js

clientlib-site.min.ACSHASH56285155e117d813a2534e7d1092dff5.js

42 ms

container.min.ACSHASHc8339545b501e3db3abc37c9a4cc2d6e.js

container.min.ACSHASHc8339545b501e3db3abc37c9a4cc2d6e.js

26 ms

clientlib-base.min.ACSHASHf6cfd90ccdef8ebd0600b1308a19c4dc.js

clientlib-base.min.ACSHASHf6cfd90ccdef8ebd0600b1308a19c4dc.js

26 ms

swap.js

swap.js

42 ms

css

css

30 ms

p.css

p.css

18 ms

utag.js

utag.js

234 ms

CenterWell_PrimaryCareAnywhere_Logo_RGB_dark-blue-light-blue-green_padding_horizontal25

CenterWell_PrimaryCareAnywhere_Logo_RGB_dark-blue-light-blue-green_padding_horizontal25

145 ms

primary-care-anywhere.html

primary-care-anywhere.html

110 ms

token.json

token.json

168 ms

Hero@2x

Hero@2x

114 ms

Bringing%20the%20doctor@2x

Bringing%20the%20doctor@2x

133 ms

Expanding%20your%20healthcare%20choices@2x

Expanding%20your%20healthcare%20choices@2x

212 ms

Board-certified@2x

Board-certified@2x

280 ms

Professional@2x

Professional@2x

231 ms

Patient%20Support@2x

Patient%20Support@2x

250 ms

No%20additional%20cost@2x

No%20additional%20cost@2x

146 ms

Convenience@2x

Convenience@2x

153 ms

Patient_RGB_2C

Patient_RGB_2C

232 ms

2023_Centrwell_Icon_RGB_OnlineForm_Dark-Blue-Green-Card-With-Background

2023_Centrwell_Icon_RGB_OnlineForm_Dark-Blue-Green-Card-With-Background

184 ms

phone-cta_dark-blue

phone-cta_dark-blue

212 ms

2023_Centrwell_Icon_RGB_Cta-Call-Phone_Dark-Blue-Green-Card-With-Background

2023_Centrwell_Icon_RGB_Cta-Call-Phone_Dark-Blue-Green-Card-With-Background

260 ms

custom_forms.js

custom_forms.js

88 ms

external_forms.js

external_forms.js

84 ms

museosans-500.woff

museosans-500.woff

214 ms

museosans-300.woff

museosans-300.woff

136 ms

museosans-100.woff

museosans-100.woff

161 ms

museosans-700.woff

museosans-700.woff

57 ms

museosans-900.woff

museosans-900.woff

76 ms

icomoon.ttf

icomoon.ttf

107 ms

Accessibility Review

help.heal.com accessibility score

98

Accessibility Issues

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best Practices

help.heal.com best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

help.heal.com SEO score

85

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

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 Help.heal.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 Help.heal.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

help.heal.com

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