2.9 sec in total
417 ms
2.1 sec
330 ms
Visit cooking-ez.com now to see the best up-to-date Cooking Ez content for Philippines and also check out these interesting facts you probably never knew about cooking-ez.com
A cool web site about easy cooking, with many delicious recipes, easy to do, and step by step explained with many photos and videos
Visit cooking-ez.comWe analyzed Cooking-ez.com page load time and found that the first response time was 417 ms and then it took 2.5 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.
cooking-ez.com performance score
name
value
score
weighting
Value4.6 s
13/100
10%
Value4.8 s
29/100
25%
Value5.0 s
63/100
10%
Value380 ms
70/100
30%
Value0.274
44/100
15%
Value7.8 s
44/100
10%
417 ms
96 ms
355 ms
17 ms
5 ms
Our browser made a total of 118 requests to load all elements on the main page. We found that 25% of them (30 requests) were addressed to the original Cooking-ez.com, 11% (13 requests) were made to S1.2mdn.net and 11% (13 requests) were made to S0.2mdn.net. The less responsive or slowest element that took the longest time to load (900 ms) belongs to the original domain Cooking-ez.com.
Page size can be reduced by 161.5 kB (30%)
536.0 kB
374.5 kB
In fact, the total size of Cooking-ez.com main page is 536.0 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. 65% of websites need less resources to load. Images take 310.6 kB which makes up the majority of the site volume.
Potential reduce by 55.8 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 55.8 kB or 79% of the original size.
Potential reduce by 9.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 Ez images are well optimized though.
Potential reduce by 66.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 66.5 kB or 57% of the original size.
Potential reduce by 29.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. Cooking-ez.com needs all CSS files to be minified and compressed as it can save up to 29.8 kB or 79% of the original size.
Number of requests can be reduced by 66 (58%)
114
48
The browser has sent 114 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Cooking Ez. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 36 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
cooking-ez.com
417 ms
ecran.css
96 ms
index.js
355 ms
jsapi
17 ms
adsbygoogle.js
5 ms
plusone.js
63 ms
cb=gapi.loaded_0
5 ms
ga.js
29 ms
like.php
173 ms
pin_it_button.png
27 ms
rss21.png
150 ms
boussole.png
150 ms
recettes_precedentes.jpg
271 ms
recettes_suivantes.jpg
268 ms
des.png
267 ms
email.png
228 ms
login_facebook_en.png
471 ms
puce_comment.png
474 ms
livre-or.png
488 ms
rss.png
488 ms
commentaires.png
489 ms
TwitterIcon.png
487 ms
facebook.png
565 ms
pinterest.png
558 ms
tumblr.png
635 ms
google_plus.png
635 ms
widgets.js
28 ms
totale.png
900 ms
icon-under.png
614 ms
google-translate.jpg
657 ms
icon-under2.png
653 ms
34 ms
__utm.gif
21 ms
default+en.css
4 ms
default.css
14 ms
default+en.I.js
11 ms
default.css
18 ms
mainmenubg.png
675 ms
rnd-white-bg.png
672 ms
content-right-bg.jpg
670 ms
arrondi_menu_bg.png
690 ms
ajs.php
85 ms
_zwRNeYSikF.css
348 ms
n09Bf9JTHe6.css
425 ms
AdP_CKHZFBh.css
489 ms
q68gy-v_YMF.js
706 ms
DFmZn3_ZO2h.js
559 ms
mfqI3d6rUg1.js
729 ms
_Qp3v7kqEMi.js
705 ms
lg.php
38 ms
ca-pub-3563316373172428.js
77 ms
zrt_lookup.html
165 ms
show_ads_impl.js
108 ms
puce_bleue.png
554 ms
cookbook.png
661 ms
button.0308b81ff1714e446f674b5b9793f2cd.js
134 ms
cb=gapi.loaded_1
73 ms
fastbutton
120 ms
puce_menu1.png
564 ms
ads
425 ms
osd.js
69 ms
ads
455 ms
postmessageRelay
99 ms
ads
401 ms
cb=gapi.loaded_0
35 ms
cb=gapi.loaded_1
45 ms
W5F8_SL0XFawnjxHGsZjJA.ttf
58 ms
tweet_button.b9740740e0bcf9b0657c5b11bd4388da.fr.html
25 ms
3193398744-postmessagerelay.js
16 ms
rpc:shindig_random.js
30 ms
cb=gapi.loaded_0
4 ms
jot
92 ms
s_0RjERnWQna_1374057504.html
101 ms
s_0R1j28YW9N_1766118946.html
89 ms
m_js_controller.js
89 ms
abg.js
108 ms
Bw8qRoQ9D-v.js
98 ms
4ylGxU24Rah.js
149 ms
cl
76 ms
creative_add_on.js
243 ms
cl
113 ms
favicon
129 ms
googlelogo_color_112x36dp.png
102 ms
nessie_icon_tiamat_white.png
44 ms
s
40 ms
x_button_blue2.png
52 ms
modernizr_2.8.3_ec185bb44fe5e6bf7455d6e8ef37ed0e_no-classes.js
102 ms
lidar.js
36 ms
Lrq7Jibxdtv2QOPyDSqncpDfQFNs3PE6SoUrUNh2GTU.js
23 ms
index.html
65 ms
index.html
25 ms
styles.css
20 ms
faucet0.png
7 ms
faucet1.png
30 ms
faucet2.png
23 ms
t0.png
23 ms
t0_white.png
26 ms
t1.png
24 ms
logo.svg
27 ms
cta_bg.png
26 ms
cta_text.png
33 ms
surly.js
78 ms
styles.css
27 ms
bathroom_bg.png
21 ms
faucet0.png
35 ms
faucet1.png
44 ms
faucet2.png
44 ms
t0.png
45 ms
t0_white.png
49 ms
t1.png
53 ms
logo.svg
49 ms
cta_bg.png
46 ms
cta_text.png
62 ms
ba.html
23 ms
4.gif
39 ms
bathroom_bg1.png
10 ms
bathroom_bg2.png
11 ms
2532.js
47 ms
cooking-ez.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
cooking-ez.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
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
cooking-ez.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
Document uses legible font sizes
EN
EN
WINDOWS-1252
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Cooking-ez.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 Cooking-ez.com main page’s claimed encoding is windows-1252. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
cooking-ez.com
Open Graph description is not detected on the main page of Cooking Ez. 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: