Tools & Wizards About Us

Report Summary

  • 6

    Performance

    Renders faster than
    21% of other websites

  • 85

    Accessibility

    Visual factors better than
    that of 58% of websites

  • 0

    Best Practices

  • 90

    SEO

    Google-friendlier than
    68% of websites

berner.be

Technische groothandel: specialist in gereedschappen en chemie | Berner Belgien NV/SA

Page Load Speed

1.7 sec in total

First Response

354 ms

Resources Loaded

1.2 sec

Page Rendered

113 ms

About Website

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

Vertrouw op de professionele gereedschappen en chemie van BERNER voor jouw dagelijks werk in construction en mobility

Visit berner.be

Key Findings

We analyzed Berner.be page load time and found that the first response time was 354 ms and then it took 1.3 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 25% of websites can load faster.

Performance Metrics

berner.be performance score

6

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value9.0 s

0/100

10%

LCP (Largest Contentful Paint)

Value73.9 s

0/100

25%

SI (Speed Index)

Value30.5 s

0/100

10%

TBT (Total Blocking Time)

Value2,300 ms

5/100

30%

CLS (Cumulative Layout Shift)

Value0.343

32/100

15%

TTI (Time to Interactive)

Value70.8 s

0/100

10%

Network Requests Diagram

berner.be

354 ms

309 ms

ruxitagentjs_ICA7NVfgqrux_10291240606133530.js

80 ms

loader.js

37 ms

uc-block.bundle.js

38 ms

Our browser made a total of 16 requests to load all elements on the main page. We found that 6% of them (1 request) were addressed to the original Berner.be, 69% (11 requests) were made to Shop.berner.eu and 13% (2 requests) were made to App.usercentrics.eu. The less responsive or slowest element that took the longest time to load (358 ms) relates to the external source Shop.berner.eu.

Page Optimization Overview & Recommendations

Page size can be reduced by 6.8 kB (3%)

Content Size

243.8 kB

After Optimization

237.0 kB

  • HTML
  • JavaScript

In fact, the total size of Berner.be main page is 243.8 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. 30% of websites need less resources to load. Javascripts take 234.2 kB which makes up the majority of the site volume.

HTML Optimization

-71%

Potential reduce by 6.8 kB

  • Original 9.5 kB
  • After minification 8.6 kB
  • After compression 2.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 6.8 kB or 71% of the original size.

JavaScript Optimization

-0%

Potential reduce by 0 B

  • Original 234.2 kB
  • After minification 234.2 kB
  • After compression 234.2 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 (36%)

Requests Now

11

After Optimization

7

  • Images
  • JavaScript
  • CSS

The browser has sent 11 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Berner. 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

Accessibility Review

berner.be accessibility score

85

Accessibility Issues

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

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.

SEO Factors

berner.be SEO score

90

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

    NL

  • Language Claimed

    NL

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Berner.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 Berner.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 description is not detected on the main page of Berner. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: