12.8 sec in total
286 ms
12.3 sec
268 ms
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.beWe analyzed Berner.be page load time and found that the first response time was 286 ms and then it took 12.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
berner.be performance score
name
value
score
weighting
Value9.7 s
0/100
10%
Value18.0 s
0/100
25%
Value14.0 s
1/100
10%
Value7,960 ms
0/100
30%
Value0.192
64/100
15%
Value25.3 s
0/100
10%
286 ms
4419 ms
975 ms
3942 ms
292 ms
Our browser made a total of 39 requests to load all elements on the main page. We found that 3% of them (1 request) were addressed to the original Berner.be, 28% (11 requests) were made to Shop.berner.eu and 18% (7 requests) were made to Mediaserver.berner.eu. The less responsive or slowest element that took the longest time to load (6.2 sec) relates to the external source Cdn4.berner.eu.
Page size can be reduced by 337.6 kB (15%)
2.3 MB
1.9 MB
In fact, the total size of Berner.be main page is 2.3 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. 25% of websites need less resources to load. Images take 1.9 MB which makes up the majority of the site volume.
Potential reduce by 232.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. This page needs HTML code to be minified as it can gain 136.1 kB, which is 54% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 232.6 kB or 92% of the original size.
Potential reduce by 73.0 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. Berner images are well optimized though.
Potential reduce by 32.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 32.0 kB or 60% of the original size.
Number of requests can be reduced by 3 (9%)
35
32
The browser has sent 35 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 4 to 1 for JavaScripts and as a result speed up the page load time.
berner.be
286 ms
start
4419 ms
combined.css
975 ms
combined.js
3942 ms
ffsuggest.block.jquery.jsonp.js
292 ms
9220849598494.png
281 ms
9220843339806.jpg
356 ms
9230360903710.jpg
677 ms
64627[TIF]-100.jpg
863 ms
9220849893406.png
278 ms
9220842127390.png
278 ms
9220849565726.png
279 ms
9220848156702.png
278 ms
56365[TIF]-100.jpg
767 ms
54452[TIF]-100.jpg
1364 ms
15834327-100.jpg
673 ms
16199[TIF]-100.jpg
770 ms
10099229-100.jpg
476 ms
10186010-100.jpg
866 ms
9231594487838.jpg
556 ms
9231594553374.jpg
557 ms
9231102869534.jpg
910 ms
9220844584990.png
1452 ms
9220844814366.jpg
276 ms
9220849762334.png
6200 ms
9220855365662.png
276 ms
gtm.js
189 ms
berner_iconfont.woff
176 ms
chooselanguage
463 ms
9220843175966.png
175 ms
glyphicons-halflings-regular.woff
196 ms
fontawesome-webfont.woff
495 ms
analytics.js
10 ms
collect
3 ms
collect
61 ms
ga-audiences
41 ms
fr-md.jpg
103 ms
nl-md.jpg
103 ms
fontawesome-webfont.ttf
391 ms
berner.be accessibility score
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
Buttons do not have an accessible name
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
berner.be SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
Document uses legible font sizes
Tap targets are not sized appropriately
NL
NL
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.
berner.be
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: