Tools & Wizards About Us
hain.org screenshot

Report Summary

  • 63

    Performance

    Renders faster than
    77% of other websites

  • 45

    Accessibility

    Visual factors better than
    that of 19% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 85

    SEO

    Google-friendlier than
    55% of websites

hain.org

Home

Page Load Speed

1.8 sec in total

First Response

22 ms

Resources Loaded

1.7 sec

Page Rendered

121 ms

hain.org screenshot

About Website

Click here to check amazing Hain content. Otherwise, check out these important facts you probably never knew about hain.org

Visit hain.org

Key Findings

We analyzed Hain.org page load time and found that the first response time was 22 ms and then it took 1.8 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

hain.org performance score

63

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.2 s

77/100

10%

LCP (Largest Contentful Paint)

Value5.9 s

14/100

25%

SI (Speed Index)

Value3.5 s

89/100

10%

TBT (Total Blocking Time)

Value20 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.453

20/100

15%

TTI (Time to Interactive)

Value2.4 s

98/100

10%

Network Requests Diagram

www.hain.org

22 ms

site.css

9 ms

duel.js

11 ms

jq.js

26 ms

7f2e3f03a19ad51befc349ab9e0ac66c

235 ms

Our browser made a total of 28 requests to load all elements on the main page. We found that 7% of them (2 requests) were addressed to the original Hain.org, 46% (13 requests) were made to Nebula.wsimg.com and 46% (13 requests) were made to Img1.wsimg.com. The less responsive or slowest element that took the longest time to load (892 ms) relates to the external source Nebula.wsimg.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 167.3 kB (2%)

Content Size

8.7 MB

After Optimization

8.6 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Hain.org main page is 8.7 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. 40% of websites need less resources to load. Images take 8.5 MB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 33.3 kB

  • Original 42.3 kB
  • After minification 42.3 kB
  • After compression 9.0 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 33.3 kB or 79% of the original size.

Image Optimization

-0%

Potential reduce by 13.4 kB

  • Original 8.5 MB
  • After minification 8.5 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. Hain images are well optimized though.

JavaScript Optimization

-61%

Potential reduce by 120.6 kB

  • Original 197.2 kB
  • After minification 197.2 kB
  • After compression 76.7 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 120.6 kB or 61% of the original size.

CSS Optimization

-1%

Potential reduce by 33 B

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

Requests Breakdown

Number of requests can be reduced by 10 (38%)

Requests Now

26

After Optimization

16

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.hain.org

www.hain.org

22 ms

site.css

site.css

9 ms

duel.js

duel.js

11 ms

jq.js

jq.js

26 ms

7f2e3f03a19ad51befc349ab9e0ac66c

7f2e3f03a19ad51befc349ab9e0ac66c

235 ms

media.gallery.js

media.gallery.js

35 ms

subNavigation.js

subNavigation.js

34 ms

cookiemanager.js

cookiemanager.js

32 ms

iebackground.js

iebackground.js

32 ms

336aa99828fb046d9426f5f13aa71f14

336aa99828fb046d9426f5f13aa71f14

260 ms

07eae34d56aae7c71d056ef38116de4c

07eae34d56aae7c71d056ef38116de4c

225 ms

scc-c2.min.js

scc-c2.min.js

36 ms

util.window.js

util.window.js

9 ms

util.instances.js

util.instances.js

7 ms

util.model.js

util.model.js

13 ms

documentHelper.js

documentHelper.js

12 ms

wsb-slideshow-arrows.png

wsb-slideshow-arrows.png

24 ms

ab78b88a90cfa764796c30d14579506d

ab78b88a90cfa764796c30d14579506d

892 ms

3e9472cc242b23fbec573c15c6b0d525

3e9472cc242b23fbec573c15c6b0d525

461 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvaorCIPrc.woff

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvaorCIPrc.woff

21 ms

580887955a68621f65f20a5633ac403a

580887955a68621f65f20a5633ac403a

577 ms

9a5a448e41b395e3257b58d02995bf98

9a5a448e41b395e3257b58d02995bf98

729 ms

2e87c96ba50264f3d52b2f094969c976

2e87c96ba50264f3d52b2f094969c976

543 ms

d7590c1b9572922bdf59e576c6e7986e

d7590c1b9572922bdf59e576c6e7986e

481 ms

cb7188b69bfbf4f1e35c7e4660195dd8

cb7188b69bfbf4f1e35c7e4660195dd8

525 ms

6dcfdbae670d46099536147ac74c1fb3

6dcfdbae670d46099536147ac74c1fb3

463 ms

e7d19a75007ee438ac6d363dbcb0d118

e7d19a75007ee438ac6d363dbcb0d118

361 ms

d65f9954540260fe8f574283586f9ddb

d65f9954540260fe8f574283586f9ddb

414 ms

Accessibility Review

hain.org accessibility score

45

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

Buttons do not have an accessible name

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

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.

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

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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

hain.org SEO score

85

Search Engine Optimization Advices

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

hain.org

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