Tools & Wizards About Us
brita.tw screenshot

Report Summary

  • 10

    Performance

    Renders faster than
    23% of other websites

  • 88

    Accessibility

    Visual factors better than
    that of 68% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 85

    SEO

    Google-friendlier than
    55% of websites

brita.tw

BRITA濾水器與淨水器系統 – 好水講究、淨水器推薦首選 | BRITA®

Page Load Speed

2.7 sec in total

First Response

638 ms

Resources Loaded

1.8 sec

Page Rendered

227 ms

brita.tw screenshot

About Website

Visit brita.tw now to see the best up-to-date BRITA content for Taiwan and also check out these interesting facts you probably never knew about brita.tw

濾水器推薦首選！BRITA德國濾水器提供濾水器、生飲淨水器、瞬熱型與櫥下型淨水器等產品選項，享受量身打造生飲淨水等級過濾水，就使用BRITA濾水及淨水系統。

Visit brita.tw

Key Findings

We analyzed Brita.tw page load time and found that the first response time was 638 ms and then it took 2 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.

Performance Metrics

brita.tw performance score

10

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.4 s

16/100

10%

LCP (Largest Contentful Paint)

Value5.5 s

19/100

25%

SI (Speed Index)

Value22.6 s

0/100

10%

TBT (Total Blocking Time)

Value1,810 ms

9/100

30%

CLS (Cumulative Layout Shift)

Value0.738

6/100

15%

TTI (Time to Interactive)

Value22.1 s

1/100

10%

Network Requests Diagram

cpd.grid

638 ms

jsapi

26 ms

jquery.min.js

239 ms

prototype.js

392 ms

scriptaculous.js

253 ms

Our browser made a total of 48 requests to load all elements on the main page. We found that 54% of them (26 requests) were addressed to the original Brita.tw, 27% (13 requests) were made to Brita.scene7.com and 8% (4 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (638 ms) belongs to the original domain Brita.tw.

Page Optimization Overview & Recommendations

Page size can be reduced by 53.2 kB (4%)

Content Size

1.5 MB

After Optimization

1.4 MB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Brita.tw main page is 1.5 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. 50% of websites need less resources to load. Images take 1.4 MB which makes up the majority of the site volume.

HTML Optimization

-74%

Potential reduce by 22.1 kB

  • Original 29.9 kB
  • After minification 29.1 kB
  • After compression 7.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 22.1 kB or 74% of the original size.

Image Optimization

-0%

Potential reduce by 4.5 kB

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

JavaScript Optimization

-38%

Potential reduce by 26.7 kB

  • Original 70.9 kB
  • After minification 63.2 kB
  • After compression 44.2 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 38% of the original size.

Requests Breakdown

Number of requests can be reduced by 19 (41%)

Requests Now

46

After Optimization

27

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

cpd.grid

cpd.grid

638 ms

jsapi

jsapi

26 ms

jquery.min.js

jquery.min.js

239 ms

prototype.js

prototype.js

392 ms

scriptaculous.js

scriptaculous.js

253 ms

standard.js

standard.js

320 ms

swfobject.js

swfobject.js

253 ms

standard.css

standard.css

328 ms

utils.js

utils.js

321 ms

socialmedia.js

socialmedia.js

325 ms

jquery-migrate-1.2.1.min.js

jquery-migrate-1.2.1.min.js

8 ms

8489713831584688.js

8489713831584688.js

331 ms

stage-home-pressuriesd-tw

stage-home-pressuriesd-tw

243 ms

cpd-home-navelia-fruits-tw

cpd-home-navelia-fruits-tw

241 ms

brita-tw-1

brita-tw-1

215 ms

brita-tw-2

brita-tw-2

299 ms

marella-water-filter-stage-tw

marella-water-filter-stage-tw

305 ms

ontap-home-stage-tw

ontap-home-stage-tw

193 ms

cpd-navelia-fruits-tile

cpd-navelia-fruits-tile

236 ms

cpd-0-video-tile

cpd-0-video-tile

342 ms

cpd_0_tile_5_mybrita

cpd_0_tile_5_mybrita

341 ms

dealerfinder_10072014

dealerfinder_10072014

292 ms

PPD_Presseservice_Kachel

PPD_Presseservice_Kachel

343 ms

bodyBG.jpg

bodyBG.jpg

86 ms

britaLogo_1

britaLogo_1

281 ms

topnavUlBG.gif

topnavUlBG.gif

86 ms

topnavLeft3Up.png

topnavLeft3Up.png

88 ms

topnavBG3Up.png

topnavBG3Up.png

83 ms

topnavRight3Up.png

topnavRight3Up.png

85 ms

mainNavBG.gif

mainNavBG.gif

87 ms

navLeft3Up.gif

navLeft3Up.gif

155 ms

navBG3Up.gif

navBG3Up.gif

163 ms

navRight3Up.gif

navRight3Up.gif

170 ms

tile-intro-bg.gif

tile-intro-bg.gif

169 ms

arrowRoundRight.gif

arrowRoundRight.gif

173 ms

tile-intro-bg.gif

tile-intro-bg.gif

455 ms

footerBG.gif

footerBG.gif

152 ms

arrowRoundRight.gif

arrowRoundRight.gif

453 ms

social-icons.png

social-icons.png

238 ms

gtm.js

gtm.js

97 ms

stageSliderButton_1

stageSliderButton_1

213 ms

ajax-loader.gif

ajax-loader.gif

211 ms

analytics.js

analytics.js

42 ms

ga.js

ga.js

65 ms

collect

collect

60 ms

__utm.gif

__utm.gif

23 ms

iconClose.gif

iconClose.gif

86 ms

white-70.png

white-70.png

84 ms

Accessibility Review

brita.tw accessibility score

88

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.tw 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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

brita.tw SEO score

85

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

High

robots.txt is not valid

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

    JA

  • Language Claimed

    TW

  • Encoding

    UTF-8

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

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: