2.1 sec in total
112 ms
1.7 sec
296 ms
Welcome to brugge.be homepage info - get ready to check Brugge best content for Belgium right away, or after learning these important things about brugge.be
Welkom op de officiële website van Stad Brugge. Maak kennis met de stad, het bestuur en wat er leeft in Brugge.
Visit brugge.beWe analyzed Brugge.be page load time and found that the first response time was 112 ms and then it took 2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.
brugge.be performance score
name
value
score
weighting
Value3.8 s
26/100
10%
Value6.4 s
10/100
25%
Value8.6 s
17/100
10%
Value5,930 ms
0/100
30%
Value0.046
99/100
15%
Value28.0 s
0/100
10%
112 ms
137 ms
673 ms
49 ms
87 ms
Our browser made a total of 38 requests to load all elements on the main page. We found that 53% of them (20 requests) were addressed to the original Brugge.be, 13% (5 requests) were made to Brugge.matomo.cloud and 11% (4 requests) were made to Prod.widgets.burgerprofiel.vlaanderen.be. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain Brugge.be.
Page size can be reduced by 274.4 kB (4%)
7.8 MB
7.6 MB
In fact, the total size of Brugge.be main page is 7.8 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. 85% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 7.4 MB which makes up the majority of the site volume.
Potential reduce by 104.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 104.3 kB or 79% of the original size.
Potential reduce by 162.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. Brugge images are well optimized though.
Potential reduce by 7.5 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. This website has mostly compressed JavaScripts.
Potential reduce by 189 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. Brugge.be has all CSS files already compressed.
Number of requests can be reduced by 17 (53%)
32
15
The browser has sent 32 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Brugge. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 18 to 1 for JavaScripts and as a result speed up the page load time.
brugge.be
112 ms
www.brugge.be
137 ms
matomo.js
673 ms
container_lXYwpEZZ.js
49 ms
otSDKStub.js
87 ms
css_w-BU8CBjPtnuD5x-4gaXc6BtcvsH2lLx9HVrBFflYcM.css
5 ms
css_gbjWcpE5pSWhabaHgZXmtNjNB56dUXnLKZQq0joIO3g.css
13 ms
embed
406 ms
js_MQWarR980NIiSQ3n3rp5b8beTCYVZJ5BcuKwReCbS-o.js
37 ms
page.js
101 ms
js_XxKMko5BGHguQZ-ii_CY-PK9Ya9ky13QqfOAr7Yz2sI.js
23 ms
index.js
624 ms
index.js
399 ms
js_dFI6y2udj2jyOMlL878w5IgB_nJs5pOWpLM19Z6CiXw.js
36 ms
webchat.bootstrap.js
667 ms
js_kvLOhFDQm8iEIBAyXUSuYOmAOPvfjLVTBXvj96kcbLo.js
35 ms
matomo.php
574 ms
018e7b64-b52b-77c6-8d19-72d56f66a101.json
51 ms
logo.svg
15 ms
DeWaterkant.jpg
571 ms
20230518_Heilige%20Bloedprocessie%202023%20Brugge_c_Frank%20Toussaint_466_72dpi.jpg
18 ms
OpenWervendagBrusk.jpg
565 ms
1ffc5dc9-89b3-452d-93a1-3db2951d3456.jpeg
931 ms
a9801291-4272-487d-a7d8-4b115b26bca1.png
693 ms
0689663e-136f-45e9-b523-c7cf57e90fa6.jpeg
1201 ms
configs.php
544 ms
configs.php
540 ms
location
50 ms
otBannerSdk.js
29 ms
index.min.js
253 ms
Poppins-Regular.woff
668 ms
Poppins-SemiBold.woff
655 ms
Poppins-Bold.woff
33 ms
Domine-Regular.woff
554 ms
sm.25.html
43 ms
eso.BRQnzO8v.js
75 ms
matomo.php
136 ms
css_2vEOQeaa6RV3PunxQgvew9O5D6dw6jfZ2ep2jv7yA0o.css
4 ms
brugge.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
[role]s do not have all required [aria-*] attributes
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
Form elements do not have associated labels
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
[id] attributes on active, focusable elements are not unique
Heading elements are not in a sequentially-descending order
brugge.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
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
brugge.be SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
NL
NL
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Brugge.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 Brugge.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.
brugge.be
Open Graph description is not detected on the main page of Brugge. 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: