3.3 sec in total
169 ms
2.8 sec
339 ms
Click here to check amazing Dutch Registry content. Otherwise, check out these important facts you probably never knew about dutchregistry.nl
Visit dutchregistry.nlWe analyzed Dutchregistry.nl page load time and found that the first response time was 169 ms and then it took 3.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
dutchregistry.nl performance score
name
value
score
weighting
Value4.8 s
12/100
10%
Value8.2 s
2/100
25%
Value8.5 s
17/100
10%
Value2,780 ms
3/100
30%
Value0.076
95/100
15%
Value17.8 s
4/100
10%
169 ms
418 ms
81 ms
159 ms
235 ms
Our browser made a total of 130 requests to load all elements on the main page. We found that 75% of them (98 requests) were addressed to the original Dutchregistry.nl, 8% (11 requests) were made to Fonts.gstatic.com and 4% (5 requests) were made to Gstatic.com. The less responsive or slowest element that took the longest time to load (888 ms) belongs to the original domain Dutchregistry.nl.
Page size can be reduced by 292.6 kB (21%)
1.4 MB
1.1 MB
In fact, the total size of Dutchregistry.nl main page is 1.4 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. 80% 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. Javascripts take 824.1 kB which makes up the majority of the site volume.
Potential reduce by 100.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. 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 100.4 kB or 77% of the original size.
Potential reduce by 4.9 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. Obviously, Dutch Registry needs image optimization as it can save up to 4.9 kB or 12% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 109.3 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 109.3 kB or 13% of the original size.
Potential reduce by 78.0 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. Dutchregistry.nl needs all CSS files to be minified and compressed as it can save up to 78.0 kB or 20% of the original size.
Number of requests can be reduced by 98 (86%)
114
16
The browser has sent 114 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Dutch Registry. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 63 to 1 for JavaScripts and from 26 to 1 for CSS and as a result speed up the page load time.
dutchregistry.nl
169 ms
dutchregistry.nl
418 ms
style.min.css
81 ms
mediaelementplayer-legacy.min.css
159 ms
wp-mediaelement.min.css
235 ms
styles.css
235 ms
front.css
241 ms
_new_jquery-ui-1.12.1.css
236 ms
_new_jquery-ui-timepicker-addon.css
238 ms
dashicons.min.css
318 ms
yith-icon.css
312 ms
color-picker.min.css
311 ms
theme_css_vars.css
313 ms
js_composer.min.css
392 ms
css
39 ms
bootstrap.css
422 ms
plugins.css
467 ms
theme.css
476 ms
shortcodes.css
496 ms
theme_shop.css
515 ms
theme_wpb.css
510 ms
dynamic_style.css
511 ms
type-builder.css
546 ms
account-login.css
545 ms
style.css
548 ms
jetpack.css
548 ms
jquery.min.js
629 ms
jquery-migrate.min.js
580 ms
jquery.blockUI.min.js
621 ms
add-to-cart.min.js
622 ms
js.cookie.min.js
623 ms
woocommerce.min.js
623 ms
woocommerce-add-to-cart.js
650 ms
s-202411.js
28 ms
wp-polyfill-inert.min.js
698 ms
regenerator-runtime.min.js
701 ms
wp-polyfill.min.js
778 ms
hooks.min.js
703 ms
wpm-public.p1.min.js
709 ms
js
78 ms
api.js
50 ms
e-202411.js
26 ms
overheid-blu-public.css
708 ms
con-gtm-google-analytics.js
699 ms
underscore.min.js
625 ms
wp-util.min.js
579 ms
cart-fragments.min.js
643 ms
image-cdn.js
640 ms
index.js
775 ms
index.js
771 ms
sourcebuster.min.js
701 ms
order-attribution.min.js
701 ms
mailchimp-woocommerce-public.min.js
699 ms
live-search.min.js
694 ms
wc-gateway-ppec-order-review.js
767 ms
core.min.js
752 ms
mouse.min.js
710 ms
draggable.min.js
677 ms
slider.min.js
675 ms
jquery.ui.touch-punch.js
671 ms
iris.min.js
742 ms
i18n.min.js
741 ms
color-picker.min.js
721 ms
datepicker.min.js
720 ms
progressbar.min.js
688 ms
add-to-cart-variation.min.js
686 ms
front.min.js
809 ms
index.js
771 ms
js_composer_front.min.js
728 ms
bootstrap.js
767 ms
jquery.cookie.min.js
771 ms
owl.carousel.min.js
746 ms
imagesloaded.min.js
771 ms
jquery.magnific-popup.min.js
724 ms
theme.js
726 ms
theme-async.js
827 ms
woocommerce-theme.js
722 ms
flags.js
723 ms
overheid-blu-public.js
755 ms
OpenLayers.js
888 ms
isotope.pkgd.min.js
729 ms
gtm.js
195 ms
gtm.js
375 ms
icon-DutchRegistry_1.png
692 ms
icon-DutchRegistry_9.png
319 ms
icon-DutchRegistry_2.png
353 ms
icon-DutchRegistry_11.png
393 ms
logo_Dutch-Registry_200_1.png
665 ms
logo_Dutch-Registry_400_1.png
665 ms
logo_Dutch-Registry_250_white.png
530 ms
logo_Dutch-Registry_500_white.png
571 ms
pxiEyp8kv8JHgFVrJJfedw.ttf
213 ms
pxiByp8kv8JHgFVrLGT9Z1xlEA.ttf
213 ms
pxiByp8kv8JHgFVrLEj6Z1xlEA.ttf
247 ms
pxiByp8kv8JHgFVrLCz7Z1xlEA.ttf
267 ms
pxiByp8kv8JHgFVrLDD4Z1xlEA.ttf
268 ms
porto.woff
511 ms
fa-regular-400.ttf
536 ms
fa-solid-900.ttf
766 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf
268 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVc.ttf
269 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf
269 ms
destination
58 ms
036c6d15d6d5b6a6b1fed2087.js
170 ms
recaptcha__en.js
44 ms
anchor
48 ms
ar.svg
153 ms
zh-CN.svg
158 ms
nl.svg
159 ms
en.svg
149 ms
fr.svg
162 ms
de.svg
161 ms
el.svg
219 ms
iw.svg
220 ms
it.svg
223 ms
ja.svg
222 ms
ko.svg
232 ms
pt.svg
224 ms
ru.svg
297 ms
es.svg
299 ms
tr.svg
326 ms
styles__ltr.css
41 ms
recaptcha__en.js
46 ms
IDLZ5bdCrEGdGR5FKKZfiIWvV7rMSlbAHUEzxUIOBQg.js
94 ms
webworker.js
90 ms
logo_48.png
71 ms
recaptcha__en.js
62 ms
KFOmCnqEu92Fr1Mu4mxP.ttf
29 ms
KFOlCnqEu92Fr1MmEU9fBBc9.ttf
27 ms
KFOlCnqEu92Fr1MmYUtfBBc9.ttf
28 ms
dutchregistry.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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
dutchregistry.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
Missing source maps for large first-party JavaScript
dutchregistry.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
Tap targets are not sized appropriately
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Dutchregistry.nl can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Dutchregistry.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.
dutchregistry.nl
Open Graph description is not detected on the main page of Dutch Registry. 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: