1.9 sec in total
148 ms
1.4 sec
408 ms
Welcome to cgiar.org homepage info - get ready to check CGIAR best content for Ethiopia right away, or after learning these important things about cgiar.org
Towards a world free of poverty, hunger and environmental degradation, CGIAR is the worlds largest global agricultural innovation network.
Visit cgiar.orgWe analyzed Cgiar.org page load time and found that the first response time was 148 ms and then it took 1.8 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.
cgiar.org performance score
name
value
score
weighting
Value5.8 s
4/100
10%
Value12.1 s
0/100
25%
Value13.6 s
2/100
10%
Value8,090 ms
0/100
30%
Value0.003
100/100
15%
Value16.0 s
6/100
10%
148 ms
282 ms
56 ms
48 ms
99 ms
Our browser made a total of 82 requests to load all elements on the main page. We found that 7% of them (6 requests) were addressed to the original Cgiar.org, 74% (61 requests) were made to Cgiarweb.s3.amazonaws.com and 5% (4 requests) were made to Fast.fonts.net. The less responsive or slowest element that took the longest time to load (596 ms) relates to the external source Cgiarweb.s3.amazonaws.com.
Page size can be reduced by 1.1 MB (44%)
2.6 MB
1.5 MB
In fact, the total size of Cgiar.org main page is 2.6 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. Images take 1.1 MB which makes up the majority of the site volume.
Potential reduce by 112.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 112.0 kB or 65% of the original size.
Potential reduce by 51.6 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. CGIAR images are well optimized though.
Potential reduce by 486.1 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 486.1 kB or 66% of the original size.
Potential reduce by 493.2 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. Cgiar.org needs all CSS files to be minified and compressed as it can save up to 493.2 kB or 83% of the original size.
Number of requests can be reduced by 45 (63%)
71
26
The browser has sent 71 CSS, Javascripts, AJAX and image requests in order to completely render the main page of CGIAR. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 27 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
cgiar.org
148 ms
www.cgiar.org
282 ms
380454df-eb4a-4370-83d2-b04ddea54e17.css
56 ms
fullcalendar.css
48 ms
style.css
99 ms
jquery.fancybox.css
33 ms
output.css
48 ms
ui.css
44 ms
jquery.js
596 ms
jquery-migrate.min.js
47 ms
jquery.cookie.min.js
49 ms
fullcalendar.min.js
55 ms
jquery.ui.core.min.js
52 ms
jquery.ui.widget.min.js
51 ms
jquery.ui.mouse.min.js
55 ms
jquery.ui.resizable.min.js
63 ms
jquery.ui.draggable.min.js
61 ms
jquery.ui.button.min.js
65 ms
jquery.ui.position.min.js
62 ms
jquery.ui.dialog.min.js
71 ms
events.js
68 ms
widgets.js
41 ms
addthis_widget.js
11 ms
jquery.flexslider-min.js
14 ms
spin.min.js
13 ms
bootstrap-transition.js
12 ms
bootstrap-tab.js
13 ms
jquery.fitvids.js
12 ms
site.js
23 ms
comment-reply.min.js
17 ms
posts-widget.js
21 ms
header-waves-6.png
26 ms
logo-bg-crop.png
186 ms
home-sprite.png
172 ms
logo-white.png
104 ms
white-linkedin-01.png
9 ms
white-google%2B-01.png
98 ms
white-youtube-01.png
8 ms
white-subscribe-01.png
98 ms
PulsesIndiaPhoto_Blog1_Zoomed-272x272.jpg
169 ms
24165834155_2cf6cc3c57_z-272x272.jpg
169 ms
Fig-2-Raisedbed-272x272.jpg
99 ms
Blog101-272x272.jpg
97 ms
slide1-272x272.jpg
99 ms
Stevie-Mann-672x4481.jpg
101 ms
hands.jpg
100 ms
partnership.jpg
101 ms
24165834155_2cf6cc3c57_z-128x128.jpg
102 ms
Exploring-underground-hpt-96x96.jpg
102 ms
RS77493_060-Hunters-Tamanga-Ekwayoli-in-the-Tumba-Ledima-Reserve-RDC-scr-96x96.jpgresize832415
166 ms
2016-04-90x96.jpgitokkxohdvq3
165 ms
2016-05-90x96.jpgitokq6axnlrx
168 ms
2015-42-90x96.jpgitokws_pv32w
167 ms
Resources-2-272x272-128x128.jpg
171 ms
image_gallery_beans2-96x96.jpeg
167 ms
bishkek2-3-96x96.jpg
168 ms
Land-Conference-2016-Branding-96x96.gif
168 ms
green-facebook-01.png
170 ms
green-twitter-01.png
169 ms
green-linkedin-01.png
225 ms
green-google%2B-01.png
417 ms
green-youtube-01.png
226 ms
green-rss-01.png
225 ms
green-subscribe-1.png
226 ms
10568933194_cfcd06e534_k-96x96.jpg
228 ms
24520176479_373201e45d_m.jpg
229 ms
24592333970_c72d7e37cc_m.jpg
228 ms
footer-waves-6.png
227 ms
all.js
58 ms
ga.js
61 ms
300lo.json
72 ms
ie67-css.d20541e614a2e495c355.js
14 ms
search-sprite.png
100 ms
20b6f036-fda6-4c21-a894-6372f9613b6f.woff
61 ms
icomoon.woff
92 ms
d546ab81-5c6c-4e39-b8c5-6f2a287d882a.woff
109 ms
37b02020-a0ec-4a3c-b5f3-7d37169e689b.woff
127 ms
sh.7c7179124ea24ac6ba46caac.html
53 ms
__utm.gif
48 ms
81 ms
xd_arbiter.php
35 ms
xd_arbiter.php
46 ms
cgiar.org 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
[aria-*] attributes do not match their roles
[aria-hidden="true"] elements contain focusable descendents
ARIA input fields do not have accessible names
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
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
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
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>).
List items (<li>) are not contained within <ul> or <ol> parent elements.
cgiar.org best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
cgiar.org SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
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
Tap targets are not sized appropriately
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Cgiar.org can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Cgiar.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.
cgiar.org
Open Graph description is not detected on the main page of CGIAR. 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: