3.9 sec in total
258 ms
3 sec
680 ms
Visit cntr.fr now to see the best up-to-date CNTR content for France and also check out these interesting facts you probably never knew about cntr.fr
Visit cntr.frWe analyzed Cntr.fr page load time and found that the first response time was 258 ms and then it took 3.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
cntr.fr performance score
name
value
score
weighting
Value3.9 s
26/100
10%
Value10.2 s
0/100
25%
Value5.3 s
58/100
10%
Value1,180 ms
21/100
30%
Value0.75
6/100
15%
Value13.8 s
10/100
10%
258 ms
754 ms
92 ms
158 ms
236 ms
Our browser made a total of 90 requests to load all elements on the main page. We found that 82% of them (74 requests) were addressed to the original Cntr.fr, 6% (5 requests) were made to Gstatic.com and 4% (4 requests) were made to Google.com. The less responsive or slowest element that took the longest time to load (856 ms) belongs to the original domain Cntr.fr.
Page size can be reduced by 121.3 kB (8%)
1.6 MB
1.5 MB
In fact, the total size of Cntr.fr main page is 1.6 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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 973.4 kB which makes up the majority of the site volume.
Potential reduce by 68.5 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 19.7 kB, which is 24% 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 68.5 kB or 83% of the original size.
Potential reduce by 45.9 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. CNTR images are well optimized though.
Potential reduce by 2.4 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.
Potential reduce by 4.5 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. Cntr.fr has all CSS files already compressed.
Number of requests can be reduced by 33 (43%)
76
43
The browser has sent 76 CSS, Javascripts, AJAX and image requests in order to completely render the main page of CNTR. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 21 to 1 for JavaScripts and from 14 to 1 for CSS and as a result speed up the page load time.
cntr.fr
258 ms
www.cntr.fr
754 ms
59970fd924.js
92 ms
style-blocks.build.css
158 ms
style.build.css
236 ms
all.min.css
237 ms
slick.min.css
240 ms
slick-theme.min.css
250 ms
jquery.fancybox.min.css
250 ms
blocks.style.css
343 ms
dnd-upload-cf7.css
313 ms
styles.css
316 ms
style-blocks.css
318 ms
style.css
412 ms
style-dev.css
330 ms
animate.min.css
390 ms
jquery.min.js
26 ms
script.js
394 ms
frontend.blocks.js
324 ms
index.js
337 ms
index.js
455 ms
codedropz-uploader-min.js
467 ms
dismiss.js
466 ms
wow.min.js
466 ms
api.js
44 ms
wp-polyfill-inert.min.js
465 ms
regenerator-runtime.min.js
466 ms
wp-polyfill.min.js
466 ms
index.js
583 ms
gtm.js
132 ms
175-logo-cntr.png
234 ms
bg-main-menu.jpg
409 ms
menu-mobile-arrow-right.svg
233 ms
menu-mobile-arrow-left.svg
205 ms
arrow-caret-right.svg
208 ms
check-red-icon.svg
248 ms
magnifying-glass.svg
286 ms
people.svg
287 ms
medal.svg
292 ms
pop-check.svg
289 ms
picto-bleu-red.svg
315 ms
Illus-Titres-Restaurants.png
404 ms
illus-salarie.svg
405 ms
small-picto-arrow-right-bleu.svg
408 ms
illus-commercant.svg
409 ms
Illus-employeur.svg
489 ms
Illus-emetteurx2-1-e1663255773953.png
451 ms
Illus-autre-acteur.svg
451 ms
warning-circle-grey.svg
482 ms
bg-emetteurs-cntr-1.jpg
856 ms
logo-benefiz.png
487 ms
logo-swile.png
523 ms
logo-resto.png
524 ms
logo-wiismile.png
533 ms
logo-worklife.svg
572 ms
Logo-Bimpli-Resto-e1678441067421.png
564 ms
logo-glady.png
602 ms
logo-pluxee-004.png
525 ms
Volkhov-BoldItalic.ttf
611 ms
Volkhov-Bold.ttf
710 ms
Jost%20Bold%20700.ttf
655 ms
Jost%20Black%20900.ttf
678 ms
Jost%20SemiBold%20600.ttf
672 ms
Jost%20Medium%20500.ttf
694 ms
recaptcha__en.js
50 ms
Jost%20Regular%20400.ttf
808 ms
sdk-slim.js
102 ms
Jost%20Thin%20250.ttf
717 ms
anchor
110 ms
Jost%20Light%20300.ttf
691 ms
logo-edenred.png
629 ms
Up-dej-one-V.-4.png
645 ms
Logo-Ekip-e1671699972999.png
694 ms
Logo-coup-de-pousse.jpg
690 ms
Logo01.png
668 ms
service-online-01.jpg
799 ms
arrow-right-white-small.svg
712 ms
service-online-02.jpg
788 ms
help-image.svg
705 ms
styles__ltr.css
3 ms
recaptcha__en.js
10 ms
R158mP-HER8cF-2W1d4Zs3A-8309t2iBf9rXxsmuGOY.js
40 ms
webworker.js
75 ms
logo_48.png
28 ms
logo-footer.png
617 ms
picto-line-red.svg
626 ms
KFOmCnqEu92Fr1Mu4mxP.ttf
49 ms
KFOlCnqEu92Fr1MmEU9fBBc9.ttf
50 ms
KFOlCnqEu92Fr1MmYUtfBBc9.ttf
53 ms
recaptcha__en.js
37 ms
cntr.fr 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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
cntr.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
General
Impact
Issue
Detected JavaScript libraries
cntr.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 Cntr.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 Cntr.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.
cntr.fr
Open Graph description is not detected on the main page of CNTR. 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: