2.6 sec in total
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
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 40% of websites can load faster.
brita.net performance score
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 size can be reduced by 87.2 kB (8%)
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.
Potential reduce by 36.8 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.
Potential reduce by 9.2 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.
Potential reduce by 26.7 kB
Potential reduce by 14.5 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.
Number of requests can be reduced by 30 (51%)
brita.net accessibility score
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.
Buttons do not have an accessible name
Links do not have a discernible name
These are opportunities to improve the legibility of your content.
Background and foreground colors do not have a sufficient contrast ratio.
These are opportunities to improve keyboard navigation in your application.
Heading elements are not in a sequentially-descending order
Some elements have a [tabindex] value greater than 0
brita.net best practices score
Trust and Safety
Does not use HTTPS
Ensure CSP is effective against XSS attacks
Serves images with low resolution
brita.net SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Links do not have descriptive text
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/).
Document uses legible font sizes
Tap targets are not sized appropriately
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.
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: