Tools & Wizards About Us
prohaus.com screenshot

Report Summary

  • 32

    Performance

    Renders faster than
    52% of other websites

  • 91

    Accessibility

    Visual factors better than
    that of 76% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

prohaus.com

ProHaus - ProHaus

Page Load Speed

3.6 sec in total

First Response

229 ms

Resources Loaded

3 sec

Page Rendered

379 ms

prohaus.com screenshot

About Website

Visit prohaus.com now to see the best up-to-date Pro Haus content for Germany and also check out these interesting facts you probably never knew about prohaus.com

Visit prohaus.com

Key Findings

We analyzed Prohaus.com page load time and found that the first response time was 229 ms and then it took 3.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.

Performance Metrics

prohaus.com performance score

32

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.2 s

42/100

10%

LCP (Largest Contentful Paint)

Value11.7 s

0/100

25%

SI (Speed Index)

Value8.9 s

15/100

10%

TBT (Total Blocking Time)

Value920 ms

30/100

30%

CLS (Cumulative Layout Shift)

Value0.028

100/100

15%

TTI (Time to Interactive)

Value11.3 s

19/100

10%

Network Requests Diagram

prohaus.com

229 ms

www.prohaus.com

1115 ms

183d1fa344.css

120 ms

Main.min.css

226 ms

Additional.min.css

314 ms

Our browser made a total of 43 requests to load all elements on the main page. We found that 79% of them (34 requests) were addressed to the original Prohaus.com, 5% (2 requests) were made to Googletagmanager.com and 5% (2 requests) were made to App.eu.usercentrics.eu. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Prohaus.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 248.6 kB (7%)

Content Size

3.7 MB

After Optimization

3.5 MB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Prohaus.com main page is 3.7 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. 40% of websites need less resources to load. Images take 3.3 MB which makes up the majority of the site volume.

HTML Optimization

-88%

Potential reduce by 96.4 kB

  • Original 109.9 kB
  • After minification 67.4 kB
  • After compression 13.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. This page needs HTML code to be minified as it can gain 42.5 kB, which is 39% 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 96.4 kB or 88% of the original size.

Image Optimization

-1%

Potential reduce by 30.6 kB

  • Original 3.3 MB
  • After minification 3.2 MB

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. Pro Haus images are well optimized though.

JavaScript Optimization

-33%

Potential reduce by 121.6 kB

  • Original 363.7 kB
  • After minification 363.7 kB
  • After compression 242.1 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 121.6 kB or 33% of the original size.

Requests Breakdown

Number of requests can be reduced by 19 (51%)

Requests Now

37

After Optimization

18

  • Images
  • JavaScript
  • CSS

The browser has sent 37 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Pro Haus. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 14 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

prohaus.com

prohaus.com

229 ms

www.prohaus.com

www.prohaus.com

1115 ms

183d1fa344.css

183d1fa344.css

120 ms

Main.min.css

Main.min.css

226 ms

Additional.min.css

Additional.min.css

314 ms

Frontend.min.css

Frontend.min.css

306 ms

main_1c5e056656c727f95f6655af2dc8572f.css

main_1c5e056656c727f95f6655af2dc8572f.css

545 ms

revolution_slider.css

revolution_slider.css

305 ms

1c900ba6f1.css

1c900ba6f1.css

300 ms

merged-ca6a9b8db749fb6cce16a30b7540b26b-f5bdd35e498b8596249e2310fe545e6d.js.gzip

merged-ca6a9b8db749fb6cce16a30b7540b26b-f5bdd35e498b8596249e2310fe545e6d.js.gzip

431 ms

js

js

69 ms

js

js

115 ms

www.prohaus.com

www.prohaus.com

672 ms

www.prohaus.com

www.prohaus.com

679 ms

merged-bd33eb4498b966af262e61850f6fe98e-f1c677f7624a8f6d5455e6c5cf0664ab.js.gzip

merged-bd33eb4498b966af262e61850f6fe98e-f1c677f7624a8f6d5455e6c5cf0664ab.js.gzip

510 ms

merged-0b742f410359c60a882ce7198a0bbc0b-ea0af99e3cd2525380153a13d6a01a70.js.gzip

merged-0b742f410359c60a882ce7198a0bbc0b-ea0af99e3cd2525380153a13d6a01a70.js.gzip

709 ms

Lux.min.js

Lux.min.js

622 ms

LuxEnterprise.min.js

LuxEnterprise.min.js

635 ms

loader.js

loader.js

21 ms

uc-block.bundle.js

uc-block.bundle.js

54 ms

fbevents.js

fbevents.js

56 ms

matomo.js

matomo.js

672 ms

Mockup_EFH_202401.png

Mockup_EFH_202401.png

734 ms

GUSSEK_Logo.svg

GUSSEK_Logo.svg

154 ms

scribble_line_light.svg

scribble_line_light.svg

143 ms

csm_BBS-ProHaus-transparent_46cf8f8dc8.png

csm_BBS-ProHaus-transparent_46cf8f8dc8.png

811 ms

csm_BBS-ProHaus-title_7c0d52de13.jpg

csm_BBS-ProHaus-title_7c0d52de13.jpg

280 ms

SH_2023.png

SH_2023.png

685 ms

einfamilienhaus.svg

einfamilienhaus.svg

221 ms

einfamilienhaus-invers.svg

einfamilienhaus-invers.svg

248 ms

bungalow.svg

bungalow.svg

260 ms

bungalow-invers.svg

bungalow-invers.svg

344 ms

mehrfamilienhaus.svg

mehrfamilienhaus.svg

358 ms

mehrfamilienhaus-invers.svg

mehrfamilienhaus-invers.svg

366 ms

unschluessig.svg

unschluessig.svg

387 ms

unschluessig-invers.svg

unschluessig-invers.svg

449 ms

GUSSEK_Logo_white.svg

GUSSEK_Logo_white.svg

465 ms

fa-solid-900.ttf

fa-solid-900.ttf

846 ms

fa-brands-400.ttf

fa-brands-400.ttf

650 ms

Market-CondMedium.otf

Market-CondMedium.otf

628 ms

Market-Bold.otf

Market-Bold.otf

746 ms

bundle.js

bundle.js

7 ms

matomo.php

matomo.php

397 ms

Accessibility Review

prohaus.com accessibility score

91

Accessibility Issues

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

High

Buttons do not have an accessible name

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best Practices

prohaus.com best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

prohaus.com SEO score

93

Search Engine Optimization Advices

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

High

Document uses legible font sizes

Language and Encoding

  • Language Detected

    DE

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Prohaus.com can be misinterpreted by Google and other search engines. Our service has detected that German is used on the page, and it does not match the claimed English language. Our system also found out that Prohaus.com 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.

Social Sharing Optimization

prohaus.com

Open Graph description is not detected on the main page of Pro Haus. 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: