4.9 sec in total
959 ms
3.3 sec
584 ms
Welcome to wholeyum.com homepage info - get ready to check Whole Yum best content for United States right away, or after learning these important things about wholeyum.com
WholeYum is a health focused site with keto, pescatarian, vegetarian, and vegan recipes, nutrition plans, and lifestyle advice to help you live your best life.
Visit wholeyum.comWe analyzed Wholeyum.com page load time and found that the first response time was 959 ms and then it took 3.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
wholeyum.com performance score
name
value
score
weighting
Value12.1 s
0/100
10%
Value25.8 s
0/100
25%
Value26.8 s
0/100
10%
Value4,300 ms
1/100
30%
Value0.011
100/100
15%
Value24.1 s
0/100
10%
959 ms
122 ms
133 ms
134 ms
26 ms
Our browser made a total of 168 requests to load all elements on the main page. We found that 37% of them (62 requests) were addressed to the original Wholeyum.com, 5% (9 requests) were made to Dsum.casalemedia.com and 4% (7 requests) were made to Tags.bluekai.com. The less responsive or slowest element that took the longest time to load (959 ms) belongs to the original domain Wholeyum.com.
Page size can be reduced by 1.3 MB (49%)
2.6 MB
1.3 MB
In fact, the total size of Wholeyum.com main page is 2.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. 70% of websites need less resources to load. Javascripts take 1.2 MB which makes up the majority of the site volume.
Potential reduce by 127.7 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 27.1 kB, which is 18% 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 127.7 kB or 84% of the original size.
Potential reduce by 169.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, Whole Yum needs image optimization as it can save up to 169.7 kB or 16% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 849.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 849.6 kB or 68% of the original size.
Potential reduce by 140.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. Wholeyum.com needs all CSS files to be minified and compressed as it can save up to 140.3 kB or 84% of the original size.
Number of requests can be reduced by 114 (78%)
146
32
The browser has sent 146 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Whole Yum. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 56 to 1 for JavaScripts and from 19 to 1 for CSS and as a result speed up the page load time.
www.wholeyum.com
959 ms
style.css
122 ms
screen.css
133 ms
fonts.css
134 ms
css
26 ms
css
39 ms
css
46 ms
css
48 ms
font-awesome.css
21 ms
owl.carousel.css
130 ms
owl.theme.css
132 ms
buttons.js
20 ms
wpfp.css
140 ms
theme-my-login.css
176 ms
css-front.css
178 ms
styles.css
189 ms
se-styles.css
191 ms
frontend-forms.css
188 ms
jquery-ui-1.9.1.custom.css
191 ms
wp-paginate.css
235 ms
colorbox.css
236 ms
jquery.js
435 ms
jquery-migrate.min.js
245 ms
js
31 ms
frontend-form.js
312 ms
jquery.ui.core.min.js
250 ms
jquery.ui.datepicker.min.js
355 ms
plupload.full.min.js
538 ms
handlers.min.js
304 ms
jquery-ui-timepicker-addon.js
505 ms
upload.js
366 ms
jquery.colorbox.1.3.32.js
470 ms
wpfp.js
416 ms
zlrecipe_print.js
427 ms
cdsad.js
61 ms
jquery.min.js
12 ms
superfish.js
442 ms
hoverIntent.js
452 ms
smooth-scroll.js
455 ms
placeholder-show.js
463 ms
jquery-1.9.1.min.js
640 ms
owl.carousel.js
641 ms
jquery.form.min.js
544 ms
scripts.js
545 ms
jquery.sonar.min.js
545 ms
cb.js
224 ms
lazy-load.js
563 ms
bounce
9 ms
jquery.ui.widget.min.js
512 ms
jquery.ui.position.min.js
567 ms
jquery.ui.menu.min.js
566 ms
jquery.ui.autocomplete.min.js
566 ms
ga.js
10 ms
suggest.min.js
589 ms
jquery.ui.mouse.min.js
589 ms
__utm.gif
12 ms
jquery.ui.slider.min.js
552 ms
ggv2.js
33 ms
gpt.js
34 ms
logo.png
349 ms
search.png
174 ms
1x1.trans.gif
180 ms
pubads_impl_81.js
22 ms
ODelI1aHBYDBqgeIAH2zlNzbP97U9sKh0jjxbPbfOKg.ttf
11 ms
toadOcfmlt9b38dHJxOBGMw1o1eFRj7wYC6JbISqOjY.ttf
12 ms
toadOcfmlt9b38dHJxOBGNNE-IuDiR70wI4zXaKqWCM.ttf
22 ms
toadOcfmlt9b38dHJxOBGLsbIrGiHa6JIepkyt5c0A0.ttf
22 ms
Zd2E9abXLFGSr9G3YK2MsDR-eWpsHSw83BRsAQElGgc.ttf
22 ms
b9QBgL0iMZfDSpmcXcE8nL3QFSXBldIn45k5A7iXhnc.ttf
20 ms
b9QBgL0iMZfDSpmcXcE8nDokq8qT6AIiNJ07Vf_NrVA.ttf
21 ms
fontawesome-webfont.woff
6 ms
ad
118 ms
ads
309 ms
container.html
37 ms
B5963203.2;sz=300x250;ord=33527243
27 ms
5447
20 ms
rand=28176
97 ms
400966.gif
5 ms
modernizr_2.8.3_ec185bb44fe5e6bf7455d6e8ef37ed0e_no-classes.js
32 ms
dfa7banner_flash_html_inpage_rendering_lib_200_104.js
31 ms
lidar.js
14 ms
ad
59 ms
usermatch
35 ms
usermatch
19 ms
ad
133 ms
casale
9 ms
pixel
27 ms
cm
15 ms
cse
217 ms
ad
37 ms
casale
8 ms
rum
11 ms
crum
11 ms
crum
13 ms
3 ms
rum
12 ms
crum
8 ms
crum
11 ms
ttj
10 ms
osd.js
9 ms
B5963203.2;sz=300x250;ord=1690752415
36 ms
sync
108 ms
usermatch
27 ms
ttj
13 ms
ad
54 ms
gr
15 ms
VtUuScAoJEkAAGyxfUMAAADc%26254
72 ms
ca
72 ms
casale
16 ms
ecs
50 ms
pixel.htm
70 ms
cse
172 ms
ad
70 ms
pixel
60 ms
crum
30 ms
ecc
123 ms
DSC_4378-300x250.jpg
163 ms
Chicken-Tomato-And-Potato-Skillet-1039-300x250.jpg
155 ms
Crockpot-Beef-Bourguignon-Recipe-300x250.jpg
150 ms
Slow-Cooked-French-Pot-Roast-300x250.jpg
237 ms
Almond-Lace-Cookies-550px-300x250.jpg
153 ms
IMG_0494-2-300x250.jpg
188 ms
cCoffee010-300x250.jpg
194 ms
romano-egg-muffins-300x250.png
399 ms
primeRib05-300x250.jpg
289 ms
Irish-colcannon-2-300x250.jpg
293 ms
chexMix_05-300x250.jpg
247 ms
ddc.htm
110 ms
m
146 ms
analytics.js
104 ms
get
136 ms
getAllAppDefault.esi
73 ms
crum
47 ms
IMG_1026-708x1024.jpg
417 ms
IMG_71801-1024x892.jpg
608 ms
IMG_4273-682x1024.jpg
419 ms
rum
37 ms
collect
33 ms
crum
17 ms
match
498 ms
p-00TsOkvHvnsZU.gif
27 ms
getSegment.php
237 ms
checkOAuth.esi
32 ms
p2
6 ms
41 ms
net.php
19 ms
generic
40 ms
xrefid.xgi
7 ms
t.dhj
38 ms
pixel.gif
71 ms
pixel.gif
101 ms
bk-static.js
101 ms
pixel.gif
84 ms
t.dhj
27 ms
s-3271.xgi
41 ms
hbpix
44 ms
cm
40 ms
xrefid.xgi
8 ms
pixel
19 ms
16 ms
52154.gif
6 ms
9 ms
4651
44 ms
2981
21 ms
3085
18 ms
4448
17 ms
4470
29 ms
1407
69 ms
wholeyum.com accessibility score
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
Buttons do not have an accessible name
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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.
wholeyum.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
wholeyum.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
robots.txt is not valid
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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Wholeyum.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 Wholeyum.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.
wholeyum.com
Open Graph description is not detected on the main page of Whole Yum. 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: