5 sec in total
357 ms
4.4 sec
222 ms
Welcome to waterland.nl homepage info - get ready to check Waterland best content for Netherlands right away, or after learning these important things about waterland.nl
Homepage
Visit waterland.nlWe analyzed Waterland.nl page load time and found that the first response time was 357 ms and then it took 4.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
waterland.nl performance score
name
value
score
weighting
Value7.3 s
1/100
10%
Value10.4 s
0/100
25%
Value9.2 s
13/100
10%
Value20 ms
100/100
30%
Value0.037
100/100
15%
Value7.6 s
46/100
10%
357 ms
670 ms
253 ms
256 ms
259 ms
Our browser made a total of 56 requests to load all elements on the main page. We found that 89% of them (50 requests) were addressed to the original Waterland.nl, 4% (2 requests) were made to Ssl.google-analytics.com and 4% (2 requests) were made to S7.addthis.com. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain Waterland.nl.
Page size can be reduced by 793.7 kB (61%)
1.3 MB
507.7 kB
In fact, the total size of Waterland.nl main page is 1.3 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. Javascripts take 978.3 kB which makes up the majority of the site volume.
Potential reduce by 51.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 51.8 kB or 73% of the original size.
Potential reduce by 8.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. Waterland images are well optimized though.
Potential reduce by 674.8 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 674.8 kB or 69% of the original size.
Potential reduce by 58.7 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. Waterland.nl needs all CSS files to be minified and compressed as it can save up to 58.7 kB or 79% of the original size.
Number of requests can be reduced by 44 (81%)
54
10
The browser has sent 54 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Waterland. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 19 to 1 for JavaScripts and from 18 to 1 for CSS and as a result speed up the page load time.
waterland.nl
357 ms
www.waterland.nl
670 ms
stylesheet_53168972c0.css
253 ms
main.css
256 ms
menu.css
259 ms
form.css
273 ms
extensions.css
277 ms
news.css
280 ms
wecmap.css
504 ms
ncgov_ris.css
520 ms
results-1.4.css
526 ms
comments.css
535 ms
multicontent.css
530 ms
intro.css
550 ms
jquery-1.7.x-1.8.x-1.2.x.js
1009 ms
jquery_functions.js
768 ms
results.js
783 ms
ADxMenu.js
786 ms
rs_exp.js
801 ms
ReadSpeaker.js
828 ms
external.css
1249 ms
jquery.min.js
61 ms
powermail_frontend.js
1039 ms
PowermailCond.js
1053 ms
ReadSpeaker.Styles.css
188 ms
ReadSpeaker.Core.js
257 ms
ReadSpeaker.pub.Config.js
394 ms
logo.png
119 ms
banner_raadsvergadering.jpg
367 ms
banner_mor.jpg
376 ms
stempotlood_banner.jpg
300 ms
rotate.php
935 ms
bullet.gif
349 ms
external_link.gif
426 ms
internal_link.gif
543 ms
mail.gif
604 ms
footer-menu.png
612 ms
bullet-white.png
617 ms
search.gif
681 ms
rs_button.png
995 ms
icon_16px.gif
874 ms
arrow.gif
886 ms
ga.js
22 ms
addthis_widget.js
38 ms
__utm.gif
17 ms
ReadSpeaker.lib.Facade.adapter.jquery.js
773 ms
ReadSpeaker.Common.Settings.js
257 ms
ReadSpeaker.PlayerAPI.js
255 ms
ReadSpeaker.HL.js
278 ms
ReadSpeaker.ui.js
279 ms
alt-90.css
131 ms
alt-91.css
92 ms
alt-92.css
278 ms
print.css
274 ms
300lo.json
81 ms
sh.8e5f85691f9aaa082472a194.html
46 ms
waterland.nl 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
waterland.nl 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
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
waterland.nl 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
NL
NL
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Waterland.nl 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 Waterland.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.
waterland.nl
Open Graph description is not detected on the main page of Waterland. 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: