Tools & Wizards About Us
whatwouldcathyeat.com screenshot

Report Summary

  • 24

    Performance

    Renders faster than
    43% of other websites

  • 81

    Accessibility

    Visual factors better than
    that of 51% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 84

    SEO

    Google-friendlier than
    52% of websites

whatwouldcathyeat.com

What Would Cathy Eat? | Heart-Healthy Food With Attitude

Page Load Speed

22.9 sec in total

First Response

189 ms

Resources Loaded

21.7 sec

Page Rendered

1 sec

whatwouldcathyeat.com screenshot

About Website

Visit whatwouldcathyeat.com now to see the best up-to-date What Would Cathy Eat content for United States and also check out these interesting facts you probably never knew about whatwouldcathyeat.com

Heart-healthy, vegetarian and vegan recipes that are always full of flavor. Fun to read, easy to cook, delicious to eat.

Visit whatwouldcathyeat.com

Key Findings

We analyzed Whatwouldcathyeat.com page load time and found that the first response time was 189 ms and then it took 22.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster. Unfortunately, there was 1 request timeout, which can generally increase the web page load time, as the browser stays idle while waiting for website response.

Performance Metrics

whatwouldcathyeat.com performance score

24

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.3 s

41/100

10%

LCP (Largest Contentful Paint)

Value7.3 s

5/100

25%

SI (Speed Index)

Value15.5 s

0/100

10%

TBT (Total Blocking Time)

Value1,590 ms

12/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value30.0 s

0/100

10%

Network Requests Diagram

whatwouldcathyeat.com

189 ms

www.whatwouldcathyeat.com

629 ms

ga_pub_5179.js

96 ms

wp-emoji-release.min.js

210 ms

style.css

206 ms

Our browser made a total of 50 requests to load all elements on the main page. We found that 64% of them (32 requests) were addressed to the original Whatwouldcathyeat.com, 12% (6 requests) were made to Widget-prime.rafflecopter.com and 6% (3 requests) were made to Static.addtoany.com. The less responsive or slowest element that took the longest time to load (20.1 sec) relates to the external source Assoc-amazon.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 131.5 kB (6%)

Content Size

2.3 MB

After Optimization

2.1 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Whatwouldcathyeat.com main page is 2.3 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. 40% of websites need less resources to load. Images take 2.0 MB which makes up the majority of the site volume.

HTML Optimization

-73%

Potential reduce by 61.6 kB

  • Original 83.8 kB
  • After minification 82.6 kB
  • After compression 22.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 61.6 kB or 73% of the original size.

Image Optimization

-3%

Potential reduce by 50.9 kB

  • Original 2.0 MB
  • After minification 1.9 MB

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. What Would Cathy Eat images are well optimized though.

JavaScript Optimization

-9%

Potential reduce by 16.1 kB

  • Original 188.5 kB
  • After minification 188.3 kB
  • After compression 172.5 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

-37%

Potential reduce by 2.9 kB

  • Original 7.9 kB
  • After minification 7.9 kB
  • After compression 5.0 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. Whatwouldcathyeat.com needs all CSS files to be minified and compressed as it can save up to 2.9 kB or 37% of the original size.

Requests Breakdown

Number of requests can be reduced by 18 (39%)

Requests Now

46

After Optimization

28

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 46 CSS, Javascripts, AJAX and image requests in order to completely render the main page of What Would Cathy Eat. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 19 to 1 for JavaScripts and as a result speed up the page load time.

Network Requests Diagram

whatwouldcathyeat.com

whatwouldcathyeat.com

189 ms

www.whatwouldcathyeat.com

www.whatwouldcathyeat.com

629 ms

ga_pub_5179.js

ga_pub_5179.js

96 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

210 ms

style.css

style.css

206 ms

style.css

style.css

199 ms

jquery.js

jquery.js

274 ms

jquery-migrate.min.js

jquery-migrate.min.js

207 ms

jquery.fitvids.js

jquery.fitvids.js

226 ms

jquery.placeholder.js

jquery.placeholder.js

385 ms

jscript.js

jscript.js

427 ms

dd-formmailer.css

dd-formmailer.css

428 ms

date_chooser.js

date_chooser.js

438 ms

launch.js

launch.js

75 ms

vertical-scroll-recent-comments.js

vertical-scroll-recent-comments.js

387 ms

asw.js

asw.js

20081 ms

ga-fixed-widget.js

ga-fixed-widget.js

438 ms

wp-embed.min.js

wp-embed.min.js

634 ms

page.js

page.js

38 ms

whatwouldcathyeat

whatwouldcathyeat

47 ms

ga.js

ga.js

40 ms

gourmetads-logo.jpg

gourmetads-logo.jpg

74 ms

2016_badge_list_v2_badge-heartdisease.png

2016_badge_list_v2_badge-heartdisease.png

60 ms

bg-wide.jpg

bg-wide.jpg

210 ms

logo-trans.png

logo-trans.png

258 ms

sprite.png

sprite.png

218 ms

dotted.gif

dotted.gif

246 ms

resized-2.jpg

resized-2.jpg

527 ms

printer_famfamfam.gif

printer_famfamfam.gif

440 ms

Mushroom-leek-tart-2.jpg

Mushroom-leek-tart-2.jpg

716 ms

Tempeh-1.jpg

Tempeh-1.jpg

734 ms

DiningatTheRavens-233x300.jpg

DiningatTheRavens-233x300.jpg

514 ms

Falafel-final.jpg

Falafel-final.jpg

760 ms

carrot-muffins1.jpg

carrot-muffins1.jpg

975 ms

IMG_8480ps2.jpg

IMG_8480ps2.jpg

939 ms

cathy-square.jpg

cathy-square.jpg

783 ms

untitled-81712-69x46.jpg

untitled-81712-69x46.jpg

915 ms

IMG_9743Cannellini-bean-stew-POSTED2-69x46.jpg

IMG_9743Cannellini-bean-stew-POSTED2-69x46.jpg

934 ms

optimizedzucchinipasta1-69x46.jpg

optimizedzucchinipasta1-69x46.jpg

949 ms

savory-spinach-muffins_1-69x46.jpg

savory-spinach-muffins_1-69x46.jpg

976 ms

load.js

load.js

15 ms

main.shims.html

main.shims.html

25 ms

__utm.gif

__utm.gif

20 ms

shims.js

shims.js

5 ms

main.js

main.js

8 ms

load.gif

load.gif

7 ms

all.js

all.js

334 ms

sm.25.html

sm.25.html

330 ms

eso.BRQnzO8v.js

eso.BRQnzO8v.js

369 ms

all.js

all.js

5 ms

Accessibility Review

whatwouldcathyeat.com accessibility score

81

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.

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

High

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

Best Practices

whatwouldcathyeat.com best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

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

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

whatwouldcathyeat.com SEO score

84

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

Content Best Practices

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

Impact

Issue

High

Image elements do not have [alt] attributes

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

High

Tap targets are not sized appropriately

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

whatwouldcathyeat.com

Open Graph description is not detected on the main page of What Would Cathy Eat. 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: