Tools & Wizards About Us
hydrobru.be screenshot

Report Summary

  • 48

    Performance

    Renders faster than
    66% of other websites

  • 91

    Accessibility

    Visual factors better than
    that of 76% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 96

    SEO

    Google-friendlier than
    90% of websites

hydrobru.be

Adoucisseur d'eau : Comparatif des Marques en Belgique et Prix

Page Load Speed

4 sec in total

First Response

724 ms

Resources Loaded

2.2 sec

Page Rendered

1 sec

hydrobru.be screenshot

About Website

Visit hydrobru.be now to see the best up-to-date Hydrobru content for Belgium and also check out these interesting facts you probably never knew about hydrobru.be

Vous souhaitez installer un Adoucisseur d'Eau, mais vous ne savez pas quelle Marque choisir ? Découvrez notre comparatif et comparez les prix en 2 minutes !

Visit hydrobru.be

Key Findings

We analyzed Hydrobru.be page load time and found that the first response time was 724 ms and then it took 3.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.

Performance Metrics

hydrobru.be performance score

48

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.2 s

42/100

10%

LCP (Largest Contentful Paint)

Value3.4 s

67/100

25%

SI (Speed Index)

Value5.5 s

54/100

10%

TBT (Total Blocking Time)

Value470 ms

61/100

30%

CLS (Cumulative Layout Shift)

Value0.978

2/100

15%

TTI (Time to Interactive)

Value9.9 s

27/100

10%

Network Requests Diagram

adoucisseur-d-eau-belgique.be

724 ms

css

41 ms

front.min.css

175 ms

screen.min.css

265 ms

front.min.css

270 ms

Our browser made a total of 62 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Hydrobru.be, 32% (20 requests) were made to Fonts.gstatic.com and 5% (3 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (724 ms) relates to the external source Adoucisseur-d-eau-belgique.be.

Page Optimization Overview & Recommendations

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

Content Size

489.3 kB

After Optimization

226.8 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Hydrobru.be main page is 489.3 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. 70% of websites need less resources to load. HTML takes 305.4 kB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 256.3 kB

  • Original 305.4 kB
  • After minification 293.1 kB
  • After compression 49.0 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 256.3 kB or 84% of the original size.

Image Optimization

-3%

Potential reduce by 5.7 kB

  • Original 182.9 kB
  • After minification 177.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. Hydrobru images are well optimized though.

JavaScript Optimization

-42%

Potential reduce by 430 B

  • Original 1.0 kB
  • After minification 1.0 kB
  • After compression 602 B

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 430 B or 42% of the original size.

Requests Breakdown

Number of requests can be reduced by 29 (78%)

Requests Now

37

After Optimization

8

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

adoucisseur-d-eau-belgique.be

adoucisseur-d-eau-belgique.be

724 ms

css

css

41 ms

front.min.css

front.min.css

175 ms

screen.min.css

screen.min.css

265 ms

front.min.css

front.min.css

270 ms

fonts.css

fonts.css

264 ms

bobex-affiliate.js

bobex-affiliate.js

264 ms

front.min.js

front.min.js

272 ms

ie-compat.min.js

ie-compat.min.js

272 ms

js

js

65 ms

all.min.css

all.min.css

331 ms

categoryIcon.min-front.css

categoryIcon.min-front.css

329 ms

bob_responsive.css

bob_responsive.css

327 ms

common-front.css

common-front.css

329 ms

form-bobex-frame-inline.css

form-bobex-frame-inline.css

326 ms

jquery.min.js

jquery.min.js

436 ms

jquery-migrate.min.js

jquery-migrate.min.js

445 ms

smooth_scroll.min.js

smooth_scroll.min.js

446 ms

js.cookie.min.js

js.cookie.min.js

448 ms

jquery.sticky-kit.min.js

jquery.sticky-kit.min.js

451 ms

front.min.js

front.min.js

452 ms

front.min.js

front.min.js

512 ms

scripts.min.js

scripts.min.js

606 ms

jquery.fitvids.js

jquery.fitvids.js

514 ms

common.js

common.js

514 ms

quotes.js

quotes.js

516 ms

link-obfuscation.js

link-obfuscation.js

517 ms

css2

css2

21 ms

css2

css2

24 ms

cnfn8snk0z

cnfn8snk0z

183 ms

gtm.js

gtm.js

149 ms

hydrobru-logo.png

hydrobru-logo.png

355 ms

comparatif-adoucisseur-eau-belgique.jpg

comparatif-adoucisseur-eau-belgique.jpg

534 ms

adoucisseur-co2.jpg

adoucisseur-co2.jpg

451 ms

adoucisseur-eau-bwt.jpg

adoucisseur-eau-bwt.jpg

536 ms

star.png

star.png

450 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4uaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4uaVc.ttf

57 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4uaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4uaVc.ttf

58 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4uaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4uaVc.ttf

82 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4uaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4uaVc.ttf

90 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4uaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4uaVc.ttf

91 ms

modules.woff

modules.woff

379 ms

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk8ZkWV4exQ.ttf

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk8ZkWV4exQ.ttf

90 ms

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk5hkWV4exQ.ttf

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk5hkWV4exQ.ttf

90 ms

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0RkxhjWV4exQ.ttf

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0RkxhjWV4exQ.ttf

90 ms

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0RkyFjWV4exQ.ttf

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0RkyFjWV4exQ.ttf

91 ms

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk0ZjWV4exQ.ttf

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk0ZjWV4exQ.ttf

112 ms

KFOlCnqEu92Fr1MmEU9vAw.ttf

KFOlCnqEu92Fr1MmEU9vAw.ttf

111 ms

KFOlCnqEu92Fr1MmEU9fChc9.ttf

KFOlCnqEu92Fr1MmEU9fChc9.ttf

111 ms

KFOmCnqEu92Fr1Me5Q.ttf

KFOmCnqEu92Fr1Me5Q.ttf

120 ms

KFOmCnqEu92Fr1Mu7GxP.ttf

KFOmCnqEu92Fr1Mu7GxP.ttf

120 ms

KFOlCnqEu92Fr1MmSU5vAw.ttf

KFOlCnqEu92Fr1MmSU5vAw.ttf

124 ms

KFOlCnqEu92Fr1MmSU5fChc9.ttf

KFOlCnqEu92Fr1MmSU5fChc9.ttf

125 ms

KFOkCnqEu92Fr1MmgVxGIzc.ttf

KFOkCnqEu92Fr1MmgVxGIzc.ttf

124 ms

KFOlCnqEu92Fr1MmWUlvAw.ttf

KFOlCnqEu92Fr1MmWUlvAw.ttf

126 ms

KFOlCnqEu92Fr1MmWUlfChc9.ttf

KFOlCnqEu92Fr1MmWUlfChc9.ttf

128 ms

KFOlCnqEu92Fr1MmYUtfChc9.ttf

KFOlCnqEu92Fr1MmYUtfChc9.ttf

126 ms

fa-solid-900.woff

fa-solid-900.woff

427 ms

fa-regular-400.woff

fa-regular-400.woff

697 ms

fa-light-300.woff

fa-light-300.woff

604 ms

clarity.js

clarity.js

44 ms

c.gif

c.gif

8 ms

Accessibility Review

hydrobru.be accessibility score

91

Accessibility Issues

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.

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

hydrobru.be best practices score

92

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

SEO Factors

hydrobru.be SEO score

96

Search Engine Optimization Advices

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

hydrobru.be

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