4.7 sec in total
716 ms
3.7 sec
284 ms
Click here to check amazing Passivhaus content for Germany. Otherwise, check out these important facts you probably never knew about passivhaus.de
Unser Schwerpunkt liegt bei der Architektur- und TGA-Planung von Wohn- und Nichtwohngebäuden im Passivhausstandard oder als Plusenergiegebäude.
Visit passivhaus.deWe analyzed Passivhaus.de page load time and found that the first response time was 716 ms and then it took 4 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
passivhaus.de performance score
name
value
score
weighting
Value2.5 s
67/100
10%
Value10.2 s
0/100
25%
Value9.5 s
11/100
10%
Value2,820 ms
3/100
30%
Value0.075
95/100
15%
Value13.3 s
12/100
10%
716 ms
200 ms
306 ms
274 ms
22 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 Passivhaus.de, 6% (2 requests) were made to Cdn.jsdelivr.net and 3% (1 request) were made to Use.fontawesome.com. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Passivhaus.de.
Page size can be reduced by 80.9 kB (3%)
2.6 MB
2.5 MB
In fact, the total size of Passivhaus.de main page is 2.6 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. 35% of websites need less resources to load. Images take 1.5 MB which makes up the majority of the site volume.
Potential reduce by 80.5 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 80.5 kB or 78% of the original size.
Potential reduce by 0 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. Passivhaus images are well optimized though.
Potential reduce by 16 B
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. This website has mostly compressed JavaScripts.
Potential reduce by 394 B
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. Passivhaus.de has all CSS files already compressed.
Number of requests can be reduced by 7 (37%)
19
12
The browser has sent 19 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Passivhaus. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 8 to 1 for JavaScripts and as a result speed up the page load time.
www.passivhaus.de
716 ms
jquery.min.js
200 ms
jquery-migrate.min.js
306 ms
lyte-min.js
274 ms
jquery.scrollTo.min.js
22 ms
jquery.localScroll.min.js
24 ms
core.min.js
282 ms
tabs.min.js
293 ms
autoptimize_4d38b415250c559dfeedd0b86e300d09.js
957 ms
all.css
45 ms
box_shadow.png
302 ms
Daenischer-Pavillon_aussen_schmal_kl.jpg
558 ms
Grundschule-Gronau.jpg
878 ms
Modul-Kita_1.jpg
838 ms
LSB-Hannover_r.jpg
866 ms
Bildungszentrum-Bad-Bederkesa_r.jpg
897 ms
Architekt.jpg
761 ms
open-sans-normal-latin-ext.woff2
856 ms
istok-web-normal-latin-ext-400.woff2
668 ms
istok-web-normal-latin-ext-700.woff2
735 ms
open-sans-italic-latin-ext.woff2
735 ms
mfn-icons.woff
1105 ms
roboto-normal-latin-ext-400.woff2
735 ms
roboto-normal-latin-ext-500.woff2
764 ms
roboto-normal-latin-ext-300.woff2
787 ms
roboto-normal-latin-ext-100.woff2
798 ms
roboto-normal-latin-ext-700.woff2
813 ms
autoptimize_cb599c7b4743b4ac7490d9de25cd74fb.css
208 ms
mfn-icons.ttf
584 ms
roboto-italic-latin-ext-400.woff2
104 ms
icons.woff
191 ms
lyteCache.php
105 ms
lytesprite.png
109 ms
mfn-icons.svg
367 ms
passivhaus.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.
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
List items (<li>) are not contained within <ul> or <ol> parent elements.
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.
passivhaus.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
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
passivhaus.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
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 Passivhaus.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 Passivhaus.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.
passivhaus.de
Open Graph data is detected on the main page of Passivhaus. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: