Report Summary

  • 29

    Performance

    Renders faster than
    49% of other websites

  • 86

    Accessibility

    Visual factors better than
    that of 61% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 89

    SEO

    Google-friendlier than
    66% of websites

healee.com

Unlock the power of patient access | Healee

Page Load Speed

2 sec in total

First Response

42 ms

Resources Loaded

908 ms

Page Rendered

1.1 sec

About Website

Click here to check amazing Healee content. Otherwise, check out these important facts you probably never knew about healee.com

Navigate the complexities of healthcare scheduling and maximize operational efficiency through Healee's advanced patient access solution

Visit healee.com

Key Findings

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

Performance Metrics

healee.com performance score

29

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.9 s

11/100

10%

LCP (Largest Contentful Paint)

Value12.6 s

0/100

25%

SI (Speed Index)

Value6.0 s

46/100

10%

TBT (Total Blocking Time)

Value1,120 ms

23/100

30%

CLS (Cumulative Layout Shift)

Value0.004

100/100

15%

TTI (Time to Interactive)

Value12.6 s

14/100

10%

Network Requests Diagram

healee.com

42 ms

www.healee.com

135 ms

gtm.js

72 ms

reb2b.js.gz

275 ms

home.1726665994776.css

36 ms

Our browser made a total of 26 requests to load all elements on the main page. We found that 92% of them (24 requests) were addressed to the original Healee.com, 4% (1 request) were made to Googletagmanager.com and 4% (1 request) were made to S3-us-west-2.amazonaws.com. The less responsive or slowest element that took the longest time to load (553 ms) belongs to the original domain Healee.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 116.4 kB (3%)

Content Size

3.9 MB

After Optimization

3.8 MB

In fact, the total size of Healee.com main page is 3.9 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 3.7 MB which makes up the majority of the site volume.

HTML Optimization

-73%

Potential reduce by 57.7 kB

  • Original 79.6 kB
  • After minification 79.5 kB
  • After compression 21.9 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. 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 57.7 kB or 73% of the original size.

Image Optimization

-2%

Potential reduce by 58.5 kB

  • Original 3.7 MB
  • After minification 3.7 MB

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. Healee images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 9 B

  • Original 48.0 kB
  • After minification 48.0 kB
  • After compression 48.0 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

-1%

Potential reduce by 231 B

  • Original 31.4 kB
  • After minification 31.4 kB
  • After compression 31.2 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. Healee.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 4 (24%)

Requests Now

17

After Optimization

13

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

Accessibility Review

healee.com accessibility score

86

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

High

Links do not have a discernible name

Best Practices

healee.com best practices score

75

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

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

healee.com SEO score

89

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 Healee.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 Healee.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

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