2.9 sec in total
263 ms
2.5 sec
132 ms
Visit config.fr now to see the best up-to-date Config content for France and also check out these interesting facts you probably never knew about config.fr
Acteur majeur sur le marché de la distribution de solutions de sécurité IT, nous offrons bien plus que de simples produits de sécurité à nos partenaires revendeurs : intégrateurs, Vars et SSII.
Visit config.frWe analyzed Config.fr page load time and found that the first response time was 263 ms and then it took 2.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
config.fr performance score
name
value
score
weighting
Value3.9 s
24/100
10%
Value8.6 s
1/100
25%
Value8.3 s
19/100
10%
Value430 ms
65/100
30%
Value0.048
99/100
15%
Value10.1 s
26/100
10%
263 ms
404 ms
257 ms
177 ms
179 ms
Our browser made a total of 76 requests to load all elements on the main page. We found that 89% of them (68 requests) were addressed to the original Config.fr, 3% (2 requests) were made to Stats.webleads-tracker.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.3 sec) belongs to the original domain Config.fr.
Page size can be reduced by 275.6 kB (53%)
519.5 kB
243.9 kB
In fact, the total size of Config.fr main page is 519.5 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. 30% of websites need less resources to load. Javascripts take 221.7 kB which makes up the majority of the site volume.
Potential reduce by 31.0 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 10.6 kB, which is 28% 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 31.0 kB or 81% of the original size.
Potential reduce by 61.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. Obviously, Config needs image optimization as it can save up to 61.9 kB or 30% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 140.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 140.5 kB or 63% of the original size.
Potential reduce by 42.2 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. Config.fr needs all CSS files to be minified and compressed as it can save up to 42.2 kB or 83% of the original size.
Number of requests can be reduced by 40 (55%)
73
33
The browser has sent 73 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Config. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 15 to 1 for JavaScripts and as a result speed up the page load time.
config.fr
263 ms
www.config.fr
404 ms
style__.css
257 ms
jquery.jcarousel.css
177 ms
all_functions.js
179 ms
swfobject.js
274 ms
jquery.js
337 ms
jquery.validationEngine.js
252 ms
jquery.validationEngine-fr.js
272 ms
jquery.jcarousel.pack.js
272 ms
chili-1.7.pack.js
357 ms
jquery.easing.js
355 ms
jquery.dimensions.js
372 ms
jquery.accordion.js
363 ms
swfobject.js
410 ms
track
288 ms
jcarousel_homepage.css
388 ms
js
232 ms
get_flash_player.gif
19 ms
body_bg.jpg
99 ms
hab-ruckus.png
323 ms
hab-trendmicro.png
296 ms
greenLogo.jpg
182 ms
acc_partner_image.gif
198 ms
acc_formation_image.gif
119 ms
news_pdt.png
187 ms
promotion_text.png
208 ms
footer_racc.gif
278 ms
piwik.js
96 ms
bt_close.png
209 ms
tab_b.png
271 ms
tab_l.png
284 ms
tab_m.png
292 ms
Business_People_01.png
375 ms
search_b.png
363 ms
tab_r.png
383 ms
arrow_language.png
377 ms
en.png
548 ms
bg_main_menu.gif
607 ms
home_orange.png
466 ms
m_solutions.png
467 ms
bg_t_sub_menu_sol_.png
475 ms
bg_main_sub_menu_sol.png
485 ms
bg_b_sub_menu_sol.png
566 ms
m_services.png
562 ms
bg_t_sub_menu_.png
578 ms
bg_main_sub_menu.png
586 ms
bg_b_sub_menu.png
648 ms
m_formations.png
702 ms
m_webinars.png
671 ms
m_promos_noir.png
677 ms
m_deal_noir.png
685 ms
m_actualites.png
696 ms
m_config.png
759 ms
778 ms
page-bg.gif
758 ms
ga.js
15 ms
accordion_select_partner.gif
740 ms
__utm.gif
10 ms
accordion_select_cmd.gif
721 ms
a_la_une.gif
686 ms
bg_news.gif
1346 ms
bg_border_news.png
687 ms
bg_top_news.gif
688 ms
arr_news_l.png
695 ms
arr_news_r.png
625 ms
bg_promos2.gif
637 ms
arrow.gif
672 ms
footer_racc_bg.gif
683 ms
contact_.png
691 ms
fbk.png
679 ms
in.php
139 ms
twitter_.png
684 ms
sitemap.png
675 ms
footer-bg2.png
690 ms
accordion_selected_partner.gif
689 ms
config.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.
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 IDs are not unique
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
Image elements do not have [alt] attributes
Links do not have a discernible name
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
config.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
Browser errors were logged to the console
Issues were logged in the Issues panel in Chrome Devtools
config.fr SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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
FR
UTF-8;
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Config.fr can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it does not match the claimed French language. Our system also found out that Config.fr main page’s claimed encoding is utf-8;. 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.
config.fr
Open Graph description is not detected on the main page of Config. 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: