3.2 sec in total
220 ms
2.7 sec
309 ms
Click here to check amazing Iplantcollaborative content for Benin. Otherwise, check out these important facts you probably never knew about iplantcollaborative.org
Visit iplantcollaborative.orgWe analyzed Iplantcollaborative.org page load time and found that the first response time was 220 ms and then it took 3 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
iplantcollaborative.org performance score
220 ms
1161 ms
145 ms
147 ms
152 ms
Our browser made a total of 79 requests to load all elements on the main page. We found that 97% of them (77 requests) were addressed to the original Iplantcollaborative.org, 3% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain Iplantcollaborative.org.
Page size can be reduced by 468.3 kB (46%)
1.0 MB
551.0 kB
In fact, the total size of Iplantcollaborative.org main page is 1.0 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. 40% of websites need less resources to load. Images take 458.1 kB which makes up the majority of the site volume.
Potential reduce by 51.3 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 51.3 kB or 82% of the original size.
Potential reduce by 46.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. Iplantcollaborative images are well optimized though.
Potential reduce by 250.4 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 250.4 kB or 71% of the original size.
Potential reduce by 120.0 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. Iplantcollaborative.org needs all CSS files to be minified and compressed as it can save up to 120.0 kB or 82% of the original size.
Number of requests can be reduced by 29 (39%)
75
46
The browser has sent 75 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Iplantcollaborative. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 23 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
iplantcollaborative.org
220 ms
www.iplantcollaborative.org
1161 ms
css_xE-rWrJf-fncB6ztZfd2huxqgxu4WO-qwma6Xer30m4.css
145 ms
css_vZ_wrMQ9Og-YPPxa1q4us3N7DsZMJa-14jShHgRoRNo.css
147 ms
css_ugmd-SSDbm1OKE5izFKyWoDlN0VLzOd_7qwRN49enDo.css
152 ms
css_uiE5QmJlV1AcLVtLwipFPe7ANxnEs7PIRDpA1AzDdOU.css
146 ms
css_3OiMs3PTB_wJsMvEJQn2yiW-TdVht2LmFim0VpIEuiA.css
157 ms
css_xmz0Ka6FqB4ZrmmsHv5t3_cnCfo5BlOVAX00Fw_SU4c.css
209 ms
css_TwWQM15EWJgo8m8lyobjiranWulynveTbIswewU4vZQ.css
215 ms
css_F0UIHN95br5bUfn2KJ-Rr572cAJNLujY5EOiYBtslZc.css
216 ms
jquery.min.js
424 ms
jquery.once.js
221 ms
drupal.js
290 ms
jquery.ui.core.min.js
278 ms
jquery.ui.widget.min.js
280 ms
views_slideshow.js
352 ms
jquery.ui.tabs.min.js
287 ms
hoverintent.minified.js
348 ms
formtips.js
348 ms
jquery.cycle.all.min.js
446 ms
views_slideshow_cycle.js
445 ms
jquery.hoverIntent.minified.js
417 ms
sfsmallscreen.js
417 ms
supposition.js
444 ms
superfish.js
488 ms
supersubs.js
487 ms
superfish.js
489 ms
iplant1.js
491 ms
jquery.royalslider.min.js
573 ms
jquery.formalize.js
500 ms
omega-mediaqueries.js
556 ms
alpha-debug.js
555 ms
bg.png
158 ms
iplant_logo.png
155 ms
globe.png
154 ms
icon_active_right.png
153 ms
button_save_tour.png
150 ms
1kp_feature.jpg
158 ms
feature_pagbooth.jpg
160 ms
feature_cows3.jpg
161 ms
message-24-ok.png
162 ms
iconDE.png
163 ms
iconATM.png
162 ms
iconDNAS.png
164 ms
iconDS.png
210 ms
iconBisque.png
211 ms
bg_login_button.png
215 ms
CIPRES_0.png
217 ms
bio_logo_0.png
219 ms
TNRtastic_0.png
219 ms
TARGet.png
279 ms
IBPnewlogo_0.png
278 ms
CoGe-logo_0.png
284 ms
BrachyBio_0.png
353 ms
CGRB_logo_0.png
284 ms
galaxy_logo.png
288 ms
SoyKB_logo.jpg
348 ms
rs-minimal-white.png
347 ms
menu-leaf.png
391 ms
logo_nse.png
390 ms
iconTw.png
391 ms
iconFB.png
417 ms
iconYT.png
416 ms
iconGH.png
421 ms
iconGgl.png
422 ms
resize-handle.png
426 ms
grid-toggle.png
429 ms
analytics.js
96 ms
block-toggle.png
347 ms
arrows-ffffff.png
345 ms
rs-universal.png
594 ms
rs-universal.png
576 ms
globe.png
645 ms
1kp_feature.jpg
357 ms
feature_cows3.jpg
409 ms
OpenSans-Light-webfont.woff
423 ms
OpenSans-Regular-webfont.woff
542 ms
OpenSans-Semibold-webfont.woff
478 ms
collect
24 ms
iplantcollaborative.org SEO score
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Iplantcollaborative.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 Iplantcollaborative.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.
iplantcollaborative.org
Open Graph description is not detected on the main page of Iplantcollaborative. 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: