6.3 sec in total
299 ms
3.1 sec
2.9 sec
Visit da.nl now to see the best up-to-date DA content for Netherlands and also check out these interesting facts you probably never knew about da.nl
Compleet aanbod in persoonlijke verzorging ✓ Deskundig gezondheidsadvies ✓ Voor 21:00 besteld, morgen in huis ✓ Afhalen in 300+ DA winkels
Visit da.nlWe analyzed Da.nl page load time and found that the first response time was 299 ms and then it took 6 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
da.nl performance score
name
value
score
weighting
Value3.9 s
25/100
10%
Value6.1 s
12/100
25%
Value9.3 s
13/100
10%
Value6,370 ms
0/100
30%
Value0.025
100/100
15%
Value22.5 s
1/100
10%
299 ms
379 ms
883 ms
125 ms
443 ms
Our browser made a total of 97 requests to load all elements on the main page. We found that 41% of them (40 requests) were addressed to the original Da.nl, 29% (28 requests) were made to Media.graphassets.com and 25% (24 requests) were made to Msxlive.da.nl. The less responsive or slowest element that took the longest time to load (1.6 sec) relates to the external source Msxlive.da.nl.
Page size can be reduced by 949.0 kB (23%)
4.1 MB
3.2 MB
In fact, the total size of Da.nl main page is 4.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. Only a small number of websites need less resources to load. Images take 3.2 MB which makes up the majority of the site volume.
Potential reduce by 847.0 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 847.0 kB or 91% of the original size.
Potential reduce by 92.8 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. DA images are well optimized though.
Potential reduce by 9.2 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 9.2 kB or 24% of the original size.
Number of requests can be reduced by 38 (40%)
94
56
The browser has sent 94 CSS, Javascripts, AJAX and image requests in order to completely render the main page of DA. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 39 to 1 for JavaScripts and as a result speed up the page load time.
da.nl
299 ms
da.nl
379 ms
www.da.nl
883 ms
gtm.js
125 ms
6e5ea8daa2d3d228.css
443 ms
polyfills-78c92fac7aa8fdd8.js
479 ms
webpack-a36a962bcf3e24ad.js
443 ms
framework-d583295f3144c491.js
549 ms
main-ae9129f06f88734a.js
478 ms
_app-a68b6fcb01b8f7d0.js
498 ms
71bdff8e-17f79d6104f10989.js
515 ms
3777-6cb2052bd8cb2fc9.js
502 ms
776-b5ba1fddadb1d0aa.js
558 ms
841-d2cb9ae91c10a48c.js
556 ms
3679-851cee761b5dd41d.js
590 ms
2334-8ce0090c806129c0.js
594 ms
5144-aef3416683521258.js
611 ms
6239-02dcdd52a6dcb756.js
640 ms
3650-350e4630f51528ad.js
649 ms
6549-7630979a8918103f.js
649 ms
7192-79dd152cf8f3df34.js
683 ms
2942-b258b978afb728be.js
686 ms
6429-5281c5070e97b43c.js
702 ms
4914-3abf9da1b48e87c9.js
734 ms
3784-80285bf0044f9639.js
741 ms
6977-83bf25d89f99bca9.js
748 ms
9946-9e0c9b3841db6511.js
775 ms
1423-f0391d4ff558cfaa.js
778 ms
8800-0b8357b2834bfa59.js
796 ms
4892-3aebf52c4953d8aa.js
828 ms
533-d61a5ef06bdd904b.js
833 ms
3122-52322442589fc402.js
840 ms
4584-9e7377233c6911b2.js
867 ms
8511-a4b9b62c43a48a55.js
870 ms
5552-4a8610417ce03dcc.js
889 ms
1709-503ef4ac4d2db80c.js
921 ms
index-3400c3e2aa110758.js
924 ms
_buildManifest.js
931 ms
_ssgManifest.js
959 ms
PTYkYKCcR2OXN2RPzkuD
58 ms
2ghJkHtRAW2EvQEgyDZy
102 ms
rdIlybfdSJi0WLQHWwS5
102 ms
1fxnJUmRPicU5OPUIFCw
106 ms
8728400341043_A1N1_1.jpg
957 ms
8728400341081_1.jpg
938 ms
8728400341128_1.jpg
762 ms
8728400341104_A1N1_1.jpg
769 ms
8728400104587_A1N1.png
860 ms
8728400105386_A1N1.png
1048 ms
885993.jpg
853 ms
956542.jpg
863 ms
8717473117006_A1N1.png
1035 ms
8728400773516_A1N1.jpg
1312 ms
3661434006555_A1N1.png
1044 ms
282478.jpg
1018 ms
970021.jpg
1026 ms
970013.jpg
1109 ms
3349668508587_A1N1.png
1478 ms
564730.jpg
1124 ms
8713713041001_A1N1.png
1136 ms
8710537762679_A1N1.png
1227 ms
8712861980026_A1N1.png
1648 ms
8713713029504_A1N1.png
1215 ms
8713713090658_A1N1.jpg
1319 ms
8713713091075_A1N1.jpg
1395 ms
8713713090870_A1N1.jpg
1502 ms
8713713089676_A1N1.png
1581 ms
jneCED5fQOqpXnQoDfoo
65 ms
ySjE2CsmQYu2hyWAzwtL
139 ms
yLZalXVSiKzkTWWSiA0h
137 ms
3hgvF6DhTni4RIVd3xDD
140 ms
z6aTEk8ET1iAIGSC3WpL
165 ms
SvjMxY3HQ6Si8NsnLe4F
144 ms
yhNSYzHRfyVAwbd0foJr
146 ms
zLwFD7djSQdDZjwQIYcK
166 ms
2KifREmQaiRwxnuI8Yev
168 ms
g1EWmlY4SCW8WgDMuGeu
169 ms
XTKNcJ9Ryxqvi2gmiHvQ
170 ms
36Uu8CJXSa6I0zfLA9bw
168 ms
SkleGkvBS7GNeQRcj5Of
177 ms
CadJT43FRBOL9dnqEh1K
171 ms
yabUPiRQTOJNCgn3cSOg
173 ms
YSDjIOQmSjPplYVSR7wT
174 ms
ng7YaKvzQvC0oy7Dmv8M
177 ms
5uwAX2RDRmuHtcipBM1M
169 ms
5VTyUTyKQyCaeHSXbGF7
172 ms
TRTXQtFITa6A07964A0w
174 ms
Ou9nwyxlTAiaX1UYcKy3
174 ms
xrTPMWR6TgG8R1eUrdrn
173 ms
fSO4OnnHSVvuuKueOYZ8
176 ms
fpvts1D6R62ODfMRSCyu
176 ms
uc.js
275 ms
js
68 ms
logo.7e0eaa1b.svg
698 ms
sqzl.js
286 ms
gezondheidscheck.aad6cf59.svg
536 ms
394f97d55f1f2cf8c900.js
18 ms
da.nl accessibility score
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
Buttons do not have an accessible name
Image elements do not have [alt] attributes
Links do not have a discernible name
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
da.nl best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
da.nl SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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 Da.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 Da.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.
da.nl
Open Graph description is not detected on the main page of DA. 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: