4.6 sec in total
350 ms
3.8 sec
519 ms
Visit dunck.nl now to see the best up-to-date Dunck content and also check out these interesting facts you probably never knew about dunck.nl
Sinds 2001 dé toonaangevende aanbieder van loyalty marketing oplossingen in Nederland. Dunck loyalty marketing bureau gevestigd in Utrecht.
Visit dunck.nlWe analyzed Dunck.nl page load time and found that the first response time was 350 ms and then it took 4.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
dunck.nl performance score
name
value
score
weighting
Value3.5 s
34/100
10%
Value5.2 s
23/100
25%
Value7.2 s
30/100
10%
Value4,440 ms
0/100
30%
Value0
100/100
15%
Value20.6 s
2/100
10%
350 ms
498 ms
94 ms
182 ms
342 ms
Our browser made a total of 133 requests to load all elements on the main page. We found that 84% of them (112 requests) were addressed to the original Dunck.nl, 3% (4 requests) were made to Surveygizmo.com and 2% (3 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (794 ms) belongs to the original domain Dunck.nl.
Page size can be reduced by 756.5 kB (24%)
3.1 MB
2.4 MB
In fact, the total size of Dunck.nl main page is 3.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. 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. Images take 2.0 MB which makes up the majority of the site volume.
Potential reduce by 268.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. 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 268.5 kB or 88% of the original size.
Potential reduce by 377.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. Obviously, Dunck needs image optimization as it can save up to 377.5 kB or 18% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 95.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 95.1 kB or 14% of the original size.
Potential reduce by 15.4 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. Dunck.nl needs all CSS files to be minified and compressed as it can save up to 15.4 kB or 13% of the original size.
Number of requests can be reduced by 92 (78%)
118
26
The browser has sent 118 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Dunck. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 50 to 1 for JavaScripts and from 44 to 1 for CSS and as a result speed up the page load time.
dunck.nl
350 ms
dunck.nl
498 ms
theme.min.css
94 ms
style.css
182 ms
bdt-uikit.css
342 ms
ep-helper.css
257 ms
frontend.css
259 ms
cleantalk-public.min.css
261 ms
eae.min.css
351 ms
style.min.css
266 ms
header-footer.min.css
347 ms
public.css
348 ms
jet-elements.css
439 ms
jet-elements-skin.css
359 ms
elementor-icons.min.css
428 ms
frontend-lite.min.css
447 ms
swiper.min.css
436 ms
post-9.css
437 ms
frontend-lite.min.css
450 ms
all.min.css
520 ms
v4-shims.min.css
523 ms
post-5.css
524 ms
post-46.css
531 ms
post-198.css
546 ms
post-4671.css
536 ms
post-29202.css
606 ms
ytprefs.min.css
607 ms
css
34 ms
linearicons25px.css
611 ms
fontawesome.min.css
619 ms
solid.min.css
621 ms
brands.min.css
633 ms
jquery.min.js
794 ms
jquery-migrate.min.js
694 ms
apbct-public-bundle.min.js
699 ms
iconHelper.js
703 ms
ytprefs.min.js
706 ms
widget-icon-list.min.css
718 ms
v2.js
663 ms
api.js
43 ms
widget-nav-menu.min.css
788 ms
widget-carousel.min.css
708 ms
post-29415.css
721 ms
post-29417.css
644 ms
post-29419.css
640 ms
post-29421.css
764 ms
peel.min.css
759 ms
elementor.css
682 ms
leadin.css
681 ms
27056299.js
677 ms
eae.min.js
669 ms
index.min.js
710 ms
wp-polyfill-inert.min.js
641 ms
regenerator-runtime.min.js
634 ms
wp-polyfill.min.js
757 ms
hooks.min.js
761 ms
vue.min.js
759 ms
jet-menu-public-scripts.js
760 ms
v4-shims.min.js
687 ms
fitvids.min.js
687 ms
bdt-uikit.min.js
686 ms
webpack.runtime.min.js
679 ms
frontend-modules.min.js
673 ms
waypoints.min.js
665 ms
core.min.js
606 ms
frontend.min.js
611 ms
ep-wrapper-link.min.js
607 ms
jquery.smartmenus.min.js
598 ms
imagesloaded.min.js
597 ms
gtm.js
88 ms
html2canvas.min.js
684 ms
font
17 ms
oridomi.js
574 ms
peeljs.js
602 ms
mouse.min.js
599 ms
draggable.min.js
592 ms
jquery.ui.touch-punch.js
588 ms
uc.js
128 ms
js
117 ms
landing
276 ms
destination
231 ms
helper.min.js
545 ms
webpack-pro.runtime.min.js
545 ms
i18n.min.js
492 ms
frontend.min.js
623 ms
elements-handlers.min.js
623 ms
jet-elements.min.js
623 ms
widgets-scripts.js
500 ms
lazyload.min.js
500 ms
GothamRnd-Book_0.ttf
455 ms
GothamRnd-Medium_0.ttf
454 ms
GothamRnd-Light_0.ttf
455 ms
GothamRnd-Bold_0.ttf
512 ms
fa-solid-900.woff
627 ms
fa-regular-400.woff
516 ms
linearicons25px.woff
685 ms
recaptcha__en.js
27 ms
GothamRnd-LightIta_0.ttf
379 ms
GothamRnd-BookIta_0.ttf
433 ms
GothamRnd-MedIta_0.ttf
488 ms
GothamRnd-BoldIta_0.ttf
490 ms
fa-brands-400.woff
546 ms
collectedforms.js
522 ms
banner.js
562 ms
27056299.js
559 ms
Logpo_Dunck_Loyalty_v02-1.svg
117 ms
Ontwerp_zonder_titel-removebg-preview-e1692276232494.png
236 ms
Afmeting-500-x-501-1.png
172 ms
Afmeting-500-x-501.png
332 ms
Hartstichting-1.jpg
234 ms
FNV-LOGO-FLASH-CMY-1536x1498.png
418 ms
cewe_owler_20190501_135430_original.png
253 ms
veh-1536x864.jpg
255 ms
Logo-Vanreusel.jpg
321 ms
amnesty-logo-01-1.png
323 ms
7COriGkI_400x400.jpg
342 ms
download.png
344 ms
Schermafbeelding-2023-01-10-112313.png
409 ms
Afbeelding7.png
411 ms
Raaak.png
420 ms
mediahuis-nederland.png
428 ms
FNV.png
437 ms
Loyalty-Facts-logowit.png
495 ms
LF-LOGO-KLEIN.png
496 ms
Privacy-Waarborg-Logo-Donkergrijs-Sterren-1-300x164.png
508 ms
Loyalty-Scan-Dunck-2-0
520 ms
jscal.css
35 ms
survey2.css
38 ms
sg-icon-font.css
36 ms
surveycrap.js
117 ms
GothamLight.css
602 ms
Leon1.png
215 ms
ApbpX4Cf0b9Vmn6uDqgB+lRl1Ev0mTqnxulzlVVZ+kJNqAky+ct6eqBm1Az9Sc2qWfrzfwHV1t8nAAAAAQAAAADVpCcIAAAAAMGsf1gAAAAA4PkMDw==
2 ms
dunck.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
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
Links do not have a discernible name
dunck.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
dunck.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 Dunck.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 Dunck.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.
dunck.nl
Open Graph data is detected on the main page of Dunck. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: