Tools & Wizards About Us
healthy-simply.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

healthy-simply.com

Simply Naturals

Page Load Speed

3.8 sec in total

First Response

193 ms

Resources Loaded

3.1 sec

Page Rendered

535 ms

healthy-simply.com screenshot

About Website

Click here to check amazing Healthy Simply content. Otherwise, check out these important facts you probably never knew about healthy-simply.com

Visit healthy-simply.com

Key Findings

We analyzed Healthy-simply.com page load time and found that the first response time was 193 ms and then it took 3.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.

Performance Metrics

healthy-simply.com performance score

0

Network Requests Diagram

113878

193 ms

goto.php

344 ms

goto.php

261 ms

c2.css

238 ms

font-awesome.min.css

319 ms

Our browser made a total of 67 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Healthy-simply.com, 1% (1 request) were made to Doctortrusted.org and 1% (1 request) were made to Portal.foregenix.com. The less responsive or slowest element that took the longest time to load (821 ms) relates to the external source Simplynaturals.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 410.1 kB (48%)

Content Size

846.0 kB

After Optimization

435.9 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-81%

Potential reduce by 34.9 kB

  • Original 43.2 kB
  • After minification 39.6 kB
  • After compression 8.3 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 34.9 kB or 81% of the original size.

Image Optimization

-13%

Potential reduce by 51.5 kB

  • Original 410.2 kB
  • After minification 358.7 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. Obviously, Healthy Simply needs image optimization as it can save up to 51.5 kB or 13% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-83%

Potential reduce by 271.5 kB

  • Original 328.8 kB
  • After minification 199.6 kB
  • After compression 57.3 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 271.5 kB or 83% of the original size.

CSS Optimization

-82%

Potential reduce by 52.2 kB

  • Original 63.8 kB
  • After minification 54.2 kB
  • After compression 11.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. Healthy-simply.com needs all CSS files to be minified and compressed as it can save up to 52.2 kB or 82% of the original size.

Requests Breakdown

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

Requests Now

60

After Optimization

36

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

113878

113878

193 ms

goto.php

goto.php

344 ms

goto.php

goto.php

261 ms

c2.css

c2.css

238 ms

font-awesome.min.css

font-awesome.min.css

319 ms

css.php

css.php

404 ms

highslide.css

highslide.css

245 ms

mousetext.js

mousetext.js

246 ms

ajax.js

ajax.js

247 ms

core3.js

core3.js

314 ms

show_prods.js

show_prods.js

328 ms

VM_FlashContent.js

VM_FlashContent.js

324 ms

jquery.js

jquery.js

821 ms

simply_funcs.js

simply_funcs.js

393 ms

highslide.js

highslide.js

476 ms

popOver.js

popOver.js

414 ms

cookies.js

cookies.js

414 ms

popOver.css

popOver.css

471 ms

mousetextstyle.js

mousetextstyle.js

407 ms

FGXseal.php

FGXseal.php

338 ms

1.jpg

1.jpg

87 ms

7.jpg

7.jpg

79 ms

9.jpg

9.jpg

82 ms

35.jpg

35.jpg

93 ms

customer_login.gif

customer_login.gif

89 ms

distributor_login.gif

distributor_login.gif

85 ms

sn_home.gif

sn_home.gif

157 ms

sizzlingminerals-videopic2.jpg

sizzlingminerals-videopic2.jpg

480 ms

paw.jpg

paw.jpg

164 ms

buynow-glossy_button_orange.png

buynow-glossy_button_orange.png

163 ms

testimonial-glossy_button_orange.png

testimonial-glossy_button_orange.png

169 ms

doctorsays-glossy_button_orange.png

doctorsays-glossy_button_orange.png

335 ms

watchvidedo-glossy_button_orange.png

watchvidedo-glossy_button_orange.png

234 ms

glossy_button_notconvinced1_orange_oval.jpg

glossy_button_notconvinced1_orange_oval.jpg

324 ms

glossy_button_readthebook_orange_oval.png

glossy_button_readthebook_orange_oval.png

330 ms

sn_headerbg.gif

sn_headerbg.gif

244 ms

sn_header.gif

sn_header.gif

380 ms

your_basket.png

your_basket.png

327 ms

sn_searchbutton.gif

sn_searchbutton.gif

393 ms

search_icon.gif

search_icon.gif

409 ms

col_200.gif

col_200.gif

400 ms

r3_navclosed.gif

r3_navclosed.gif

407 ms

col_520.gif

col_520.gif

450 ms

seal_1257128.js

seal_1257128.js

52 ms

get_health_news.php

get_health_news.php

561 ms

sn_footerbg.gif

sn_footerbg.gif

453 ms

sn_footer.gif

sn_footer.gif

529 ms

FGXsealLogo.php

FGXsealLogo.php

386 ms

get_featured_products.php

get_featured_products.php

563 ms

zoomout.cur

zoomout.cur

86 ms

1.png

1.png

81 ms

2.png

2.png

81 ms

3.png

3.png

84 ms

4.png

4.png

98 ms

5.png

5.png

128 ms

6.png

6.png

158 ms

7.png

7.png

159 ms

8.png

8.png

169 ms

122.jpg

122.jpg

118 ms

124.jpg

124.jpg

130 ms

17.jpg

17.jpg

166 ms

78.jpg

78.jpg

265 ms

80.jpg

80.jpg

192 ms

107.jpg

107.jpg

199 ms

136.jpg

136.jpg

206 ms

170.jpg

170.jpg

209 ms

find_out_more_230.gif

find_out_more_230.gif

248 ms

SEO Factors

healthy-simply.com SEO score

0

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    N/A

  • Encoding

    ISO-8859-1

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Healthy-simply.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else) and no language is claimed in <html> or <meta> tags either. Our system also found out that Healthy-simply.com main page’s claimed encoding is iso-8859-1. 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.

Social Sharing Optimization

healthy-simply.com

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