5 sec in total
1.5 sec
3.3 sec
226 ms
Visit cooknow.fr now to see the best up-to-date Cook Now content and also check out these interesting facts you probably never knew about cooknow.fr
Blog culinaire
Visit cooknow.frWe analyzed Cooknow.fr page load time and found that the first response time was 1.5 sec and then it took 3.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
cooknow.fr performance score
name
value
score
weighting
Value3.6 s
31/100
10%
Value8.2 s
2/100
25%
Value6.6 s
37/100
10%
Value320 ms
76/100
30%
Value0.767
5/100
15%
Value6.2 s
62/100
10%
1523 ms
80 ms
469 ms
236 ms
239 ms
Our browser made a total of 61 requests to load all elements on the main page. We found that 80% of them (49 requests) were addressed to the original Cooknow.fr, 5% (3 requests) were made to Staticxx.facebook.com and 3% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.5 sec) belongs to the original domain Cooknow.fr.
Page size can be reduced by 445.1 kB (36%)
1.2 MB
793.8 kB
In fact, the total size of Cooknow.fr 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. 50% of websites need less resources to load. Images take 654.1 kB which makes up the majority of the site volume.
Potential reduce by 33.3 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 6.1 kB, which is 14% 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 33.3 kB or 78% of the original size.
Potential reduce by 20.2 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. Cook Now images are well optimized though.
Potential reduce by 199.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 199.9 kB or 63% of the original size.
Potential reduce by 191.7 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. Cooknow.fr needs all CSS files to be minified and compressed as it can save up to 191.7 kB or 84% of the original size.
Number of requests can be reduced by 16 (29%)
55
39
The browser has sent 55 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Cook Now. 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 from 6 to 1 for CSS and as a result speed up the page load time.
cooknow.fr
1523 ms
fonts.css
80 ms
bootstrap.min.css
469 ms
jquery.ui.css
236 ms
font-awesome.min.css
239 ms
animate.min.css
313 ms
main.css
240 ms
api.js
49 ms
jquery.min.js
30 ms
bootstrap.min.js
244 ms
jquery.ui.min.js
714 ms
jquery.h5validate.js
316 ms
tags.js
318 ms
app.js
407 ms
cookiechoices.js
388 ms
recaptcha__fr.js
99 ms
logo-cooknow.png
97 ms
slider11.jpg
317 ms
slider2.jpg
314 ms
slider31.jpg
417 ms
Brochette-de-poulet-grill%C3%A9-%C3%A0-la-citronnelle-375x400.jpg
929 ms
7c1b0b813d51659cd561bf17878d2469-bpfull-1433092414-683.jpg
156 ms
Cr%C3%A8me-de-petits-pois-375x400.jpg
994 ms
3863b3982b8a5072f979090158cddb64-bpfull-1433092415-703.jpg
298 ms
photo-restobn.jpg
454 ms
thierryblanqui-100x100.jpg
392 ms
23318-196x196.jpg
394 ms
23315-196x196.jpg
471 ms
23308-196x196.jpg
474 ms
19219-360x360.jpg
503 ms
rastanyan-1458398856-5042.png
555 ms
new-logo-1457877407-5023.jpg
556 ms
untitled-1456319847-4982.jpg
556 ms
941016-108819989494502-1668391528259940775-n-1454255777-4975.jpg
586 ms
mbwf8-p-1453676826-4971.png
612 ms
profil-fred1-1453498603-4970.png
626 ms
tisane-anis2-1452017490-4962.jpg
630 ms
better-call-saul-1447258594-4942.jpg
666 ms
80f26e7d2aa49970a7cb9556358ec7b4-bpfull-1433092445-2768.jpg
690 ms
4c70efa2fc79eaf105a9dd295eeb1cef-bpfull-1433092422-2648.jpg
704 ms
8e489a843df177e987b191c7a7d18d6b-bpfull-1433092445-2342.jpg
708 ms
487d005ab035829f79235e760c23b59b-bpfull-1433092445-2206.jpg
748 ms
60c6dfee01c0f778bea31b64382f6132-bpfull-1433092445-2205.jpg
769 ms
64f380751ebc2143e55f1a1810611da9-bpfull-1433092443-2027.jpg
793 ms
394a1f07b169fca273a7f6a64a120045-bpfull-1433092441-1839.jpg
795 ms
20e62fa71f43dce7be0a4b98a82363ca-bpfull-1433092440-1820.jpg
831 ms
4ba27838061b6415a32f09f94b8b11a8-bpfull-1433092436-1528.jpg
848 ms
70561db6a7fc977bee203c235c84d05b-bpfull-1433092436-1485.jpg
860 ms
19758be642072eeadc3fc14908329da6-bpfull-1433092428-1182.jpg
874 ms
f1f8473af183fa44bb4b24ff07093c04-bpfull-1433092427-1100.jpg
911 ms
fontawesome-webfont.woff
856 ms
harabara-webfont.woff
851 ms
count.js
35 ms
ga.js
19 ms
sdk.js
269 ms
__utm.gif
13 ms
collect
61 ms
146 ms
xd_arbiter.php
228 ms
xd_arbiter.php
433 ms
xd_arbiter.php
138 ms
cooknow.fr accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
[aria-*] attributes do not match their roles
[aria-hidden="true"] elements contain focusable descendents
ARIA input fields do not have accessible names
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
[aria-*] attributes do not have valid values
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
cooknow.fr 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
cooknow.fr 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
Tap targets are not sized appropriately
FR
FR
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Cooknow.fr can be misinterpreted by Google and other search engines. Our service has detected that French is used on the page, and it matches the claimed language. Our system also found out that Cooknow.fr 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.
cooknow.fr
Open Graph data is detected on the main page of Cook Now. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: