7.3 sec in total
1.2 sec
6 sec
129 ms
Visit volkshaus.ch now to see the best up-to-date Volkshaus content for Switzerland and also check out these interesting facts you probably never knew about volkshaus.ch
Volkshaus Zürich
Visit volkshaus.chWe analyzed Volkshaus.ch page load time and found that the first response time was 1.2 sec and then it took 6.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
volkshaus.ch performance score
name
value
score
weighting
Value2.4 s
71/100
10%
Value4.1 s
48/100
25%
Value4.4 s
74/100
10%
Value270 ms
82/100
30%
Value0.001
100/100
15%
Value4.7 s
80/100
10%
1199 ms
1443 ms
227 ms
640 ms
203 ms
Our browser made a total of 57 requests to load all elements on the main page. We found that 58% of them (33 requests) were addressed to the original Volkshaus.ch, 14% (8 requests) were made to Apis.google.com and 5% (3 requests) were made to S7.addthis.com. The less responsive or slowest element that took the longest time to load (1.6 sec) belongs to the original domain Volkshaus.ch.
Page size can be reduced by 362.2 kB (41%)
879.2 kB
516.9 kB
In fact, the total size of Volkshaus.ch main page is 879.2 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. 50% of websites need less resources to load. Javascripts take 466.3 kB which makes up the majority of the site volume.
Potential reduce by 51.8 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 51.8 kB or 70% of the original size.
Potential reduce by 12.8 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. Volkshaus images are well optimized though.
Potential reduce by 297.7 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 297.7 kB or 64% of the original size.
Number of requests can be reduced by 31 (56%)
55
24
The browser has sent 55 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Volkshaus. 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 as a result speed up the page load time.
volkshaus.ch
1199 ms
www.volkshaus.ch
1443 ms
48b3e2035edecb0640034a40d1409025-cache-plg_jch_optimize-4095d0adbac78e6165fd74736c557d5d.css
227 ms
48b3e2035edecb0640034a40d1409025-cache-plg_jch_optimize-2df16da4e7f66e66252f22f9203b81b5.js
640 ms
custom.js
203 ms
addthis_widget.js
10 ms
lightbox.js
1579 ms
mediaelement-and-player.js
1585 ms
spotlight.js
1576 ms
ga.js
23 ms
bg.gif
1562 ms
header.gif
1563 ms
csg-ed6fff83af0126c1ca9f2fcc208845d3.png
1562 ms
small-size.png
1563 ms
reset-size.png
1563 ms
big-size.png
1563 ms
search-icon.png
1564 ms
nav-bg.gif
1564 ms
nav-h.gif
1565 ms
treppen.jpg
1569 ms
top-m.gif
1564 ms
top-rt.gif
1564 ms
top-lt.gif
1565 ms
bottom-m.gif
1566 ms
bottom-rt.gif
1565 ms
bottom-lt.gif
1566 ms
mid.png
1566 ms
leitbild-volkshaus-zuerich-3eb13175a2.jpg
1567 ms
logo-iage.png
1566 ms
slideshow.js
210 ms
300lo.json
71 ms
de.js
46 ms
plusone.js
64 ms
all.js&version=v2.0
391 ms
close.png
107 ms
blank.gif
142 ms
sh.8e5f85691f9aaa082472a194.html
32 ms
__utm.gif
31 ms
cb=gapi.loaded_0
32 ms
cb=gapi.loaded_1
30 ms
fastbutton
92 ms
postmessageRelay
58 ms
cb=gapi.loaded_0
21 ms
cb=gapi.loaded_1
20 ms
theater_01.jpg
301 ms
volkshaus_nacht_02.jpg
401 ms
saal_gelb_01.jpg
305 ms
3193398744-postmessagerelay.js
22 ms
rpc:shindig_random.js
32 ms
cb=gapi.loaded_0
3 ms
117 ms
xd_arbiter.php
144 ms
xd_arbiter.php
270 ms
ping
53 ms
like.php
73 ms
qeKvIRsJabD.js
293 ms
LVx-xkvaJ0b.png
326 ms
volkshaus.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
Links do not have a discernible name
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
volkshaus.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
Browser errors were logged to the console
volkshaus.ch SEO score
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
DE
DE
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Volkshaus.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 Volkshaus.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.
volkshaus.ch
Open Graph description is not detected on the main page of Volkshaus. 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: