2.6 sec in total
534 ms
1.5 sec
482 ms
Visit barrierekompass.de now to see the best up-to-date Barrierekompass content for Germany and also check out these interesting facts you probably never knew about barrierekompass.de
Ist meine Internetseite barrierefrei oder bietet sie Hürden und Barrieren für behinderte Menschen und Senioren? Barrierefreies Webdesign, PDF, Dokumente oder Formulare für den öffentlichen Sektor (eGo...
Visit barrierekompass.deWe analyzed Barrierekompass.de page load time and found that the first response time was 534 ms and then it took 2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.
barrierekompass.de performance score
name
value
score
weighting
Value2.1 s
80/100
10%
Value2.5 s
89/100
25%
Value5.6 s
53/100
10%
Value1,190 ms
21/100
30%
Value0.431
22/100
15%
Value6.4 s
59/100
10%
534 ms
137 ms
386 ms
305 ms
302 ms
Our browser made a total of 34 requests to load all elements on the main page. We found that 91% of them (31 requests) were addressed to the original Barrierekompass.de, 9% (3 requests) were made to Piwik.anatom5.de. The less responsive or slowest element that took the longest time to load (534 ms) belongs to the original domain Barrierekompass.de.
Page size can be reduced by 124.2 kB (45%)
277.3 kB
153.1 kB
In fact, the total size of Barrierekompass.de main page is 277.3 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 146.0 kB which makes up the majority of the site volume.
Potential reduce by 12.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 12.2 kB or 71% of the original size.
Potential reduce by 149 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. Barrierekompass images are well optimized though.
Potential reduce by 92.5 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 92.5 kB or 63% of the original size.
Potential reduce by 19.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. Barrierekompass.de needs all CSS files to be minified and compressed as it can save up to 19.3 kB or 78% of the original size.
Number of requests can be reduced by 11 (46%)
24
13
The browser has sent 24 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Barrierekompass. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 6 to 1 for JavaScripts and as a result speed up the page load time.
barrierekompass.de
534 ms
layout.css
137 ms
jquery.js
386 ms
jquery-ui.custom.js
305 ms
jquery.syncheight.js
302 ms
jquery.colorbox.js
217 ms
jquery.init.js
218 ms
logo_barrierekompass.png
302 ms
btn_search-submit.png
331 ms
package_test.png
460 ms
package_pdf.png
465 ms
package_web.png
475 ms
barrierekompass_fotolia_7829651.jpg
491 ms
piwik.php
491 ms
bg.png
308 ms
bg_nav-site.png
351 ms
bg_search-input.png
399 ms
bg_teaser.png
407 ms
bg_footer.gif
441 ms
aller_bd-webfont.woff
412 ms
aller_rg-webfont.woff
417 ms
aller_lt-webfont.woff
417 ms
aller_bdit-webfont.woff
357 ms
aller_it-webfont.woff
370 ms
aller_ltit-webfont.woff
398 ms
piwik.js
210 ms
ico_ext.png
312 ms
piwik.php
187 ms
aller_bdit-webfont.ttf
109 ms
aller_it-webfont.ttf
130 ms
aller_ltit-webfont.ttf
120 ms
aller_bdit-webfont.svg
121 ms
aller_it-webfont.svg
112 ms
aller_ltit-webfont.svg
124 ms
barrierekompass.de accessibility score
barrierekompass.de 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
Page has valid source maps
barrierekompass.de 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 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 Barrierekompass.de 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 Barrierekompass.de 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.
barrierekompass.de
Open Graph description is not detected on the main page of Barrierekompass. 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: