Tools & Wizards About Us
hungryheart.org screenshot

Report Summary

  • 48

    Performance

    Renders faster than
    66% of other websites

  • 77

    Accessibility

    Visual factors better than
    that of 44% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

hungryheart.org

Emotional Eating Help Online | The Hungry Heart Program

Page Load Speed

1.7 sec in total

First Response

63 ms

Resources Loaded

1.4 sec

Page Rendered

244 ms

hungryheart.org screenshot

About Website

Visit hungryheart.org now to see the best up-to-date Hungry Heart content and also check out these interesting facts you probably never knew about hungryheart.org

Lose those extra pounds once and for all. Food is the most heavily abused drug. Get our emotional eating help online. Proven program for over 15 years.

Visit hungryheart.org

Key Findings

We analyzed Hungryheart.org page load time and found that the first response time was 63 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

hungryheart.org performance score

48

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.6 s

14/100

10%

LCP (Largest Contentful Paint)

Value5.8 s

15/100

25%

SI (Speed Index)

Value6.9 s

34/100

10%

TBT (Total Blocking Time)

Value350 ms

73/100

30%

CLS (Cumulative Layout Shift)

Value0.082

94/100

15%

TTI (Time to Interactive)

Value8.5 s

37/100

10%

Network Requests Diagram

hungryheart.org

63 ms

thehungryheart.org

394 ms

wp-emoji-release.min.js

63 ms

main.css

122 ms

style.min.css

181 ms

Our browser made a total of 48 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Hungryheart.org, 52% (25 requests) were made to Thehungryheart.org and 27% (13 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (394 ms) relates to the external source Thehungryheart.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 50.4 kB (8%)

Content Size

626.7 kB

After Optimization

576.3 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Hungryheart.org main page is 626.7 kB. 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. Javascripts take 450.8 kB which makes up the majority of the site volume.

HTML Optimization

-72%

Potential reduce by 31.7 kB

  • Original 44.3 kB
  • After minification 42.3 kB
  • After compression 12.6 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 31.7 kB or 72% of the original size.

Image Optimization

-0%

Potential reduce by 11 B

  • Original 41.0 kB
  • After minification 41.0 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. Hungry Heart images are well optimized though.

JavaScript Optimization

-2%

Potential reduce by 10.8 kB

  • Original 450.8 kB
  • After minification 450.8 kB
  • After compression 440.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

-9%

Potential reduce by 7.9 kB

  • Original 90.6 kB
  • After minification 90.6 kB
  • After compression 82.7 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. Hungryheart.org has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 26 (84%)

Requests Now

31

After Optimization

5

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

hungryheart.org

hungryheart.org

63 ms

thehungryheart.org

thehungryheart.org

394 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

63 ms

main.css

main.css

122 ms

style.min.css

style.min.css

181 ms

styles.css

styles.css

185 ms

diggdigg-style.css

diggdigg-style.css

190 ms

css

css

43 ms

css

css

60 ms

style.css

style.css

190 ms

shortcodes.css

shortcodes.css

203 ms

shortcodes_responsive.css

shortcodes_responsive.css

184 ms

jquery.min.js

jquery.min.js

244 ms

jquery-migrate.min.js

jquery-migrate.min.js

241 ms

site.js

site.js

242 ms

E-v1.js

E-v1.js

30 ms

vertical-m.css

vertical-m.css

257 ms

scripts.js

scripts.js

248 ms

jquery.fitvids.js

jquery.fitvids.js

248 ms

waypoints.min.js

waypoints.min.js

298 ms

jquery.magnific-popup.js

jquery.magnific-popup.js

301 ms

custom.js

custom.js

302 ms

smoothscroll.js

smoothscroll.js

308 ms

wp-embed.min.js

wp-embed.min.js

306 ms

E-v1.js

E-v1.js

20 ms

style.css

style.css

135 ms

analytics.js

analytics.js

96 ms

thehungryheartlogo70.gif

thehungryheartlogo70.gif

95 ms

homekick.jpg

homekick.jpg

95 ms

all.js

all.js

93 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4uaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4uaVc.ttf

85 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4uaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4uaVc.ttf

112 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4uaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4uaVc.ttf

155 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4uaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4uaVc.ttf

152 ms

S6uyw4BMUTPHjx4wWw.ttf

S6uyw4BMUTPHjx4wWw.ttf

155 ms

S6u9w4BMUTPHh7USSwiPHA.ttf

S6u9w4BMUTPHh7USSwiPHA.ttf

155 ms

S6u8w4BMUTPHh30AXC-v.ttf

S6u8w4BMUTPHh30AXC-v.ttf

154 ms

S6u9w4BMUTPHh6UVSwiPHA.ttf

S6u9w4BMUTPHh6UVSwiPHA.ttf

154 ms

S6u9w4BMUTPHh50XSwiPHA.ttf

S6u9w4BMUTPHh50XSwiPHA.ttf

156 ms

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk8ZkWV4exQ.ttf

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk8ZkWV4exQ.ttf

115 ms

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk5hkWV4exQ.ttf

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk5hkWV4exQ.ttf

117 ms

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0RkyFjWV4exQ.ttf

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0RkyFjWV4exQ.ttf

113 ms

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk0ZjWV4exQ.ttf

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk0ZjWV4exQ.ttf

118 ms

ETmodules_v2.ttf

ETmodules_v2.ttf

144 ms

ETmodules_v2.ttf

ETmodules_v2.ttf

143 ms

all.js

all.js

51 ms

collect

collect

76 ms

js

js

77 ms

Accessibility Review

hungryheart.org accessibility score

77

Accessibility Issues

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

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

hungryheart.org best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

hungryheart.org SEO score

100

Search Engine Optimization Advices

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 Hungryheart.org 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 Hungryheart.org 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

hungryheart.org

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