Tools & Wizards About Us
heures.be screenshot

Report Summary

  • 14

    Performance

    Renders faster than
    26% of other websites

  • 73

    Accessibility

    Visual factors better than
    that of 38% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 98

    SEO

    Google-friendlier than
    92% of websites

heures.be

Heures d'ouverture et horaire de tous les commerces en Belgique sur Heures.be

Page Load Speed

4.2 sec in total

First Response

378 ms

Resources Loaded

3.7 sec

Page Rendered

157 ms

heures.be screenshot

About Website

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

Sur Heures.be vous trouverez les heures d'ouverture des magasins Belges. Vous ne savez pas si votre magasin préféré est ouvert ? Recherchez vite ses horaires ! Vous trouverez également ici les magasin...

Visit heures.be

Key Findings

We analyzed Heures.be page load time and found that the first response time was 378 ms and then it took 3.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.

Performance Metrics

heures.be performance score

14

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.0 s

24/100

10%

LCP (Largest Contentful Paint)

Value4.7 s

32/100

25%

SI (Speed Index)

Value8.6 s

17/100

10%

TBT (Total Blocking Time)

Value3,040 ms

2/100

30%

CLS (Cumulative Layout Shift)

Value1.103

1/100

15%

TTI (Time to Interactive)

Value14.3 s

9/100

10%

Network Requests Diagram

heures.be

378 ms

heures.be

383 ms

www.heures.be

502 ms

global.css

97 ms

responsive.css

193 ms

Our browser made a total of 102 requests to load all elements on the main page. We found that 42% of them (43 requests) were addressed to the original Heures.be, 15% (15 requests) were made to Pagead2.googlesyndication.com and 12% (12 requests) were made to Googleads.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (579 ms) relates to the external source Googleads.g.doubleclick.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 246.3 kB (18%)

Content Size

1.4 MB

After Optimization

1.1 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Heures.be main page is 1.4 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. 65% of websites need less resources to load. Javascripts take 1.0 MB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 40.3 kB

  • Original 49.9 kB
  • After minification 44.5 kB
  • After compression 9.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. This page needs HTML code to be minified as it can gain 5.4 kB, which is 11% 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 40.3 kB or 81% of the original size.

Image Optimization

-10%

Potential reduce by 25.0 kB

  • Original 259.9 kB
  • After minification 234.9 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. Heures images are well optimized though.

JavaScript Optimization

-17%

Potential reduce by 179.8 kB

  • Original 1.0 MB
  • After minification 1.0 MB
  • After compression 858.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 179.8 kB or 17% of the original size.

CSS Optimization

-13%

Potential reduce by 1.2 kB

  • Original 9.6 kB
  • After minification 9.6 kB
  • After compression 8.4 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. Heures.be needs all CSS files to be minified and compressed as it can save up to 1.2 kB or 13% of the original size.

Requests Breakdown

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

Requests Now

94

After Optimization

46

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

heures.be

heures.be

378 ms

heures.be

heures.be

383 ms

www.heures.be

www.heures.be

502 ms

global.css

global.css

97 ms

responsive.css

responsive.css

193 ms

heures.js

heures.js

280 ms

jquery.min.js

jquery.min.js

33 ms

js

js

120 ms

autocolumn.js

autocolumn.js

298 ms

jquery.ui.addons.min.js

jquery.ui.addons.min.js

300 ms

jquery.bxslider.min.js

jquery.bxslider.min.js

295 ms

adsbygoogle.js

adsbygoogle.js

175 ms

testab.js

testab.js

323 ms

ads.js

ads.js

295 ms

body_bg.png

body_bg.png

99 ms

nav_icon.png

nav_icon.png

103 ms

heures_logo_full.png

heures_logo_full.png

103 ms

menu_bg_hover.png

menu_bg_hover.png

101 ms

menu_bg.png

menu_bg.png

102 ms

content_bg.png

content_bg.png

100 ms

slotcar_library.js

slotcar_library.js

81 ms

show_ads_impl.js

show_ads_impl.js

386 ms

button.png

button.png

117 ms

LargeSquare16.png

LargeSquare16.png

303 ms

icon_henegouwen.png

icon_henegouwen.png

116 ms

icon_luik.png

icon_luik.png

117 ms

icon_luxemburg.png

icon_luxemburg.png

115 ms

icon_namen.png

icon_namen.png

117 ms

icon_waals_brabant.png

icon_waals_brabant.png

203 ms

icon_brussel.png

icon_brussel.png

210 ms

icon_antwerpen.png

icon_antwerpen.png

210 ms

icon_limburg.png

icon_limburg.png

211 ms

icon_oost_vlaanderen.png

icon_oost_vlaanderen.png

212 ms

icon_vlaams_brabant.png

icon_vlaams_brabant.png

297 ms

icon_west_vlaanderen.png

icon_west_vlaanderen.png

305 ms

logo_decathlon.png

logo_decathlon.png

304 ms

logo_lidl.png

logo_lidl.png

306 ms

logo_colruyt.png

logo_colruyt.png

306 ms

logo_aldi.png

logo_aldi.png

420 ms

logo_jbc.png

logo_jbc.png

420 ms

logo_carrefour.png

logo_carrefour.png

420 ms

logo_delhaize.png

logo_delhaize.png

420 ms

logo_dreamland.png

logo_dreamland.png

421 ms

logo_gamma.png

logo_gamma.png

421 ms

logo_bpost.png

logo_bpost.png

482 ms

logo_csc.png

logo_csc.png

491 ms

logo_action.png

logo_action.png

494 ms

footer_bg.png

footer_bg.png

473 ms

zrt_lookup.html

zrt_lookup.html

42 ms

ads

ads

347 ms

ads

ads

520 ms

ads

ads

579 ms

ads

ads

348 ms

reactive_library.js

reactive_library.js

256 ms

ca-pub-4682217505739942

ca-pub-4682217505739942

185 ms

pixel

pixel

209 ms

dv3.js

dv3.js

208 ms

window_focus.js

window_focus.js

18 ms

qs_click_protection.js

qs_click_protection.js

21 ms

ufs_web_display.js

ufs_web_display.js

16 ms

gen_204

gen_204

219 ms

pixel

pixel

191 ms

gen_204

gen_204

190 ms

6044053332501058535

6044053332501058535

367 ms

abg_lite.js

abg_lite.js

185 ms

omrhp.js

omrhp.js

240 ms

Q12zgMmT.js

Q12zgMmT.js

179 ms

icon.png

icon.png

130 ms

pixel

pixel

389 ms

7f032190f136c4d8e9a385e88120dc8d.js

7f032190f136c4d8e9a385e88120dc8d.js

353 ms

load_preloaded_resource.js

load_preloaded_resource.js

196 ms

af5cf33f216dd68f5f355584e69bf9d6.js

af5cf33f216dd68f5f355584e69bf9d6.js

387 ms

abg_lite.js

abg_lite.js

208 ms

5f7468413707c3abfd197d65a482477f.js

5f7468413707c3abfd197d65a482477f.js

387 ms

pixel

pixel

381 ms

ad

ad

183 ms

62bHydCX.html

62bHydCX.html

154 ms

s

s

203 ms

fullscreen_api_adapter.js

fullscreen_api_adapter.js

144 ms

interstitial_ad_frame.js

interstitial_ad_frame.js

165 ms

feedback_grey600_24dp.png

feedback_grey600_24dp.png

191 ms

settings_grey600_24dp.png

settings_grey600_24dp.png

191 ms

14763004658117789537

14763004658117789537

191 ms

html_inpage_rendering_lib_200_280.js

html_inpage_rendering_lib_200_280.js

182 ms

activeview

activeview

222 ms

pixel

pixel

284 ms

ad

ad

204 ms

gen_204

gen_204

255 ms

css

css

194 ms

ckySkFmwfmQXT3S4i881M7X0Dq040p3kAeEpVWKJmn8.js

ckySkFmwfmQXT3S4i881M7X0Dq040p3kAeEpVWKJmn8.js

29 ms

rum

rum

139 ms

bounce

bounce

79 ms

249 ms

11501585815148055454

11501585815148055454

160 ms

dc_oe=ChMIrojkyIndhwMVQQloCB0XuTxdEAAYACDujphoQhMIq_XByIndhwMVnrLRBB2q5yx-;dc_eps=AHas8cDHDs-FBCMadr2FRGROZC5i_dWY1dZAE6aKp4n3LNOT-O66zh2bNzdq4MvY2HDshte_zHKumRf9wfPRg1rm1Lc;met=1;×tamp=1722834210558;eid1=9;ecn1=1;etm1=0;

dc_oe=ChMIrojkyIndhwMVQQloCB0XuTxdEAAYACDujphoQhMIq_XByIndhwMVnrLRBB2q5yx-;dc_eps=AHas8cDHDs-FBCMadr2FRGROZC5i_dWY1dZAE6aKp4n3LNOT-O66zh2bNzdq4MvY2HDshte_zHKumRf9wfPRg1rm1Lc;met=1;×tamp=1722834210558;eid1=9;ecn1=1;etm1=0;

298 ms

pixel

pixel

138 ms

pixel

pixel

138 ms

activeview

activeview

150 ms

rum

rum

111 ms

4Ua_rENHsxJlGDuGo1OIlJfC6l_24rlCK1Yo_Iqcsih3SAyH6cAwhX9RFD48TE63OOYKtrw2IJllpyw.ttf

4Ua_rENHsxJlGDuGo1OIlJfC6l_24rlCK1Yo_Iqcsih3SAyH6cAwhX9RFD48TE63OOYKtrw2IJllpyw.ttf

121 ms

4Ua_rENHsxJlGDuGo1OIlJfC6l_24rlCK1Yo_Iqcsih3SAyH6cAwhX9RFD48TE63OOYKtrwEIJllpyw.ttf

4Ua_rENHsxJlGDuGo1OIlJfC6l_24rlCK1Yo_Iqcsih3SAyH6cAwhX9RFD48TE63OOYKtrwEIJllpyw.ttf

122 ms

activeview

activeview

94 ms

Accessibility Review

heures.be accessibility score

73

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.

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

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

Form elements do not have associated labels

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.

Best Practices

heures.be best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

heures.be SEO score

98

Search Engine Optimization Advices

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

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Heures.be can be misinterpreted by Google and other search engines. Our service has detected that French is used on the page, and it does not match the claimed English language. Our system also found out that Heures.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

heures.be

Open Graph description is not detected on the main page of Heures. 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: