5 sec in total
284 ms
4.5 sec
214 ms
Visit harol.be now to see the best up-to-date Harol content for Belgium and also check out these interesting facts you probably never knew about harol.be
Duurzame zonwering, rolluiken en terrasoverkappingen van Harol. Ontdek hoe natuurlijke koeling je leefcomfort verhoogt in en rondom de woning.
Visit harol.beWe analyzed Harol.be page load time and found that the first response time was 284 ms and then it took 4.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
harol.be performance score
name
value
score
weighting
Value3.8 s
27/100
10%
Value13.8 s
0/100
25%
Value11.6 s
4/100
10%
Value660 ms
45/100
30%
Value0.229
54/100
15%
Value18.6 s
3/100
10%
284 ms
1547 ms
84 ms
164 ms
165 ms
Our browser made a total of 63 requests to load all elements on the main page. We found that 81% of them (51 requests) were addressed to the original Harol.be, 10% (6 requests) were made to Dealers.harol.be and 3% (2 requests) were made to S7.addthis.com. The less responsive or slowest element that took the longest time to load (1.5 sec) belongs to the original domain Harol.be.
Page size can be reduced by 607.4 kB (22%)
2.7 MB
2.1 MB
In fact, the total size of Harol.be main page is 2.7 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. 40% of websites need less resources to load. Images take 1.9 MB which makes up the majority of the site volume.
Potential reduce by 74.3 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 74.3 kB or 76% of the original size.
Potential reduce by 66.4 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. Harol images are well optimized though.
Potential reduce by 401.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 401.9 kB or 68% of the original size.
Potential reduce by 64.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. Harol.be needs all CSS files to be minified and compressed as it can save up to 64.9 kB or 81% of the original size.
Number of requests can be reduced by 30 (53%)
57
27
The browser has sent 57 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Harol. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 6 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
harol.be
284 ms
www.harol.be
1547 ms
css_xE-rWrJf-fncB6ztZfd2huxqgxu4WO-qwma6Xer30m4.css
84 ms
css_ubzgGJ35RgxN1IJggmIbJzwcE6NtKXa-uNCjJJK6XVo.css
164 ms
css_8htAelt9h_gKeIyesv_LaozgnblOGraqvbE7ot1AXNY.css
165 ms
css_92FJvazJvtijHqbXVH0SPnwbFsqp0TbqGd7G9pLElF0.css
166 ms
js_UWQINlriydSoeSiGQxToOUdv493zEa7dpsXC1OtYlZU.js
424 ms
js_q9Sdwv8HNz4LKsxIGv2ihnnDAfXABjUsVx7lHrAusFo.js
1317 ms
js_MQGlsBnV07CUUq924WcpN9CodXk1GwRvpkXKkz61yEk.js
172 ms
addthis_widget.js
9 ms
ga.js
177 ms
facebook.png
287 ms
pinterest.png
287 ms
twitter.png
287 ms
header_bg.png
157 ms
logo.png
185 ms
navigation_element_left_border.png
155 ms
navigation_element_bg.png
158 ms
button_search.png
156 ms
menu_sub_top.png
158 ms
menu_sub_repeat.png
183 ms
menu_sub_item_bg.png
211 ms
menu_seperator.png
184 ms
term_products_homepage.png
209 ms
slideshow_border.png
210 ms
HAROLdagen_2016_slideshow_691x379%20HABNL.jpg
321 ms
transparent.png
242 ms
HAROL_2016_ZONWERING_online_slideshow_691x379%20HABNL.jpg
402 ms
HAROL_2016_BUITENLEVEN_online_slideshow_691x379%20HABNL.jpg
403 ms
HAROL_2016_POORTEN_online_slideshow_691x379%20HABNL.jpg
405 ms
NOMO.png
923 ms
FUSION.png
1127 ms
VZ080-ZIP_NL.png
841 ms
SP800-compactoNL.png
1043 ms
HAROL_2015_banners_online_slideshow_691x379%20HAN4.jpg
564 ms
slideshow_left.png
484 ms
slideshow_right.png
565 ms
home_bg_top_news.png
645 ms
home_bg_news.png
646 ms
home_bg_bottom_news.png
725 ms
image_striped_bg.gif
727 ms
contentblock_bg_left.png
807 ms
contentblock_bg_right.png
808 ms
logo1.png
888 ms
contentblock_bg.png
889 ms
logo2.png
920 ms
logo3.png
970 ms
logo4.png
971 ms
komop_tegen_kanker_2014.png
1002 ms
300lo.json
75 ms
combinatielogo_trimmed.jpg
859 ms
doormat_bg.png
1066 ms
loading_animation.gif
905 ms
controls.png
936 ms
language_dropdown.png
935 ms
sh.8e5f85691f9aaa082472a194.html
50 ms
__utm.gif
37 ms
menu_sub_bottom.png
947 ms
collect
68 ms
facebook.png
350 ms
pinterest.png
351 ms
twitter.png
355 ms
css_f0-6IWLya3d0q9QSrarxCmDSRvOolt4_zcQaLcLMUu8.css
83 ms
harol.be accessibility score
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
[aria-*] attributes do not match their roles
[aria-hidden="true"] elements contain focusable descendents
ARIA input fields do not have accessible names
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
Image elements do not have [alt] attributes
Links do not have a discernible name
harol.be best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
harol.be SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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 Harol.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 Harol.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.
harol.be
Open Graph description is not detected on the main page of Harol. 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: