730 ms in total
17 ms
528 ms
185 ms
Visit healthfree.com now to see the best up-to-date Healthfree content for United States and also check out these interesting facts you probably never knew about healthfree.com
Visit healthfree.comWe analyzed Healthfree.com page load time and found that the first response time was 17 ms and then it took 713 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 10% of websites can load faster.
healthfree.com performance score
name
value
score
weighting
Value1.8 s
89/100
10%
Value2.1 s
96/100
25%
Value3.2 s
92/100
10%
Value420 ms
65/100
30%
Value0.356
31/100
15%
Value8.9 s
35/100
10%
17 ms
121 ms
4 ms
9 ms
23 ms
Our browser made a total of 57 requests to load all elements on the main page. We found that 77% of them (44 requests) were addressed to the original Healthfree.com, 5% (3 requests) were made to Google-analytics.com and 4% (2 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (357 ms) relates to the external source Facebook.com.
Page size can be reduced by 95.5 kB (6%)
1.6 MB
1.5 MB
In fact, the total size of Healthfree.com main page is 1.6 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. 35% of websites need less resources to load. Images take 1.4 MB which makes up the majority of the site volume.
Potential reduce by 25.4 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 4.4 kB, which is 13% 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 25.4 kB or 77% of the original size.
Potential reduce by 35.1 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. Healthfree images are well optimized though.
Potential reduce by 33.6 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 33.6 kB or 25% of the original size.
Potential reduce by 1.3 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. Healthfree.com needs all CSS files to be minified and compressed as it can save up to 1.3 kB or 38% of the original size.
Number of requests can be reduced by 25 (46%)
54
29
The browser has sent 54 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Healthfree. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 14 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
healthfree.com
17 ms
healthfree.com
121 ms
healthfree.css
4 ms
hfr-desktop.css
9 ms
google.js
23 ms
flexslider.css
22 ms
awt_analytics.js
112 ms
jquery.min.js
46 ms
ga.js
22 ms
b_jsonp.php
134 ms
hfr_mobile_tel.js
29 ms
jquery.flexslider.min.js
29 ms
email-hide.js
29 ms
gtm.js
82 ms
like.php
357 ms
PP_Acceptance_Marks_for_LogoCenter_76x48.png
36 ms
top2.jpg
28 ms
leftfade.jpg
27 ms
leftnavBG.jpg
27 ms
BUTTON%20on%20sale%20ver%203.png
28 ms
facebook_icon.png
27 ms
twitter_icon.png
31 ms
cart.jpg
32 ms
leftnavArrow.gif
31 ms
gobutton.gif
30 ms
navbottom.gif
32 ms
tonic-supreme-immune-lungs-slider.jpg
39 ms
SLIDER%20Miracle%20II%20600x200.jpg
36 ms
slider-chlorella-spirulina-600x200.png
40 ms
slider-nourishing-adrenal-thyroid-duo.jpg
39 ms
BUTTON%20clean%20&%20detox.png
35 ms
BUTTON%20herbal%20support.jpg
39 ms
button-skin-hair-and-home.jpg
38 ms
button-superfoods-and-supplements.jpg
41 ms
info-button-guide-to-cleansing.jpg
43 ms
info-button-blood-flow.png
45 ms
info-button-eat-your-way.jpg
45 ms
info-button-chlorella-spirulina-500x200.png
45 ms
info-button-natural-remedies-lifestyle.jpg
47 ms
topdivider.gif
45 ms
cc_logos.png
47 ms
google.html
146 ms
whitefade.gif
41 ms
rightfade.jpg
43 ms
analytics.js
52 ms
g1.js
20 ms
g2.js
20 ms
ecommerce.js
27 ms
collect
33 ms
__utm.gif
26 ms
print.css
8 ms
flexslider-icon.woff
11 ms
mobile.css
4 ms
collect
30 ms
js
56 ms
TttXWwYVW0v.js
25 ms
FEppCFCt76d.png
18 ms
healthfree.com accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
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
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
Links do not have a discernible name
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
List items (<li>) are not contained within <ul> or <ol> parent elements.
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
healthfree.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
healthfree.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
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
Document uses legible font sizes
Tap targets are not sized appropriately
EN
N/A
WINDOWS-1252
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Healthfree.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 Healthfree.com main page’s claimed encoding is windows-1252. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
healthfree.com
Open Graph description is not detected on the main page of Healthfree. 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: