Tools & Wizards About Us
whyfoodworks.com screenshot

Report Summary

  • 53

    Performance

    Renders faster than
    70% of other websites

  • 78

    Accessibility

    Visual factors better than
    that of 45% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

whyfoodworks.com

WhyFoodWorks | know better, eat better | Washington D.C.

Page Load Speed

4.6 sec in total

First Response

1.4 sec

Resources Loaded

2.8 sec

Page Rendered

499 ms

whyfoodworks.com screenshot

About Website

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.com

Key Findings

We analyzed Whyfoodworks.com page load time and found that the first response time was 1.4 sec and then it took 3.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.

Performance Metrics

whyfoodworks.com performance score

53

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.7 s

28/100

10%

LCP (Largest Contentful Paint)

Value8.1 s

2/100

25%

SI (Speed Index)

Value5.6 s

53/100

10%

TBT (Total Blocking Time)

Value250 ms

84/100

30%

CLS (Cumulative Layout Shift)

Value0.026

100/100

15%

TTI (Time to Interactive)

Value8.3 s

39/100

10%

Network Requests Diagram

whyfoodworks.com

1351 ms

autoptimize_d5bd15eaa27a27bc3611fb066e26bd1b.css

264 ms

css

44 ms

css

63 ms

jquery.min.js

205 ms

Our browser made a total of 62 requests to load all elements on the main page. We found that 48% of them (30 requests) were addressed to the original Whyfoodworks.com, 42% (26 requests) were made to Fonts.gstatic.com and 5% (3 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (1.4 sec) belongs to the original domain Whyfoodworks.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 43.8 kB (5%)

Content Size

890.2 kB

After Optimization

846.5 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Whyfoodworks.com main page is 890.2 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. 70% of websites need less resources to load. Javascripts take 336.1 kB which makes up the majority of the site volume.

HTML Optimization

-75%

Potential reduce by 41.3 kB

  • Original 55.3 kB
  • After minification 55.3 kB
  • After compression 14.0 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 41.3 kB or 75% of the original size.

Image Optimization

-1%

Potential reduce by 1.7 kB

  • Original 329.3 kB
  • After minification 327.6 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. Why Food Works images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 12 B

  • Original 336.1 kB
  • After minification 336.1 kB
  • After compression 336.1 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. This website has mostly compressed JavaScripts.

CSS Optimization

-0%

Potential reduce by 723 B

  • Original 169.5 kB
  • After minification 169.5 kB
  • After compression 168.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. Whyfoodworks.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 13 (38%)

Requests Now

34

After Optimization

21

  • Images
  • JavaScript
  • CSS

The browser has sent 34 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 6 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

whyfoodworks.com

whyfoodworks.com

1351 ms

autoptimize_d5bd15eaa27a27bc3611fb066e26bd1b.css

autoptimize_d5bd15eaa27a27bc3611fb066e26bd1b.css

264 ms

css

css

44 ms

css

css

63 ms

jquery.min.js

jquery.min.js

205 ms

css

css

65 ms

font-awesome.min.css

font-awesome.min.css

51 ms

js

js

72 ms

autoptimize_9398c9346cc260c8dbcf26b8fea196d3.js

autoptimize_9398c9346cc260c8dbcf26b8fea196d3.js

479 ms

pinit_fg_en_rect_red_28.png

pinit_fg_en_rect_red_28.png

197 ms

sbi-sprite.png

sbi-sprite.png

117 ms

004-instagram-logo-1.png

004-instagram-logo-1.png

116 ms

005-facebook-logo-button-1.png

005-facebook-logo-button-1.png

116 ms

002-pinterest-1.png

002-pinterest-1.png

146 ms

003-twitter-logo-button-1.png

003-twitter-logo-button-1.png

146 ms

001-rss-1.png

001-rss-1.png

146 ms

Why-Food-Works-Logo_HOZ-e1585137812860.png

Why-Food-Works-Logo_HOZ-e1585137812860.png

184 ms

carosel-image-1_welcome.jpg

carosel-image-1_welcome.jpg

399 ms

hpAWESOMEbg.jpg

hpAWESOMEbg.jpg

215 ms

hpBLOGbg.jpg

hpBLOGbg.jpg

216 ms

washingpost-e1587645795290.png

washingpost-e1587645795290.png

215 ms

dc-refined-e1587644550511.png

dc-refined-e1587644550511.png

217 ms

Good-Morning-Washington-1-e1587644346243.png

Good-Morning-Washington-1-e1587644346243.png

258 ms

sheknows-e1587644529887.jpg

sheknows-e1587644529887.jpg

282 ms

photo-1527933053326-89d1746b76b9-400x250.jpg

photo-1527933053326-89d1746b76b9-400x250.jpg

304 ms

IMG_7450-400x250.jpg

IMG_7450-400x250.jpg

282 ms

Why-Food-Works-Sarah-PA170781-scaled-e1587645190768.jpg

Why-Food-Works-Sarah-PA170781-scaled-e1587645190768.jpg

283 ms

Sarah-Waybright-Why-Food-Works_1-e1587644419912.png

Sarah-Waybright-Why-Food-Works_1-e1587644419912.png

291 ms

Sarah-Waybright-Why-Food-Works_2-e1587644432203.png

Sarah-Waybright-Why-Food-Works_2-e1587644432203.png

308 ms

Sarah-Waybright-Why-Food-Works_3-e1587644401295.png

Sarah-Waybright-Why-Food-Works_3-e1587644401295.png

307 ms

Sarah-Waybright-Why-Food-Works_4-e1587644499703.png

Sarah-Waybright-Why-Food-Works_4-e1587644499703.png

310 ms

Quote-no-line-e1587644372431.png

Quote-no-line-e1587644372431.png

342 ms

P4170322-400x250.jpg

P4170322-400x250.jpg

357 ms

IMG_6575-400x250.jpg

IMG_6575-400x250.jpg

361 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aX8.ttf

47 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Ew-.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Ew-.ttf

67 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw5aX8.ttf

73 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Ew-.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Ew-.ttf

89 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Hw5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Hw5aX8.ttf

90 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Ew-.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Ew-.ttf

90 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr6Ew-.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr6Ew-.ttf

74 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Uw-.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Uw-.ttf

89 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu173w5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu173w5aX8.ttf

89 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu170w-.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu170w-.ttf

93 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w5aX8.ttf

94 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM70w-.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM70w-.ttf

93 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr73w5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr73w5aX8.ttf

94 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr70w-.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr70w-.ttf

93 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvC70w-.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvC70w-.ttf

95 ms

wlppgwHKFkZgtmSR3NB0oRJX1C1GDNNV.ttf

wlppgwHKFkZgtmSR3NB0oRJX1C1GDNNV.ttf

135 ms

wlppgwHKFkZgtmSR3NB0oRJX1C12Cw.ttf

wlppgwHKFkZgtmSR3NB0oRJX1C12Cw.ttf

135 ms

wlppgwHKFkZgtmSR3NB0oRJXsCxGDNNV.ttf

wlppgwHKFkZgtmSR3NB0oRJXsCxGDNNV.ttf

98 ms

wlppgwHKFkZgtmSR3NB0oRJXsCx2Cw.ttf

wlppgwHKFkZgtmSR3NB0oRJXsCx2Cw.ttf

135 ms

wlp2gwHKFkZgtmSR3NB0oRJfbwhW.ttf

wlp2gwHKFkZgtmSR3NB0oRJfbwhW.ttf

135 ms

wlp2gwHKFkZgtmSR3NB0oRJvaA.ttf

wlp2gwHKFkZgtmSR3NB0oRJvaA.ttf

134 ms

wlprgwHKFkZgtmSR3NB0oRJfajDqDuNS_LA.ttf

wlprgwHKFkZgtmSR3NB0oRJfajDqDuNS_LA.ttf

136 ms

wlprgwHKFkZgtmSR3NB0oRJfajDqDtNV.ttf

wlprgwHKFkZgtmSR3NB0oRJfajDqDtNV.ttf

137 ms

wlprgwHKFkZgtmSR3NB0oRJfajCOD9NV.ttf

wlprgwHKFkZgtmSR3NB0oRJfajCOD9NV.ttf

136 ms

wlpogwHKFkZgtmSR3NB0oRJfajhRK_M.ttf

wlpogwHKFkZgtmSR3NB0oRJfajhRK_M.ttf

135 ms

wlpogwHKFkZgtmSR3NB0oRJfaghW.ttf

wlpogwHKFkZgtmSR3NB0oRJfaghW.ttf

137 ms

modules.ttf

modules.ttf

293 ms

autoptimize_645e25746732f92ab8912b8a07744c57.css

autoptimize_645e25746732f92ab8912b8a07744c57.css

55 ms

Accessibility Review

whyfoodworks.com accessibility score

78

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

whyfoodworks.com best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

whyfoodworks.com SEO score

93

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

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

High

Document uses legible font sizes

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    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.

Social Sharing Optimization

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: