4.3 sec in total
1 sec
3 sec
231 ms
Visit gigaherz.ch now to see the best up-to-date Gigaherz content for Germany and also check out these interesting facts you probably never knew about gigaherz.ch
Visit gigaherz.chWe analyzed Gigaherz.ch page load time and found that the first response time was 1 sec and then it took 3.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
gigaherz.ch performance score
name
value
score
weighting
Value4.7 s
12/100
10%
Value6.3 s
10/100
25%
Value6.9 s
33/100
10%
Value1,160 ms
22/100
30%
Value0.07
96/100
15%
Value7.0 s
53/100
10%
1045 ms
179 ms
196 ms
289 ms
293 ms
Our browser made a total of 47 requests to load all elements on the main page. We found that 85% of them (40 requests) were addressed to the original Gigaherz.ch, 9% (4 requests) were made to Fonts.gstatic.com and 4% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (1 sec) belongs to the original domain Gigaherz.ch.
Page size can be reduced by 461.8 kB (52%)
889.5 kB
427.8 kB
In fact, the total size of Gigaherz.ch main page is 889.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. 40% of websites need less resources to load. Javascripts take 345.0 kB which makes up the majority of the site volume.
Potential reduce by 27.2 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 27.2 kB or 82% of the original size.
Potential reduce by 3.6 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. Gigaherz images are well optimized though.
Potential reduce by 235.0 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 235.0 kB or 68% of the original size.
Potential reduce by 195.9 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. Gigaherz.ch needs all CSS files to be minified and compressed as it can save up to 195.9 kB or 84% of the original size.
Number of requests can be reduced by 29 (71%)
41
12
The browser has sent 41 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Gigaherz. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 18 to 1 for JavaScripts and from 13 to 1 for CSS and as a result speed up the page load time.
www.gigaherz.ch
1045 ms
wp-emoji-release.min.js
179 ms
styles.css
196 ms
prettyPhoto.css
289 ms
tribe-events-full.min.css
293 ms
css
25 ms
css
39 ms
style.css
427 ms
font-awesome.css
293 ms
icomoon.css
273 ms
skin-override.css
385 ms
settings.css
464 ms
jquery.fancybox.css
386 ms
style.css
383 ms
jquery.js
578 ms
jquery-migrate.min.js
480 ms
jquery.prettyPhoto.js
575 ms
front.js
481 ms
fitvids.js
522 ms
jquery.fancybox.pack.js
560 ms
jquery.themepunch.showbizpro.min.js
672 ms
jquery.form.min.js
524 ms
scripts.js
544 ms
core.min.js
584 ms
widget.min.js
597 ms
accordion.min.js
655 ms
tabs.min.js
656 ms
jquery.hellobar.min.js
657 ms
jquery.mobile-menu.min.js
679 ms
functions.js
693 ms
logo-gigaherz.png
130 ms
berge.jpg
193 ms
hr_shadow.png
130 ms
Regierungsgeb%C3%A4ude-Schwyz-500x281.jpg
131 ms
nocebo-500x281.jpg
157 ms
Lauerz.jpg
172 ms
acebr-500x281.jpg
194 ms
rundbrief_94-1-500x281.jpg
195 ms
Ostermundigen3.jpg
216 ms
logo-gigaherz-w.png
254 ms
piwik.js
480 ms
cJZKeOuBrn4kERxqtaUH3T8E0i7KZn-EPnyo3HZu7kw.woff
5 ms
k3k702ZOKiLJc3WVjuplzHhCUOGz7vYGh680lGh-uXM.woff
9 ms
fontawesome-webfont.woff
232 ms
IczWvq5y_Cwwv_rBjOtT0w.woff
9 ms
JbtMzqLaYbbbCL9X6EvaIxsxEYwM7FgeyaSgU71cLG0.woff
8 ms
tribe-events-full-mobile.min.css
99 ms
gigaherz.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
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
gigaherz.ch best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
gigaherz.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 Gigaherz.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 Gigaherz.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.
gigaherz.ch
Open Graph description is not detected on the main page of Gigaherz. 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: