Tools & Wizards About Us
myhealbe.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

myhealbe.com

Healbe GoBe: The only way to automatically measure calorie intake

Page Load Speed

4.5 sec in total

First Response

320 ms

Resources Loaded

3.4 sec

Page Rendered

754 ms

myhealbe.com screenshot

About Website

Welcome to myhealbe.com homepage info - get ready to check My Healbe best content right away, or after learning these important things about myhealbe.com

Healbe GoBe is the only wearable device that automatically measures the calories you consume and burn, by reading the glucose in your cells.

Visit myhealbe.com

Key Findings

We analyzed Myhealbe.com page load time and found that the first response time was 320 ms and then it took 4.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.

Performance Metrics

myhealbe.com performance score

0

Network Requests Diagram

myhealbe.com

320 ms

555 ms

css

53 ms

angular.min.js

28 ms

angular-sanitize.min.js

32 ms

Our browser made a total of 89 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Myhealbe.com, 29% (26 requests) were made to Static.healbe.com and 28% (25 requests) were made to Healbe.com. The less responsive or slowest element that took the longest time to load (952 ms) relates to the external source Healbe.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 669.3 kB (22%)

Content Size

3.0 MB

After Optimization

2.4 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-79%

Potential reduce by 30.0 kB

  • Original 37.8 kB
  • After minification 28.5 kB
  • After compression 7.8 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 9.3 kB, which is 25% 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 30.0 kB or 79% of the original size.

Image Optimization

-1%

Potential reduce by 26.0 kB

  • Original 2.2 MB
  • After minification 2.1 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. My Healbe images are well optimized though.

JavaScript Optimization

-66%

Potential reduce by 286.3 kB

  • Original 432.5 kB
  • After minification 432.3 kB
  • After compression 146.1 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 286.3 kB or 66% of the original size.

CSS Optimization

-83%

Potential reduce by 327.0 kB

  • Original 393.2 kB
  • After minification 392.7 kB
  • After compression 66.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. Myhealbe.com needs all CSS files to be minified and compressed as it can save up to 327.0 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 40 (51%)

Requests Now

79

After Optimization

39

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

myhealbe.com

myhealbe.com

320 ms

555 ms

css

css

53 ms

angular.min.js

angular.min.js

28 ms

angular-sanitize.min.js

angular-sanitize.min.js

32 ms

angular-animate.min.js

angular-animate.min.js

36 ms

angular-cookies.min.js

angular-cookies.min.js

35 ms

angular-touch.min.js

angular-touch.min.js

37 ms

site_scripts.js

site_scripts.js

462 ms

index.js

index.js

90 ms

bootstrap.css

bootstrap.css

657 ms

site_styles.css

site_styles.css

556 ms

index.css

index.css

179 ms

gtm.js

gtm.js

236 ms

gtm.js

gtm.js

285 ms

analytics.js

analytics.js

252 ms

bg.jpg

bg.jpg

639 ms

beNq3iQVGPQ

beNq3iQVGPQ

272 ms

export_data_form_close.png

export_data_form_close.png

212 ms

logo.png

logo.png

212 ms

inputPopupBg.png

inputPopupBg.png

211 ms

us.png

us.png

315 ms

mobile_menu.png

mobile_menu.png

351 ms

ru.png

ru.png

333 ms

cz.png

cz.png

424 ms

top_cover_sm.png

top_cover_sm.png

570 ms

feautured2.jpg

feautured2.jpg

515 ms

device.png

device.png

524 ms

slider_overlay_1.png

slider_overlay_1.png

645 ms

slider_overlay_2.png

slider_overlay_2.png

656 ms

slider_overlay_3.png

slider_overlay_3.png

736 ms

slider_overlay_4.png

slider_overlay_4.png

683 ms

slider_overlay_5.png

slider_overlay_5.png

799 ms

flow.png

flow.png

645 ms

chart_2.png

chart_2.png

745 ms

pack-1.png

pack-1.png

803 ms

facebook.png

facebook.png

755 ms

twitter.png

twitter.png

767 ms

insta.png

insta.png

814 ms

logowhite.png

logowhite.png

843 ms

running_girl.jpg

running_girl.jpg

450 ms

slider1_1.jpg

slider1_1.jpg

707 ms

slider2_1.jpg

slider2_1.jpg

711 ms

slider3_1.jpg

slider3_1.jpg

767 ms

slider4_1.jpg

slider4_1.jpg

952 ms

slider5_1.jpg

slider5_1.jpg

731 ms

background.jpg

background.jpg

702 ms

design1.jpg

design1.jpg

796 ms

design2.jpg

design2.jpg

784 ms

design3.jpg

design3.jpg

803 ms

design4.jpg

design4.jpg

826 ms

design5.jpg

design5.jpg

852 ms

left_slide.png

left_slide.png

859 ms

right_slide.png

right_slide.png

882 ms

round.png

round.png

894 ms

roundout.png

roundout.png

918 ms

checkauth

checkauth

802 ms

user.png

user.png

659 ms

sl1.png

sl1.png

745 ms

sl2.png

sl2.png

788 ms

sl3.png

sl3.png

794 ms

pack-1.png

pack-1.png

820 ms

RjgO7rYTmqiVp7vzi-Q5UaCWcynf_cDxXwCLxiixG1c.ttf

RjgO7rYTmqiVp7vzi-Q5UaCWcynf_cDxXwCLxiixG1c.ttf

84 ms

DXI1ORHCpsQm3Vp6mXoaTfOEPOIfcPv-fZ-WyMUtx48.ttf

DXI1ORHCpsQm3Vp6mXoaTfOEPOIfcPv-fZ-WyMUtx48.ttf

126 ms

k3k702ZOKiLJc3WVjuplzPOEPOIfcPv-fZ-WyMUtx48.ttf

k3k702ZOKiLJc3WVjuplzPOEPOIfcPv-fZ-WyMUtx48.ttf

154 ms

fbevents.js

fbevents.js

342 ms

oct.js

oct.js

232 ms

hotjar-81356.js

hotjar-81356.js

302 ms

collect

collect

41 ms

www-embed-player-vfl-z2BtK.css

www-embed-player-vfl-z2BtK.css

105 ms

www-embed-player.js

www-embed-player.js

129 ms

rtrg

rtrg

526 ms

collect

collect

165 ms

collect

collect

146 ms

fBnyGA8Aionz5086-mElmoOSPUuyQ1M9Un647_EjucU.js

fBnyGA8Aionz5086-mElmoOSPUuyQ1M9Un647_EjucU.js

49 ms

ad_status.js

ad_status.js

50 ms

zN7GBFwfMP4uA6AR0HCoLQ.ttf

zN7GBFwfMP4uA6AR0HCoLQ.ttf

27 ms

RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf

RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf

27 ms

ga-audiences

ga-audiences

41 ms

adsct

adsct

147 ms

adsct

adsct

95 ms

ga-audiences

ga-audiences

32 ms

modules-79ac3e471402dedc7fa595a0b4974f10.js

modules-79ac3e471402dedc7fa595a0b4974f10.js

52 ms

34 ms

37 ms

visit-data

visit-data

222 ms

nr-892.min.js

nr-892.min.js

98 ms

healbe.jsp

healbe.jsp

275 ms

eaac77efd5

eaac77efd5

103 ms

SEO Factors

myhealbe.com SEO score

0

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

myhealbe.com

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