Tools & Wizards About Us
bauhaus.fi screenshot

Report Summary

  • 17

    Performance

    Renders faster than
    32% of other websites

  • 81

    Accessibility

    Visual factors better than
    that of 51% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

bauhaus.fi

BAUHAUS | Edulliset hinnat ja laaja valikoima | bauhaus.fi

Page Load Speed

23.2 sec in total

First Response

459 ms

Resources Loaded

21.8 sec

Page Rendered

885 ms

bauhaus.fi screenshot

About Website

Click here to check amazing BAUHAUS content for Finland. Otherwise, check out these important facts you probably never knew about bauhaus.fi

Tutustu laajaan valikoimaan ja ajankohtaisiin tarjouksiin. Verkkokaupastamme tilaat tuotteet helposti kotiin tai noudettavaksi tavarataloistamme. 7000+ tyytyväistä asiakasta!

Visit bauhaus.fi

Key Findings

We analyzed Bauhaus.fi page load time and found that the first response time was 459 ms and then it took 22.7 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster. Unfortunately, there was 1 request timeout, which can generally increase the web page load time, as the browser stays idle while waiting for website response.

Performance Metrics

bauhaus.fi performance score

17

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.3 s

17/100

10%

LCP (Largest Contentful Paint)

Value23.2 s

0/100

25%

SI (Speed Index)

Value11.1 s

6/100

10%

TBT (Total Blocking Time)

Value5,570 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.003

100/100

15%

TTI (Time to Interactive)

Value30.8 s

0/100

10%

Network Requests Diagram

bauhaus.fi

459 ms

www.bauhaus.fi

1821 ms

gtm.js

99 ms

exponea.min.js

1169 ms

modifications.min.js

1281 ms

Our browser made a total of 96 requests to load all elements on the main page. We found that 2% of them (2 requests) were addressed to the original Bauhaus.fi, 81% (78 requests) were made to Cdn.bauhaus.fi and 3% (3 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (20.2 sec) relates to the external source Admin.bauhaus.fi.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.3 MB (47%)

Content Size

2.8 MB

After Optimization

1.5 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Bauhaus.fi main page is 2.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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. HTML takes 1.4 MB which makes up the majority of the site volume.

HTML Optimization

-91%

Potential reduce by 1.2 MB

  • Original 1.4 MB
  • After minification 1.1 MB
  • After compression 117.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. This page needs HTML code to be minified as it can gain 278.0 kB, which is 20% 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 1.2 MB or 91% of the original size.

Image Optimization

-6%

Potential reduce by 50.4 kB

  • Original 851.8 kB
  • After minification 801.3 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. BAUHAUS images are well optimized though.

JavaScript Optimization

-6%

Potential reduce by 32.8 kB

  • Original 525.4 kB
  • After minification 525.4 kB
  • After compression 492.6 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. This website has mostly compressed JavaScripts.

CSS Optimization

-0%

Potential reduce by 313 B

  • Original 104.4 kB
  • After minification 104.4 kB
  • After compression 104.0 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. Bauhaus.fi has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 28 (31%)

Requests Now

90

After Optimization

62

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 90 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 29 to 1 for JavaScripts and as a result speed up the page load time.

Network Requests Diagram

bauhaus.fi

bauhaus.fi

459 ms

www.bauhaus.fi

www.bauhaus.fi

1821 ms

gtm.js

gtm.js

99 ms

exponea.min.js

exponea.min.js

1169 ms

modifications.min.js

modifications.min.js

1281 ms

logo.svg

logo.svg

1266 ms

onsite_banner_HERO_HZ240508_badge.png

onsite_banner_HERO_HZ240508_badge.png

20190 ms

banner_puutarhakoneet_ota_2_15_TEXT_3.png

banner_puutarhakoneet_ota_2_15_TEXT_3.png

614 ms

banner_valokatteet_4_3_TEXT_2.png

banner_valokatteet_4_3_TEXT_2.png

611 ms

amppeli_TUOTE_banner.jpg

amppeli_TUOTE_banner.jpg

1167 ms

kingstone_cliff_TUOTE_banner.jpg

kingstone_cliff_TUOTE_banner.jpg

608 ms

karcher_k5_TUOTE_banner.jpg

karcher_k5_TUOTE_banner.jpg

618 ms

puutarhamulta_TUOTE_banner.jpg

puutarhamulta_TUOTE_banner.jpg

613 ms

23913.jpg

23913.jpg

692 ms

5148.png

5148.png

1082 ms

sunfun.png

sunfun.png

693 ms

4670.png

4670.png

696 ms

24272.png

24272.png

694 ms

karcher.png

karcher.png

698 ms

4578.png

4578.png

696 ms

hyvalta_nayttaa_ribbon_1.png

hyvalta_nayttaa_ribbon_1.png

698 ms

24256.png

24256.png

699 ms

23863.png

23863.png

700 ms

4921.png

4921.png

701 ms

8744.png

8744.png

976 ms

4365.png

4365.png

852 ms

katkaisu-ja-jiirisaha_einhell_TUOTE_banner.jpg

katkaisu-ja-jiirisaha_einhell_TUOTE_banner.jpg

701 ms

camargue_wc_istuin_TUOTE_banner.jpg

camargue_wc_istuin_TUOTE_banner.jpg

703 ms

kaasugrilli_napoleon_TUOTE_banner_1.jpg

kaasugrilli_napoleon_TUOTE_banner_1.jpg

704 ms

puutarhap_yt__sofia_TUOTE_banner.jpg

puutarhap_yt__sofia_TUOTE_banner.jpg

1232 ms

8804.png

8804.png

733 ms

24208.png

24208.png

735 ms

luoman.png

luoman.png

736 ms

kota.png

kota.png

740 ms

23956.png

23956.png

751 ms

f.png

f.png

763 ms

24231.png

24231.png

1139 ms

24214.png

24214.png

860 ms

banner_philips_ulkovalaisimet_30_TEXT_2.png

banner_philips_ulkovalaisimet_30_TEXT_2.png

871 ms

banner_ryobi_puutarhasahat_15_TEXT.png

banner_ryobi_puutarhasahat_15_TEXT.png

884 ms

biolan_pikakompostori_eco_TUOTE_banner.jpg

biolan_pikakompostori_eco_TUOTE_banner.jpg

908 ms

luoman_lillevilla_TUOTE_banner.jpg

luoman_lillevilla_TUOTE_banner.jpg

920 ms

snippet.js

snippet.js

378 ms

klevu.js

klevu.js

291 ms

quick-search-theme.js

quick-search-theme.js

305 ms

uc.js

uc.js

359 ms

js

js

114 ms

analytics.js

analytics.js

315 ms

destination

destination

231 ms

modifications.min.js

modifications.min.js

142 ms

require.js

require.js

347 ms

mixins.js

mixins.js

357 ms

mixin-filter.js

mixin-filter.js

365 ms

requirejs-config.js

requirejs-config.js

377 ms

ieUrlPolyfill.js

ieUrlPolyfill.js

386 ms

ruobi_iskeva_ruuvinvaannin_TUOTE_banner.jpg

ruobi_iskeva_ruuvinvaannin_TUOTE_banner.jpg

460 ms

puukiuas_kuru_20_TUOTE_banner.jpg

puukiuas_kuru_20_TUOTE_banner.jpg

386 ms

blog_oven_mitoitus_feature_img.jpg

blog_oven_mitoitus_feature_img.jpg

385 ms

d-c-fix_thumbnail.jpg

d-c-fix_thumbnail.jpg

385 ms

Blog-featured-image_yllattiko-talvi.jpg

Blog-featured-image_yllattiko-talvi.jpg

386 ms

Blog-featured-image_lattian-valintaopas.jpg

Blog-featured-image_lattian-valintaopas.jpg

384 ms

bootstrap.js

bootstrap.js

94 ms

bauhaus-common.js

bauhaus-common.js

59 ms

lazysizes.js

lazysizes.js

54 ms

ls.native-loading.js

ls.native-loading.js

64 ms

ls.unveilhooks.js

ls.unveilhooks.js

63 ms

ls.attr-change.js

ls.attr-change.js

111 ms

ls.init.js

ls.init.js

109 ms

text.js

text.js

109 ms

v7.js

v7.js

97 ms

mfblogunveil.js

mfblogunveil.js

91 ms

jquery-mixin.js

jquery-mixin.js

58 ms

modal.js

modal.js

18 ms

js-translation.json

js-translation.json

302 ms

modal-popup.html

modal-popup.html

342 ms

modal-slide.html

modal-slide.html

319 ms

modal-custom.html

modal-custom.html

328 ms

landing

landing

106 ms

collect

collect

38 ms

collect

collect

679 ms

validation-rules.js

validation-rules.js

19 ms

styles-m.min.css

styles-m.min.css

21 ms

toimitus.svg

toimitus.svg

72 ms

maksutavat.svg

maksutavat.svg

316 ms

vaihto_palautus.svg

vaihto_palautus.svg

76 ms

toimitus.svg

toimitus.svg

74 ms

vaihto_palautus.svg

vaihto_palautus.svg

73 ms

maksutavat.svg

maksutavat.svg

76 ms

tarjouslehti.svg

tarjouslehti.svg

79 ms

uutiskirje.svg

uutiskirje.svg

78 ms

bauhaus.woff

bauhaus.woff

17 ms

taz-bold.woff

taz-bold.woff

517 ms

taz-black.woff

taz-black.woff

610 ms

blog-new.min.css

blog-new.min.css

23 ms

print.min.css

print.min.css

47 ms

collect

collect

5 ms

Accessibility Review

bauhaus.fi accessibility score

81

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[aria-*] attributes do not match their roles

High

[role]s do not have all required [aria-*] attributes

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

High

Links do not have a discernible name

Best Practices

bauhaus.fi best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

bauhaus.fi SEO score

92

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

    FI

  • Language Claimed

    FI

  • Encoding

    UTF-8

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

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: