Tools & Wizards About Us
bwt.be screenshot

Report Summary

  • 29

    Performance

    Renders faster than
    49% of other websites

  • 82

    Accessibility

    Visual factors better than
    that of 52% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

bwt.be

BWT Belgium – Ontdek waterbehandeling en zuiver water - BWT

Page Load Speed

4 sec in total

First Response

268 ms

Resources Loaded

2.9 sec

Page Rendered

773 ms

bwt.be screenshot

About Website

Click here to check amazing BWT content. Otherwise, check out these important facts you probably never knew about bwt.be

BWT Belgium is een waterbehandelingsspecialist! Waterontharders, (tafel)waterfilters en -kannen, professionele apparatuur... Ontdek de website!

Visit bwt.be

Key Findings

We analyzed Bwt.be page load time and found that the first response time was 268 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.be performance score

29

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)

Value9.4 s

12/100

10%

TBT (Total Blocking Time)

Value1,180 ms

21/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value9.6 s

29/100

10%

Network Requests Diagram

bwt.be

268 ms

bwt.be

340 ms

890 ms

Hyphenopoly_Loader.js

38 ms

install.js

609 ms

Our browser made a total of 30 requests to load all elements on the main page. We found that 7% of them (2 requests) were addressed to the original Bwt.be, 90% (27 requests) were made to Bwt.com and 3% (1 request) were made to Bwt.app.baqend.com. The less responsive or slowest element that took the longest time to load (966 ms) relates to the external source Bwt.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 89.6 kB (23%)

Content Size

386.5 kB

After Optimization

296.9 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Bwt.be main page is 386.5 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. 40% of websites need less resources to load. Images take 275.5 kB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 84.3 kB

  • Original 107.6 kB
  • After minification 107.4 kB
  • After compression 23.4 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 84.3 kB or 78% of the original size.

Image Optimization

-2%

Potential reduce by 5.1 kB

  • Original 275.5 kB
  • After minification 270.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 3 (16%)

Requests Now

19

After Optimization

16

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

bwt.be

bwt.be

268 ms

bwt.be

bwt.be

340 ms

890 ms

Hyphenopoly_Loader.js

Hyphenopoly_Loader.js

38 ms

install.js

install.js

609 ms

websiteStyles.css

websiteStyles.css

57 ms

style.css

style.css

44 ms

home_icon_bwt-pink_1280x1280.png

home_icon_bwt-pink_1280x1280.png

565 ms

group-people_icon_bwt-pink_1280x1280.png

group-people_icon_bwt-pink_1280x1280.png

87 ms

service_icon_bwt-pink_1280x1280.png

service_icon_bwt-pink_1280x1280.png

566 ms

ajax-loader.gif

ajax-loader.gif

37 ms

websiteScripts.js

websiteScripts.js

73 ms

script.js

script.js

35 ms

email.svg

email.svg

19 ms

support.svg

support.svg

480 ms

location.svg

location.svg

48 ms

calendar.svg

calendar.svg

63 ms

google-play.png

google-play.png

68 ms

app-store.png

app-store.png

477 ms

CeraPRO-Regular.woff

CeraPRO-Regular.woff

625 ms

CeraPRO-Regular.woff

CeraPRO-Regular.woff

608 ms

store-api

store-api

607 ms

unmute.svg

unmute.svg

36 ms

mute.svg

mute.svg

406 ms

servicemann.png

servicemann.png

966 ms

NexaSlabBoldOblique.woff

NexaSlabBoldOblique.woff

590 ms

icons-webfont2.woff

icons-webfont2.woff

548 ms

CeraPRO-Bold.woff

CeraPRO-Bold.woff

192 ms

CeraPRO-Regular.woff

CeraPRO-Regular.woff

743 ms

NexaSlab-Bold.woff

NexaSlab-Bold.woff

876 ms

Accessibility Review

bwt.be accessibility score

82

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

    NL

  • Language Claimed

    NL

  • Encoding

    UTF-8

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

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: