Tools & Wizards About Us

Report Summary

  • 68

    Performance

    Renders faster than
    80% of other websites

  • 100

    Accessibility

    Visual factors better than
    that of 97% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

be.brussels

Welcome on the website of the Brussels Capital-Region | Brussels-Capital Region

Page Load Speed

3 sec in total

First Response

342 ms

Resources Loaded

2.5 sec

Page Rendered

111 ms

About Website

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

Welcome to the portal site of the Brussels-Capital Region. Here you will find all information on the administrations, cabinets and much more within the Brussels Region.

Visit be.brussels

Key Findings

We analyzed Be.brussels page load time and found that the first response time was 342 ms and then it took 2.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.

Performance Metrics

be.brussels performance score

68

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.5 s

66/100

10%

LCP (Largest Contentful Paint)

Value3.0 s

78/100

25%

SI (Speed Index)

Value3.8 s

84/100

10%

TBT (Total Blocking Time)

Value670 ms

44/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value6.9 s

53/100

10%

Network Requests Diagram

be.brussels

342 ms

be.brussels

381 ms

en

499 ms

5c0a6c41e1a5a0d8.css

111 ms

8e2683c18649ffd8.css

220 ms

Our browser made a total of 40 requests to load all elements on the main page. We found that all of those requests were addressed to Be.brussels and no external sources were called. The less responsive or slowest element that took the longest time to load (1 sec) belongs to the original domain Be.brussels.

Page Optimization Overview & Recommendations

Page size can be reduced by 329.3 kB (23%)

Content Size

1.4 MB

After Optimization

1.1 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Be.brussels 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. 30% of websites need less resources to load. Images take 957.9 kB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 63.1 kB

  • Original 75.9 kB
  • After minification 75.9 kB
  • After compression 12.8 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 63.1 kB or 83% of the original size.

Image Optimization

-3%

Potential reduce by 28.5 kB

  • Original 957.9 kB
  • After minification 929.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. Be images are well optimized though.

JavaScript Optimization

-62%

Potential reduce by 237.6 kB

  • Original 385.9 kB
  • After minification 385.9 kB
  • After compression 148.3 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.

CSS Optimization

-28%

Potential reduce by 63 B

  • Original 224 B
  • After minification 202 B
  • After compression 161 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.

Requests Breakdown

Number of requests can be reduced by 33 (89%)

Requests Now

37

After Optimization

4

  • Images
  • JavaScript
  • CSS

The browser has sent 37 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 28 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

Accessibility Review

be.brussels accessibility score

100

Accessibility Issues

Best Practices

be.brussels best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

be.brussels SEO score

100

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

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    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 matches the claimed 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.

Social Sharing Optimization

Open Graph data is detected on the main page of Be. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: