4.6 sec in total
361 ms
3.9 sec
364 ms
Click here to check amazing Cordaid content for Netherlands. Otherwise, check out these important facts you probably never knew about cordaid.org
We stand with those hit hardest by poverty and conflict. We support them to move beyond survival and to fully participate in equitable societies.
Visit cordaid.orgWe analyzed Cordaid.org page load time and found that the first response time was 361 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 65% of websites can load faster.
cordaid.org performance score
name
value
score
weighting
Value3.8 s
27/100
10%
Value15.2 s
0/100
25%
Value8.9 s
15/100
10%
Value1,040 ms
26/100
30%
Value0.024
100/100
15%
Value14.5 s
9/100
10%
361 ms
266 ms
337 ms
334 ms
256 ms
Our browser made a total of 106 requests to load all elements on the main page. We found that 64% of them (68 requests) were addressed to the original Cordaid.org, 5% (5 requests) were made to A.tiles.mapbox.com and 4% (4 requests) were made to S3.amazonaws.com. The less responsive or slowest element that took the longest time to load (1.4 sec) belongs to the original domain Cordaid.org.
Page size can be reduced by 2.6 MB (66%)
3.9 MB
1.3 MB
In fact, the total size of Cordaid.org main page is 3.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. 60% of websites need less resources to load. Javascripts take 1.9 MB which makes up the majority of the site volume.
Potential reduce by 898.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 898.4 kB or 88% of the original size.
Potential reduce by 17.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. Cordaid images are well optimized though.
Potential reduce by 1.3 MB
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 1.3 MB or 69% of the original size.
Potential reduce by 352.9 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. Cordaid.org needs all CSS files to be minified and compressed as it can save up to 352.9 kB or 91% of the original size.
Number of requests can be reduced by 59 (63%)
94
35
The browser has sent 94 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Cordaid. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 33 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
cordaid.org
361 ms
www.cordaid.org
266 ms
337 ms
screen.css
334 ms
events.css
256 ms
jquery-ui-1.10.0.custom.css
260 ms
cookielaw.css
261 ms
screen.css
258 ms
mapbox.css
28 ms
pqselect.min.css
257 ms
jquery-1.8.1.min.js
521 ms
jquery-ui-1.10.4.custom.min.js
614 ms
pqselect.min.js
378 ms
d3.v3.min.js
552 ms
d3pie.js
463 ms
jquery.form.js
264 ms
jquery.loadmask.min.js
307 ms
jquery-fancybox.min.js
364 ms
carousel.js
533 ms
jquery.placeholder.js
397 ms
ce.js
456 ms
script.js
513 ms
projects.js
532 ms
cookielaw.js
531 ms
jquery-jvectormap-1.1.1.min.js
533 ms
jquery-jvectormap-world-mill-en.js
645 ms
addthis_widget.js
36 ms
jquery.cookie-1.4.1.min.js
560 ms
takeover.js
604 ms
mapbox.js
23 ms
conversion.js
38 ms
j.php
63 ms
logo-cordaid-big.png
406 ms
54f7d667ebb834fae1fc534d9e1ce4c5.jpg
1123 ms
7e6943639bcb83ffc4bbf87106e1a1c2.jpg
876 ms
b23fa0224d18f2eb77495a0980627a39.jpg
1124 ms
21799cffa7095a8db32d8d3d682e08a9.jpg
1122 ms
fa852cacbb4e47e4e600be683bcb5b0f.jpg
1124 ms
f73713ab305bc62ad863d33649c8ed2b.jpg
875 ms
8db2acfcd1969c774e7a7acec3b3e26e.jpg
1122 ms
7228e4090b2949bb4d5e2d0bc736f71e.jpg
1120 ms
fb92981abda7c2c9ee61e776280baca0.jpg
1273 ms
3223ee04ccb063eafa2c6d025f0efe8b.jpg
1273 ms
3e16734e9cef4f398ad792f0d2f7f625.jpg
1272 ms
5de62ff6cd026f886ef957196197a311.jpg
1272 ms
01aad720e1eb110c3f605db3b5cec13e.jpg
1272 ms
c54b920cea05754d33b6ecb7f12c478e.jpg
1271 ms
54e1356524a9d7eb67e0e0b9037fd0c1.jpg
1365 ms
87be1f9c3d393f3b3aa6f3c913e82424.jpg
1445 ms
gtm.js
115 ms
d403df66d8d83b181a3191bb8672fdea.jpg
1348 ms
main-nav-bg.png
1312 ms
WF-019156-002044-000003-1378720433.woff
98 ms
WF-019156-002044-000054-1378720434.woff
138 ms
WF-019156-002044-000011-1378720433.woff
126 ms
WF-019156-002044-000055-1378720434.woff
182 ms
v.gif
49 ms
ClanWeb-News.woff
1298 ms
ClanWeb-Black.woff
1343 ms
small-arrow-grey-down.png
1373 ms
analytics.js
60 ms
iframe_api
66 ms
icon-search.png
1306 ms
cross.png
1296 ms
nav-arrow.png
1286 ms
small-arrow-white-right.png
1350 ms
linkid.js
5 ms
www-widgetapi.js
66 ms
collect
15 ms
collect
97 ms
icon-linkedin-large.png
1265 ms
icon-facebook-large.png
1265 ms
icon-twitter-large.png
1218 ms
icon-rss-large.png
1218 ms
icon-newsletter-large.png
1217 ms
icon-rss-feed.png
1285 ms
icon-newsletter.png
1284 ms
2184.js
38 ms
icon-calendar.png
1256 ms
shadow-bigquote.png
1219 ms
footer-s3b520e2b01.png
1399 ms
hotjar-27626.js
759 ms
584 ms
fbds.js
878 ms
barseghyanartur.lngl56m4.json
1063 ms
icons-000000@2x.png
545 ms
layers.3643cb2e25fb91c29386.js
293 ms
300lo.json
470 ms
marker-icon-small.png
582 ms
ui-bg_flat_100_f1efeb_40x100.png
580 ms
small-arrow-black-down.png
601 ms
pagination-bullet.png
605 ms
pagination-bullet-active.png
663 ms
232 ms
sh.7c7179124ea24ac6ba46caac.html
210 ms
modules-1f5c71aea63f8df71401422ed80fbe5f.js
71 ms
121 ms
1.png
475 ms
features.json
548 ms
2.png
602 ms
1.png
537 ms
1.png
424 ms
2.png
469 ms
2.png
470 ms
visit-data
207 ms
24 ms
cordaid.org 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
[id] attributes on active, focusable elements are not unique
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
cordaid.org 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
cordaid.org 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
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Cordaid.org 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 Cordaid.org 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.
cordaid.org
Open Graph data is detected on the main page of Cordaid. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: