Report Summary

  • 10

    Performance

    Renders faster than
    23% of other websites

  • 84

    Accessibility

    Visual factors better than
    that of 56% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 87

    SEO

    Google-friendlier than
    65% of websites

brico.be

Brico.be | Plus grands magasins de bricolage en Belgique

Page Load Speed

3.5 sec in total

First Response

15 ms

Resources Loaded

2.8 sec

Page Rendered

711 ms

brico.be screenshot

About Website

Click here to check amazing Brico content for Belgium. Otherwise, check out these important facts you probably never knew about brico.be

Tout pour vos projets de bricolage, jardinage et rénovation en magasin & en ligne. Plus de 150 magasins DYI en belgique. Plus grand assortiment de belgique

Visit brico.be

Key Findings

We analyzed Brico.be page load time and found that the first response time was 15 ms and then it took 3.5 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

brico.be performance score

10

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.3 s

17/100

10%

LCP (Largest Contentful Paint)

Value17.4 s

0/100

25%

SI (Speed Index)

Value7.9 s

22/100

10%

TBT (Total Blocking Time)

Value5,860 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.296

40/100

15%

TTI (Time to Interactive)

Value18.6 s

3/100

10%

Network Requests Diagram

brico.be

15 ms

brico.be

222 ms

www.brico.be

638 ms

fabrics-client-dispatcher-0.0.3-alpha.0.js

46 ms

mxd-bc6169657e.brico.new.css

54 ms

Our browser made a total of 79 requests to load all elements on the main page. We found that 4% of them (3 requests) were addressed to the original Brico.be, 44% (35 requests) were made to Images.ctfassets.net and 35% (28 requests) were made to D1pb0z5hi4vdgm.cloudfront.net. The less responsive or slowest element that took the longest time to load (1.5 sec) relates to the external source Fonts.gstatic.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 422.0 kB (43%)

Content Size

983.1 kB

After Optimization

561.1 kB

In fact, the total size of Brico.be main page is 983.1 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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. HTML takes 506.8 kB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 421.3 kB

  • Original 506.8 kB
  • After minification 501.6 kB
  • After compression 85.5 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 421.3 kB or 83% of the original size.

Image Optimization

-0%

Potential reduce by 7 B

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

JavaScript Optimization

-0%

Potential reduce by 114 B

  • Original 316.2 kB
  • After minification 316.2 kB
  • After compression 316.1 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.

CSS Optimization

-0%

Potential reduce by 601 B

  • Original 148.5 kB
  • After minification 148.5 kB
  • After compression 147.9 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. Brico.be has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 30 (42%)

Requests Now

71

After Optimization

41

The browser has sent 71 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Brico. 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 13 to 1 for CSS and as a result speed up the page load time.

Accessibility Review

brico.be accessibility score

84

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

[id] attributes on active, focusable elements are not unique

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 IDs are not unique

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

Best Practices

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

brico.be SEO score

87

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

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    FR

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Brico.be can be misinterpreted by Google and other search engines. Our service has detected that French is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Brico.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

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