Tools & Wizards About Us
whatscookingdoc.com screenshot

Report Summary

  • 16

    Performance

    Renders faster than
    30% of other websites

  • 93

    Accessibility

    Visual factors better than
    that of 80% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 90

    SEO

    Google-friendlier than
    68% of websites

whatscookingdoc.com

WHAT'S COOKING DOC? - THE HABITS DOCTOR - Dr Chan Tat Hon

Page Load Speed

3.1 sec in total

First Response

177 ms

Resources Loaded

2.6 sec

Page Rendered

295 ms

whatscookingdoc.com screenshot

About Website

Welcome to whatscookingdoc.com homepage info - get ready to check WHAT S COOKING DOC best content right away, or after learning these important things about whatscookingdoc.com

The adventures of Dr Chan Tat Hon - from a doctor, coach, speaker, teacher and chef of all things food and health

Visit whatscookingdoc.com

Key Findings

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

Performance Metrics

whatscookingdoc.com performance score

16

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.4 s

17/100

10%

LCP (Largest Contentful Paint)

Value16.3 s

0/100

25%

SI (Speed Index)

Value8.6 s

17/100

10%

TBT (Total Blocking Time)

Value3,640 ms

1/100

30%

CLS (Cumulative Layout Shift)

Value0.118

85/100

15%

TTI (Time to Interactive)

Value26.9 s

0/100

10%

Network Requests Diagram

whatscookingdoc.com

177 ms

www.whatscookingdoc.com

386 ms

adsbygoogle.js

129 ms

sites.css

24 ms

fancybox.css

32 ms

Our browser made a total of 118 requests to load all elements on the main page. We found that 8% of them (10 requests) were addressed to the original Whatscookingdoc.com, 22% (26 requests) were made to Static.cdninstagram.com and 19% (23 requests) were made to Static.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Whatscookingdoc.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 560.6 kB (27%)

Content Size

2.1 MB

After Optimization

1.5 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Whatscookingdoc.com main page is 2.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. Only a small number of websites need less resources to load. Javascripts take 1.4 MB which makes up the majority of the site volume.

HTML Optimization

-75%

Potential reduce by 54.3 kB

  • Original 72.2 kB
  • After minification 71.1 kB
  • After compression 17.9 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 54.3 kB or 75% of the original size.

Image Optimization

-1%

Potential reduce by 2.9 kB

  • Original 519.5 kB
  • After minification 516.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. WHAT S COOKING DOC images are well optimized though.

JavaScript Optimization

-36%

Potential reduce by 503.0 kB

  • Original 1.4 MB
  • After minification 1.4 MB
  • After compression 898.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 503.0 kB or 36% of the original size.

CSS Optimization

-0%

Potential reduce by 441 B

  • Original 97.5 kB
  • After minification 97.5 kB
  • After compression 97.1 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. Whatscookingdoc.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 75 (72%)

Requests Now

104

After Optimization

29

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 104 CSS, Javascripts, AJAX and image requests in order to completely render the main page of WHAT S COOKING DOC. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 62 to 1 for JavaScripts and from 15 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

whatscookingdoc.com

whatscookingdoc.com

177 ms

www.whatscookingdoc.com

www.whatscookingdoc.com

386 ms

adsbygoogle.js

adsbygoogle.js

129 ms

sites.css

sites.css

24 ms

fancybox.css

fancybox.css

32 ms

social-icons.css

social-icons.css

40 ms

main_style.css

main_style.css

176 ms

font.css

font.css

40 ms

font.css

font.css

39 ms

font.css

font.css

39 ms

jquery-1.8.3.min.js

jquery-1.8.3.min.js

40 ms

stl.js

stl.js

37 ms

main.js

main.js

53 ms

stl.js

stl.js

41 ms

embed.js

embed.js

157 ms

show_ads_impl.js

show_ads_impl.js

796 ms

zrt_lookup_nohtml.html

zrt_lookup_nohtml.html

128 ms

plugins.js

plugins.js

113 ms

custom.js

custom.js

112 ms

mobile.js

mobile.js

183 ms

main-customer-accounts-site.js

main-customer-accounts-site.js

111 ms

R304Y4kG8t8

R304Y4kG8t8

265 ms

qmDpJOJ42Ek

qmDpJOJ42Ek

410 ms

what-s-cooking-doc-banner-for-wcd-website-v4_orig.jpg

what-s-cooking-doc-banner-for-wcd-website-v4_orig.jpg

875 ms

my-1280-x-720-habits-as-medicine-15.png

my-1280-x-720-habits-as-medicine-15.png

283 ms

whats-cooking-doc-meetup-banner-final-final-2nd-half_orig.jpg

whats-cooking-doc-meetup-banner-final-final-2nd-half_orig.jpg

1125 ms

sdk.js

sdk.js

33 ms

medium.woff

medium.woff

10 ms

regular.woff

regular.woff

13 ms

light.woff

light.woff

13 ms

ultralight.woff

ultralight.woff

12 ms

semibold.woff

semibold.woff

13 ms

bold.woff

bold.woff

26 ms

bold.woff

bold.woff

27 ms

regular.woff

regular.woff

26 ms

wsocial.woff

wsocial.woff

26 ms

sdk.js

sdk.js

10 ms

169 ms

analytics.js

analytics.js

81 ms

ga.js

ga.js

48 ms

snowday262.js

snowday262.js

46 ms

883 ms

www-player.css

www-player.css

58 ms

www-embed-player.js

www-embed-player.js

90 ms

base.js

base.js

152 ms

611 ms

like.php

like.php

609 ms

page.php

page.php

467 ms

collect

collect

97 ms

js

js

612 ms

ad_status.js

ad_status.js

540 ms

6mt_jkCC8QEMfVv4UaXe0WVRezbgElH9_VSMBGBwk28.js

6mt_jkCC8QEMfVv4UaXe0WVRezbgElH9_VSMBGBwk28.js

438 ms

embed.js

embed.js

155 ms

HADo6_noYei.css

HADo6_noYei.css

291 ms

8njxFR0-pKg.css

8njxFR0-pKg.css

382 ms

7lsEVUweoYF.css

7lsEVUweoYF.css

394 ms

BFVUlNP835L.js

BFVUlNP835L.js

653 ms

BECqV_OB-Tv.js

BECqV_OB-Tv.js

409 ms

teTZ2tZqwkq.js

teTZ2tZqwkq.js

408 ms

XC4Un5GdVZt.js

XC4Un5GdVZt.js

414 ms

q4SZVAjzsaO.js

q4SZVAjzsaO.js

415 ms

p55HfXW__mM.js

p55HfXW__mM.js

414 ms

e7Tp58KLYmo.js

e7Tp58KLYmo.js

515 ms

cMurRu-0m07.js

cMurRu-0m07.js

687 ms

rMzNGFrxoTb.js

rMzNGFrxoTb.js

700 ms

L-RRi9KXBOI.js

L-RRi9KXBOI.js

687 ms

JVpNdAH_hLQ.js

JVpNdAH_hLQ.js

700 ms

HkvD17iqK-X.js

HkvD17iqK-X.js

714 ms

Glmz_lYOBT1.js

Glmz_lYOBT1.js

715 ms

HzxD9aAXSyD.js

HzxD9aAXSyD.js

724 ms

cFnio4gi1vh2CYU0Ett6xA0G_Vyd_QBYpQEc_-VJhJY.js

cFnio4gi1vh2CYU0Ett6xA0G_Vyd_QBYpQEc_-VJhJY.js

313 ms

a7LoXQDbYK9.js

a7LoXQDbYK9.js

719 ms

tp2

tp2

545 ms

FEppCFCt76d.png

FEppCFCt76d.png

581 ms

id

id

146 ms

KFOmCnqEu92Fr1Mu4mxM.woff

KFOmCnqEu92Fr1Mu4mxM.woff

501 ms

KFOlCnqEu92Fr1MmEU9fBBc-.woff

KFOlCnqEu92Fr1MmEU9fBBc-.woff

538 ms

ads

ads

132 ms

Create

Create

218 ms

Create

Create

424 ms

lR-qKzj3caJ.css

lR-qKzj3caJ.css

470 ms

x2P-_PcUB_k.css

x2P-_PcUB_k.css

636 ms

UaX0f9-Tct6.css

UaX0f9-Tct6.css

661 ms

kLSS5jBYv8y.css

kLSS5jBYv8y.css

662 ms

BFVUlNP835L.js

BFVUlNP835L.js

677 ms

350107288_1190637291614932_338532931817918142_n.png

350107288_1190637291614932_338532931817918142_n.png

354 ms

350487635_1194538921231039_4886591925274926627_n.jpg

350487635_1194538921231039_4886591925274926627_n.jpg

311 ms

UXtr_j2Fwe-.png

UXtr_j2Fwe-.png

104 ms

GenerateIT

GenerateIT

221 ms

GenerateIT

GenerateIT

222 ms

Xod3uulfej0.js

Xod3uulfej0.js

172 ms

kCwDvxe1QsQ.js

kCwDvxe1QsQ.js

172 ms

44y2ROYOC9X.js

44y2ROYOC9X.js

173 ms

16465082_1208617795919375_8531732309055897600_a.jpg

16465082_1208617795919375_8531732309055897600_a.jpg

66 ms

16464987_410025602668399_6874506696719335424_n.jpg

16464987_410025602668399_6874506696719335424_n.jpg

70 ms

431363433_803190538504960_4975990845977433960_n.jpg

431363433_803190538504960_4975990845977433960_n.jpg

76 ms

430315192_741671427937568_7067153060572651220_n.jpg

430315192_741671427937568_7067153060572651220_n.jpg

87 ms

hwgTSgiJXcc.png

hwgTSgiJXcc.png

44 ms

9b9cYKfYm7O.js

9b9cYKfYm7O.js

18 ms

YBQL2uZEXqT.js

YBQL2uZEXqT.js

18 ms

5-CNhD1hzUM.js

5-CNhD1hzUM.js

13 ms

RKK6hMCj3R1.js

RKK6hMCj3R1.js

16 ms

a8BhFw4p2fz.js

a8BhFw4p2fz.js

29 ms

5kEgrdqEi-T.js

5kEgrdqEi-T.js

29 ms

bzTgFvFWKWw.js

bzTgFvFWKWw.js

32 ms

HDiX03ZTkcn.js

HDiX03ZTkcn.js

30 ms

9lDiey1l9HS.js

9lDiey1l9HS.js

29 ms

waPKrglUzck.js

waPKrglUzck.js

31 ms

h2CxxVe5yZg.js

h2CxxVe5yZg.js

32 ms

pyjzcI4X28y.js

pyjzcI4X28y.js

32 ms

YCPNwHcFmXs.js

YCPNwHcFmXs.js

35 ms

j6qreeXbbeM.js

j6qreeXbbeM.js

35 ms

alp2YZacTXN.js

alp2YZacTXN.js

33 ms

nrOWia4kAGv.js

nrOWia4kAGv.js

71 ms

9XbYvBxdW3R.js

9XbYvBxdW3R.js

71 ms

R8pD4fnxcVE.js

R8pD4fnxcVE.js

92 ms

VYDy4xvT73U.js

VYDy4xvT73U.js

90 ms

kUHqC7ZrNXt.js

kUHqC7ZrNXt.js

91 ms

Accessibility Review

whatscookingdoc.com accessibility score

93

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

Best Practices

whatscookingdoc.com best practices score

75

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

Page has valid source maps

SEO Factors

whatscookingdoc.com SEO score

90

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

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

whatscookingdoc.com

Open Graph data is detected on the main page of WHAT S COOKING DOC. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: