10.6 sec in total
1.1 sec
8.8 sec
642 ms
Click here to check amazing Antwerpen content for Belgium. Otherwise, check out these important facts you probably never knew about antwerpen.be
Officiële website van de stad Antwerpen met online dienstverlening (e-loket en afspraken maken), praktische informatie (contactgegevens en openingsuren), nieuws op maat, stadsplan, vrijetijdskalender ...
Visit antwerpen.beWe analyzed Antwerpen.be page load time and found that the first response time was 1.1 sec and then it took 9.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
antwerpen.be performance score
name
value
score
weighting
Value8.6 s
0/100
10%
Value10.5 s
0/100
25%
Value10.3 s
8/100
10%
Value960 ms
29/100
30%
Value0.525
14/100
15%
Value10.8 s
22/100
10%
1142 ms
91 ms
181 ms
268 ms
270 ms
Our browser made a total of 101 requests to load all elements on the main page. We found that 80% of them (81 requests) were addressed to the original Antwerpen.be, 16% (16 requests) were made to Assets.antwerpen.be and 2% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (3.4 sec) relates to the external source Assets.antwerpen.be.
Page size can be reduced by 1.4 MB (49%)
2.9 MB
1.5 MB
In fact, the total size of Antwerpen.be main page is 2.9 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 1.2 MB which makes up the majority of the site volume.
Potential reduce by 45.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 10.6 kB, which is 20% 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 45.4 kB or 84% of the original size.
Potential reduce by 18.2 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. Antwerpen images are well optimized though.
Potential reduce by 719.4 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 719.4 kB or 78% of the original size.
Potential reduce by 652.6 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. Antwerpen.be needs all CSS files to be minified and compressed as it can save up to 652.6 kB or 89% of the original size.
Number of requests can be reduced by 42 (42%)
99
57
The browser has sent 99 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Antwerpen. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 27 to 1 for JavaScripts and from 17 to 1 for CSS and as a result speed up the page load time.
www.antwerpen.be
1142 ms
MarkerCluster.Default.css
91 ms
MarkerCluster.css
181 ms
cropper.min.css
268 ms
leaflet.css
270 ms
perfect-scrollbar-0.4.9.min.css
310 ms
v-accordion.css
306 ms
kaai.css
422 ms
aos-split-blessed1.css
671 ms
aos-split.css
620 ms
e-loket-20160202135723.min.css
356 ms
reports-20160202135723.min.css
404 ms
overzicht-20160122124012.min.css
512 ms
info-20160112141450.min.css
445 ms
stadsplan-20160201164149.min.css
507 ms
vacatures-20150707162646.min.css
536 ms
kalender-20151209121746.min.css
604 ms
aOS-vendors-20160204111014.min.js
1562 ms
e-loket-20160202135723.min.js
847 ms
reports-20160202135723.min.js
657 ms
overzicht-20160122124012.min.js
803 ms
info-20160112141450.min.js
782 ms
stadsplan-20160201164149.min.js
833 ms
stadsplanTemplates.js
791 ms
search-20151204164448.min.js
794 ms
vacatures-20150707162646.min.js
877 ms
organisations-20160128114955.min.js
885 ms
kalender-20151209121746.min.js
901 ms
user-20160202132728.min.js
914 ms
common-20160204111014.min.js
1042 ms
context-20160204111014.min.js
981 ms
helper-20160204111014.min.js
975 ms
dialog-20160204111014.min.js
998 ms
form-20160204111014.min.js
1061 ms
frConfig-20160204111014.min.js
1064 ms
kaai-20160204111014.min.js
1081 ms
media-20160204111014.min.js
1034 ms
renderer-20160204111014.min.js
983 ms
snippets-20160204111014.min.js
915 ms
user-20160204111014.min.js
906 ms
widgets-20160204111014.min.js
898 ms
templates-20160204111014.min.js
921 ms
aOS-20160204111014.min.js
911 ms
_serviceroutes.config.js
900 ms
analytics.js
82 ms
OpenSans-400.woff
468 ms
OpenSans-300.woff
502 ms
OpenSans-600.woff
530 ms
OpenSans-700.woff
571 ms
1838 ms
list
1152 ms
loading.htm
92 ms
me
277 ms
header.htm
151 ms
statusbar.htm
144 ms
home.htm
100 ms
collect
40 ms
packery.htm
92 ms
bar-notification
1133 ms
10
290 ms
homepage-link-set
111 ms
%7B%7BoverviewLink.image%7D%7D
1169 ms
kaai.htm
193 ms
request.svg
3254 ms
list.svg
3270 ms
conversation.svg
3252 ms
calendar.svg
3395 ms
location.svg
3396 ms
letter.svg
3395 ms
message.svg
3421 ms
vrijetijdskalender.svg
3387 ms
acons.svg
1033 ms
popout.htm
794 ms
flyout.htm
907 ms
kaai-search.svg
1440 ms
a-logo.svg
1438 ms
search.svg
1882 ms
profile_previewupload
3057 ms
mediaitem.htm
1092 ms
slideshow.htm
1056 ms
mediaembed.htm
948 ms
%7B%7BrenderableObject.channel.image%7D%7D
2506 ms
%7B%7BrenderableObject.file[0].src%7D%7D
2505 ms
teaser-overview.htm
2091 ms
teaser-notifications.htm
2242 ms
teaser-profile.htm
2198 ms
teaser-login.htm
2036 ms
dropdown-arrow.svg
1734 ms
newsfeed_1columns
1789 ms
newsfeed_1columns
2065 ms
newsfeed_1columns
1839 ms
newsfeed_1columns
1769 ms
newsfeed_1columns
1827 ms
newsfeed_1columns
1677 ms
newsfeed_1columns
1827 ms
newsfeed_1columns
2503 ms
kaai-profile.svg
409 ms
kaai-overview.svg
300 ms
user-avatar.htm
304 ms
missing-user.svg
164 ms
print.css
150 ms
antwerpen.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
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
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
Links do not have a discernible name
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
antwerpen.be best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
antwerpen.be SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
robots.txt is not valid
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 Antwerpen.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 Antwerpen.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.
antwerpen.be
Open Graph description is not detected on the main page of Antwerpen. 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: