Tools & Wizards About Us
wholeme.com screenshot

Report Summary

  • 46

    Performance

    Renders faster than
    65% of other websites

  • 85

    Accessibility

    Visual factors better than
    that of 58% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 97

    SEO

    Google-friendlier than
    91% of websites

wholeme.com

WholeMe – A whole new way to snack. Delicious. Nutritious. Foods.

Page Load Speed

3.2 sec in total

First Response

76 ms

Resources Loaded

2.6 sec

Page Rendered

554 ms

wholeme.com screenshot

About Website

Visit wholeme.com now to see the best up-to-date Whole Me content and also check out these interesting facts you probably never knew about wholeme.com

Grain-free, gluten-free, Non-GMO verified ingredients you can trust. Made with healthy fats for sustained energy and real sweeteners for full-bodied flavor.

Visit wholeme.com

Key Findings

We analyzed Wholeme.com page load time and found that the first response time was 76 ms and then it took 3.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.

Performance Metrics

wholeme.com performance score

46

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.7 s

29/100

10%

LCP (Largest Contentful Paint)

Value11.0 s

0/100

25%

SI (Speed Index)

Value8.6 s

17/100

10%

TBT (Total Blocking Time)

Value320 ms

77/100

30%

CLS (Cumulative Layout Shift)

Value0.031

100/100

15%

TTI (Time to Interactive)

Value9.3 s

31/100

10%

Network Requests Diagram

wholeme.com

76 ms

wholeme.com

348 ms

fbevents.js

17 ms

layerslider.css

38 ms

style.min.css

41 ms

Our browser made a total of 70 requests to load all elements on the main page. We found that 81% of them (57 requests) were addressed to the original Wholeme.com, 16% (11 requests) were made to Use.typekit.net and 1% (1 request) were made to Connect.facebook.net. The less responsive or slowest element that took the longest time to load (1 sec) belongs to the original domain Wholeme.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.1 MB (9%)

Content Size

12.4 MB

After Optimization

11.2 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Wholeme.com main page is 12.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. Only a small number of websites need less resources to load. Images take 11.7 MB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 99.8 kB

  • Original 121.2 kB
  • After minification 116.8 kB
  • After compression 21.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. 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 99.8 kB or 82% of the original size.

Image Optimization

-9%

Potential reduce by 1.0 MB

  • Original 11.7 MB
  • After minification 10.7 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. Whole Me images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 2.1 kB

  • Original 291.3 kB
  • After minification 291.3 kB
  • After compression 289.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. This website has mostly compressed JavaScripts.

CSS Optimization

-2%

Potential reduce by 3.8 kB

  • Original 210.0 kB
  • After minification 209.8 kB
  • After compression 206.2 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. Wholeme.com has all CSS files already compressed.

Requests Breakdown

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

Requests Now

57

After Optimization

17

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

wholeme.com

wholeme.com

76 ms

wholeme.com

wholeme.com

348 ms

fbevents.js

fbevents.js

17 ms

layerslider.css

layerslider.css

38 ms

style.min.css

style.min.css

41 ms

wc-blocks-vendors-style.css

wc-blocks-vendors-style.css

40 ms

wc-blocks-style.css

wc-blocks-style.css

57 ms

index.css

index.css

39 ms

styles.css

styles.css

46 ms

settings.css

settings.css

348 ms

woocommerce.css

woocommerce.css

63 ms

bundle.css

bundle.css

69 ms

full-styles.css

full-styles.css

514 ms

mkhb-grid.css

mkhb-grid.css

66 ms

mkhb-render.css

mkhb-render.css

66 ms

theme-options-production.css

theme-options-production.css

73 ms

masterslider.main.css

masterslider.main.css

390 ms

custom.css

custom.css

87 ms

webfontloader.js

webfontloader.js

83 ms

greensock.js

greensock.js

43 ms

jquery.min.js

jquery.min.js

48 ms

jquery-migrate.min.js

jquery-migrate.min.js

350 ms

layerslider.kreaturamedia.jquery.js

layerslider.kreaturamedia.jquery.js

70 ms

layerslider.transitions.js

layerslider.transitions.js

61 ms

jquery.themepunch.tools.min.js

jquery.themepunch.tools.min.js

79 ms

jquery.themepunch.revolution.min.js

jquery.themepunch.revolution.min.js

88 ms

jquery.blockUI.min.js

jquery.blockUI.min.js

95 ms

add-to-cart.min.js

add-to-cart.min.js

103 ms

woocommerce-add-to-cart.js

woocommerce-add-to-cart.js

107 ms

wc-quantity-increment.min.js

wc-quantity-increment.min.js

173 ms

number-polyfill.min.js

number-polyfill.min.js

122 ms

js_composer.min.css

js_composer.min.css

152 ms

index.js

index.js

167 ms

index.js

index.js

586 ms

js.cookie.min.js

js.cookie.min.js

192 ms

woocommerce.min.js

woocommerce.min.js

206 ms

full-scripts.js

full-scripts.js

231 ms

mkhb-render.js

mkhb-render.js

244 ms

pixel-cat.min.js

pixel-cat.min.js

258 ms

video.js

video.js

273 ms

js_composer_front.min.js

js_composer_front.min.js

288 ms

forms.js

forms.js

311 ms

ajax-forms.min.js

ajax-forms.min.js

310 ms

aob0cyc.js

aob0cyc.js

166 ms

logov2-01_1497904385__36105.png

logov2-01_1497904385__36105.png

36 ms

dummy-transparent-nhpimtqurc8rbu08t0cjhtg2zz1msxr4rawmt9sutc.png

dummy-transparent-nhpimtqurc8rbu08t0cjhtg2zz1msxr4rawmt9sutc.png

573 ms

dummy-transparent-nhpimtqqlsmgi7x14xhqktl069eb0q8gr2lm5hbs8w.png

dummy-transparent-nhpimtqqlsmgi7x14xhqktl069eb0q8gr2lm5hbs8w.png

35 ms

wm_reversed-e1511232651670-nhq8z0fm2dsswq1gpfsex8g6bpv2kxpp4ljgcyupiw.png

wm_reversed-e1511232651670-nhq8z0fm2dsswq1gpfsex8g6bpv2kxpp4ljgcyupiw.png

573 ms

font.woff

font.woff

26 ms

d

d

265 ms

d

d

277 ms

d

d

333 ms

d

d

331 ms

d

d

333 ms

d

d

406 ms

d

d

277 ms

d

d

277 ms

d

d

278 ms

d

d

278 ms

homepage_banner.png

homepage_banner.png

1037 ms

wholeme_almondcoconut_front-1024x1024.png

wholeme_almondcoconut_front-1024x1024.png

76 ms

wholeme_almondcoconut_back_update_110719_1500-1024x1024.jpg

wholeme_almondcoconut_back_update_110719_1500-1024x1024.jpg

72 ms

wholeme_lemonberry_front-1024x1024.png

wholeme_lemonberry_front-1024x1024.png

75 ms

wholeme_lemonberry_back_updated_110719_1500-1024x1024.jpg

wholeme_lemonberry_back_updated_110719_1500-1024x1024.jpg

71 ms

wholeme_cinbanana_front-1024x1024.png

wholeme_cinbanana_front-1024x1024.png

73 ms

wholeme_cinbanana_back_update_110719_1500-1024x1024.jpg

wholeme_cinbanana_back_update_110719_1500-1024x1024.jpg

77 ms

wholeme_saltedpeanut_front-1024x1024.png

wholeme_saltedpeanut_front-1024x1024.png

78 ms

wholeme_saltedpeanut_back_update_110719_1500-683x1024.jpg

wholeme_saltedpeanut_back_update_110719_1500-683x1024.jpg

77 ms

secondary_banner_edit.png

secondary_banner_edit.png

527 ms

p.gif

p.gif

21 ms

Accessibility Review

wholeme.com accessibility score

85

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.

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

Links do not have a discernible name

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

wholeme.com best practices score

83

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

wholeme.com SEO score

97

Search Engine Optimization Advices

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

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Wholeme.com 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 Wholeme.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

wholeme.com

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