Tools & Wizards About Us
brita.net screenshot

Report Summary

  • 21

    Performance

    Renders faster than
    39% of other websites

  • 86

    Accessibility

    Visual factors better than
    that of 61% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 90

    SEO

    Google-friendlier than
    68% of websites

brita.net

BRITA water filter | BRITA®

Page Load Speed

2.6 sec in total

First Response

208 ms

Resources Loaded

2.2 sec

Page Rendered

188 ms

brita.net screenshot

About Website

Click here to check amazing BRITA content for Turkey. Otherwise, check out these important facts you probably never knew about brita.net

BRITA: Water filters for great tasting water and reduced limescale build-up. Find the right one for your water wants and needs. Learn more.

Visit brita.net

Key Findings

We analyzed Brita.net page load time and found that the first response time was 208 ms and then it took 2.4 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.

Performance Metrics

brita.net performance score

21

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.4 s

38/100

10%

LCP (Largest Contentful Paint)

Value8.2 s

2/100

25%

SI (Speed Index)

Value5.1 s

62/100

10%

TBT (Total Blocking Time)

Value2,160 ms

6/100

30%

CLS (Cumulative Layout Shift)

Value0.258

48/100

15%

TTI (Time to Interactive)

Value11.8 s

17/100

10%

Network Requests Diagram

brita.net

208 ms

www.brita.net

333 ms

cpd.grid

450 ms

jsapi

16 ms

jquery.min.js

249 ms

Our browser made a total of 64 requests to load all elements on the main page. We found that 3% of them (2 requests) were addressed to the original Brita.net, 55% (35 requests) were made to Brita.de and 27% (17 requests) were made to Brita.scene7.com. The less responsive or slowest element that took the longest time to load (517 ms) relates to the external source Brita.scene7.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 87.2 kB (8%)

Content Size

1.0 MB

After Optimization

956.5 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Brita.net main page is 1.0 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 923.0 kB which makes up the majority of the site volume.

HTML Optimization

-76%

Potential reduce by 36.8 kB

  • Original 48.3 kB
  • After minification 46.5 kB
  • After compression 11.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 36.8 kB or 76% of the original size.

Image Optimization

-1%

Potential reduce by 9.2 kB

  • Original 923.0 kB
  • After minification 913.8 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. BRITA images are well optimized though.

JavaScript Optimization

-49%

Potential reduce by 26.7 kB

  • Original 55.0 kB
  • After minification 47.4 kB
  • After compression 28.3 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 26.7 kB or 49% of the original size.

CSS Optimization

-83%

Potential reduce by 14.5 kB

  • Original 17.4 kB
  • After minification 11.8 kB
  • After compression 2.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. Brita.net needs all CSS files to be minified and compressed as it can save up to 14.5 kB or 83% of the original size.

Requests Breakdown

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

Requests Now

59

After Optimization

29

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

brita.net

brita.net

208 ms

www.brita.net

www.brita.net

333 ms

cpd.grid

cpd.grid

450 ms

jsapi

jsapi

16 ms

jquery.min.js

jquery.min.js

249 ms

prototype.js

prototype.js

397 ms

scriptaculous.js

scriptaculous.js

245 ms

standard.js

standard.js

323 ms

swfobject.js

swfobject.js

269 ms

standard.css

standard.css

330 ms

utils.js

utils.js

330 ms

socialmedia.js

socialmedia.js

332 ms

cookies.js

cookies.js

338 ms

jquery-migrate-1.2.1.min.js

jquery-migrate-1.2.1.min.js

3 ms

8489713831584688.js

8489713831584688.js

424 ms

cookies.css

cookies.css

43 ms

cpd-elemaris-blue-stage-de

cpd-elemaris-blue-stage-de

132 ms

BRITA_Buehne_rotation_Neo4_delogo

BRITA_Buehne_rotation_Neo4_delogo

239 ms

BRITA_Buehne_rotation_taps_de

BRITA_Buehne_rotation_taps_de

196 ms

fillgo-slider-de2

fillgo-slider-de2

105 ms

Brita_CPD_front_page_tile5_teststrip

Brita_CPD_front_page_tile5_teststrip

74 ms

dealerfinder_10072014

dealerfinder_10072014

268 ms

Brita_cpd_tile_ks

Brita_cpd_tile_ks

517 ms

cpd_tile_voucher5_DE

cpd_tile_voucher5_DE

246 ms

cpd_0_tile_logo_au

cpd_0_tile_logo_au

317 ms

bodyBG.jpg

bodyBG.jpg

87 ms

britaLogo_1

britaLogo_1

204 ms

navLeft3UpShopBlue

navLeft3UpShopBlue

258 ms

navBG3UpShopBlue

navBG3UpShopBlue

437 ms

navRight3UpShopBlue

navRight3UpShopBlue

368 ms

topnavUlBG.gif

topnavUlBG.gif

87 ms

topnavLeft3Up.png

topnavLeft3Up.png

88 ms

topnavBG3Up.png

topnavBG3Up.png

86 ms

topnavRight3Up.png

topnavRight3Up.png

87 ms

mainNavBG.gif

mainNavBG.gif

86 ms

navLeft3Up.gif

navLeft3Up.gif

162 ms

navBG3Up.gif

navBG3Up.gif

170 ms

navRight3Up.gif

navRight3Up.gif

170 ms

infoNavBG.gif

infoNavBG.gif

176 ms

icon_cart2Up.gif

icon_cart2Up.gif

175 ms

arrowRoundRight2Up.gif

arrowRoundRight2Up.gif

175 ms

tile-intro-bg.gif

tile-intro-bg.gif

253 ms

arrowRoundRight.gif

arrowRoundRight.gif

256 ms

footerBG.gif

footerBG.gif

251 ms

transButtonArrow

transButtonArrow

251 ms

cookieStateActiveDT

cookieStateActiveDT

250 ms

social-icons.png

social-icons.png

239 ms

gtm.js

gtm.js

73 ms

stageSliderButton_1

stageSliderButton_1

221 ms

dummy_facebook_de.png

dummy_facebook_de.png

204 ms

dummy_twitter_custom.png

dummy_twitter_custom.png

199 ms

socialshareprivacy_on_off.png

socialshareprivacy_on_off.png

275 ms

infoBlue.gif

infoBlue.gif

278 ms

settings.png

settings.png

278 ms

ajax-loader.gif

ajax-loader.gif

307 ms

analytics.js

analytics.js

34 ms

fbevents.js

fbevents.js

4 ms

39 ms

ec.js

ec.js

20 ms

collect

collect

11 ms

collect

collect

55 ms

ga-audiences

ga-audiences

40 ms

iconClose.gif

iconClose.gif

85 ms

white.png

white.png

85 ms

Accessibility Review

brita.net accessibility score

86

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

High

Links do not have a discernible 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

High

Some elements have a [tabindex] value greater than 0

Best Practices

brita.net 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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

brita.net SEO score

90

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Links do not have descriptive text

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

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    DE

  • Encoding

    UTF-8

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

brita.net

Open Graph data is detected on the main page of BRITA. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: