Tools & Wizards About Us
bwt.fr screenshot

Report Summary

  • 31

    Performance

    Renders faster than
    51% of other websites

  • 80

    Accessibility

    Visual factors better than
    that of 49% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 84

    SEO

    Google-friendlier than
    52% of websites

bwt.fr

Traitement de l'eau BWT : filtration, purification et amélioration de l’eau - BWT

Page Load Speed

3.9 sec in total

First Response

199 ms

Resources Loaded

2.5 sec

Page Rendered

1.3 sec

bwt.fr screenshot

About Website

Visit bwt.fr now to see the best up-to-date BWT content for France and also check out these interesting facts you probably never knew about bwt.fr

Chez BWT, l'eau est notre mission. Retrouvez notre gamme de solutions de traitement de l'eau pour les particuliers, les collectivités et les industries.

Visit bwt.fr

Key Findings

We analyzed Bwt.fr page load time and found that the first response time was 199 ms and then it took 3.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.

Performance Metrics

bwt.fr performance score

31

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.4 s

38/100

10%

LCP (Largest Contentful Paint)

Value9.7 s

0/100

25%

SI (Speed Index)

Value7.2 s

30/100

10%

TBT (Total Blocking Time)

Value1,120 ms

23/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value10.4 s

24/100

10%

Network Requests Diagram

bwt.fr

199 ms

bwt.fr

343 ms

649 ms

Hyphenopoly_Loader.js

16 ms

install.js

60 ms

Our browser made a total of 27 requests to load all elements on the main page. We found that 7% of them (2 requests) were addressed to the original Bwt.fr, 81% (22 requests) were made to Bwt.com and 4% (1 request) were made to Bwt.app.baqend.com. The less responsive or slowest element that took the longest time to load (1.1 sec) relates to the external source Goodmeal.fr.

Page Optimization Overview & Recommendations

Page size can be reduced by 115.1 kB (54%)

Content Size

213.4 kB

After Optimization

98.3 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Bwt.fr main page is 213.4 kB. 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. HTML takes 142.6 kB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 114.8 kB

  • Original 142.6 kB
  • After minification 142.4 kB
  • After compression 27.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 114.8 kB or 81% of the original size.

Image Optimization

-0%

Potential reduce by 20 B

  • Original 67.5 kB
  • After minification 67.5 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. BWT images are well optimized though.

JavaScript Optimization

-8%

Potential reduce by 248 B

  • Original 3.3 kB
  • After minification 3.2 kB
  • After compression 3.0 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.

Requests Breakdown

Number of requests can be reduced by 4 (25%)

Requests Now

16

After Optimization

12

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

bwt.fr

bwt.fr

199 ms

bwt.fr

bwt.fr

343 ms

649 ms

Hyphenopoly_Loader.js

Hyphenopoly_Loader.js

16 ms

install.js

install.js

60 ms

js

js

151 ms

websiteStyles.css

websiteStyles.css

65 ms

style.css

style.css

53 ms

websiteScripts.js

websiteScripts.js

150 ms

script.js

script.js

31 ms

1632.svg

1632.svg

1117 ms

bwt_icon_call_200x200_2.png

bwt_icon_call_200x200_2.png

127 ms

bwt_icon_handshake_238x238_2.png

bwt_icon_handshake_238x238_2.png

32 ms

bwt_icon_delivery_200x200_2.png

bwt_icon_delivery_200x200_2.png

126 ms

bwt_icon_certificate1280x1280_2.png

bwt_icon_certificate1280x1280_2.png

543 ms

google-play.png

google-play.png

126 ms

app-store.png

app-store.png

127 ms

ajax-loader.gif

ajax-loader.gif

464 ms

bwt-hovering-logo.svg

bwt-hovering-logo.svg

465 ms

CeraPRO-Regular.woff

CeraPRO-Regular.woff

556 ms

CeraPRO-Regular.woff

CeraPRO-Regular.woff

570 ms

CeraPRO-Regular.woff

CeraPRO-Regular.woff

571 ms

store-api

store-api

393 ms

NexaSlabBoldOblique.woff

NexaSlabBoldOblique.woff

590 ms

icons-webfont2.woff

icons-webfont2.woff

55 ms

CeraPRO-Bold.woff

CeraPRO-Bold.woff

664 ms

NexaSlab-Bold.woff

NexaSlab-Bold.woff

560 ms

Accessibility Review

bwt.fr accessibility score

80

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 input fields do not have accessible names

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

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

Best Practices

bwt.fr 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

bwt.fr SEO score

84

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

Page is blocked from indexing

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

    FR

  • Language Claimed

    FR

  • Encoding

    UTF-8

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

bwt.fr

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