3.3 sec in total
304 ms
2.6 sec
388 ms
Click here to check amazing BAUWIKI content for Germany. Otherwise, check out these important facts you probably never knew about bau-wiki.de
BAUWIKI - Die Wissensdatenbank für Innentüren, Haustüren, Dachfenster und Garagentore mit großer Tür-Ausstellung, Tor-Ausstellung und Fenster-Ausstellung.
Visit bau-wiki.deWe analyzed Bau-wiki.de page load time and found that the first response time was 304 ms and then it took 3 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
bau-wiki.de performance score
name
value
score
weighting
Value3.3 s
41/100
10%
Value13.3 s
0/100
25%
Value11.5 s
5/100
10%
Value14,200 ms
0/100
30%
Value0.007
100/100
15%
Value19.4 s
2/100
10%
304 ms
686 ms
101 ms
199 ms
201 ms
Our browser made a total of 59 requests to load all elements on the main page. We found that 88% of them (52 requests) were addressed to the original Bau-wiki.de, 3% (2 requests) were made to Stats.g.doubleclick.net and 3% (2 requests) were made to Google.com. The less responsive or slowest element that took the longest time to load (776 ms) belongs to the original domain Bau-wiki.de.
Page size can be reduced by 511.1 kB (29%)
1.8 MB
1.2 MB
In fact, the total size of Bau-wiki.de main page is 1.8 MB. 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. Images take 1.1 MB which makes up the majority of the site volume.
Potential reduce by 35.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. This page needs HTML code to be minified as it can gain 15.2 kB, which is 36% 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 35.8 kB or 85% of the original size.
Potential reduce by 1.7 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. BAUWIKI images are well optimized though.
Potential reduce by 233.4 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 233.4 kB or 70% of the original size.
Potential reduce by 240.1 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. Bau-wiki.de needs all CSS files to be minified and compressed as it can save up to 240.1 kB or 84% of the original size.
Number of requests can be reduced by 13 (24%)
55
42
The browser has sent 55 CSS, Javascripts, AJAX and image requests in order to completely render the main page of BAUWIKI. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 4 to 1 for JavaScripts and from 11 to 1 for CSS and as a result speed up the page load time.
bau-wiki.de
304 ms
www.bau-wiki.de
686 ms
news-basic.css
101 ms
normalize.css
199 ms
style.css
201 ms
grid.css
197 ms
layout.css
296 ms
jquery.fancybox-1.3.4.css
202 ms
global.css
303 ms
extend.css
294 ms
bauwiki.css
491 ms
litebox.css
300 ms
vhs-assets-foundationcss-bauwiki-legacycss-bauwikicss.css
591 ms
vhs-assets-modernizerjs-picturefill.js
484 ms
conversion.js
13 ms
vhs-assets-jqueryjs-terrificjs-matchmediajs-matchmedialistenerjs-fastclickjs-ssmjs-selectricjs-resizeimagetoparentjs-functions-setup-tcdefaultjs-inlinejs.js
776 ms
dc.js
30 ms
__utm.gif
13 ms
ga-audiences
156 ms
staticmap
289 ms
bauwiki_logo.png
101 ms
bauwiki_logo_print.png
104 ms
bauwiki_sprite.png
102 ms
csm_slider_2_innentueren_c71e8d42dd.jpg
102 ms
csm_slider_haustueren_8ab90e6ac0.jpg
107 ms
csm_slider_garagen_ea693af6cc.jpg
198 ms
csm_teaser_startseite_tueren_2d8e105ea9.jpg
200 ms
csm_teaser_startseite_tueren2_02f0395b78.jpg
197 ms
csm_teaser_startseite_tueren3_8bc9232086.jpg
200 ms
csm_teaser_startseite_tueren4_6bfc40c545.jpg
211 ms
csm_teaser_startseite_tueren5_da73d61085.jpg
240 ms
csm_teaser_startseite_tueren6_2ae9120e7d.jpg
295 ms
csm_teaser_startseite_haustueren_77e9a3d303.jpg
297 ms
csm_teaser_startseite_haustueren1_fd0d4038f0.jpg
294 ms
csm_teaser_startseite_haustueren2_8ba982bbe0.jpg
299 ms
csm_teaser_startseite_haustueren3_95d40b8076.jpg
315 ms
csm_teaser_startseite_haustueren4_f95e1b30cd.jpg
331 ms
csm_teaser_startseite_haustueren5_b169362ef5.jpg
395 ms
csm_teaser_startseite_tore_16d44a556f.jpg
396 ms
csm_teaser_startseite_tore2_533050f854.jpg
395 ms
csm_teaser_startseite_tore3_51fcc5be2d.jpg
397 ms
csm_teaser_startseite_tore4_d9183c6bfa.jpg
409 ms
csm_teaser_startseite_tore5_90934ff06a.jpg
424 ms
csm_teaser_startseite_tore6_8b339bd2b9.jpg
489 ms
csm_Altera_weiss_lackiert_glas_satinato_0eb8b702e5.jpg
489 ms
hautueren_teaser_right.jpg
489 ms
tor_teaser_right.jpg
491 ms
csm_teaser_stilfinder_heigher_52fe0da471.jpg
513 ms
csm_wohngesunde_innentueren_1_702x350_413f44f0bb.jpg
523 ms
csm_Ausbau_der_alten_Zarge_9582e9049c_fc8c956252.jpg
583 ms
41 ms
vhs-assets-css-4d9e143f7e6d6e0de0e890b36510e0f5.woff
624 ms
MaterialIcons-Regular.woff
526 ms
16 ms
slick.js
441 ms
csm_slider_2_innentueren_cc85a29a8b.jpg
722 ms
csm_slider_haustueren_ff443b8683.jpg
681 ms
csm_slider_garagen_8475659402.jpg
650 ms
vhs-assets-css-fbb1af98955caad63b96a41159b62aea.gif
101 ms
bau-wiki.de 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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
Form elements do not have associated labels
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.
bau-wiki.de 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
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
bau-wiki.de SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
robots.txt is not valid
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 Bau-wiki.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 Bau-wiki.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.
bau-wiki.de
Open Graph description is not detected on the main page of BAUWIKI. 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: