Tools & Wizards About Us
grohe.de screenshot

Report Summary

  • 18

    Performance

    Renders faster than
    34% of other websites

  • 83

    Accessibility

    Visual factors better than
    that of 54% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

grohe.de

GROHE Premium Badarmaturen, Duschen & Küchenarmaturen | GROHE

Page Load Speed

3.7 sec in total

First Response

313 ms

Resources Loaded

3 sec

Page Rendered

376 ms

grohe.de screenshot

About Website

Click here to check amazing GROHE content for Germany. Otherwise, check out these important facts you probably never knew about grohe.de

Luxuriöse Armaturen für außergewöhnliche Bäder und Küchen. Große Auswahl an Badarmaturen, Duschen und Küchenarmaturen für alle Einrichtungsstile und Budgets.

Visit grohe.de

Key Findings

We analyzed Grohe.de page load time and found that the first response time was 313 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

grohe.de performance score

18

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value10.2 s

0/100

10%

LCP (Largest Contentful Paint)

Value41.7 s

0/100

25%

SI (Speed Index)

Value18.1 s

0/100

10%

TBT (Total Blocking Time)

Value1,650 ms

11/100

30%

CLS (Cumulative Layout Shift)

Value0.013

100/100

15%

TTI (Time to Interactive)

Value41.7 s

0/100

10%

Network Requests Diagram

grohe.de

313 ms

www.grohe.de

278 ms

www.grohe.de

374 ms

190 ms

OtAutoBlock.js

64 ms

Our browser made a total of 32 requests to load all elements on the main page. We found that 13% of them (4 requests) were addressed to the original Grohe.de, 50% (16 requests) were made to Cdn.cloud.grohe.com and 13% (4 requests) were made to Fe.grohe.com. The less responsive or slowest element that took the longest time to load (1.1 sec) relates to the external source Fe.grohe.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 4.4 MB (66%)

Content Size

6.7 MB

After Optimization

2.3 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Grohe.de main page is 6.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. Only a small number of websites need less resources to load. Javascripts take 4.1 MB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 107.2 kB

  • Original 126.3 kB
  • After minification 124.0 kB
  • After compression 19.0 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 107.2 kB or 85% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 1.2 MB
  • After minification 1.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. GROHE images are well optimized though.

JavaScript Optimization

-83%

Potential reduce by 3.4 MB

  • Original 4.1 MB
  • After minification 4.1 MB
  • After compression 694.5 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 3.4 MB or 83% of the original size.

CSS Optimization

-72%

Potential reduce by 924.1 kB

  • Original 1.3 MB
  • After minification 1.3 MB
  • After compression 366.9 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. Grohe.de needs all CSS files to be minified and compressed as it can save up to 924.1 kB or 72% of the original size.

Requests Breakdown

Number of requests can be reduced by 5 (24%)

Requests Now

21

After Optimization

16

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

grohe.de

grohe.de

313 ms

www.grohe.de

www.grohe.de

278 ms

www.grohe.de

www.grohe.de

374 ms

190 ms

OtAutoBlock.js

OtAutoBlock.js

64 ms

otSDKStub.js

otSDKStub.js

82 ms

bootstrap.css

bootstrap.css

526 ms

main.css

main.css

998 ms

pl-vendor-libraries.js

pl-vendor-libraries.js

1065 ms

pl-source.js

pl-source.js

1067 ms

api.js

api.js

49 ms

18b737a3-7136-4c59-b26f-8710179aab94.json

18b737a3-7136-4c59-b26f-8710179aab94.json

44 ms

location

location

61 ms

GRO99419_Shower_Campaign_Website_Banner_AwarenessConsideration_Desktop_TempestaCube250_Chrome_1920x823px_21_9_21_9.jpg

GRO99419_Shower_Campaign_Website_Banner_AwarenessConsideration_Desktop_TempestaCube250_Chrome_1920x823px_21_9_21_9.jpg

337 ms

grohe_Phantom_Black_21_9_21_9.jpg

grohe_Phantom_Black_21_9_21_9.jpg

409 ms

ZZH_T26670I02_000_01_Head_shower_21_9_21_9.jpg

ZZH_T26670I02_000_01_Head_shower_21_9_21_9.jpg

410 ms

Keyvisual_Eurosmart_21_9_21_9.jpg

Keyvisual_Eurosmart_21_9_21_9.jpg

793 ms

ZZH_T24316I01_000_01_Keyvisual_21_9_21_9.jpg

ZZH_T24316I01_000_01_Keyvisual_21_9_21_9.jpg

422 ms

Header_lokal_LandingpageDE_1280x550_21_9.jpg

Header_lokal_LandingpageDE_1280x550_21_9.jpg

430 ms

39354SH1_21_9_21_9.jpg

39354SH1_21_9_21_9.jpg

417 ms

shower.sv

shower.sv

822 ms

washbasin.sv

washbasin.sv

802 ms

wc.sv

wc.sv

824 ms

sink.sv

sink.sv

814 ms

ZZH_T23403G05_000_01_21_9_21_9.jpg

ZZH_T23403G05_000_01_21_9_21_9.jpg

434 ms

GROHE_Professional_Testimonial_German_Keyvisual_Family_21_9_21_9.jpg

GROHE_Professional_Testimonial_German_Keyvisual_Family_21_9_21_9.jpg

441 ms

home-WS-teaser_21_9.jpg

home-WS-teaser_21_9.jpg

460 ms

non-DIY_4_3.jpg

non-DIY_4_3.jpg

471 ms

GROHE_QF_2023_4_3.jpg

GROHE_QF_2023_4_3.jpg

474 ms

0LybBL1Q==

0LybBL1Q==

11 ms

AUi4TP8=

AUi4TP8=

9 ms

AfBiTYA=

AfBiTYA=

7 ms

Accessibility Review

grohe.de accessibility score

83

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

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.

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

grohe.de 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

grohe.de 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 Grohe.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 Grohe.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.

Social Sharing Optimization

grohe.de

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