Tools & Wizards About Us
ediblehaven.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

ediblehaven.com

Page Load Speed

5.6 sec in total

First Response

2.1 sec

Resources Loaded

3.3 sec

Page Rendered

196 ms

ediblehaven.com screenshot

About Website

Click here to check amazing Ediblehaven content. Otherwise, check out these important facts you probably never knew about ediblehaven.com

Coconut Oil Health & Beauty Benefits • Boosts The Body’s Immune System! • Helps You Lose Weight – Contains Short And Medium-Chain Fatty   Acids! • Fantastic Source Of Saturated Medium Chain Triglyceri...

Visit ediblehaven.com

Key Findings

We analyzed Ediblehaven.com page load time and found that the first response time was 2.1 sec and then it took 3.5 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

ediblehaven.com performance score

0

Network Requests Diagram

ediblehaven.com

2145 ms

wp-emoji-release.min.js

201 ms

styles.css

228 ms

settings.css

219 ms

captions.css

215 ms

Our browser made a total of 58 requests to load all elements on the main page. We found that 84% of them (49 requests) were addressed to the original Ediblehaven.com, 3% (2 requests) were made to Youtube.com and 3% (2 requests) were made to S.ytimg.com. The less responsive or slowest element that took the longest time to load (2.1 sec) belongs to the original domain Ediblehaven.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 695.4 kB (49%)

Content Size

1.4 MB

After Optimization

715.1 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-70%

Potential reduce by 23.5 kB

  • Original 33.7 kB
  • After minification 32.4 kB
  • After compression 10.1 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 23.5 kB or 70% of the original size.

Image Optimization

-6%

Potential reduce by 29.5 kB

  • Original 502.3 kB
  • After minification 472.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. Ediblehaven images are well optimized though.

JavaScript Optimization

-67%

Potential reduce by 331.0 kB

  • Original 491.2 kB
  • After minification 488.5 kB
  • After compression 160.2 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 331.0 kB or 67% of the original size.

CSS Optimization

-81%

Potential reduce by 311.3 kB

  • Original 383.2 kB
  • After minification 370.6 kB
  • After compression 71.9 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. Ediblehaven.com needs all CSS files to be minified and compressed as it can save up to 311.3 kB or 81% of the original size.

Requests Breakdown

Number of requests can be reduced by 28 (52%)

Requests Now

54

After Optimization

26

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

ediblehaven.com

ediblehaven.com

2145 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

201 ms

styles.css

styles.css

228 ms

settings.css

settings.css

219 ms

captions.css

captions.css

215 ms

lightbox.min.css

lightbox.min.css

251 ms

css

css

27 ms

genericons.css

genericons.css

237 ms

style.css

style.css

281 ms

woocommerce.css

woocommerce.css

336 ms

jquery.js

jquery.js

429 ms

jquery-migrate.min.js

jquery-migrate.min.js

319 ms

jquery.themepunch.plugins.min.js

jquery.themepunch.plugins.min.js

326 ms

jquery.themepunch.revolution.min.js

jquery.themepunch.revolution.min.js

388 ms

jquery.form.min.js

jquery.form.min.js

323 ms

scripts.js

scripts.js

373 ms

wp-lightbox-2.min.js

wp-lightbox-2.min.js

432 ms

comment-reply.min.js

comment-reply.min.js

384 ms

masonry.min.js

masonry.min.js

443 ms

jquery.masonry.min.js

jquery.masonry.min.js

453 ms

functions.js

functions.js

490 ms

add-to-cart.min.js

add-to-cart.min.js

479 ms

jquery.blockUI.min.js

jquery.blockUI.min.js

480 ms

woocommerce.min.js

woocommerce.min.js

498 ms

jquery.cookie.min.js

jquery.cookie.min.js

554 ms

cart-fragments.min.js

cart-fragments.min.js

530 ms

jquery.placeholder.min.js

jquery.placeholder.min.js

574 ms

logo.png

logo.png

275 ms

fb.png

fb.png

275 ms

twt.png

twt.png

273 ms

you_tb.png

you_tb.png

273 ms

cart.png

cart.png

230 ms

niv_bg.png

niv_bg.png

271 ms

home_icon.png

home_icon.png

291 ms

slider-03.jpg

slider-03.jpg

584 ms

slider-04.jpg

slider-04.jpg

537 ms

banner_img.jpg

banner_img.jpg

529 ms

01_img.png

01_img.png

365 ms

02_img.png

02_img.png

473 ms

03_img.png

03_img.png

366 ms

purchasr.jpg

purchasr.jpg

444 ms

Lilcoco.png

Lilcoco.png

483 ms

links_back.png

links_back.png

545 ms

arlrdbd.woff

arlrdbd.woff

546 ms

6htitEuOe80

6htitEuOe80

95 ms

iog4rlBJ0Do

iog4rlBJ0Do

84 ms

www-embed-player-vflfNyN_r.css

www-embed-player-vflfNyN_r.css

75 ms

www-embed-player.js

www-embed-player.js

98 ms

timer.png

timer.png

384 ms

loader.gif

loader.gif

427 ms

shadow2.png

shadow2.png

428 ms

Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js

Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js

32 ms

ad_status.js

ad_status.js

37 ms

zN7GBFwfMP4uA6AR0HCoLQ.ttf

zN7GBFwfMP4uA6AR0HCoLQ.ttf

47 ms

RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf

RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf

48 ms

bullet.png

bullet.png

83 ms

large_left.png

large_left.png

87 ms

large_right.png

large_right.png

99 ms

SEO Factors

ediblehaven.com SEO score

0

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ediblehaven.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), while the claimed language is English. Our system also found out that Ediblehaven.com 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

ediblehaven.com

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