3.2 sec in total
319 ms
2.6 sec
301 ms
Welcome to fci.be homepage info - get ready to check Fci best content for Spain right away, or after learning these important things about fci.be
Visit fci.beWe analyzed Fci.be page load time and found that the first response time was 319 ms and then it took 2.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
fci.be performance score
name
value
score
weighting
Value5.2 s
8/100
10%
Value20.7 s
0/100
25%
Value7.7 s
24/100
10%
Value180 ms
92/100
30%
Value0.011
100/100
15%
Value11.0 s
21/100
10%
319 ms
657 ms
248 ms
345 ms
518 ms
Our browser made a total of 67 requests to load all elements on the main page. We found that 72% of them (48 requests) were addressed to the original Fci.be, 15% (10 requests) were made to Static.xx.fbcdn.net and 3% (2 requests) were made to Facebook.com. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Fci.be.
Page size can be reduced by 653.3 kB (51%)
1.3 MB
618.9 kB
In fact, the total size of Fci.be main page is 1.3 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. 55% of websites need less resources to load. Javascripts take 646.2 kB which makes up the majority of the site volume.
Potential reduce by 38.6 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.4 kB, which is 11% 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 38.6 kB or 67% of the original size.
Potential reduce by 36.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. Fci images are well optimized though.
Potential reduce by 530.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 530.5 kB or 82% of the original size.
Potential reduce by 47.9 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. Fci.be needs all CSS files to be minified and compressed as it can save up to 47.9 kB or 77% of the original size.
Number of requests can be reduced by 18 (29%)
62
44
The browser has sent 62 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Fci. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 16 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
fci.be
319 ms
657 ms
StyleSheet.min.css
248 ms
font-awesome.min.css
345 ms
jquery-1.11.1.min.js
518 ms
jquery.mousewheel-3.0.6.pack.js
179 ms
bootstrap.min.css
278 ms
bootstrap.min.js
268 ms
jquery.carousel.min.js
331 ms
WebResource.axd
252 ms
ScriptResource.axd
568 ms
ScriptResource.axd
288 ms
logo.png
150 ms
dogdotcom.png
148 ms
search.png
149 ms
home.png
148 ms
VIS-FCI-EWC-1-2165.JPG
259 ms
VIS-FCI-EWC-123-2163.JPG
265 ms
VIS-D2F-0241-2050.JPG
1019 ms
banner-EDS-slider-1996.jpg
531 ms
EM-logo-1-2168.jpg
431 ms
fci-esh-2016-banner-2169.jpg
348 ms
image001-2237.jpg
364 ms
Cobby_en.png
361 ms
Fci.jpg
432 ms
NomenclatureStandards.jpg
450 ms
Membres.jpg
453 ms
Calendriers.jpg
520 ms
Reglements.jpg
517 ms
resultats.png
539 ms
Commissions.jpg
541 ms
Sante.png
598 ms
Affixes.png
603 ms
telechargement.png
619 ms
catalogue.png
627 ms
presse.jpg
629 ms
downactus.png
681 ms
partenariat.png
689 ms
sdk.js
67 ms
fci.jpg
561 ms
nomenclatureStandards.jpg
575 ms
calendriers.jpg
578 ms
reglements.jpg
625 ms
commissions.jpg
635 ms
FciYouth.png
646 ms
147 ms
puceactus.png
633 ms
xd_arbiter.php
132 ms
xd_arbiter.php
191 ms
calibri-light.woff
1095 ms
calibri-regular.woff
668 ms
calibri-bold.woff
680 ms
analytics.js
80 ms
collect
10 ms
page.php
458 ms
o_zjiOVHPPW.css
85 ms
_rx8naC75Dy.js
125 ms
t-KLv3gqZy0.js
142 ms
maPem_J3nWE.js
192 ms
10460318_10153010750832627_8797575199829890052_n.jpg
52 ms
428400_10151246319002627_162756180_n.jpg
12 ms
wL6VQj7Ab77.png
24 ms
CSXXCvknpgK.png
24 ms
R9a_DtVRZgv.js
18 ms
cUDgRFxaoIk.js
20 ms
0JBr1QHp8Gi.js
19 ms
kDOzhTr2W91.js
34 ms
fci.be 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
button, link, and menuitem elements do not have accessible names.
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
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
<input type="image"> elements do not have [alt] text
Links do not have a discernible name
fci.be 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
fci.be 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
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Fci.be can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Fci.be 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.
fci.be
Open Graph description is not detected on the main page of Fci. 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: