2.2 sec in total
314 ms
1.6 sec
381 ms
Welcome to mycookingplace.com homepage info - get ready to check My Cooking Place best content for Sweden right away, or after learning these important things about mycookingplace.com
A place to find your homemade recipes and inspiration of interesting recipes from all around the world organized by different categories or themes.
Visit mycookingplace.comWe analyzed Mycookingplace.com page load time and found that the first response time was 314 ms and then it took 1.9 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.
mycookingplace.com performance score
name
value
score
weighting
Value2.2 s
77/100
10%
Value11.0 s
0/100
25%
Value5.4 s
56/100
10%
Value1,550 ms
13/100
30%
Value0.145
77/100
15%
Value12.6 s
14/100
10%
314 ms
109 ms
50 ms
69 ms
47 ms
Our browser made a total of 59 requests to load all elements on the main page. We found that 12% of them (7 requests) were addressed to the original Mycookingplace.com, 20% (12 requests) were made to Pagead2.googlesyndication.com and 17% (10 requests) were made to Googleads.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (482 ms) relates to the external source Googleads.g.doubleclick.net.
Page size can be reduced by 308.5 kB (21%)
1.5 MB
1.1 MB
In fact, the total size of Mycookingplace.com main page is 1.5 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. 60% of websites need less resources to load. Javascripts take 1.1 MB which makes up the majority of the site volume.
Potential reduce by 70.1 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. This page needs HTML code to be minified as it can gain 24.9 kB, which is 30% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 70.1 kB or 85% of the original size.
Potential reduce by 3.3 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. My Cooking Place images are well optimized though.
Potential reduce by 232.9 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 232.9 kB or 20% of the original size.
Potential reduce by 2.3 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. Mycookingplace.com needs all CSS files to be minified and compressed as it can save up to 2.3 kB or 22% of the original size.
Number of requests can be reduced by 34 (63%)
54
20
The browser has sent 54 CSS, Javascripts, AJAX and image requests in order to completely render the main page of My Cooking Place. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 25 to 1 for JavaScripts and as a result speed up the page load time.
mycookingplace.com
314 ms
LnSWelcomeScreen24.min.css
109 ms
jquery-1.11.3.min.js
50 ms
adsbygoogle.js
69 ms
jsapi
47 ms
button.prod.min.js
97 ms
loader.js
16 ms
loader.js
54 ms
sprite1722170651.jpg
225 ms
1_dollar_green.png
195 ms
1_chef_hat_green.png
194 ms
sprite1722170708.jpg
425 ms
latest_recipes1724649668.jpg
469 ms
show_ads_impl.js
87 ms
tooltip.css
8 ms
util.css
9 ms
jsapi_compiled_default_module.js
14 ms
jsapi_compiled_graphics_module.js
12 ms
jsapi_compiled_ui_module.js
36 ms
jsapi_compiled_geo_module.js
12 ms
jsapi_compiled_geochart_module.js
34 ms
zrt_lookup.html
32 ms
ads
121 ms
ads
471 ms
ads
416 ms
ads
482 ms
ca-pub-2712154741110792
75 ms
gen_204
67 ms
pixel
24 ms
dv3.js
47 ms
pixel.gif
22 ms
window_focus.js
38 ms
qs_click_protection.js
65 ms
ufs_web_display.js
38 ms
pixel
75 ms
pixel
75 ms
pixel
52 ms
gen_204
165 ms
ad
50 ms
ad
222 ms
126 ms
TMTo
218 ms
mvxm6axg_160x600.jpg
216 ms
ca
136 ms
setuid
114 ms
html_inpage_rendering_lib_200_280.js
258 ms
omrhp.js
196 ms
abg_lite.js
190 ms
Q12zgMmT.js
190 ms
icon.png
190 ms
rum
78 ms
activeview
65 ms
pixel
61 ms
activeview
39 ms
pixel
39 ms
62bHydCX.html
37 ms
rum
22 ms
z4ilzwD7EeyNPNt7L_5soWXfV8nS4IY_jbv2qtZMWp8.js
20 ms
bS-y1CAWm52ted35ON97X8ypz1nqoVE7foyXyvKmCB4.js
19 ms
mycookingplace.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.
mycookingplace.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
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
mycookingplace.com SEO score
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
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Mycookingplace.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 Mycookingplace.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.
mycookingplace.com
Open Graph description is not detected on the main page of My Cooking Place. 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: