2.8 sec in total
645 ms
1.8 sec
326 ms
Click here to check amazing Botanic content for United States. Otherwise, check out these important facts you probably never knew about botanic.org
Free botanic and community garden with over 30 unique notable features including a solar greenhouse and significant contributions from senior, handicapped and
Visit botanic.orgWe analyzed Botanic.org page load time and found that the first response time was 645 ms and then it took 2.2 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.
botanic.org performance score
name
value
score
weighting
Value3.2 s
43/100
10%
Value7.0 s
6/100
25%
Value3.7 s
86/100
10%
Value260 ms
83/100
30%
Value0.259
47/100
15%
Value6.2 s
62/100
10%
645 ms
221 ms
176 ms
160 ms
188 ms
Our browser made a total of 84 requests to load all elements on the main page. We found that 86% of them (72 requests) were addressed to the original Botanic.org, 4% (3 requests) were made to Facebook.com and 2% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (645 ms) belongs to the original domain Botanic.org.
Page size can be reduced by 820.2 kB (27%)
3.1 MB
2.2 MB
In fact, the total size of Botanic.org main page is 3.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. 65% of websites need less resources to load. Images take 2.1 MB which makes up the majority of the site volume.
Potential reduce by 45.6 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 45.6 kB or 82% of the original size.
Potential reduce by 52.3 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. Botanic images are well optimized though.
Potential reduce by 644.7 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 644.7 kB or 79% of the original size.
Potential reduce by 77.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. Botanic.org needs all CSS files to be minified and compressed as it can save up to 77.6 kB or 83% of the original size.
Number of requests can be reduced by 32 (39%)
83
51
The browser has sent 83 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Botanic. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 20 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.
botanic.org
645 ms
style.css
221 ms
events.css
176 ms
style_for_map.css
160 ms
calendar-jos.css
188 ms
jquery-ui-spinner.css
213 ms
pagenavi-css.css
153 ms
jquery.js
288 ms
jquery-migrate.min.js
192 ms
jquery.pjax.js
206 ms
events.js
213 ms
main_front_end.js
253 ms
js
24 ms
if_gmap_front_end.js
237 ms
calendar.js
273 ms
calendar-setup.js
249 ms
calendar_function.js
245 ms
jquery-ui.js
393 ms
jquery.ui.slider.js
318 ms
wp-embed.min.js
272 ms
jquery.min.js
65 ms
cycle.js
293 ms
script.js
286 ms
reset.css
104 ms
typography.css
107 ms
layout.css
113 ms
wp-emoji-release.min.js
73 ms
analytics.js
41 ms
layout.jpg
32 ms
collect
200 ms
all.js
63 ms
logo.png
53 ms
nav-dots.png
52 ms
email-icon.png
51 ms
hand-icon.png
187 ms
contact-icon.png
186 ms
search-btn.jpg
189 ms
search-label.jpg
187 ms
header-stripe.jpg
190 ms
AboutTheGardens-480x190.jpg
191 ms
Support1-480x190.jpg
192 ms
Copy-of-P1020342-480x190.jpg
202 ms
Picture1-480x190.png
250 ms
GardeningTipsResources-480x190.jpg
191 ms
DiscoverTheGardens-480x190.jpg
192 ms
Image481-480x190.jpg
194 ms
children-village-480x190.jpg
193 ms
garden-bridge-480x190.jpg
250 ms
VisitTheGardens-480x190.jpg
194 ms
nav-roll-bg.png
199 ms
big-picture-top.png
194 ms
big-picture-btm.png
250 ms
Support1.jpg
469 ms
big-picture-label.jpg
612 ms
big-picture-link.png
252 ms
children-village.jpg
606 ms
Copy-of-P1020342-924x368.jpg
288 ms
P1040619-924x368.jpg
358 ms
DiscoverTheGardens.jpg
354 ms
garden-bridge.jpg
365 ms
big-picture-controls.png
386 ms
big-picture-left-control.png
389 ms
big-picture-right-control.png
392 ms
hr-dots.png
409 ms
HOME_BANNER.png
441 ms
sm-picture-top.png
421 ms
sm-picture-btm.png
401 ms
highlight.jpg
408 ms
home-coa-link.png
421 ms
highlight.png
324 ms
wordpress-cropped-stained-glass-250x146.jpg
302 ms
GardenTipsResource.jpg
316 ms
footer-bg.jpg
341 ms
blue-footer-dots.png
327 ms
APGA16a.png
344 ms
ArtsCheyenne31-100x100.jpg
347 ms
facebook.jpg
353 ms
54 ms
xd_arbiter.php
38 ms
xd_arbiter.php
45 ms
ping
25 ms
like.php
73 ms
qeKvIRsJabD.js
30 ms
LVx-xkvaJ0b.png
23 ms
botanic.org accessibility score
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.
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 IDs are not unique
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
Some elements have a [tabindex] value greater than 0
botanic.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
botanic.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
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 Botanic.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 Botanic.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.
botanic.org
Open Graph description is not detected on the main page of Botanic. 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: