Tools & Wizards About Us
healthymize.com screenshot

Report Summary

  • 30

    Performance

    Renders faster than
    50% of other websites

  • 61

    Accessibility

    Visual factors better than
    that of 27% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 85

    SEO

    Google-friendlier than
    55% of websites

healthymize.com

HEALTHYMIZE | Personalized, artificial intelligence (AI) based Voice Monitoring for Voice-Affecting Diseases

Page Load Speed

1.2 sec in total

First Response

102 ms

Resources Loaded

786 ms

Page Rendered

301 ms

healthymize.com screenshot

About Website

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

HEALTHYMIZE provides Personalized, artificial intelligence (AI) based Voice Monitoring for Voice-Affecting Diseases.

Visit healthymize.com

Key Findings

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

Performance Metrics

healthymize.com performance score

30

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.3 s

3/100

10%

LCP (Largest Contentful Paint)

Value8.7 s

1/100

25%

SI (Speed Index)

Value9.0 s

14/100

10%

TBT (Total Blocking Time)

Value180 ms

91/100

30%

CLS (Cumulative Layout Shift)

Value1.007

2/100

15%

TTI (Time to Interactive)

Value16.2 s

6/100

10%

Network Requests Diagram

healthymize.com

102 ms

animate.css

70 ms

bootstrap.css

114 ms

et-line-icons.css

47 ms

font-awesome.min.css

69 ms

Our browser made a total of 71 requests to load all elements on the main page. We found that 76% of them (54 requests) were addressed to the original Healthymize.com, 7% (5 requests) were made to Fonts.gstatic.com and 6% (4 requests) were made to Maps.googleapis.com. The less responsive or slowest element that took the longest time to load (487 ms) relates to the external source Google.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.1 MB (48%)

Content Size

2.3 MB

After Optimization

1.2 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Healthymize.com main page is 2.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 862.1 kB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 29.5 kB

  • Original 34.8 kB
  • After minification 20.0 kB
  • After compression 5.3 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 14.8 kB, which is 43% 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 29.5 kB or 85% of the original size.

Image Optimization

-2%

Potential reduce by 13.8 kB

  • Original 862.1 kB
  • After minification 848.3 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. HEALTHYMIZE images are well optimized though.

JavaScript Optimization

-67%

Potential reduce by 514.6 kB

  • Original 767.5 kB
  • After minification 628.8 kB
  • After compression 252.9 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 514.6 kB or 67% of the original size.

CSS Optimization

-88%

Potential reduce by 537.1 kB

  • Original 613.1 kB
  • After minification 480.2 kB
  • After compression 75.9 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. Healthymize.com needs all CSS files to be minified and compressed as it can save up to 537.1 kB or 88% of the original size.

Requests Breakdown

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

Requests Now

64

After Optimization

20

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

healthymize.com

healthymize.com

102 ms

animate.css

animate.css

70 ms

bootstrap.css

bootstrap.css

114 ms

et-line-icons.css

et-line-icons.css

47 ms

font-awesome.min.css

font-awesome.min.css

69 ms

extralayers.css

extralayers.css

89 ms

settings.css

settings.css

91 ms

magnific-popup.css

magnific-popup.css

71 ms

owl.carousel.css

owl.carousel.css

91 ms

owl.transitions.css

owl.transitions.css

94 ms

full-slider.css

full-slider.css

94 ms

text-effect.css

text-effect.css

117 ms

style.css

style.css

158 ms

responsive.css

responsive.css

135 ms

jquery.min.js

jquery.min.js

137 ms

modernizr.js

modernizr.js

117 ms

healthymize.js

healthymize.js

134 ms

bootstrap-hover-dropdown.js

bootstrap-hover-dropdown.js

117 ms

jquery.easing.1.3.js

jquery.easing.1.3.js

120 ms

skrollr.min.js

skrollr.min.js

145 ms

jquery.viewport.mini.js

jquery.viewport.mini.js

146 ms

smooth-scroll.js

smooth-scroll.js

146 ms

wow.min.js

wow.min.js

145 ms

page-scroll.js

page-scroll.js

146 ms

jquery.easypiechart.js

jquery.easypiechart.js

167 ms

jquery.parallax-1.1.3.js

jquery.parallax-1.1.3.js

166 ms

jquery.isotope.min.js

jquery.isotope.min.js

168 ms

owl.carousel.min.js

owl.carousel.min.js

166 ms

jquery.magnific-popup.min.js

jquery.magnific-popup.min.js

166 ms

popup-gallery.js

popup-gallery.js

166 ms

text-effect.js

text-effect.js

281 ms

jquery.tools.min.js

jquery.tools.min.js

283 ms

jquery.revolution.js

jquery.revolution.js

336 ms

counter.js

counter.js

282 ms

jquery.fitvids.js

jquery.fitvids.js

282 ms

imagesloaded.pkgd.min.js

imagesloaded.pkgd.min.js

282 ms

one-page-main.js

one-page-main.js

296 ms

main.js

main.js

272 ms

css

css

19 ms

css

css

38 ms

css

css

42 ms

embed

embed

266 ms

embed

embed

487 ms

Preloader_2.gif

Preloader_2.gif

66 ms

_healthymize_logo_70.png

_healthymize_logo_70.png

50 ms

_healthymize_doctor_tablet_1920_1200.jpg

_healthymize_doctor_tablet_1920_1200.jpg

100 ms

_healthymize_technology_1920_1100.jpg

_healthymize_technology_1920_1100.jpg

100 ms

_healthymize_doctors_xray_1920_960.jpg

_healthymize_doctors_xray_1920_960.jpg

50 ms

shady-lg-gr.jpg

shady-lg-gr.jpg

119 ms

daniel-lg-gr.jpg

daniel-lg-gr.jpg

115 ms

rafi-new-gr.jpg

rafi-new-gr.jpg

116 ms

maura-lg-gr.jpg

maura-lg-gr.jpg

117 ms

hazar-new.jpg

hazar-new.jpg

117 ms

alon-lg-gr.jpg

alon-lg-gr.jpg

118 ms

social-facebook-32.png

social-facebook-32.png

118 ms

social-linkedin-32.png

social-linkedin-32.png

119 ms

social-twitter-32.png

social-twitter-32.png

119 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVcUwaEQXjM.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVcUwaEQXjM.ttf

20 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVcUwaEQXjM.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVcUwaEQXjM.ttf

112 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVcUwaEQXjM.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVcUwaEQXjM.ttf

41 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVcUwaEQXjM.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVcUwaEQXjM.ttf

41 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4gaVcUwaEQXjM.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4gaVcUwaEQXjM.ttf

40 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

112 ms

analytics.js

analytics.js

43 ms

icon-move-light.png

icon-move-light.png

52 ms

collect

collect

28 ms

js

js

58 ms

js

js

26 ms

geometry.js

geometry.js

4 ms

search.js

search.js

6 ms

main.js

main.js

13 ms

Accessibility Review

healthymize.com accessibility score

61

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.

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

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

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

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

healthymize.com best practices score

83

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

SEO Factors

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

robots.txt is not valid

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Image elements do not have [alt] attributes

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

healthymize.com

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