12.4 sec in total
554 ms
11.7 sec
123 ms
Welcome to wholelife.com homepage info - get ready to check Wholelife best content right away, or after learning these important things about wholelife.com
The description should optimally be between 150-160 characters.
Visit wholelife.comWe analyzed Wholelife.com page load time and found that the first response time was 554 ms and then it took 11.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
wholelife.com performance score
554 ms
2710 ms
3328 ms
665 ms
1367 ms
Our browser made a total of 62 requests to load all elements on the main page. We found that 58% of them (36 requests) were addressed to the original Wholelife.com, 13% (8 requests) were made to Fonts.gstatic.com and 6% (4 requests) were made to S.ytimg.com. The less responsive or slowest element that took the longest time to load (3.3 sec) belongs to the original domain Wholelife.com.
Page size can be reduced by 1.5 MB (74%)
2.0 MB
503.7 kB
In fact, the total size of Wholelife.com main page is 2.0 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. 55% of websites need less resources to load. Javascripts take 1.0 MB which makes up the majority of the site volume.
Potential reduce by 18.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. This page needs HTML code to be minified as it can gain 9.6 kB, which is 43% 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 18.1 kB or 81% of the original size.
Potential reduce by 27.1 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, Wholelife needs image optimization as it can save up to 27.1 kB or 25% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 732.8 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 732.8 kB or 71% of the original size.
Potential reduce by 691.7 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. Wholelife.com needs all CSS files to be minified and compressed as it can save up to 691.7 kB or 86% of the original size.
Number of requests can be reduced by 40 (78%)
51
11
The browser has sent 51 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Wholelife. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 29 to 1 for JavaScripts and from 13 to 1 for CSS and as a result speed up the page load time.
wholelife.com
554 ms
www.wholelife.com
2710 ms
style.css
3328 ms
modernizr.custom.js
665 ms
jquery.min.js
1367 ms
jquery.easings.min.js
665 ms
bootstrap.min.js
2678 ms
velocity.min.js
922 ms
velocity.ui.min.js
921 ms
notifyMe.js
922 ms
contact-me.js
1158 ms
vegas-youtube-mobile.js
1158 ms
jquery.mb.YTPlayer.js
1612 ms
jquery.mousewheel.js
1378 ms
jquery.mCustomScrollbar.js
3344 ms
classie.js
1610 ms
dialogFx.js
1625 ms
photoswipe.js
2350 ms
photoswipe-ui-default.js
1851 ms
constellation.js
1864 ms
jquery.countdown.js
2102 ms
main.js
2113 ms
login.js
2360 ms
font-awesome.min.css
726 ms
ionicons.min.css
978 ms
bootstrap.min.css
1225 ms
animate.css
1925 ms
photoswipe.css
236 ms
default-skin.css
501 ms
jquery.mCustomScrollbar.css
1698 ms
vegas.css
993 ms
css
131 ms
css
177 ms
logo.png
705 ms
fullscreen.png
302 ms
background-newsletter.jpg
754 ms
cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf
303 ms
DXI1ORHCpsQm3Vp6mXoaTYnF5uFdDttMLvmWuJdhhgs.ttf
448 ms
MTP_ySUJH_bn48VBG8sNSonF5uFdDttMLvmWuJdhhgs.ttf
464 ms
k3k702ZOKiLJc3WVjuplzInF5uFdDttMLvmWuJdhhgs.ttf
541 ms
IQHow_FEYlDC4Gzy_m8fcvEr6Hm6RMS0v1dtXsGir4g.ttf
496 ms
zhcz-_WihjSQC0oHJ9TCYC3USBnSvpkopQaUR-2r7iU.ttf
496 ms
fontawesome-webfont.woff
1467 ms
ionicons.ttf
2427 ms
player_api
406 ms
160105738
406 ms
www-widgetapi.js
219 ms
player.js
470 ms
player.css
352 ms
ga.js
297 ms
vuid.min.js
350 ms
xPdQk1JICIc
1097 ms
__utm.gif
63 ms
proxy.html
88 ms
xPdQk1JICIc
113 ms
www-embed-player-vfl-z2BtK.css
102 ms
www-embed-player.js
215 ms
base.js
405 ms
Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js
62 ms
ad_status.js
61 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
58 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
100 ms
wholelife.com SEO score
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Wholelife.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 Wholelife.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.
wholelife.com
Open Graph description is not detected on the main page of Wholelife. 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: