12 sec in total
2.2 sec
9 sec
871 ms
Visit whatthefatbook.com now to see the best up-to-date Whatthefatbook content and also check out these interesting facts you probably never knew about whatthefatbook.com
Visit whatthefatbook.comWe analyzed Whatthefatbook.com page load time and found that the first response time was 2.2 sec and then it took 9.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.
whatthefatbook.com performance score
name
value
score
weighting
Value22.0 s
0/100
10%
Value31.3 s
0/100
25%
Value53.3 s
0/100
10%
Value18,810 ms
0/100
30%
Value0.029
100/100
15%
Value69.2 s
0/100
10%
2190 ms
367 ms
385 ms
402 ms
386 ms
Our browser made a total of 93 requests to load all elements on the main page. We found that 95% of them (88 requests) were addressed to the original Whatthefatbook.com, 2% (2 requests) were made to Google-analytics.com and 1% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (3.9 sec) belongs to the original domain Whatthefatbook.com.
Page size can be reduced by 1.8 MB (44%)
4.1 MB
2.3 MB
In fact, the total size of Whatthefatbook.com main page is 4.1 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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 1.9 MB which makes up the majority of the site volume.
Potential reduce by 76.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 76.3 kB or 79% of the original size.
Potential reduce by 32.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. Whatthefatbook images are well optimized though.
Potential reduce by 995.4 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 995.4 kB or 77% of the original size.
Potential reduce by 693.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. Whatthefatbook.com needs all CSS files to be minified and compressed as it can save up to 693.3 kB or 87% of the original size.
Number of requests can be reduced by 52 (57%)
91
39
The browser has sent 91 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Whatthefatbook. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 38 to 1 for JavaScripts and from 16 to 1 for CSS and as a result speed up the page load time.
whatthefatbook.com
2190 ms
wp-emoji-release.min.js
367 ms
styles.css
385 ms
woocommerce-layout.css
402 ms
woocommerce.css
386 ms
css
27 ms
style.css
395 ms
mediaelementplayer.min.css
401 ms
wp-mediaelement.css
555 ms
rgs.css
573 ms
font-awesome.min.css
577 ms
style.css
589 ms
responsive.css
779 ms
woocommerce.css
590 ms
ascend.css
745 ms
js_composer.css
957 ms
jquery.js
1159 ms
jquery-migrate.min.js
784 ms
tracking.js
46 ms
custom.js
780 ms
modernizr.js
931 ms
ProgressCircle.js
967 ms
jquery.vc_chart.js
969 ms
core.min.js
809 ms
widget.min.js
962 ms
position.min.js
981 ms
menu.min.js
998 ms
autocomplete.min.js
1002 ms
wpss-search-suggest.js
1001 ms
jquery.form.min.js
1154 ms
scripts.js
1175 ms
frontend.js
1182 ms
add-to-cart.min.js
1190 ms
jquery.blockUI.min.js
1195 ms
woocommerce.min.js
1194 ms
jquery.cookie.min.js
1344 ms
cart-fragments.min.js
1366 ms
jquery.uniform.min.js
1375 ms
custom.js
1383 ms
idle-timer.min.js
1200 ms
superfish.js
1182 ms
respond.js
1326 ms
sticky.js
1333 ms
prettyPhoto.js
1342 ms
isotope.min.js
1545 ms
init.js
2032 ms
infinitescroll.js
1395 ms
mediaelement-and-player.min.js
1517 ms
style.css
1718 ms
wp-mediaelement.js
1342 ms
nectar-slider.js
1838 ms
comment-reply.min.js
1356 ms
js_composer_front.js
1375 ms
analytics.js
107 ms
logo.png
951 ms
logo@2x.png
953 ms
img_home_bookduo.png
1057 ms
img_pete_evans.png
1416 ms
What-the-Fat-09.11.2015-129-500x500.jpg
956 ms
willpower-500x412.jpg
954 ms
will-power-300x235.jpg
957 ms
Green-Smoothie1-500x500.jpg
954 ms
Green-Smoothie1.jpg
958 ms
bulletproof-500x500.jpg
1055 ms
bulletproof-300x200.jpg
958 ms
cream-150x150.jpg
1054 ms
nuts-300x150.jpg
1093 ms
coconut-oil-300x200.jpg
1181 ms
img_grant_triathlon.jpg
1934 ms
newsletter_signup.png
1181 ms
OpenSans-Regular-webfont.woff
1062 ms
klinicslab-bolditalic-webfont.woff
1178 ms
klinicslab-book-webfont.woff
1212 ms
kievitpro-book.woff
1433 ms
klinicslab-bold-webfont.woff
1290 ms
klinicslab-bookitalic-webfont.woff
1370 ms
OpenSans-Semibold-webfont.woff
1391 ms
OpenSansBold-webfont.woff
1631 ms
fontawesome-webfont.svg
2220 ms
kievitpro-bold.woff
1755 ms
icomoon.woff
1579 ms
collect
780 ms
admin-ajax.php
3927 ms
diagonal_line.png
800 ms
sportsperfomance_dark.jpg
1339 ms
grid.png
992 ms
img_home_bg.jpg
1201 ms
bg_4.jpg
2099 ms
bg_3.jpg
1946 ms
collect
132 ms
sketchblock-bold-webfont.woff
1974 ms
fontawesome-webfont.woff
202 ms
woocommerce-smallscreen.css
194 ms
whatthefatbook.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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
Image elements do not have [alt] attributes
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.
whatthefatbook.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
Missing source maps for large first-party JavaScript
whatthefatbook.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
Image elements do not have [alt] attributes
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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 Whatthefatbook.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 Whatthefatbook.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.
whatthefatbook.com
Open Graph description is not detected on the main page of Whatthefatbook. 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: