Report Summary

  • 30

    Performance

    Renders faster than
    50% of other websites

  • 86

    Accessibility

    Visual factors better than
    that of 69% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    86% of websites

  • 77

    SEO

    Google-friendlier than
    45% of websites

healthy.net

Healthy.net

Page Load Speed

1.9 sec in total

First Response

122 ms

Resources Loaded

1.5 sec

Page Rendered

198 ms

healthy.net screenshot

About Website

Visit healthy.net now to see the best up-to-date Healthy content for United States and also check out these interesting facts you probably never knew about healthy.net

Healthy.net is a large source of wellness, integrative medicine, alternative therapies and mind-body-spirit health information. Comprehensive, in-depth collection of expert content and services includ...

Visit healthy.net

Key Findings

We analyzed Healthy.net page load time and found that the first response time was 122 ms and then it took 1.7 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 30% of websites can load faster.

Performance Metrics

healthy.net performance score

30

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.2 s

43/100

10%

LCP (Largest Contentful Paint)

Value9.6 s

0/100

25%

SI (Speed Index)

Value5.9 s

48/100

10%

TBT (Total Blocking Time)

Value660 ms

45/100

30%

CLS (Cumulative Layout Shift)

Value0.386

27/100

15%

TTI (Time to Interactive)

Value8.9 s

35/100

10%

Network Requests Diagram

healthy.net

122 ms

www.healthy.net

141 ms

Healthy.js

52 ms

Fcheck.js

54 ms

urchin.js

22 ms

Our browser made a total of 68 requests to load all elements on the main page. We found that 57% of them (39 requests) were addressed to the original Healthy.net, 22% (15 requests) were made to Scontent.xx.fbcdn.net and 15% (10 requests) were made to Static.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (395 ms) relates to the external source Scontent.xx.fbcdn.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 146.2 kB (30%)

Content Size

484.4 kB

After Optimization

338.2 kB

In fact, the total size of Healthy.net main page is 484.4 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. 40% of websites need less resources to load. Images take 308.7 kB which makes up the majority of the site volume.

HTML Optimization

-76%

Potential reduce by 33.9 kB

  • Original 44.7 kB
  • After minification 41.6 kB
  • After compression 10.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. 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.9 kB or 76% of the original size.

Image Optimization

-5%

Potential reduce by 13.9 kB

  • Original 308.7 kB
  • After minification 294.8 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. Healthy images are well optimized though.

JavaScript Optimization

-70%

Potential reduce by 56.9 kB

  • Original 81.6 kB
  • After minification 66.9 kB
  • After compression 24.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 56.9 kB or 70% of the original size.

CSS Optimization

-84%

Potential reduce by 41.5 kB

  • Original 49.3 kB
  • After minification 42.1 kB
  • After compression 7.8 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. Healthy.net needs all CSS files to be minified and compressed as it can save up to 41.5 kB or 84% of the original size.

Requests Breakdown

Number of requests can be reduced by 35 (55%)

Requests Now

64

After Optimization

29

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

Accessibility Review

healthy.net 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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

healthy.net best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

healthy.net SEO score

77

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

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

High

Tap targets are not sized appropriately

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 Healthy.net 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 Healthy.net 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 description is not detected on the main page of Healthy. 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: