3.5 sec in total
689 ms
2.7 sec
164 ms
Welcome to brussel.be homepage info - get ready to check Brussel best content for Belgium right away, or after learning these important things about brussel.be
De officiële website van de Stad Brussel, hoofdstad van België: e-loket, online afspraak maken, nieuws, agenda, webcams,...
Visit brussel.beWe analyzed Brussel.be page load time and found that the first response time was 689 ms and then it took 2.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
brussel.be performance score
name
value
score
weighting
Value4.3 s
17/100
10%
Value4.7 s
32/100
25%
Value11.7 s
4/100
10%
Value1,030 ms
26/100
30%
Value0.002
100/100
15%
Value15.5 s
7/100
10%
689 ms
565 ms
402 ms
321 ms
21 ms
Our browser made a total of 60 requests to load all elements on the main page. We found that 93% of them (56 requests) were addressed to the original Brussel.be, 3% (2 requests) were made to Ajax.googleapis.com and 3% (2 requests) were made to Stats.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (689 ms) belongs to the original domain Brussel.be.
Page size can be reduced by 424.8 kB (30%)
1.4 MB
971.7 kB
In fact, the total size of Brussel.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. 35% of websites need less resources to load. Images take 862.6 kB which makes up the majority of the site volume.
Potential reduce by 36.4 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 9.7 kB, which is 21% 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 36.4 kB or 80% of the original size.
Potential reduce by 11.1 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. Brussel images are well optimized though.
Potential reduce by 197.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 197.0 kB or 72% of the original size.
Potential reduce by 180.2 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. Brussel.be needs all CSS files to be minified and compressed as it can save up to 180.2 kB or 85% of the original size.
Number of requests can be reduced by 30 (52%)
58
28
The browser has sent 58 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Brussel. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 14 to 1 for JavaScripts and from 10 to 1 for CSS and as a result speed up the page load time.
artdet.cfm
689 ms
bootstrap.min.css
565 ms
bxl.css
402 ms
component.css
321 ms
jquery-ui.css
21 ms
cookiecuttr.css
167 ms
lightcase.css
243 ms
footable.core.min.css
171 ms
swfobject.js
252 ms
ttkSlider.css
401 ms
datepicker3.css
404 ms
jquery.min.js
20 ms
compressed.js
485 ms
momentlocales.js
332 ms
bootstrap-datepicker.js
496 ms
bootstrap.min.js
339 ms
lightcase.js
506 ms
jquery.cookie.js
338 ms
modernizr.custom.js
500 ms
jquery.dlmenu.js
501 ms
brussels_jquery.js
501 ms
jquery.cookiecuttr.js
502 ms
jquery_ttkSlider.js
502 ms
dc.js
30 ms
__utm.gif
52 ms
33.gif
126 ms
header.jpg
166 ms
logo_cityofbrussels_new.gif
126 ms
name_city_nl.png
126 ms
search_button.gif
126 ms
arrow_link.png
127 ms
name_city_nl_print.png
166 ms
search_btn.png
165 ms
btn_newsletter.png
166 ms
btn_rss.png
166 ms
btn_facebook.png
195 ms
btn_twitter.png
251 ms
btn_foursquare.png
248 ms
btn_google.png
250 ms
btn_pinterest.png
253 ms
btn_scoop.png
252 ms
mainpage.cfm
531 ms
mainpage.cfm
428 ms
mainpage.cfm
345 ms
mainpage.cfm
436 ms
mainpage.cfm
514 ms
mainpage.cfm
513 ms
mainpage.cfm
525 ms
mainpage.cfm
524 ms
mainpage.cfm
531 ms
arrow_blue.png
593 ms
mainpage.cfm
599 ms
mainpage.cfm
609 ms
editor_homepage_box_1.jpg
605 ms
logo_unesco.gif
609 ms
slider_nav.png
496 ms
slider_play_pause.png
557 ms
slider_pointer.png
565 ms
museo500-regular-webfont.woff
569 ms
bxl_print.css
83 ms
brussel.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
button, link, and menuitem elements do not have accessible names.
ARIA IDs are not unique
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
Form elements do not have associated labels
Links do not have a discernible name
brussel.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
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
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
brussel.be SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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 Brussel.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 Brussel.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.
brussel.be
Open Graph description is not detected on the main page of Brussel. 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: