5.2 sec in total
309 ms
3.7 sec
1.2 sec
Visit fcl.ch now to see the best up-to-date FC L content for Switzerland and also check out these interesting facts you probably never knew about fcl.ch
Hier erfahren Sie top aktuell und aus erster Hand spannendes und wissenswertes rund um den FC Luzern.
Visit fcl.chWe analyzed Fcl.ch page load time and found that the first response time was 309 ms and then it took 4.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
fcl.ch performance score
name
value
score
weighting
Value4.7 s
12/100
10%
Value17.1 s
0/100
25%
Value17.0 s
0/100
10%
Value7,340 ms
0/100
30%
Value0.345
32/100
15%
Value41.7 s
0/100
10%
309 ms
629 ms
246 ms
107 ms
30 ms
Our browser made a total of 62 requests to load all elements on the main page. We found that 37% of them (23 requests) were addressed to the original Fcl.ch, 27% (17 requests) were made to D1mjaohu992wjw.cloudfront.net and 24% (15 requests) were made to Imgs.creanet.ch. The less responsive or slowest element that took the longest time to load (1 sec) relates to the external source D1mjaohu992wjw.cloudfront.net.
Page size can be reduced by 388.1 kB (29%)
1.3 MB
929.1 kB
In fact, the total size of Fcl.ch 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. 40% of websites need less resources to load. Images take 826.6 kB which makes up the majority of the site volume.
Potential reduce by 76.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 18.1 kB, which is 20% 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 76.3 kB or 84% of the original size.
Potential reduce by 10.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. FC L images are well optimized though.
Potential reduce by 156.8 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 156.8 kB or 68% of the original size.
Potential reduce by 144.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. Fcl.ch needs all CSS files to be minified and compressed as it can save up to 144.7 kB or 85% of the original size.
Number of requests can be reduced by 11 (28%)
40
29
The browser has sent 40 CSS, Javascripts, AJAX and image requests in order to completely render the main page of FC L. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 9 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
fcl.ch
309 ms
home
629 ms
dscss_50170.css
246 ms
css
107 ms
font-awesome.min.css
30 ms
combined_50170.css
883 ms
jquery-1.7.2.min.js
974 ms
creanetlibrary.min.js
743 ms
creanetGallery.min.js
740 ms
creanetContentSlider.min.js
726 ms
formcheck.min.js
724 ms
shadowbox.js
976 ms
dropdownmenu.min.js
819 ms
isotope.min.js
995 ms
radio.min.js
825 ms
background_1700_1900.jpg
989 ms
fcl_logo.png
208 ms
blind.gif
207 ms
EEE54A27-9706-3840-0C659F23463FF014.jpg
651 ms
839838E1-CF3A-FC4C-3BE86976E14FC2A2.jpg
617 ms
cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf
214 ms
DXI1ORHCpsQm3Vp6mXoaTYnF5uFdDttMLvmWuJdhhgs.ttf
240 ms
MTP_ySUJH_bn48VBG8sNSonF5uFdDttMLvmWuJdhhgs.ttf
285 ms
k3k702ZOKiLJc3WVjuplzInF5uFdDttMLvmWuJdhhgs.ttf
285 ms
C9EFCD14-E47B-3F43-DE63A6129F6774EF.jpg=s207
841 ms
dynasite.cfm
371 ms
dynasite.cfm
406 ms
dynasite.cfm
512 ms
dynasite.cfm
475 ms
loadingcircle.gif
313 ms
9E02E73D-03FC-B956-71BA1D9BF55CD1E6.jpg=s207
760 ms
ACC32D6C-F7A2-5E53-D41ACDBE555F80C9.jpg=x96
803 ms
849C4FAE-E7BA-3735-3AEE6A205BD4F03D.jpg=x96
802 ms
BDE579DB-DCAC-EFDE-1A30E0FC77023BDD.jpg=x96
801 ms
photo_290814195801937.gif=x96
859 ms
81F79A27-D89C-F628-B416A19BB4DA6AB5.jpg=x96
859 ms
fontawesome-webfont.woff
8 ms
ECB98C28-AFD7-5038-F1BBFD739235B064.png=x60
609 ms
608F9E7A-A1A0-CA54-3AB95836DF7B66CC.png=x60
622 ms
609A93AB-92C0-049C-10F896901DEAC091.png=x60
605 ms
photo_260814083122602.png=x60
622 ms
ECB83D34-DD01-5211-64B06274FCAC63FB.png=x60
622 ms
ECB6A1BE-AE44-8CEC-2669B996E9474068.png=x60
624 ms
photo_210914122825324.png=x60
637 ms
83999007-A021-FAF8-6F111BE9740EBC59.jpg=s1000
496 ms
C9EFCD14-E47B-3F43-DE63A6129F6774EF.jpg=s207
1017 ms
9D6C979A-9A50-B6CA-9E05F28FDCF0AF6E.jpg=s207
997 ms
CA5F4526-E517-2D65-2F1B958996FDF7B0.jpg=s207
876 ms
9E02E73D-03FC-B956-71BA1D9BF55CD1E6.jpg=s207
964 ms
849C4FAE-E7BA-3735-3AEE6A205BD4F03D.jpg=x96
143 ms
BDE579DB-DCAC-EFDE-1A30E0FC77023BDD.jpg=x96
144 ms
ACC32D6C-F7A2-5E53-D41ACDBE555F80C9.jpg=x96
141 ms
photo_290814195801937.gif=x96
87 ms
81F79A27-D89C-F628-B416A19BB4DA6AB5.jpg=x96
87 ms
ECB98C28-AFD7-5038-F1BBFD739235B064.png=x60
77 ms
609A93AB-92C0-049C-10F896901DEAC091.png=x60
75 ms
608F9E7A-A1A0-CA54-3AB95836DF7B66CC.png=x60
75 ms
photo_260814083122602.png=x60
140 ms
ECB83D34-DD01-5211-64B06274FCAC63FB.png=x60
64 ms
ECB6A1BE-AE44-8CEC-2669B996E9474068.png=x60
139 ms
photo_210914122825324.png=x60
129 ms
83999007-A021-FAF8-6F111BE9740EBC59.jpg=s1000
195 ms
fcl.ch 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
Buttons do not have an accessible name
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
Links do not have a discernible name
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
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>).
fcl.ch 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
Displays images with incorrect aspect ratio
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
fcl.ch 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
Tap targets are not sized appropriately
DE
DE
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Fcl.ch can be misinterpreted by Google and other search engines. Our service has detected that German is used on the page, and it matches the claimed language. Our system also found out that Fcl.ch 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.
fcl.ch
Open Graph description is not detected on the main page of FC L. 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: