1.7 sec in total
506 ms
864 ms
293 ms
Visit pim.cgiar.org now to see the best up-to-date Pim Cgiar content for Ethiopia and also check out these interesting facts you probably never knew about pim.cgiar.org
Visit pim.cgiar.orgWe analyzed Pim.cgiar.org page load time and found that the first response time was 506 ms and then it took 1.2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 20% of websites can load faster.
pim.cgiar.org performance score
name
value
score
weighting
Value3.1 s
47/100
10%
Value10.5 s
0/100
25%
Value11.5 s
5/100
10%
Value540 ms
55/100
30%
Value0.284
42/100
15%
Value11.8 s
17/100
10%
506 ms
10 ms
27 ms
24 ms
40 ms
Our browser made a total of 29 requests to load all elements on the main page. We found that 86% of them (25 requests) were addressed to the original Pim.cgiar.org, 7% (2 requests) were made to Ifpri.info and 3% (1 request) were made to S7.addthis.com. The less responsive or slowest element that took the longest time to load (506 ms) belongs to the original domain Pim.cgiar.org.
Page size can be reduced by 492.4 kB (53%)
928.8 kB
436.4 kB
In fact, the total size of Pim.cgiar.org main page is 928.8 kB. 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. Javascripts take 602.7 kB which makes up the majority of the site volume.
Potential reduce by 58.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 58.2 kB or 73% of the original size.
Potential reduce by 19.7 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. Pim Cgiar images are well optimized though.
Potential reduce by 392.9 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 392.9 kB or 65% 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. Pim.cgiar.org needs all CSS files to be minified and compressed as it can save up to 21.6 kB or 80% of the original size.
Number of requests can be reduced by 13 (46%)
28
15
The browser has sent 28 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Pim 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 10 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
pim.cgiar.org
506 ms
wp-emoji-release.min.js
10 ms
styles.css
27 ms
style.css
24 ms
jquery.js
40 ms
jquery-migrate.min.js
22 ms
vigilance.js
27 ms
mss_autocomplete.css
26 ms
addthis_widget.js
34 ms
output.css
35 ms
suggest.min.js
24 ms
jquery.form.min.js
34 ms
scripts.js
36 ms
wp-embed.min.js
35 ms
master.css
18 ms
analytics.js
294 ms
email-icon-md.png
270 ms
crp2-banner.png
71 ms
crp2_596by200_photo.jpg
73 ms
CIP-sweet-potato-virieties-150x150.jpg
70 ms
group-2-150x150.png
68 ms
18882797573_24e682455d_z-150x150.jpg
70 ms
EDM-special-edition-150x150.png
71 ms
DSpielman-blog-photo-HarvestPlus-150x150.jpg
72 ms
FAO-PIM-infographics-landowners-vs-farmholders-150x150.png
71 ms
list-item.gif
71 ms
crp2-footer.png
70 ms
nav-arrows.png
71 ms
rss_icon2.png
72 ms
pim.cgiar.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
Heading elements are not in a sequentially-descending order
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
Form elements do not have associated labels
Links do not have a discernible name
pim.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
Browser errors were logged to the console
Issues were logged in the Issues panel in Chrome Devtools
pim.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
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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Pim.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 Pim.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.
pim.cgiar.org
Open Graph description is not detected on the main page of Pim 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: