7.9 sec in total
267 ms
4.3 sec
3.4 sec
Visit 10e.nl now to see the best up-to-date 10 E content for Netherlands and also check out these interesting facts you probably never knew about 10e.nl
weblog van Martine de Jong — sedert 1999
Visit 10e.nlWe analyzed 10e.nl page load time and found that the first response time was 267 ms and then it took 7.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
10e.nl performance score
name
value
score
weighting
Value0.7 s
100/100
10%
Value0.7 s
100/100
25%
Value0.8 s
100/100
10%
Value0 ms
100/100
30%
Value0
100/100
15%
Value0.7 s
100/100
10%
267 ms
899 ms
189 ms
264 ms
470 ms
Our browser made a total of 137 requests to load all elements on the main page. We found that 7% of them (10 requests) were addressed to the original 10e.nl, 55% (75 requests) were made to 10enl.s3-eu-west-1.amazonaws.com and 9% (12 requests) were made to Static.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (1.6 sec) relates to the external source 10enl.s3-eu-west-1.amazonaws.com.
Page size can be reduced by 376.1 kB (8%)
4.9 MB
4.5 MB
In fact, the total size of 10e.nl main page is 4.9 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. 85% 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 4.4 MB which makes up the majority of the site volume.
Potential reduce by 60.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 60.4 kB or 85% of the original size.
Potential reduce by 76.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. 10 E images are well optimized though.
Potential reduce by 217.7 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 217.7 kB or 55% of the original size.
Potential reduce by 21.6 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. 10e.nl needs all CSS files to be minified and compressed as it can save up to 21.6 kB or 79% of the original size.
Number of requests can be reduced by 32 (24%)
133
101
The browser has sent 133 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 10 E. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 30 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
10e.nl
267 ms
www.10e.nl
899 ms
wp-emoji-release.min.js
189 ms
app.css
264 ms
jquery.js
470 ms
jquery-migrate.min.js
219 ms
app.js
424 ms
widgets.js
42 ms
adsbygoogle.js
23 ms
plusone.js
115 ms
wp-embed.min.js
188 ms
analytics.js
18 ms
collect
67 ms
collect
75 ms
cropped-header-10logo4.jpg
383 ms
banner1b.jpg
578 ms
banner2b.jpg
534 ms
header-20160313-590x451.jpg
582 ms
20160313A-590x443.jpg
612 ms
20160313B-590x443.jpg
575 ms
20160313C-442x590.jpg
534 ms
20160313D-590x443.jpg
706 ms
20160313E-590x443.jpg
706 ms
20160313F-590x443.jpg
746 ms
20160313G-590x443.jpg
860 ms
20160313H.jpg
795 ms
20160313I-442x590.jpg
793 ms
20160313J-590x443.jpg
991 ms
20160313K-442x590.jpg
905 ms
header-20160312-590x451.jpg
996 ms
20160312A-590x261.jpg
976 ms
20160312B-590x443.jpg
989 ms
20160312C.jpg
1112 ms
20160312D-590x443.jpg
1192 ms
20160312E-590x443.jpg
1188 ms
20160312F-442x590.jpg
1196 ms
20160312G-590x443.jpg
1402 ms
20160312H-590x443.jpg
1211 ms
20160312I-590x443.jpg
1258 ms
20160312J-590x443.jpg
1368 ms
20160312K-590x443.jpg
1443 ms
20160312L-590x443.jpg
1414 ms
20160312M-590x443.jpg
1427 ms
20160312N.jpg
1443 ms
20160312O-590x443.jpg
1546 ms
20160312P-590x443.jpg
1599 ms
20160312Q-590x443.jpg
1515 ms
20160312R-590x443.jpg
1540 ms
20160312S-590x443.jpg
1639 ms
20160312T.jpg
1646 ms
like.php
340 ms
mrseavita-webfont.woff
369 ms
socialmedia.png
341 ms
like.php
332 ms
ca-pub-3929888862859532.js
427 ms
zrt_lookup.html
342 ms
show_ads_impl.js
367 ms
cb=gapi.loaded_0
289 ms
cb=gapi.loaded_1
393 ms
fastbutton
438 ms
fastbutton
439 ms
fastbutton
432 ms
index.php
314 ms
button.0308b81ff1714e446f674b5b9793f2cd.js
202 ms
likebox.php
194 ms
like.php
150 ms
qeKvIRsJabD.js
608 ms
header-20160311-590x451.jpg
1345 ms
LVx-xkvaJ0b.png
576 ms
ads
255 ms
osd.js
56 ms
20160311A-590x443.jpg
1238 ms
postmessageRelay
138 ms
20160311B-590x442.jpg
1217 ms
rs=AGLTcCOyEe7xIoYbKqvJH6xA3ail6lX-YA
45 ms
kyEKgjk51ZE.css
399 ms
xgj7bXhJNEH.css
391 ms
q68gy-v_YMF.js
492 ms
FJmpeSpHpjS.js
514 ms
0wM5s1Khldu.js
433 ms
1bNoFZUdlYZ.js
429 ms
20160311BA-590x207.jpg
1134 ms
20160311C-590x334.jpg
1193 ms
20160311D-590x383.jpg
1210 ms
tweet_button.b9740740e0bcf9b0657c5b11bd4388da.nl.html
74 ms
cb=gapi.loaded_0
76 ms
cb=gapi.loaded_1
75 ms
20160311E-590x237.jpg
1264 ms
W5F8_SL0XFawnjxHGsZjJA.ttf
110 ms
3193398744-postmessagerelay.js
106 ms
rpc:shindig_random.js
73 ms
ajax-loader.gif
150 ms
20160311F-590x443.jpg
1154 ms
20160311G-590x518.jpg
1174 ms
20160311H-590x384.jpg
1142 ms
m_js_controller.js
28 ms
abg.js
42 ms
cb=gapi.loaded_0
45 ms
20160311I-590x443.jpg
1189 ms
20160311J-590x443.jpg
1125 ms
googlelogo_color_112x36dp.png
76 ms
imgad
39 ms
nessie_icon_tiamat_white.png
40 ms
s
38 ms
x_button_blue2.png
28 ms
20160311K-590x443.jpg
1217 ms
Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js
12 ms
20160311L-590x443.jpg
1153 ms
20160311M-590x443.jpg
1097 ms
20160311N-590x332.jpg
1021 ms
20160311O-590x443.jpg
1127 ms
20160311P-590x443.jpg
1080 ms
jot.html
2 ms
29318_127064353974532_6627912_n.jpg
289 ms
wL6VQj7Ab77.png
77 ms
s7jcwEQH7Sx.png
76 ms
20160311Q-590x443.jpg
1028 ms
20160311R-590x443.jpg
977 ms
20160311S-590x442.jpg
1090 ms
20160311T-590x404.jpg
981 ms
20160311U-590x443.jpg
970 ms
20160311V-590x443.jpg
1053 ms
20160311W-590x443.jpg
1006 ms
I6-MnjEovm5.js
71 ms
pQrUxxo5oQp.js
136 ms
20160311X-590x443.jpg
1054 ms
20160311Y-590x443.jpg
972 ms
header-20160313-100x75.jpg
889 ms
header-20160312-100x75.jpg
946 ms
header-20160311-100x75.jpg
1008 ms
header-20160310-100x75.jpg
903 ms
header-widm-finale-100x75.jpg
937 ms
header-centerparcs1-100x75.jpg
938 ms
header-widm-09-100x75.jpg
902 ms
header-widm-08-100x75.jpg
890 ms
header-widm-07-100x75.jpg
882 ms
still21-100x75.jpg
863 ms
10e.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.
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
10e.nl best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Browser errors were logged to the console
10e.nl SEO score
NL
NL
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise 10e.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 10e.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.
10e.nl
Open Graph data is detected on the main page of 10 E. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: