5.6 sec in total
295 ms
5 sec
306 ms
Visit waldbrandgefahr.ch now to see the best up-to-date Waldbrandgefahr content for Switzerland and also check out these interesting facts you probably never knew about waldbrandgefahr.ch
Übersicht der Waldbrandgefahrenlagen und Massnahmen in den Kantonen und dem Fürstentum Liechtenstein
Visit waldbrandgefahr.chWe analyzed Waldbrandgefahr.ch page load time and found that the first response time was 295 ms and then it took 5.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster. This domain responded with an error, which can significantly jeopardize Waldbrandgefahr.ch rating and web reputation
waldbrandgefahr.ch performance score
name
value
score
weighting
Value4.2 s
20/100
10%
Value16.4 s
0/100
25%
Value9.0 s
14/100
10%
Value250 ms
84/100
30%
Value1.164
1/100
15%
Value12.9 s
13/100
10%
295 ms
1505 ms
195 ms
200 ms
195 ms
Our browser made a total of 45 requests to load all elements on the main page. We found that 87% of them (39 requests) were addressed to the original Waldbrandgefahr.ch, 11% (5 requests) were made to Fast.fonts.net and 2% (1 request) were made to Ajax.googleapis.com. The less responsive or slowest element that took the longest time to load (1.5 sec) belongs to the original domain Waldbrandgefahr.ch.
Page size can be reduced by 543.0 kB (74%)
729.5 kB
186.5 kB
In fact, the total size of Waldbrandgefahr.ch main page is 729.5 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 506.5 kB which makes up the majority of the site volume.
Potential reduce by 11.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. This page needs HTML code to be minified as it can gain 3.2 kB, which is 22% 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 11.7 kB or 81% of the original size.
Potential reduce by 2.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. Obviously, Waldbrandgefahr needs image optimization as it can save up to 2.4 kB or 21% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 364.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 364.7 kB or 72% of the original size.
Potential reduce by 164.3 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. Waldbrandgefahr.ch needs all CSS files to be minified and compressed as it can save up to 164.3 kB or 83% of the original size.
Number of requests can be reduced by 33 (83%)
40
7
The browser has sent 40 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Waldbrandgefahr. 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 18 to 1 for CSS and as a result speed up the page load time.
waldbrandgefahr.ch
295 ms
1505 ms
stylesheet_15e5175da3.css
195 ms
reset.css
200 ms
smoothness.min.css
195 ms
styles.css
198 ms
layout.css
196 ms
menu.css
200 ms
rte.css
387 ms
extensions.css
388 ms
gridelements.css
389 ms
jquery.fancybox.css
388 ms
flexslider.css
388 ms
9a75de7b-d960-4a65-9c53-6bc24de853c0.css
63 ms
responsive.css
388 ms
javascript_b9ac716825.js
575 ms
jquery.min.js
6 ms
jquery.datetimepicker.js
579 ms
parsley.min.js
577 ms
tabs.js
574 ms
form.js
580 ms
powermail_frontend.js
579 ms
jquery-1.10.2-min.js
879 ms
jquery.scrollTo-1.4.2-min.js
778 ms
jquery.mousewheel-3.0.6-pack.js
777 ms
jquery.fancybox-2.1.5-pack.js
778 ms
jquery.ui-1.10.3-min.js
881 ms
jquery.flexslider-min.js
782 ms
iframeResizer.min.js
966 ms
jquery.begasoft.js
968 ms
reset.css
781 ms
aktuelle_lage.jsf
428 ms
logo_suisse.png
194 ms
3fbbd6b1-cfa7-4ff0-97ea-af1b2c489f15.woff
68 ms
9aa32a81-1124-4c43-b3db-15bfb1f7aed2.woff
86 ms
print.css
207 ms
theme.css.jsf
217 ms
reset.css
202 ms
styles.css
202 ms
iframeResizer.contentWindows.js
202 ms
9a75de7b-d960-4a65-9c53-6bc24de853c0.js
33 ms
gefahrenkarte.gif;jsessionid=43B147A452B23FE7847076940948EAC4
575 ms
stufe1.png;jsessionid=43B147A452B23FE7847076940948EAC4
233 ms
stufe2.png;jsessionid=43B147A452B23FE7847076940948EAC4
232 ms
af97a512-f55a-4f61-b2ce-659c883930fc.eot
36 ms
waldbrandgefahr.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
[aria-*] attributes do not match their roles
waldbrandgefahr.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
Missing source maps for large first-party JavaScript
waldbrandgefahr.ch SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Page is blocked from indexing
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 Waldbrandgefahr.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 Waldbrandgefahr.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.
waldbrandgefahr.ch
Open Graph description is not detected on the main page of Waldbrandgefahr. 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: