6.3 sec in total
1.3 sec
4.8 sec
247 ms
Visit voedselanders.nl now to see the best up-to-date Voedsel Anders content for Netherlands and also check out these interesting facts you probably never knew about voedselanders.nl
naar een ander systeem van landbouw en voedsel
Visit voedselanders.nlWe analyzed Voedselanders.nl page load time and found that the first response time was 1.3 sec and then it took 5 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
voedselanders.nl performance score
name
value
score
weighting
Value6.7 s
2/100
10%
Value9.8 s
0/100
25%
Value10.5 s
7/100
10%
Value350 ms
73/100
30%
Value0.011
100/100
15%
Value14.7 s
8/100
10%
1298 ms
105 ms
23 ms
306 ms
205 ms
Our browser made a total of 115 requests to load all elements on the main page. We found that 28% of them (32 requests) were addressed to the original Voedselanders.nl, 10% (11 requests) were made to Pixel.wp.com and 9% (10 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1.3 sec) belongs to the original domain Voedselanders.nl.
Page size can be reduced by 703.7 kB (58%)
1.2 MB
511.5 kB
In fact, the total size of Voedselanders.nl main page is 1.2 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. 70% of websites need less resources to load. Javascripts take 551.9 kB which makes up the majority of the site volume.
Potential reduce by 50.2 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 50.2 kB or 79% of the original size.
Potential reduce by 17.2 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. Voedsel Anders images are well optimized though.
Potential reduce by 379.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 379.7 kB or 69% of the original size.
Potential reduce by 256.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. Voedselanders.nl needs all CSS files to be minified and compressed as it can save up to 256.7 kB or 74% of the original size.
Number of requests can be reduced by 75 (74%)
102
27
The browser has sent 102 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Voedsel Anders. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 42 to 1 for JavaScripts and from 21 to 1 for CSS and as a result speed up the page load time.
www.voedselanders.nl
1298 ms
wp-emoji-release.min.js
105 ms
css
23 ms
dashicons.min.css
306 ms
style.min.css
205 ms
styles.css
202 ms
displaystyle.css
212 ms
tribe-events-full.min.css
212 ms
mediaelementplayer.min.css
217 ms
wp-mediaelement.css
303 ms
genericons.css
405 ms
jetpack.css
308 ms
jquery.js
413 ms
jquery-migrate.min.js
317 ms
spin.js
435 ms
jquery.spin.js
437 ms
tiled-gallery.js
438 ms
in.js
5 ms
yikes-inc-easy-mailchimp-extender-public.min.css
436 ms
jquery.form.min.js
510 ms
scripts.js
529 ms
devicepx-jetpack.js
4 ms
jetpack-carousel.js
629 ms
mediaelement-and-player.min.js
642 ms
wp-mediaelement.js
570 ms
gprofiles.js
53 ms
wpgroho.js
568 ms
fitvids.min.js
608 ms
theme.min.js
614 ms
wp-embed.min.js
654 ms
yikes-mc-ajax-forms.min.js
656 ms
sharing.js
709 ms
e-201611.js
4 ms
library.js
228 ms
1596995_250290415144454_930614606_o1.jpg
583 ms
stamp-150x150.jpg
436 ms
sdk.js
394 ms
cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf
28 ms
DXI1ORHCpsQm3Vp6mXoaTYnF5uFdDttMLvmWuJdhhgs.ttf
47 ms
MTP_ySUJH_bn48VBG8sNSonF5uFdDttMLvmWuJdhhgs.ttf
61 ms
k3k702ZOKiLJc3WVjuplzInF5uFdDttMLvmWuJdhhgs.ttf
61 ms
EInbV5DfGHOiMmvb1Xr-honF5uFdDttMLvmWuJdhhgs.ttf
61 ms
6nvU963vW96zvuZHXyGvkNfLa8try2vLa8try2vLa8try2vLaPbzi90vRj6IfRT+KfhS9KHpR9KLoRdGLohdFL4peFL0oelH0ouhF0YuiF0Uvil4UvSh6UfSi6EXRi6IXRS+KXhS9KHpR9KHoQ9GHog9FH4o+FD0oelD0oOToN3TgiAFDRg4b9C8VmLmgAAAAAVWwJZkAAA==
4 ms
Genericons.svg
596 ms
8AAnjaY2BgYGQAgosrjpwF0ZcUq9bCaABTzgdAAAA=
3 ms
secureAnonymousFramework
85 ms
widgets.js
27 ms
xjAJXh38I15wypJXxuGMBp0EAVxt0G0biEntp43Qt6E.ttf
29 ms
PRmiXeptR36kaC0GEAetxrfB31yxOzP-czbf6AAKCVo.ttf
28 ms
PRmiXeptR36kaC0GEAetxi8cqLH4MEiSE0ROcU-qHOA.ttf
28 ms
PRmiXeptR36kaC0GEAetxp_TkvowlIOtbR7ePgFOpF4.ttf
28 ms
PRmiXeptR36kaC0GEAetxlDMrAYtoOisqqMDW9M_Mqc.ttf
29 ms
hovercard.css
55 ms
services.css
80 ms
share
96 ms
g.gif
28 ms
graph.facebook.com
89 ms
share
96 ms
graph.facebook.com
141 ms
share
93 ms
graph.facebook.com
141 ms
share
86 ms
graph.facebook.com
138 ms
share
91 ms
graph.facebook.com
140 ms
timeline.d11f7a3b3287fb94220e8ee6d03cc772.js
85 ms
g.gif
32 ms
g.gif
32 ms
g.gif
33 ms
g.gif
33 ms
g.gif
32 ms
g.gif
32 ms
g.gif
39 ms
g.gif
62 ms
g.gif
62 ms
xdrpc.html
52 ms
g.gif
60 ms
91 ms
xd_arbiter.php
265 ms
xd_arbiter.php
469 ms
followcompany
73 ms
syndication
123 ms
576371674074992640
143 ms
css
33 ms
anonymoususerspace
20 ms
js
41 ms
css
69 ms
js
84 ms
tribe-events-full-mobile.min.css
103 ms
sprite_connect_v15.png
15 ms
proxy.jpg
27 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css
2 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css
4 ms
ZNDPu3ZD_normal.jpeg
86 ms
NatuurSUPER_logo_bij_twitter_normal.jpg
125 ms
syndication_bundle_v1_64fcb3dd2f6da5b5f976d91a319ef73e329c1a5d.css
75 ms
syndication_bundle_v1_64fcb3dd2f6da5b5f976d91a319ef73e329c1a5d.css
88 ms
proxy.jpg
3 ms
page.php
108 ms
LUdypCgtRlc.css
288 ms
q68gy-v_YMF.js
488 ms
YvxwM8R7ol8.js
626 ms
ihptErjAmMX.js
560 ms
jot.html
2 ms
1920354_250290415144454_930614606_n.jpg
543 ms
1526437_250289835144512_546154025_n.jpg
612 ms
1653943_665583476886170_7279249306114717578_n.jpg
739 ms
11054852_10206761824537907_371562610223166608_n.jpg
744 ms
10609496_366270923527953_7381976221990508748_n.jpg
792 ms
wL6VQj7Ab77.png
76 ms
s7jcwEQH7Sx.png
77 ms
R9a_DtVRZgv.js
70 ms
cUDgRFxaoIk.js
71 ms
0JBr1QHp8Gi.js
71 ms
kDOzhTr2W91.js
136 ms
voedselanders.nl accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
[role] values are not valid
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
Links do not have a discernible name
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
voedselanders.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
voedselanders.nl SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
NL
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Voedselanders.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 Voedselanders.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.
voedselanders.nl
Open Graph data is detected on the main page of Voedsel Anders. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: