3.6 sec in total
1.2 sec
2.1 sec
236 ms
Click here to check amazing Wholefoodscooking content. Otherwise, check out these important facts you probably never knew about wholefoodscooking.ca
Rooted Nutrition Vancouver
Visit wholefoodscooking.caWe analyzed Wholefoodscooking.ca page load time and found that the first response time was 1.2 sec and then it took 2.4 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.
wholefoodscooking.ca performance score
1226 ms
16 ms
136 ms
12 ms
155 ms
Our browser made a total of 99 requests to load all elements on the main page. We found that 62% of them (61 requests) were addressed to the original Wholefoodscooking.ca, 4% (4 requests) were made to A.collective-media.net and 4% (4 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain Wholefoodscooking.ca.
Page size can be reduced by 1.1 MB (57%)
1.9 MB
819.0 kB
In fact, the total size of Wholefoodscooking.ca main page is 1.9 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. 60% of websites need less resources to load. Javascripts take 1.2 MB which makes up the majority of the site volume.
Potential reduce by 65.6 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 65.6 kB or 73% of the original size.
Potential reduce by 15.4 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. Wholefoodscooking images are well optimized though.
Potential reduce by 845.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 845.3 kB or 69% of the original size.
Potential reduce by 173.8 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. Wholefoodscooking.ca needs all CSS files to be minified and compressed as it can save up to 173.8 kB or 87% of the original size.
Number of requests can be reduced by 69 (73%)
95
26
The browser has sent 95 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Wholefoodscooking. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 30 to 1 for JavaScripts and from 15 to 1 for CSS and as a result speed up the page load time.
wholefoodscooking.ca
1226 ms
ga.js
16 ms
wp-emoji-release.min.js
136 ms
__utm.gif
12 ms
styles.css
155 ms
social_widget.css
138 ms
checkbox.min.css
139 ms
form.min.css
140 ms
jquery-ui-1.8.16.custom.css
168 ms
custom.css
204 ms
wpgmza_style.css
218 ms
jquery.js
325 ms
jquery-migrate.min.js
219 ms
mailchimp-ajax.js
237 ms
mailchimp-ajax.css
268 ms
buttons.js
14 ms
scd.css
283 ms
jscolor.js
285 ms
shortcodes.css
306 ms
shortcode.js
356 ms
jquery-ui-1.7.2.min.js
362 ms
cufon-yui.js
361 ms
LiberationSans.font.js
557 ms
jquery.cycle.all.min.js
390 ms
superfish.min.js
399 ms
supersubs.min.js
414 ms
jquery.overlabel.min.js
415 ms
jquery.prettyPhoto.js
449 ms
prettyPhoto.css
452 ms
load.js
458 ms
cufon.css
478 ms
style.css
479 ms
fancy.css
513 ms
__utm.gif
21 ms
addthis_widget.js
15 ms
output.css
183 ms
jquery.fullcalendar.min.js
273 ms
jquery.simplemodal.1.4.3.min.js
196 ms
jquery.mousewheel.min.js
197 ms
jquery.jgrowl.min.js
272 ms
core.min.js
348 ms
datepicker.min.js
352 ms
jquery.init_show_calendar.js
279 ms
e-201611.js
12 ms
e-201611.js
24 ms
backgroundwhite.jpg
128 ms
shadow.png
127 ms
rss.gif
128 ms
RootedNutrition250.png
247 ms
button.png
148 ms
menu-bg.png
148 ms
s_input-small.png
149 ms
s_submit-small.png
150 ms
scroll-bg.png
244 ms
slider-cont-bg.png
323 ms
more-learn.png
330 ms
thumb.php
481 ms
thumb.php
565 ms
thumb.php
565 ms
thumb.php
682 ms
zoom-play.png
387 ms
thumb.php
494 ms
thumb.php
594 ms
thumb.php
623 ms
thumb.php
630 ms
rss_16.png
632 ms
facebook_16.png
633 ms
twitter_16.png
661 ms
__utm.gif
19 ms
statistics.asp
211 ms
track.js
214 ms
g.gif
18 ms
300lo.json
52 ms
getAllAppDefault.esi
130 ms
statistics.asp
104 ms
sh.8e5f85691f9aaa082472a194.html
36 ms
push
208 ms
track-visibility.aspx
158 ms
datapair
39 ms
5 ms
datapair
39 ms
datapair
40 ms
datapair
41 ms
pixel
25 ms
getSegment.php
168 ms
checkOAuth.esi
50 ms
pixel
15 ms
pixel
17 ms
t.dhj
9 ms
t.dhj
13 ms
cm
18 ms
x35248
123 ms
hbpix
30 ms
20 ms
s-3271.xgi
7 ms
18 ms
xrefid.xgi
6 ms
pixel
15 ms
2981
24 ms
wholefoodscooking.ca SEO score
N/A
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Wholefoodscooking.ca 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 Wholefoodscooking.ca 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.
wholefoodscooking.ca
Open Graph description is not detected on the main page of Wholefoodscooking. 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: