Tools & Wizards About Us
bauhaus.at screenshot

Report Summary

  • 7

    Performance

    Renders faster than
    22% of other websites

  • 90

    Accessibility

    Visual factors better than
    that of 74% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

bauhaus.at

Der BAUHAUS Online-Shop für Werkstatt, Haus und Garten

Page Load Speed

4.6 sec in total

First Response

392 ms

Resources Loaded

2.8 sec

Page Rendered

1.4 sec

bauhaus.at screenshot

About Website

Welcome to bauhaus.at homepage info - get ready to check BAUHAUS best content for Austria right away, or after learning these important things about bauhaus.at

BAUHAUS Online-Shop - Ihr Fachcentrum wenn es gut werden muss. Wir sind Ihr Spezialist für Werkzeuge, Baumaterialien und Gartenbedarf.

Visit bauhaus.at

Key Findings

We analyzed Bauhaus.at page load time and found that the first response time was 392 ms and then it took 4.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.

Performance Metrics

bauhaus.at performance score

7

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.4 s

17/100

10%

LCP (Largest Contentful Paint)

Value9.9 s

0/100

25%

SI (Speed Index)

Value10.9 s

6/100

10%

TBT (Total Blocking Time)

Value2,360 ms

5/100

30%

CLS (Cumulative Layout Shift)

Value0.413

24/100

15%

TTI (Time to Interactive)

Value24.4 s

0/100

10%

Network Requests Diagram

bauhaus.at

392 ms

bauhaus.at

458 ms

www.bauhaus.at

739 ms

loader.js

27 ms

porthole.min.js

382 ms

Our browser made a total of 68 requests to load all elements on the main page. We found that 26% of them (18 requests) were addressed to the original Bauhaus.at, 68% (46 requests) were made to Media.cdn.bauhaus and 3% (2 requests) were made to App.usercentrics.eu. The less responsive or slowest element that took the longest time to load (819 ms) relates to the external source Media.cdn.bauhaus.

Page Optimization Overview & Recommendations

Page size can be reduced by 587.6 kB (14%)

Content Size

4.3 MB

After Optimization

3.7 MB

  • HTML
  • Images
  • JavaScript

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

HTML Optimization

-83%

Potential reduce by 107.3 kB

  • Original 129.4 kB
  • After minification 112.8 kB
  • After compression 22.1 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 16.5 kB, which is 13% 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 107.3 kB or 83% of the original size.

Image Optimization

-0%

Potential reduce by 4.4 kB

  • Original 3.3 MB
  • After minification 3.3 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. BAUHAUS images are well optimized though.

JavaScript Optimization

-57%

Potential reduce by 475.9 kB

  • Original 831.3 kB
  • After minification 831.3 kB
  • After compression 355.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 475.9 kB or 57% of the original size.

Requests Breakdown

Number of requests can be reduced by 10 (16%)

Requests Now

62

After Optimization

52

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

bauhaus.at

bauhaus.at

392 ms

bauhaus.at

bauhaus.at

458 ms

www.bauhaus.at

www.bauhaus.at

739 ms

loader.js

loader.js

27 ms

porthole.min.js

porthole.min.js

382 ms

mainold.css

mainold.css

409 ms

modernizr.custom.js

modernizr.custom.js

478 ms

launch-ENc967421472cc47e69b4585f7ba1a42f6.min.js

launch-ENc967421472cc47e69b4585f7ba1a42f6.min.js

24 ms

bundle.js

bundle.js

11 ms

all.js

all.js

797 ms

head.js

head.js

488 ms

require.js

require.js

620 ms

compareandbookmark.js

compareandbookmark.js

529 ms

lightbox.js

lightbox.js

529 ms

26.jpg

26.jpg

178 ms

26.jpg

26.jpg

481 ms

26.jpg

26.jpg

239 ms

26.jpg

26.jpg

194 ms

26.jpg

26.jpg

415 ms

26.jpg

26.jpg

568 ms

26.jpg

26.jpg

235 ms

26.jpg

26.jpg

214 ms

26.jpg

26.jpg

415 ms

26.jpg

26.jpg

379 ms

26.jpg

26.jpg

368 ms

26.jpg

26.jpg

567 ms

26.jpg

26.jpg

568 ms

26.jpg

26.jpg

568 ms

26.jpg

26.jpg

475 ms

26.jpg

26.jpg

599 ms

26.jpg

26.jpg

569 ms

26.jpg

26.jpg

569 ms

26.jpg

26.jpg

654 ms

26.jpg

26.jpg

639 ms

26.jpg

26.jpg

636 ms

26.jpg

26.jpg

641 ms

26.jpg

26.jpg

667 ms

26.jpg

26.jpg

599 ms

26.jpg

26.jpg

621 ms

26.jpg

26.jpg

740 ms

26.jpg

26.jpg

677 ms

26.jpg

26.jpg

775 ms

26.jpg

26.jpg

756 ms

26.jpg

26.jpg

685 ms

26.jpg

26.jpg

819 ms

26.jpg

26.jpg

804 ms

26.jpg

26.jpg

812 ms

26.jpg

26.jpg

758 ms

26.jpg

26.jpg

815 ms

22.png

22.png

770 ms

logo-bauhaus-sm.png

logo-bauhaus-sm.png

140 ms

logo-s.png

logo-s.png

236 ms

icon.svg

icon.svg

460 ms

Taz_500_a.woff

Taz_500_a.woff

429 ms

Taz_700_a.woff

Taz_700_a.woff

272 ms

bauhaus.woff

bauhaus.woff

236 ms

22.png

22.png

625 ms

22.png

22.png

601 ms

22.png

22.png

596 ms

22.png

22.png

588 ms

26.png

26.png

588 ms

26.png

26.png

458 ms

26.png

26.png

465 ms

26.png

26.png

416 ms

26.png

26.png

411 ms

26.png

26.png

356 ms

logo-bauhaus-lg.png

logo-bauhaus-lg.png

103 ms

main.js

main.js

103 ms

Accessibility Review

bauhaus.at accessibility score

90

Accessibility Issues

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.

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

Links do not have a discernible name

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

bauhaus.at best practices score

83

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

Missing source maps for large first-party JavaScript

SEO Factors

bauhaus.at SEO score

93

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

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

High

Document uses legible font sizes

Language and Encoding

  • Language Detected

    DE

  • Language Claimed

    DE

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Bauhaus.at 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 Bauhaus.at 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

bauhaus.at

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