7.2 sec in total
265 ms
6.6 sec
350 ms
Visit fntc.org now to see the best up-to-date FNTC content for France and also check out these interesting facts you probably never knew about fntc.org
FNTC - Fédération des Tiers de Confiance
Visit fntc.orgWe analyzed Fntc.org page load time and found that the first response time was 265 ms and then it took 6.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
fntc.org performance score
name
value
score
weighting
Value0
0/100
10%
Value0
0/100
25%
Value0
0/100
10%
Value0
0/100
30%
Value0.08
94/100
15%
Value0
0/100
10%
265 ms
369 ms
1742 ms
95 ms
185 ms
Our browser made a total of 123 requests to load all elements on the main page. We found that 91% of them (112 requests) were addressed to the original Fntc.org, 5% (6 requests) were made to Fonts.googleapis.com and 2% (2 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (2.2 sec) belongs to the original domain Fntc.org.
Page size can be reduced by 1.3 MB (47%)
2.8 MB
1.5 MB
In fact, the total size of Fntc.org main page is 2.8 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. 40% of websites need less resources to load. Images take 1.3 MB which makes up the majority of the site volume.
Potential reduce by 60.2 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 16.4 kB, which is 23% 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 60.2 kB or 83% of the original size.
Potential reduce by 123.4 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. FNTC images are well optimized though.
Potential reduce by 480.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 480.9 kB or 69% of the original size.
Potential reduce by 652.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. Fntc.org needs all CSS files to be minified and compressed as it can save up to 652.8 kB or 84% of the original size.
Number of requests can be reduced by 73 (64%)
114
41
The browser has sent 114 CSS, Javascripts, AJAX and image requests in order to completely render the main page of FNTC. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 29 to 1 for JavaScripts and from 36 to 1 for CSS and as a result speed up the page load time.
fntc.org
265 ms
fntc.org
369 ms
www.fntc.org
1742 ms
k2.css
95 ms
widgetkit-992ee359.css
185 ms
menu-c90d860e34be848c54002775c9378ef5.css
277 ms
grid-responsive.css
342 ms
grid-responsive.css
339 ms
master-4a5a58d1836c3251bc3a58676f8d8c51.css
359 ms
master-c90087d7230d1a7585e1be71c6e43a69.css
376 ms
master-d0a7827d3a4c3670dcbb3f1b54e32420.css
394 ms
style2.css
392 ms
mediaqueries.css
420 ms
css
63 ms
gantry-custom.css
423 ms
btcontentslider.css
447 ms
style3.css
456 ms
showcase.css
450 ms
rokajaxsearch.css
454 ms
rokajaxsearch-theme.css
504 ms
headlines.css
506 ms
style2.0.css
535 ms
mootools-core.js
548 ms
core.js
545 ms
jquery.min.js
91 ms
k2.js
547 ms
caption.js
586 ms
jquery.js
684 ms
widgetkit-2700078e.js
622 ms
mootools-more.js
822 ms
browser-engines.js
638 ms
rokmediaqueries.js
635 ms
load-transition.js
670 ms
rokmediaqueries.js
712 ms
responsive.js
721 ms
responsive-selectbox.js
727 ms
slides.js
758 ms
default.js
767 ms
jquery.easing.1.3.js
800 ms
engine.mootools.js
809 ms
mootools-mobile.js
813 ms
rokmediaqueries.js
763 ms
roksprocket.js
679 ms
css
25 ms
moofx.js
630 ms
features.js
576 ms
showcase.js
583 ms
bottom-.less
545 ms
button-.less
550 ms
header-.less
538 ms
rokajaxsearch.js
586 ms
headlines.js
581 ms
template.css
588 ms
jquery.simplemodal.js
575 ms
default.js
1088 ms
roksprocket.css
91 ms
kunena.css
95 ms
button-styles.css
98 ms
pricing-tables-styles.css
91 ms
table-styles.css
88 ms
demo-styles.css
172 ms
bt-login.css
174 ms
tab-slide-styles.css
182 ms
acymailing_module_default.css
174 ms
news_showpro_gk4.css
182 ms
image_show_gk4.css
259 ms
css
15 ms
css
22 ms
css
23 ms
css
26 ms
lightbox.js
96 ms
mediaelement-and-player.js
98 ms
spotlight.js
92 ms
bg_body.jpg
375 ms
bg_shadow_container01.png
295 ms
bg_top_container.png
386 ms
icon_user_login.png
96 ms
bandeau_930x305_formations_dcembre%202015.jpg
468 ms
bandeau%20bigdata2.jpg
461 ms
bandeau_930x305_nouveaux%20guides.jpg
562 ms
bandeau%20accueil_FNTC%20master-15sept14.jpg
954 ms
bandeau%20conference%20compac%202.jpg
840 ms
CEV_Cachet%20Electronique%20Visible_3%20fvrier%202015.jpg
939 ms
TTP11bis.jpg
1366 ms
TTP_tiff.jpg
1015 ms
drapeau____anglais_mini.png
848 ms
drapeau%20espagnol.JPG
1131 ms
mini%20bandeaux%20trophes%202015.jpg
1138 ms
guide%20RIC.jpg
1227 ms
annuaire_labels_vert_350.jpg
1329 ms
150x40-modele150.jpg
1299 ms
150x40-UFHJ%20bandeau.png
1419 ms
150x40-ADEC.png
1416 ms
150x40-cs_web.jpg
1516 ms
150x40-OpenBee_FNTC.png
1587 ms
150x40-CVTrust_150_40.png
1616 ms
150x40-Sood.png
1646 ms
150x40-weproov.png
1694 ms
150x40-labanquepostale.png
1706 ms
150x40-eurovote_150x40.png
1803 ms
150x40-dhatim_150x40.png
1864 ms
150x40-mgmr.png
1903 ms
social-icons.png
1899 ms
bg_header_container.png
2022 ms
fntc_new.png
1950 ms
bg_mainmenu.png
2057 ms
bg_mainmenu_hover.png
2109 ms
menu_separator.png
2158 ms
bg_showcase.png
1984 ms
guC5lwT5Dw7anV_xfpCGqw.ttf
16 ms
yUkc6bor5XCjwNWLpzDf8Q.ttf
159 ms
analytics.js
141 ms
fontawesome-webfont.woff
2143 ms
collect
12 ms
search-icon.png
2016 ms
bg_feature_container.png
1778 ms
module_arrows.png
2016 ms
bg_footer.png
1980 ms
bg_bottom.jpg
1964 ms
bg_acymailing_module_button.png
1729 ms
bg-header.png
1545 ms
150x40-modele150.jpg
1739 ms
loading.gif
1715 ms
fntc.org accessibility score
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
<frame> or <iframe> elements do not have a title
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
fntc.org best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Missing source maps for large first-party JavaScript
fntc.org SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
robots.txt is not valid
N/A
FR
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Fntc.org 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), while the claimed language is French. Our system also found out that Fntc.org 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.
fntc.org
Open Graph description is not detected on the main page of FNTC. 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: