4.5 sec in total
846 ms
3.2 sec
495 ms
Visit be.brussels now to see the best up-to-date Be content for Belgium and also check out these interesting facts you probably never knew about be.brussels
Visit be.brusselsWe analyzed Be.brussels page load time and found that the first response time was 846 ms and then it took 3.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
be.brussels performance score
name
value
score
weighting
Value8.3 s
0/100
10%
Value9.8 s
0/100
25%
Value17.7 s
0/100
10%
Value14,760 ms
0/100
30%
Value0.001
100/100
15%
Value25.1 s
0/100
10%
846 ms
164 ms
326 ms
167 ms
169 ms
Our browser made a total of 97 requests to load all elements on the main page. We found that 80% of them (78 requests) were addressed to the original Be.brussels, 4% (4 requests) were made to S7.addthis.com and 4% (4 requests) were made to Cdn.media.agenda.be. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain Be.brussels.
Page size can be reduced by 351.2 kB (24%)
1.5 MB
1.1 MB
In fact, the total size of Be.brussels main page is 1.5 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 957.9 kB which makes up the majority of the site volume.
Potential reduce by 85.0 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 12.0 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 85.0 kB or 75% of the original size.
Potential reduce by 28.5 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. Be images are well optimized though.
Potential reduce by 237.6 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 237.6 kB or 62% of the original size.
Potential reduce by 63 B
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. Be.brussels needs all CSS files to be minified and compressed as it can save up to 63 B or 28% of the original size.
Number of requests can be reduced by 38 (40%)
94
56
The browser has sent 94 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Be. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 17 to 1 for JavaScripts and from 11 to 1 for CSS and as a result speed up the page load time.
be.brussels
846 ms
reset-cachekey-d6aef8322b0aaead035a3edf23dae119.css
164 ms
public-cachekey-b358c3929732480884115a1e502d84ab.css
326 ms
myjquery-cachekey-a052cff5ee0126c53d1c8e030b299770.css
167 ms
resourcejekylldiagnosis-cachekey-3c436ad865f9d0451be04158c42a2075.css
169 ms
resourceprb.workflow.cssmember-cachekey-6d84eb5d0a5741cac969460c35e99256.css
170 ms
resourcejquery-ui-themessunburstjqueryui-cachekey-b6ebcdf709d079cb5ffbedda2d0f5b3c.css
320 ms
resourceprb.arsene50arsene50-cachekey-d94672315a39e87f9de558281bd9b98a.css
242 ms
resourcecollective.js.bootstrapcssbootstrap.min-cachekey-c25e59514bd41f1376dec326a51e742a.css
611 ms
themeplonetheme.prbcsstheme-cachekey-cc64a4eab9808f6224a07a6f6e10dc0a.css
406 ms
resourcecookiepolicycookiepolicy-cachekey-1974d8d1cbd4d7dbe9dd5b0f172cf7e0.css
251 ms
resourceplone.app.jquery-cachekey-2c32cbaceb29069fd335bf8d5150da7b.js
1165 ms
formsubmithelpers-cachekey-1eb4e723f286cb24b9a6ddc19682f222.js
334 ms
plone_javascript_variables-cachekey-4df50e24523e31b838dda35c181a31b4.js
401 ms
modernizr-cachekey-1400cd2c478aed9a5fa7c437c5f954cf.js
403 ms
resourceanalytics_config-cachekey-2bd0f29c6834b2a2298efc936d3d714a.js
416 ms
resourcejquery.datatablesextrasTableToolsmediajsZeroClipboard-cachekey-d3e2492490b7505c28c9c39bfe1cd3ed.js
482 ms
themeplonetheme.prbjstheme-cachekey-b38f3b401bf9332b4138f09f439ad770.js
486 ms
resourcejquery.galleriffic-cachekey-231f352c04c3497892619dc7ced3f52d.js
485 ms
resourcejquery.opacityrollover-cachekey-03f7e7cdba746c2f2d11969e44449895.js
496 ms
resourcejquery.history-cachekey-bb9524b333419cb6e3aee0db242f0115.js
564 ms
resourcecollective.js.bootstrapjsbootstrap.min-cachekey-9b6e949f125b18a088f3231f077cdd7b.js
645 ms
css
25 ms
addthis_widget.js
8 ms
ga.js
13 ms
header_row_bg.jpg
342 ms
6618761adc736b1dff2438af50fb75c797aaa404.jpg
782 ms
header.png
344 ms
ls_spacer.gif
338 ms
ls_sprite.png
332 ms
searchButton-white.png
343 ms
searchButton.png
345 ms
be-chez-vous-be-brussels.png
347 ms
nav_header_bg_vab.jpg
357 ms
nav_ul_li.jpg
348 ms
nav_header_bg_ctl.jpg
352 ms
nav_header_bg_te.jpg
351 ms
portlet_header_bg.jpg
348 ms
bxl_img_trans.gif
354 ms
hp_votre-photo-ici_stop.png
356 ms
hp_votre-photo-ici_play.png
359 ms
image_preview
363 ms
logo_agenda.png
360 ms
visitbrussels.png
367 ms
bruxelles-gratuit
420 ms
services-en-ligne
417 ms
primes-et-subsides
420 ms
taxes-regionales
417 ms
siamu
481 ms
image
480 ms
image
576 ms
Web_Night_Icon16.png
568 ms
pollu_3_fr.gif
574 ms
image
585 ms
image_thumb
604 ms
image_thumb
605 ms
image_mini
623 ms
label_anysurfer_50x40.png
606 ms
region-bruxelles-capitale-brussels-hoofdstedelijk-gewest.jpg
728 ms
8c914035d9d598fcc9423f70101d31a722bae77a.jpg
357 ms
flagey-31f54011470428fa6d5446cda3e22649eab0df86.jpg
345 ms
flagey-2ec5dbb54d5ab7aa4a129c69737c1a57760ac13f.jpg
343 ms
all.js
363 ms
300lo.json
88 ms
379.2897044bcdaf764dc874.js
69 ms
counter.e06ccbeb85753d56d6a9.js
105 ms
nav_header_bg_mt.jpg
319 ms
nav_header_bg_ef.jpg
410 ms
image
410 ms
hp_votre-photo-ici_header_bg.png
403 ms
image
487 ms
image
538 ms
image
664 ms
partagez-vos-photos.gif
433 ms
hp_votre-photo-ici_nav_off.png
430 ms
hp_slider_left_on.jpg
428 ms
hp_slider_right_on.jpg
492 ms
sitemap_bg.jpg
491 ms
bg.gif
489 ms
nomensa-logo-small.gif
552 ms
button-play.gif
568 ms
button-rewind.gif
567 ms
button-forward.gif
563 ms
timeline-bg.gif
598 ms
timeline-point.gif
622 ms
timeline-played.gif
643 ms
guC5lwT5Dw7anV_xfpCGqw.ttf
98 ms
timeline-loaded.gif
622 ms
sh.7c7179124ea24ac6ba46caac.html
94 ms
__utm.gif
166 ms
hp_votre-photo-ici_nav_on.png
587 ms
spinner.gif
621 ms
shares.json
114 ms
collect
201 ms
141 ms
xd_arbiter.php
219 ms
xd_arbiter.php
422 ms
be.brussels 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
<frame> or <iframe> elements do not have a title
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
[id] attributes on active, focusable elements are not unique
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.
be.brussels 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
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
be.brussels SEO score
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
EN
FR
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Be.brussels can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it does not match the claimed French language. Our system also found out that Be.brussels 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.
be.brussels
Open Graph description is not detected on the main page of Be. 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: