2.9 sec in total
202 ms
2.4 sec
273 ms
Welcome to de.nl homepage info - get ready to check De best content for Netherlands right away, or after learning these important things about de.nl
Welke type koffie ook je voorkeur heeft, wij willen voor iedereen de perfecte kop maken. Ga naar DE.nl en ontdek de rijke wereld van koffie.
Visit de.nlWe analyzed De.nl page load time and found that the first response time was 202 ms and then it took 2.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
de.nl performance score
name
value
score
weighting
Value3.6 s
32/100
10%
Value11.5 s
0/100
25%
Value6.9 s
33/100
10%
Value2,000 ms
8/100
30%
Value0.953
3/100
15%
Value13.7 s
10/100
10%
202 ms
581 ms
391 ms
199 ms
200 ms
Our browser made a total of 70 requests to load all elements on the main page. We found that 57% of them (40 requests) were addressed to the original De.nl, 14% (10 requests) were made to Static.xx.fbcdn.net and 10% (7 requests) were made to Scontent-iad3-1.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (1.3 sec) belongs to the original domain De.nl.
Page size can be reduced by 371.7 kB (26%)
1.4 MB
1.1 MB
In fact, the total size of De.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. 50% of websites need less resources to load. Images take 1.0 MB which makes up the majority of the site volume.
Potential reduce by 67.1 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 67.1 kB or 78% of the original size.
Potential reduce by 101.3 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. De images are well optimized though.
Potential reduce by 49.6 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 49.6 kB or 39% of the original size.
Potential reduce by 153.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. De.nl needs all CSS files to be minified and compressed as it can save up to 153.7 kB or 83% of the original size.
Number of requests can be reduced by 24 (38%)
64
40
The browser has sent 64 CSS, Javascripts, AJAX and image requests in order to completely render the main page of De. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 15 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
de.nl
202 ms
www.de.nl
581 ms
style.min.css
391 ms
additional.css
199 ms
style.min.css
200 ms
modernizr-2.5.3.min.js
298 ms
jquery.min.js
32 ms
pinit.js
10 ms
script.min.js
411 ms
j.php
6 ms
nav-logo-gray.png
150 ms
DElogonieuwv2.png
309 ms
de-popup.png
217 ms
senseo-logo_DN.png
212 ms
senseo-popup.png
435 ms
senseosarista-logo_DN.png
259 ms
senseosarista-popup.png
268 ms
LOR_nieuw.png
314 ms
lor-popup.png
321 ms
DEprof_nieuw.png
350 ms
deprofessional-popup.png
377 ms
zakelijke-koffiemachines-DouweEgberts_resized.png
532 ms
portal-column2-blokker.png
444 ms
portal-column3-locations.png
628 ms
gtm.js
77 ms
all.js
39 ms
v.gif
5 ms
sprite.png
536 ms
header-bottom.png
472 ms
DE-nav%20logo.png
526 ms
logo-arrow.png
986 ms
m03_pads.jpg
871 ms
divider-bean_white.png
602 ms
arrow-button_white.png
660 ms
m03_nieuw.jpg
748 ms
arrow-button_gray.png
701 ms
HOMEPAGE_BANNER.jpg
927 ms
arrow-1.png
762 ms
arrow-2.png
799 ms
arrow-3.png
854 ms
spr_rebrand.png
866 ms
MarselisSlabComp.ttf
1262 ms
MarselisSlabCompBold.ttf
1018 ms
MarselisSlabCompItalic.ttf
1128 ms
van_condensed-bold.svg
1329 ms
van_condensed-regular.svg
1089 ms
pinit_main.js
69 ms
186 ms
xd_arbiter.php
60 ms
xd_arbiter.php
125 ms
ga.js
132 ms
__utm.gif
10 ms
like_box.php
124 ms
xYm_UD1pmAz.css
50 ms
TGpOWuX6Pv8.css
54 ms
_rx8naC75Dy.js
67 ms
x5F9OMjKyLw.js
88 ms
ICDbTSzjQEg.js
85 ms
TTCre3391I0.js
85 ms
1380687_10151915001951897_1813177211_n.png
48 ms
1513819_10153462591606897_4504212692257789127_n.png
13 ms
408151_106290702831572_1514160810_n.jpg
16 ms
533642_258495787606654_117880949_n.jpg
17 ms
12278959_1511709309156039_2773880424091661492_n.jpg
16 ms
11218844_985082834891338_428846101781772156_n.jpg
45 ms
12108712_812785475492409_4255474904456831371_n.jpg
16 ms
wL6VQj7Ab77.png
13 ms
s7jcwEQH7Sx.png
12 ms
I6-MnjEovm5.js
8 ms
vlXaquuXMrr.js
15 ms
de.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
Form elements do not have associated labels
Links do not have a discernible name
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
[id] attributes on active, focusable elements are not unique
Heading elements are not in a sequentially-descending order
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
de.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
de.nl SEO score
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
Document doesn't have a valid hreflang
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
NL
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise De.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 De.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.
de.nl
Open Graph description is not detected on the main page of De. 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: