Tools & Wizards About Us
braem.be screenshot

Report Summary

  • 25

    Performance

    Renders faster than
    44% of other websites

  • 81

    Accessibility

    Visual factors better than
    that of 51% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 85

    SEO

    Google-friendlier than
    55% of websites

braem.be

Braem - Tweedehands vrachtwagens, vrachtwagen onderdelen & services - Braem Trucks, Parts & Services

Page Load Speed

3.5 sec in total

First Response

281 ms

Resources Loaded

2.8 sec

Page Rendered

430 ms

braem.be screenshot

About Website

Welcome to braem.be homepage info - get ready to check Braem best content for France right away, or after learning these important things about braem.be

Tweedehands vrachtwagens: alle merken, MAN & Mercedes vrachtwagen onderdelen: nieuw en tweedehands. Braem NV - Dé one-stop shop voor uw truck!

Visit braem.be

Key Findings

We analyzed Braem.be page load time and found that the first response time was 281 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

braem.be performance score

25

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.4 s

36/100

10%

LCP (Largest Contentful Paint)

Value13.0 s

0/100

25%

SI (Speed Index)

Value9.0 s

14/100

10%

TBT (Total Blocking Time)

Value1,680 ms

11/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value11.5 s

18/100

10%

Network Requests Diagram

braem.be

281 ms

www.braem.com

524 ms

styles-m.min.css

40 ms

styles.min.css

64 ms

styles.min.css

65 ms

Our browser made a total of 51 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Braem.be, 90% (46 requests) were made to Braem.com and 2% (1 request) were made to Google.com. The less responsive or slowest element that took the longest time to load (1.4 sec) relates to the external source Braem.com.

Page Optimization Overview & Recommendations

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

Content Size

2.0 MB

After Optimization

2.0 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Braem.be main page is 2.0 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. 60% of websites need less resources to load. Images take 1.6 MB which makes up the majority of the site volume.

HTML Optimization

-76%

Potential reduce by 81.6 kB

  • Original 107.2 kB
  • After minification 105.7 kB
  • After compression 25.6 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 81.6 kB or 76% of the original size.

Image Optimization

-0%

Potential reduce by 1.2 kB

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

JavaScript Optimization

-0%

Potential reduce by 986 B

  • Original 209.9 kB
  • After minification 209.9 kB
  • After compression 208.9 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 269 B

  • Original 117.5 kB
  • After minification 117.5 kB
  • After compression 117.2 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. Braem.be has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 21 (48%)

Requests Now

44

After Optimization

23

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

braem.be

braem.be

281 ms

www.braem.com

www.braem.com

524 ms

styles-m.min.css

styles-m.min.css

40 ms

styles.min.css

styles.min.css

64 ms

styles.min.css

styles.min.css

65 ms

owl.carousel.min.css

owl.carousel.min.css

64 ms

owl.theme.min.css

owl.theme.min.css

32 ms

styles-l.min.css

styles-l.min.css

32 ms

02164e9a34a8cdff79174277c8ca9829.min.js

02164e9a34a8cdff79174277c8ca9829.min.js

73 ms

api.js

api.js

72 ms

javascript.gp

javascript.gp

404 ms

email-decode.min.js

email-decode.min.js

72 ms

recaptcha__en.js

recaptcha__en.js

31 ms

bundle-common.min.js

bundle-common.min.js

753 ms

hqdefault.jpg

hqdefault.jpg

61 ms

nl.jpg

nl.jpg

382 ms

en.jpg

en.jpg

44 ms

fr.jpg

fr.jpg

45 ms

de.jpg

de.jpg

36 ms

es.jpg

es.jpg

45 ms

pl.jpg

pl.jpg

320 ms

ru.jpg

ru.jpg

61 ms

ro.jpg

ro.jpg

81 ms

ar.jpg

ar.jpg

60 ms

logo.svg

logo.svg

349 ms

slide_1.jpg

slide_1.jpg

83 ms

slide_2.jpg

slide_2.jpg

84 ms

slide_3.jpg

slide_3.jpg

813 ms

slide_4.jpg

slide_4.jpg

812 ms

truckbanner_2.jpg

truckbanner_2.jpg

333 ms

Flytt_banner_1.jpg

Flytt_banner_1.jpg

350 ms

revisie.jpg

revisie.jpg

822 ms

cdn.jpg

cdn.jpg

922 ms

areashot_braem_bw.jpg

areashot_braem_bw.jpg

398 ms

combinatielogo_esf.png

combinatielogo_esf.png

417 ms

betrouwbaar_1.jpg

betrouwbaar_1.jpg

461 ms

modal-show.min.js

modal-show.min.js

430 ms

fcce277c-07e2-4c88-ad8b-a71b484e2cbe.woff

fcce277c-07e2-4c88-ad8b-a71b484e2cbe.woff

896 ms

57055fe4-c2d3-4287-bac2-eece43fdcbd3.woff

57055fe4-c2d3-4287-bac2-eece43fdcbd3.woff

822 ms

cad22c74-45b4-4c49-9e6a-0cd3768a7bc7.woff

cad22c74-45b4-4c49-9e6a-0cd3768a7bc7.woff

1170 ms

Blank-Theme-Icons.woff

Blank-Theme-Icons.woff

792 ms

title_visual.svg

title_visual.svg

1043 ms

trucks_bg.jpg

trucks_bg.jpg

768 ms

plus.svg

plus.svg

796 ms

short_seperator.svg

short_seperator.svg

797 ms

triangle-bottom-right-icon.svg

triangle-bottom-right-icon.svg

1072 ms

aggregates_bg.jpg

aggregates_bg.jpg

808 ms

parts_bg.jpg

parts_bg.jpg

815 ms

services_bg.jpg

services_bg.jpg

1284 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

1393 ms

print.min.css

print.min.css

14 ms

Accessibility Review

braem.be accessibility score

81

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-hidden="true"] elements contain focusable descendents

High

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

High

[role]s are not contained by their required parent element

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.

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

Links do not have a discernible name

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

Best Practices

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

High

Missing source maps for large first-party JavaScript

SEO Factors

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

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

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

braem.be

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