7.7 sec in total
1.8 sec
5.3 sec
586 ms
Welcome to whyfoodworks.com homepage info - get ready to check Why Food Works best content right away, or after learning these important things about whyfoodworks.com
My passion is to help you find the foods that fit, show you how to prepare them, and make the food systems in your life that work for you.
Visit whyfoodworks.comWe analyzed Whyfoodworks.com page load time and found that the first response time was 1.8 sec and then it took 5.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
whyfoodworks.com performance score
name
value
score
weighting
Value7.5 s
1/100
10%
Value10.2 s
0/100
25%
Value28.5 s
0/100
10%
Value14,110 ms
0/100
30%
Value0.054
98/100
15%
Value24.9 s
0/100
10%
1773 ms
282 ms
222 ms
219 ms
227 ms
Our browser made a total of 82 requests to load all elements on the main page. We found that 46% of them (38 requests) were addressed to the original Whyfoodworks.com, 32% (26 requests) were made to Fonts.gstatic.com and 4% (3 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (1.8 sec) belongs to the original domain Whyfoodworks.com.
Page size can be reduced by 121.1 kB (14%)
836.4 kB
715.3 kB
In fact, the total size of Whyfoodworks.com main page is 836.4 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 85% 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 429.6 kB which makes up the majority of the site volume.
Potential reduce by 119.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. 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 119.7 kB or 79% of the original size.
Potential reduce by 785 B
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. Why Food Works images are well optimized though.
Potential reduce by 237 B
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 368 B
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. Whyfoodworks.com has all CSS files already compressed.
Number of requests can be reduced by 25 (47%)
53
28
The browser has sent 53 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Why Food Works. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 11 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
whyfoodworks.com
1773 ms
autoptimize_a92b7683b93602d1000fc155b0ec1320.css
282 ms
js
222 ms
css
219 ms
css
227 ms
jquery.min.js
512 ms
css
239 ms
font-awesome.min.css
222 ms
autoptimize_0e9f5b9aa3b92ba0c397e5beca8295f2.js
687 ms
analytics.js
298 ms
wp-emoji-release.min.js
937 ms
pinit_fg_en_rect_red_28.png
883 ms
004-instagram-logo-1.png
878 ms
005-facebook-logo-button-1.png
878 ms
002-pinterest-1.png
1253 ms
003-twitter-logo-button-1.png
1254 ms
001-rss-1.png
1252 ms
Why-Food-Works-Logo_HOZ-e1585137812860.png
1254 ms
carosel-image-1_welcome.jpg
1621 ms
hpAWESOMEbg.jpg
1381 ms
hpBLOGbg.jpg
1255 ms
washingpost-e1587645795290.png
1382 ms
dc-refined-e1587644550511.png
1382 ms
Good-Morning-Washington-1-e1587644346243.png
1397 ms
sheknows-e1587644529887.jpg
1395 ms
photo-1527933053326-89d1746b76b9-400x250.jpg
1619 ms
IMG_7450-400x250.jpg
1614 ms
Why-Food-Works-Sarah-PA170781-scaled-e1587645190768.jpg
1618 ms
Sarah-Waybright-Why-Food-Works_1-e1587644419912.png
1618 ms
Sarah-Waybright-Why-Food-Works_2-e1587644432203.png
1618 ms
Sarah-Waybright-Why-Food-Works_3-e1587644401295.png
1772 ms
Sarah-Waybright-Why-Food-Works_4-e1587644499703.png
1770 ms
Quote-no-line-e1587644372431.png
1771 ms
P4170322-400x250.jpg
1777 ms
IMG_6575-400x250.jpg
1776 ms
placeholder.png
1776 ms
sdk.js
608 ms
widgets.js
644 ms
share-button.js
610 ms
widgets.js
465 ms
platform.js
606 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aX8.ttf
516 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Ew-.ttf
700 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw5aX8.ttf
798 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Ew-.ttf
858 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Hw5aX8.ttf
975 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Ew-.ttf
981 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr6Ew-.ttf
982 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Uw-.ttf
981 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu173w5aX8.ttf
973 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu170w-.ttf
982 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w5aX8.ttf
988 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM70w-.ttf
988 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr73w5aX8.ttf
990 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr70w-.ttf
993 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvC70w-.ttf
991 ms
wlppgwHKFkZgtmSR3NB0oRJX1C1GDNNV.ttf
991 ms
wlppgwHKFkZgtmSR3NB0oRJX1C12Cw.ttf
1001 ms
wlppgwHKFkZgtmSR3NB0oRJXsCxGDNNV.ttf
999 ms
wlppgwHKFkZgtmSR3NB0oRJXsCx2Cw.ttf
993 ms
wlp2gwHKFkZgtmSR3NB0oRJfbwhW.ttf
992 ms
wlp2gwHKFkZgtmSR3NB0oRJvaA.ttf
999 ms
wlprgwHKFkZgtmSR3NB0oRJfajDqDuNS_LA.ttf
1004 ms
wlprgwHKFkZgtmSR3NB0oRJfajDqDtNV.ttf
1002 ms
wlprgwHKFkZgtmSR3NB0oRJfajCOD9NV.ttf
1005 ms
wlpogwHKFkZgtmSR3NB0oRJfajhRK_M.ttf
975 ms
wlpogwHKFkZgtmSR3NB0oRJfaghW.ttf
979 ms
modules.ttf
1080 ms
pinit_main.js
305 ms
whyfoodworks.com
1136 ms
70372242_130557198276783_3641261972602503010_nlow.jpg
775 ms
69418821_1305274832973215_6195623275818049298_nlow.jpg
775 ms
66064521_685078705341878_8122940524083829490_nlow.jpg
775 ms
65776986_962873480719411_2530694161135214937_nlow.jpg
774 ms
65488367_159414631885170_3098557924940081395_nlow.jpg
864 ms
66028184_392477411391475_3878650398198003410_nlow.jpg
864 ms
collect
110 ms
collect
271 ms
sdk.js
222 ms
widget_iframe.7dae38096d06923d683a2a807172322a.html
279 ms
settings
309 ms
autoptimize_541e2ced151704f4ff1844c6de47ec02.css
67 ms
whyfoodworks.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.
whyfoodworks.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
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
whyfoodworks.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
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 Whyfoodworks.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 Whyfoodworks.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.
whyfoodworks.com
Open Graph data is detected on the main page of Why Food Works. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: