2.7 sec in total
306 ms
2 sec
418 ms
Click here to check amazing Farago content. Otherwise, check out these important facts you probably never knew about farago.ch
Top-Domains - Finden Sie Ihre .ch, .li, .com, .de, .at, .biz, .org, .xxx Wunschdomain.
Visit farago.chWe analyzed Farago.ch page load time and found that the first response time was 306 ms and then it took 2.4 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.
farago.ch performance score
name
value
score
weighting
Value8.9 s
0/100
10%
Value10.9 s
0/100
25%
Value9.7 s
10/100
10%
Value90 ms
99/100
30%
Value0.016
100/100
15%
Value10.0 s
26/100
10%
306 ms
192 ms
230 ms
80 ms
157 ms
Our browser made a total of 60 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Farago.ch, 85% (51 requests) were made to Top-domains.ch and 3% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (620 ms) relates to the external source Top-domains.ch.
Page size can be reduced by 387.7 kB (77%)
502.4 kB
114.8 kB
In fact, the total size of Farago.ch main page is 502.4 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. 20% of websites need less resources to load. Javascripts take 389.2 kB which makes up the majority of the site volume.
Potential reduce by 33.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. 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 33.0 kB or 82% of the original size.
Potential reduce by 247 B
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. Farago images are well optimized though.
Potential reduce by 300.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 300.8 kB or 77% of the original size.
Potential reduce by 53.6 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. Farago.ch needs all CSS files to be minified and compressed as it can save up to 53.6 kB or 80% of the original size.
Number of requests can be reduced by 45 (80%)
56
11
The browser has sent 56 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Farago. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 19 to 1 for JavaScripts and from 20 to 1 for CSS and as a result speed up the page load time.
farago.ch
306 ms
farago.ch
192 ms
farago.ch
230 ms
lightbox.css
80 ms
lightbox_blue.css
157 ms
popup.css
158 ms
style.css
161 ms
topnummer.css
164 ms
basic.css
156 ms
content.css
165 ms
fonts.css
232 ms
forms.css
232 ms
navigation.css
233 ms
portlets.css
237 ms
picker.js
237 ms
calendar.js
238 ms
calendar_de.js
308 ms
prototype.js
620 ms
scriptaculous.js
309 ms
phpcomasy.js
312 ms
popup.js
392 ms
lightbox.js
315 ms
reflection.js
386 ms
selectreplace.js
388 ms
atrk.js
56 ms
a
53 ms
helper.css
235 ms
basic.css
238 ms
management.css
308 ms
content.css
310 ms
modules.css
312 ms
forms.css
316 ms
calendar.css
316 ms
builder.js
79 ms
effects.js
159 ms
dragdrop.js
83 ms
controls.js
85 ms
slider.js
86 ms
sound.js
85 ms
ga.js
19 ms
btn-SL-certified.gif
18 ms
atrk.gif
99 ms
header_bg.gif
82 ms
navigations_bg.gif
81 ms
navi_right.png
81 ms
navi_left.png
80 ms
button_right.png
82 ms
button_left.png
81 ms
content_top.gif
157 ms
portlet_bottom.gif
160 ms
portlet_top.gif
158 ms
test.png
183 ms
s.gif
33 ms
__utm.gif
41 ms
footer_top.gif
115 ms
loading.gif
115 ms
arrow_select.gif
117 ms
ellipsoideogram-webfont.woff
192 ms
style_print.css
79 ms
print.css
78 ms
farago.ch 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.
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
Form elements do not have associated labels
Links do not have a discernible name
farago.ch best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
farago.ch SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
DE
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Farago.ch can be misinterpreted by Google and other search engines. Our service has detected that German 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 Farago.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.
farago.ch
Open Graph description is not detected on the main page of Farago. 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: