5.6 sec in total
339 ms
4.6 sec
658 ms
Welcome to stadhuis.nl homepage info - get ready to check Stad Huis best content for Netherlands right away, or after learning these important things about stadhuis.nl
Website description
Visit stadhuis.nlWe analyzed Stadhuis.nl page load time and found that the first response time was 339 ms and then it took 5.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
stadhuis.nl performance score
name
value
score
weighting
Value3.6 s
32/100
10%
Value7.9 s
3/100
25%
Value8.6 s
17/100
10%
Value960 ms
28/100
30%
Value0.011
100/100
15%
Value14.5 s
8/100
10%
339 ms
1823 ms
141 ms
257 ms
167 ms
Our browser made a total of 127 requests to load all elements on the main page. We found that 40% of them (51 requests) were addressed to the original Stadhuis.nl, 16% (20 requests) were made to Public.parariusoffice.nl and 16% (20 requests) were made to Static.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (1.8 sec) belongs to the original domain Stadhuis.nl.
Page size can be reduced by 317.5 kB (28%)
1.1 MB
825.2 kB
In fact, the total size of Stadhuis.nl main page is 1.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. 55% of websites need less resources to load. Images take 733.9 kB which makes up the majority of the site volume.
Potential reduce by 51.5 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 22.7 kB, which is 38% 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 51.5 kB or 86% of the original size.
Potential reduce by 34.5 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. Stad Huis images are well optimized though.
Potential reduce by 150.9 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 150.9 kB or 59% of the original size.
Potential reduce by 80.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. Stadhuis.nl needs all CSS files to be minified and compressed as it can save up to 80.6 kB or 85% of the original size.
Number of requests can be reduced by 52 (43%)
121
69
The browser has sent 121 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Stad Huis. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 30 to 1 for JavaScripts and from 13 to 1 for CSS and as a result speed up the page load time.
stadhuis.nl
339 ms
1823 ms
styles.css
141 ms
jquery.js
257 ms
jquery-migrate.min.js
167 ms
style.css
176 ms
mobile.css
175 ms
stylesheet.css
167 ms
custom-form-elements.js
222 ms
jquery.fancybox-1.3.4.css
248 ms
parariusoffice.css
250 ms
jquery.form.min.js
334 ms
scripts.js
334 ms
jquery.ui.core.min.js
335 ms
jquery.ui.widget.min.js
336 ms
jquery.ui.tabs.min.js
379 ms
js
24 ms
jquery.fancybox-1.3.4.pack.js
380 ms
parariusoffice.js
381 ms
analytics.js
53 ms
logo.png
114 ms
social_img3.png
113 ms
social_img2.png
116 ms
social_img1.png
133 ms
languageli_sep.png
132 ms
banner.jpg
762 ms
menuMobile.png
163 ms
menu-bg.png
164 ms
menu-sep.png
194 ms
shadow.png
213 ms
select_bg.png
214 ms
inputbtn.png
248 ms
status437_img2.png
247 ms
status887_img2.png
276 ms
status436_img2.png
296 ms
status444_img2.png
296 ms
pararius.png
339 ms
photo_img.png
408 ms
shine.png
366 ms
adresslogo.png
381 ms
breda.jpg
382 ms
53ff36e3e2e96-dsc_0014_20.jpg
349 ms
newli_bg.png
398 ms
next.png
420 ms
waitingli_bg.png
452 ms
2741122.1458053267-166.JPG
341 ms
2741107.1453816727-165.JPG
342 ms
53ff43944f444-img_3065_2.jpg
341 ms
2713184.1450453088-352.JPG
341 ms
2740990.1425388732-497.JPG
340 ms
53ff36e3ec75f-dsc_0015_3.jpg
493 ms
2603282.1457962189-509.JPG
496 ms
2603290.1417513600-339.JPG
495 ms
2741050.1457967336-314.JPG
496 ms
2741108.1452789032-819.JPG
496 ms
2741046.1433932009-222.JPG
493 ms
53ff36e40a467-dsc_0070_4.jpg
641 ms
2741035.1430389061-865.JPG
640 ms
2603365.1424265523-539.JPG
651 ms
2741110.1453293433-460.JPG
648 ms
53ff36e3e15a6-dsc_0173_6.jpg
651 ms
53ff4ca9892e7-studio_met_raam_img_2042.jpg
651 ms
2604192.1433773636-920.JPG
834 ms
2741112.1454510309-606.JPG
834 ms
OpenSans-Semibold-webfont.woff
521 ms
OpenSans-Regular-webfont.woff
591 ms
widgets.js
80 ms
407 ms
collect
38 ms
collect
34 ms
photoli_bg1.png
428 ms
photorightli_bg.png
450 ms
photooverlay.png
476 ms
addressbox_bg.png
547 ms
adress_img2.png
575 ms
adress_img3.png
576 ms
OpenSans-Bold-webfont.woff
609 ms
likebox.php
210 ms
timeline.d11f7a3b3287fb94220e8ee6d03cc772.js
128 ms
syndication
117 ms
455668083101687809
171 ms
410ucuAGgaJ.css
197 ms
tSbl8xBI27R.css
251 ms
VyhHmC9SnBT.css
338 ms
q68gy-v_YMF.js
419 ms
FJmpeSpHpjS.js
459 ms
0wM5s1Khldu.js
380 ms
1bNoFZUdlYZ.js
383 ms
OloiM1PZafe.js
383 ms
LTv6ZK-5zxz.js
499 ms
1FCa-btixu2.js
480 ms
Oagsvfb4VWi.js
482 ms
pObvZSrFc_4.js
480 ms
HgJbVwzBr8E.js
481 ms
H3EKDTObx05.js
526 ms
OZFAYTv-ZUg.js
528 ms
776 ms
proxy.jpg
24 ms
proxy.jpg
19 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css
31 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css
60 ms
stadhuis-woning-huren_normal.png
54 ms
syndication_bundle_v1_64fcb3dd2f6da5b5f976d91a319ef73e329c1a5d.css
109 ms
syndication_bundle_v1_64fcb3dd2f6da5b5f976d91a319ef73e329c1a5d.css
134 ms
proxy.jpg
28 ms
proxy.jpg
11 ms
1385297_514600298632909_40412811_n.jpg
319 ms
1238238_514594155300190_2016519923_n.jpg
358 ms
12096182_10207455210279290_5507920935821180665_n.jpg
445 ms
1927667_816731245103048_7528079162713079059_n.jpg
506 ms
10251942_631968260216512_4663030071843275773_n.jpg
599 ms
10530897_1071343012877246_3428119666138143952_n.jpg
502 ms
11952032_758824754240302_4965879492235889024_n.jpg
497 ms
1723251_10153581893079325_1510875153999705149_n.jpg
541 ms
1509683_10205834132761777_6434244560542709363_n.jpg
538 ms
wL6VQj7Ab77.png
83 ms
s7jcwEQH7Sx.png
84 ms
gxbPuQdXIZP.png
46 ms
jot.html
29 ms
analytics.js
31 ms
bg.gif
130 ms
stars.png
253 ms
starholder.png
364 ms
button.png
365 ms
collect
14 ms
I6-MnjEovm5.js
43 ms
pQrUxxo5oQp.js
79 ms
stadhuis.nl 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.
stadhuis.nl best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
stadhuis.nl 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
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Stadhuis.nl can be misinterpreted by Google and other search engines. Our service has detected that Dutch is used on the page, and it does not match the claimed English language. Our system also found out that Stadhuis.nl 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.
stadhuis.nl
Open Graph description is not detected on the main page of Stad Huis. 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: