3.2 sec in total
1.1 sec
1.9 sec
204 ms
Visit botany.org now to see the best up-to-date Botany content for United States and also check out these interesting facts you probably never knew about botany.org
leading scientists and educators since 1893
Visit botany.orgWe analyzed Botany.org page load time and found that the first response time was 1.1 sec and then it took 2.1 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.
botany.org performance score
name
value
score
weighting
Value3.6 s
33/100
10%
Value6.6 s
8/100
25%
Value4.3 s
76/100
10%
Value530 ms
56/100
30%
Value0.301
40/100
15%
Value6.4 s
60/100
10%
1128 ms
14 ms
42 ms
28 ms
41 ms
Our browser made a total of 44 requests to load all elements on the main page. We found that 43% of them (19 requests) were addressed to the original Botany.org, 14% (6 requests) were made to Cms.botany.org and 7% (3 requests) were made to S.ytimg.com. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Botany.org.
Page size can be reduced by 652.3 kB (59%)
1.1 MB
451.3 kB
In fact, the total size of Botany.org main page is 1.1 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. CSS take 393.6 kB which makes up the majority of the site volume.
Potential reduce by 64.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. This page needs HTML code to be minified as it can gain 13.5 kB, which is 18% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 64.2 kB or 84% of the original size.
Potential reduce by 24.0 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. Botany images are well optimized though.
Potential reduce by 232.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 232.9 kB or 65% of the original size.
Potential reduce by 331.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. Botany.org needs all CSS files to be minified and compressed as it can save up to 331.2 kB or 84% of the original size.
Number of requests can be reduced by 18 (44%)
41
23
The browser has sent 41 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Botany. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 14 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
botany.org
1128 ms
styles.css
14 ms
swfobject.js
42 ms
jquery-1.11.1.min.js
28 ms
jquery-1.9.1.min.js
41 ms
bootstrap.css
36 ms
yamm.css
34 ms
submenu.css
78 ms
style.css
35 ms
dropdown.js
78 ms
submenu.js
79 ms
widget.js
94 ms
plant13.jpg
41 ms
ccmtblv2.png
96 ms
_join.png
81 ms
_donate.png
75 ms
current-s.jpg
76 ms
psb_cover-s.jpg
77 ms
apps-s.jpg
77 ms
B2010Posters.jpg
77 ms
find_us_on_facebook_badge.gif
78 ms
twitter_logo.gif
78 ms
flkr-doyou.gif
79 ms
current.jpg
79 ms
psb_cover.jpg
81 ms
cib.gif
93 ms
IFeature1.gif
81 ms
PS-Emporia22005.jpg
79 ms
zeTri.gif
79 ms
P5lwyqgSPUY
164 ms
widgets.js
125 ms
analytics.js
74 ms
88x31.png
46 ms
collect
13 ms
timeline.1b43d11859b7663a2225b885f87704a5.js
135 ms
www-embed-player-vflZsBgOl.css
74 ms
www-embed-player.js
104 ms
base.js
199 ms
syndication
206 ms
347039084843253762
333 ms
yrK4EqpSRdoujKQmsJoZ5WaLgeULvcWnibQMQSxOOnM.js
57 ms
ad_status.js
61 ms
CrYjSnGjrRCn0pd9VQsnFOvvDin1pK8aKteLpeZ5c0A.woff
105 ms
RxZJdnzeo3R5zSexge8UUbO3LdcAZYWl9Si6vvxL-qU.woff
114 ms
botany.org accessibility score
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
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
Image elements do not have [alt] attributes
Form elements do not have associated labels
Links do not have a discernible name
botany.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
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Issues were logged in the Issues panel in Chrome Devtools
botany.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
EN
EN
ISO-8859-1
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Botany.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 Botany.org main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
botany.org
Open Graph description is not detected on the main page of Botany. 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: