4.1 sec in total
142 ms
3.3 sec
569 ms
Click here to check amazing Woonpunt content. Otherwise, check out these important facts you probably never knew about woonpunt.be
Visit woonpunt.beWe analyzed Woonpunt.be page load time and found that the first response time was 142 ms and then it took 3.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
woonpunt.be performance score
name
value
score
weighting
Value2.5 s
69/100
10%
Value2.8 s
82/100
25%
Value2.5 s
98/100
10%
Value90 ms
99/100
30%
Value0.029
100/100
15%
Value2.8 s
97/100
10%
142 ms
672 ms
163 ms
29 ms
187 ms
Our browser made a total of 73 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Woonpunt.be, 49% (36 requests) were made to Citify-antwerp.be and 23% (17 requests) were made to Maps.googleapis.com. The less responsive or slowest element that took the longest time to load (835 ms) relates to the external source Citify-antwerp.be.
Page size can be reduced by 2.1 MB (34%)
6.1 MB
4.0 MB
In fact, the total size of Woonpunt.be main page is 6.1 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. 70% of websites need less resources to load. Images take 4.9 MB which makes up the majority of the site volume.
Potential reduce by 40 B
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 40 B or 22% of the original size.
Potential reduce by 1.2 MB
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. Obviously, Woonpunt needs image optimization as it can save up to 1.2 MB or 24% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 531.1 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 531.1 kB or 67% of the original size.
Potential reduce by 408.8 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. Woonpunt.be needs all CSS files to be minified and compressed as it can save up to 408.8 kB or 86% of the original size.
Number of requests can be reduced by 43 (65%)
66
23
The browser has sent 66 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Woonpunt. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 26 to 1 for JavaScripts and from 14 to 1 for CSS and as a result speed up the page load time.
woonpunt.be
142 ms
citify-antwerp.be
672 ms
language-selector.css
163 ms
css
29 ms
styles.css
187 ms
wpml-mod.css
186 ms
grid.css
184 ms
base.css
182 ms
layout.css
415 ms
shortcodes.css
565 ms
magnific-popup.css
255 ms
mediaelementplayer.css
334 ms
enfold.css
576 ms
custom.css
252 ms
jquery.js
598 ms
jquery-migrate.min.js
335 ms
avia-compat.js
421 ms
jquery.form.min.js
351 ms
scripts.js
424 ms
avia.js
597 ms
shortcodes.js
755 ms
jquery.magnific-popup.min.js
524 ms
mediaelement-and-player.min.js
595 ms
wp-mediaelement.js
595 ms
comment-reply.min.js
595 ms
wp-embed.min.js
596 ms
js
28 ms
wp-emoji-release.min.js
569 ms
analytics.js
49 ms
Citify-869x1030.png
421 ms
Citify-Antwerp-slide-2.jpg
833 ms
Citify-footer-864x1030.png
198 ms
Citify-web-1.png
835 ms
Citify-web-2.png
534 ms
Citify-web-3.png
675 ms
Bezoek-de-kijkunit.png
531 ms
Citify-footer-2.png
530 ms
URdUfE0ePw9inz9dceNoVA.woff
45 ms
entypo-fontello.woff
502 ms
collect
30 ms
common.js
87 ms
map.js
88 ms
util.js
87 ms
marker.js
87 ms
ajax-loader.gif
181 ms
StaticMapService.GetMapImage
116 ms
onion.js
47 ms
openhand_8_8.cur
42 ms
infowindow.js
51 ms
ViewportInfoService.GetViewportInfo
45 ms
stats.js
42 ms
controls.js
36 ms
transparent.png
42 ms
css
27 ms
spotlight-poi.png
96 ms
google4.png
78 ms
mapcnt6.png
80 ms
print.css
116 ms
vt
31 ms
vt
134 ms
vt
61 ms
vt
59 ms
vt
47 ms
tmapctrl.png
53 ms
2UX7WLTfW3W8TclTUvlFyQ.woff
40 ms
RxZJdnzeo3R5zSexge8UUT8E0i7KZn-EPnyo3HZu7kw.woff
47 ms
Hgo13k-tfSpn0qi1SFdUfT8E0i7KZn-EPnyo3HZu7kw.woff
43 ms
d-6IYplOFocCacKzxwXSOD8E0i7KZn-EPnyo3HZu7kw.woff
47 ms
cb_scout5.png
110 ms
tmapctrl4.png
108 ms
arrow-down.png
106 ms
imgs8.png
108 ms
AuthenticationService.Authenticate
196 ms
woonpunt.be accessibility score
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
<frame> or <iframe> elements do not have a title
woonpunt.be best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
woonpunt.be 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
N/A
N/A
N/A
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Woonpunt.be can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else) and no language is claimed in <html> or <meta> tags either. Our system also found out that Woonpunt.be main page’s claimed encoding is . Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
woonpunt.be
Open Graph description is not detected on the main page of Woonpunt. 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: