14.8 sec in total
1 sec
6.6 sec
7.1 sec
Click here to check amazing Cooking content for United States. Otherwise, check out these important facts you probably never knew about cooking.com
cooking.com by Hoffman Media
Visit cooking.comWe analyzed Cooking.com page load time and found that the first response time was 1 sec and then it took 13.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
cooking.com performance score
name
value
score
weighting
Value0.6 s
100/100
10%
Value1.7 s
99/100
25%
Value0.6 s
100/100
10%
Value20 ms
100/100
30%
Value0
100/100
15%
Value1.4 s
100/100
10%
1037 ms
2484 ms
2566 ms
1680 ms
2522 ms
Our browser made a total of 20 requests to load all elements on the main page. We found that 35% of them (7 requests) were addressed to the original Cooking.com, 15% (3 requests) were made to Cdnjs.cloudflare.com and 10% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (3.4 sec) relates to the external source Cdn.jsdelivr.net.
Page size can be reduced by 597.7 kB (20%)
2.9 MB
2.4 MB
In fact, the total size of Cooking.com main page is 2.9 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. 70% of websites need less resources to load. Images take 2.2 MB which makes up the majority of the site volume.
Potential reduce by 10.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 10.9 kB or 72% of the original size.
Potential reduce by 15.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. Cooking images are well optimized though.
Potential reduce by 264.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 264.7 kB or 71% of the original size.
Potential reduce by 306.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.com needs all CSS files to be minified and compressed as it can save up to 306.8 kB or 79% of the original size.
Number of requests can be reduced by 11 (69%)
16
5
The browser has sent 16 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Cooking. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 7 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
www.cooking.com
1037 ms
font-awesome.min.css
2484 ms
bootstrap.min.css
2566 ms
style.css
1680 ms
css
2522 ms
css
2534 ms
animate.min.css
2468 ms
jquery.js
1645 ms
modernizr-custom.js
2117 ms
purl.min.js
2496 ms
jquery.cookie.min.js
3442 ms
jquery.fitvids.min.js
1677 ms
scripts.js
1306 ms
cooking-coming-soon.png
821 ms
analytics.js
1271 ms
hm-logo-305r.png
1185 ms
cJZKeOuBrn4kERxqtaUH3T8E0i7KZn-EPnyo3HZu7kw.woff
1403 ms
pR0sBQVcY0JZc_ciXjFsK5Rby8KfwQsaipLBqMCVNtM.woff
547 ms
collect
396 ms
collect
603 ms
cooking.com accessibility score
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
cooking.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
cooking.com SEO score
N/A
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Cooking.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else) and no language is claimed in <html> or <meta> tags either. Our system also found out that Cooking.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.
cooking.com
Open Graph data is detected on the main page of Cooking. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: