3.7 sec in total
447 ms
2.5 sec
765 ms
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.comWe analyzed Wholeme.com page load time and found that the first response time was 447 ms and then it took 3.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
wholeme.com performance score
name
value
score
weighting
Value3.8 s
28/100
10%
Value11.4 s
0/100
25%
Value9.0 s
14/100
10%
Value520 ms
56/100
30%
Value0.031
100/100
15%
Value9.8 s
28/100
10%
447 ms
21 ms
64 ms
60 ms
379 ms
Our browser made a total of 69 requests to load all elements on the main page. We found that 81% of them (56 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.1 sec) relates to the external source P.typekit.net.
Page size can be reduced by 1.2 MB (9%)
12.3 MB
11.1 MB
In fact, the total size of Wholeme.com main page is 12.3 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. 70% of websites need less resources to load. Images take 11.6 MB which makes up the majority of the site volume.
Potential reduce by 100.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 100.3 kB or 82% of the original size.
Potential reduce by 1.0 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.
Potential reduce by 3.1 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.
Potential reduce by 10.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.
Number of requests can be reduced by 40 (70%)
57
17
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.
wholeme.com
447 ms
fbevents.js
21 ms
layerslider.css
64 ms
style.min.css
60 ms
wc-blocks-vendors-style.css
379 ms
wc-blocks-style.css
49 ms
index.css
47 ms
styles.css
65 ms
settings.css
65 ms
woocommerce.css
68 ms
bundle.css
72 ms
full-styles.css
73 ms
mkhb-grid.css
73 ms
mkhb-render.css
97 ms
theme-options-production.css
98 ms
masterslider.main.css
105 ms
custom.css
110 ms
webfontloader.js
108 ms
greensock.js
15 ms
jquery.min.js
13 ms
jquery-migrate.min.js
11 ms
layerslider.kreaturamedia.jquery.js
12 ms
layerslider.transitions.js
15 ms
jquery.themepunch.tools.min.js
20 ms
jquery.themepunch.revolution.min.js
22 ms
jquery.blockUI.min.js
27 ms
add-to-cart.min.js
25 ms
woocommerce-add-to-cart.js
25 ms
wc-quantity-increment.min.js
38 ms
number-polyfill.min.js
34 ms
js_composer.min.css
36 ms
index.js
35 ms
index.js
36 ms
js.cookie.min.js
41 ms
woocommerce.min.js
48 ms
full-scripts.js
47 ms
mkhb-render.js
48 ms
pixel-cat.min.js
44 ms
video.js
50 ms
js_composer_front.min.js
52 ms
forms.js
57 ms
ajax-forms.min.js
56 ms
aob0cyc.js
134 ms
logov2-01_1497904385__36105.png
62 ms
dummy-transparent-nhpimtqurc8rbu08t0cjhtg2zz1msxr4rawmt9sutc.png
134 ms
dummy-transparent-nhpimtqqlsmgi7x14xhqktl069eb0q8gr2lm5hbs8w.png
135 ms
wm_reversed-e1511232651670-nhq8z0fm2dsswq1gpfsex8g6bpv2kxpp4ljgcyupiw.png
134 ms
font.woff
113 ms
d
19 ms
d
114 ms
d
113 ms
d
115 ms
d
114 ms
d
117 ms
d
116 ms
d
115 ms
d
115 ms
d
141 ms
p.gif
1054 ms
homepage_banner.png
970 ms
wholeme_almondcoconut_front-1024x1024.png
27 ms
wholeme_almondcoconut_back_update_110719_1500-1024x1024.jpg
269 ms
wholeme_lemonberry_front-1024x1024.png
716 ms
wholeme_lemonberry_back_updated_110719_1500-1024x1024.jpg
11 ms
wholeme_cinbanana_front-1024x1024.png
829 ms
wholeme_cinbanana_back_update_110719_1500-1024x1024.jpg
23 ms
wholeme_saltedpeanut_front-1024x1024.png
33 ms
wholeme_saltedpeanut_back_update_110719_1500-683x1024.jpg
39 ms
secondary_banner_edit.png
626 ms
wholeme.com accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
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
Links do not have a discernible name
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.
wholeme.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
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
wholeme.com SEO score
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
EN
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.
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: