Tools & Wizards About Us
cookingwithpoo.com screenshot

Report Summary

  • 64

    Performance

    Renders faster than
    77% of other websites

  • 91

    Accessibility

    Visual factors better than
    that of 76% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

cookingwithpoo.com

Cooking with Poo and Friends | A Thai Cooking School

Page Load Speed

2.8 sec in total

First Response

94 ms

Resources Loaded

2.6 sec

Page Rendered

61 ms

cookingwithpoo.com screenshot

About Website

Visit cookingwithpoo.com now to see the best up-to-date Cooking With Poo content for Thailand and also check out these interesting facts you probably never knew about cookingwithpoo.com

Cooking classes based in the Klong Toey slum of Bangkok, Thailand. Run by the residents themselves.

Visit cookingwithpoo.com

Key Findings

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

Performance Metrics

cookingwithpoo.com performance score

64

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.3 s

74/100

10%

LCP (Largest Contentful Paint)

Value3.5 s

65/100

25%

SI (Speed Index)

Value4.5 s

73/100

10%

TBT (Total Blocking Time)

Value520 ms

56/100

30%

CLS (Cumulative Layout Shift)

Value0.011

100/100

15%

TTI (Time to Interactive)

Value11.8 s

17/100

10%

Network Requests Diagram

www.cookingwithpoo.com

94 ms

minified.js

58 ms

focus-within-polyfill.js

55 ms

polyfill.min.js

1218 ms

thunderbolt-commons.236a53ec.bundle.min.js

84 ms

Our browser made a total of 55 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Cookingwithpoo.com, 49% (27 requests) were made to Static.parastorage.com and 22% (12 requests) were made to Static.wixstatic.com. The less responsive or slowest element that took the longest time to load (1.2 sec) relates to the external source Polyfill-fastly.io.

Page Optimization Overview & Recommendations

Page size can be reduced by 551.4 kB (48%)

Content Size

1.2 MB

After Optimization

606.0 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Cookingwithpoo.com main page is 1.2 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. 55% of websites need less resources to load. HTML takes 672.2 kB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 536.3 kB

  • Original 672.2 kB
  • After minification 670.6 kB
  • After compression 135.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 536.3 kB or 80% of the original size.

Image Optimization

-5%

Potential reduce by 10.9 kB

  • Original 234.3 kB
  • After minification 223.4 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. Cooking With Poo images are well optimized though.

JavaScript Optimization

-2%

Potential reduce by 4.2 kB

  • Original 250.9 kB
  • After minification 250.9 kB
  • After compression 246.7 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.

Requests Breakdown

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

Requests Now

28

After Optimization

17

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.cookingwithpoo.com

www.cookingwithpoo.com

94 ms

minified.js

minified.js

58 ms

focus-within-polyfill.js

focus-within-polyfill.js

55 ms

polyfill.min.js

polyfill.min.js

1218 ms

thunderbolt-commons.236a53ec.bundle.min.js

thunderbolt-commons.236a53ec.bundle.min.js

84 ms

main.3f2ce92a.bundle.min.js

main.3f2ce92a.bundle.min.js

86 ms

main.renderer.1d21f023.bundle.min.js

main.renderer.1d21f023.bundle.min.js

80 ms

lodash.min.js

lodash.min.js

81 ms

react.production.min.js

react.production.min.js

80 ms

react-dom.production.min.js

react-dom.production.min.js

83 ms

siteTags.bundle.min.js

siteTags.bundle.min.js

69 ms

wix-perf-measure.umd.min.js

wix-perf-measure.umd.min.js

71 ms

CWP%26Friends%20-%20logo.png

CWP%26Friends%20-%20logo.png

292 ms

Cooking%20With%20Poo%2007_16_14%20(Web)%20-%2057.jpg

Cooking%20With%20Poo%2007_16_14%20(Web)%20-%2057.jpg

595 ms

4100f1_2316ad08634e4600868cea2654ddf9ed.gif

4100f1_2316ad08634e4600868cea2654ddf9ed.gif

297 ms

4100f1_0d25fdffc1f84a6b832e59f637149f82.jpg

4100f1_0d25fdffc1f84a6b832e59f637149f82.jpg

541 ms

4100f1_42e685c6b79a48209be22f61e6a906bf.jpg

4100f1_42e685c6b79a48209be22f61e6a906bf.jpg

602 ms

4100f1_1340fd5b8cc542ddad8b930ab1869178~mv2.jpg

4100f1_1340fd5b8cc542ddad8b930ab1869178~mv2.jpg

634 ms

4100f1_97bb72f5a9014cd78c7591b8f3738dfb.jpg

4100f1_97bb72f5a9014cd78c7591b8f3738dfb.jpg

524 ms

4100f1_e5c68f73625d4e1484ad4293e6ed7f71.jpg

4100f1_e5c68f73625d4e1484ad4293e6ed7f71.jpg

653 ms

4100f1_24bb5ae7f7b744c2ace171c9747d06f3.png

4100f1_24bb5ae7f7b744c2ace171c9747d06f3.png

820 ms

4100f1_56a0ab1d1d5d481796bd9632bc6e6568.jpg

4100f1_56a0ab1d1d5d481796bd9632bc6e6568.jpg

882 ms

Cooking%20With%20Poo%2007_16_14%20(Web)%20-%2073.jpg

Cooking%20With%20Poo%2007_16_14%20(Web)%20-%2073.jpg

881 ms

Cooking%20With%20Poo%2007_16_14%20(Web)%20-%2011.jpg

Cooking%20With%20Poo%2007_16_14%20(Web)%20-%2011.jpg

1068 ms

bundle.min.js

bundle.min.js

52 ms

WmVKXVcOuffP_qmCpFuyzRsxEYwM7FgeyaSgU71cLG0.woff

WmVKXVcOuffP_qmCpFuyzRsxEYwM7FgeyaSgU71cLG0.woff

43 ms

STBOO2waD2LpX45SXYjQBRsxEYwM7FgeyaSgU71cLG0.woff

STBOO2waD2LpX45SXYjQBRsxEYwM7FgeyaSgU71cLG0.woff

45 ms

234c98b8-36ae-45ab-8a55-77980708b2bc.woff

234c98b8-36ae-45ab-8a55-77980708b2bc.woff

45 ms

301e2ea2-8153-453c-9051-0a729098e682.woff

301e2ea2-8153-453c-9051-0a729098e682.woff

45 ms

73381861-eb6a-4f7c-8c14-cd34a714f943.woff

73381861-eb6a-4f7c-8c14-cd34a714f943.woff

44 ms

83ae2051-dcdd-4931-9946-8be747a40d00.woff

83ae2051-dcdd-4931-9946-8be747a40d00.woff

44 ms

764779cf-076d-427a-87b4-136ccc83fba0.woff

764779cf-076d-427a-87b4-136ccc83fba0.woff

46 ms

571d67cb-de3d-41af-8c0a-06a53d490466.woff

571d67cb-de3d-41af-8c0a-06a53d490466.woff

47 ms

bc176270-17fa-4c78-a343-9fe52824e501.woff

bc176270-17fa-4c78-a343-9fe52824e501.woff

47 ms

07d62b21-8d7a-4c36-be86-d32ab1089972.woff

07d62b21-8d7a-4c36-be86-d32ab1089972.woff

47 ms

a9e95a29-98a7-404a-90ee-1929ad09c696.woff

a9e95a29-98a7-404a-90ee-1929ad09c696.woff

46 ms

111 ms

118 ms

116 ms

110 ms

114 ms

106 ms

150 ms

147 ms

144 ms

148 ms

151 ms

150 ms

deprecation-en.v5.html

deprecation-en.v5.html

6 ms

bolt-performance

bolt-performance

29 ms

deprecation-style.v5.css

deprecation-style.v5.css

8 ms

right-arrow.svg

right-arrow.svg

21 ms

WixMadeforDisplay_W_Bd.woff

WixMadeforDisplay_W_Bd.woff

4 ms

WixMadeforText_W_Bd.woff

WixMadeforText_W_Bd.woff

5 ms

WixMadeforText_W_Rg.woff

WixMadeforText_W_Rg.woff

4 ms

Accessibility Review

cookingwithpoo.com accessibility score

91

Accessibility Issues

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

Buttons do not have an accessible name

High

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

Best Practices

cookingwithpoo.com best practices score

92

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

Page has valid source maps

SEO Factors

cookingwithpoo.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 Cookingwithpoo.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 Cookingwithpoo.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

cookingwithpoo.com

Open Graph data is detected on the main page of Cooking With Poo. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: