1.8 sec in total
282 ms
1.4 sec
140 ms
Welcome to fczforum.ch homepage info - get ready to check FCZForum best content for Switzerland right away, or after learning these important things about fczforum.ch
Visit fczforum.chWe analyzed Fczforum.ch page load time and found that the first response time was 282 ms and then it took 1.5 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 30% of websites can load faster.
fczforum.ch performance score
name
value
score
weighting
Value3.5 s
35/100
10%
Value4.2 s
44/100
25%
Value5.3 s
59/100
10%
Value3,820 ms
1/100
30%
Value0
100/100
15%
Value26.8 s
0/100
10%
282 ms
246 ms
9 ms
13 ms
11 ms
Our browser made a total of 85 requests to load all elements on the main page. We found that 53% of them (45 requests) were addressed to the original Fczforum.ch, 14% (12 requests) were made to Tpc.googlesyndication.com and 7% (6 requests) were made to Googleads.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (321 ms) relates to the external source Googleads.g.doubleclick.net.
Page size can be reduced by 224.5 kB (52%)
433.7 kB
209.2 kB
In fact, the total size of Fczforum.ch main page is 433.7 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. 45% of websites need less resources to load. Javascripts take 275.7 kB which makes up the majority of the site volume.
Potential reduce by 17.7 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. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 17.7 kB or 77% of the original size.
Potential reduce by 2.5 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. FCZForum images are well optimized though.
Potential reduce by 139.1 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 139.1 kB or 50% of the original size.
Potential reduce by 65.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. Fczforum.ch needs all CSS files to be minified and compressed as it can save up to 65.2 kB or 76% of the original size.
Number of requests can be reduced by 55 (73%)
75
20
The browser has sent 75 CSS, Javascripts, AJAX and image requests in order to completely render the main page of FCZForum. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 17 to 1 for JavaScripts and from 16 to 1 for CSS and as a result speed up the page load time.
fczforum.ch
282 ms
246 ms
stylesheet.css
9 ms
stylesheet.css
13 ms
profileleft.css
11 ms
afr.php
190 ms
ag.php
89 ms
jquery.min.js
20 ms
core.js
11 ms
forum_fn.js
8 ms
ajax.js
10 ms
phpbb_seo.js
10 ms
common.css
14 ms
links.css
16 ms
content.css
11 ms
buttons.css
18 ms
cp.css
16 ms
forms.css
18 ms
colours.css
18 ms
imageset.css
23 ms
imp
14 ms
imp
17 ms
imp
16 ms
imp
20 ms
imp
20 ms
bg_header.gif
4 ms
site_logo.gif
6 ms
icons_button.png
5 ms
icon_faq.gif
21 ms
icon_logout.gif
194 ms
icon_register.gif
20 ms
icon_home.gif
8 ms
phpbb-seo.png
18 ms
inv.gif
14 ms
inv.gif
11 ms
inv.gif
11 ms
inv.gif
11 ms
inv.gif
9 ms
afr.php
102 ms
afr.php
179 ms
analytics.js
60 ms
bg_list.gif
12 ms
gradient.gif
13 ms
forum_read.gif
25 ms
icon_topic_latest.gif
26 ms
bg_button.gif
25 ms
icon_delete_cookies.gif
25 ms
icon_team.gif
27 ms
icon_pm.gif
26 ms
loading.gif
28 ms
icon_search.gif
27 ms
adsbygoogle.js
24 ms
lg.php
95 ms
lg.php
91 ms
collect
32 ms
ca-pub-0072280697052441.js
111 ms
zrt_lookup.html
41 ms
show_ads_impl.js
58 ms
collect
94 ms
lg.php
110 ms
ads
231 ms
osd.js
14 ms
ads
143 ms
ads
153 ms
ads
321 ms
print.css
9 ms
responsive.css
25 ms
suggestion_autolayout_V2_7.css
67 ms
suggestion_autolayout_V2_7.js
77 ms
layout_engine.js
86 ms
abg.js
194 ms
css
135 ms
m_js_controller.js
188 ms
suggestion_autolayout_V2.css
15 ms
suggestion_autolayout_V2.js
94 ms
googlelogo_color_112x36dp.png
111 ms
6933574313795811046
86 ms
7236775735970716089
70 ms
s
56 ms
8573514214996375071
64 ms
x_button_blue2.png
40 ms
favicon
116 ms
nessie_icon_thin_arrow_big_white.png
23 ms
Hgo13k-tfSpn0qi1SFdUfbO3LdcAZYWl9Si6vvxL-qU.woff
82 ms
MdyApZkAHG2-UELdOwjNjjFZXSz-CGj4o1JtDR7aGgs.js
2 ms
fczforum.ch 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
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
[role]s are not contained by their required parent element
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>).
List items (<li>) are not contained within <ul> or <ol> parent elements.
fczforum.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
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
fczforum.ch 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 doesn't use 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 Fczforum.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 Fczforum.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.
fczforum.ch
Open Graph description is not detected on the main page of FCZForum. 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: