5.5 sec in total
979 ms
4.3 sec
269 ms
Click here to check amazing Botanical Garden Berkeley content for United States. Otherwise, check out these important facts you probably never knew about botanicalgarden.berkeley.edu
UC Botanical Garden
Visit botanicalgarden.berkeley.eduWe analyzed Botanicalgarden.berkeley.edu page load time and found that the first response time was 979 ms and then it took 4.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
botanicalgarden.berkeley.edu performance score
name
value
score
weighting
Value5.2 s
8/100
10%
Value12.4 s
0/100
25%
Value9.1 s
14/100
10%
Value650 ms
46/100
30%
Value0.089
92/100
15%
Value11.0 s
21/100
10%
979 ms
307 ms
162 ms
235 ms
159 ms
Our browser made a total of 89 requests to load all elements on the main page. We found that 85% of them (76 requests) were addressed to the original Botanicalgarden.berkeley.edu, 7% (6 requests) were made to Fonts.gstatic.com and 2% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (2.2 sec) belongs to the original domain Botanicalgarden.berkeley.edu.
Page size can be reduced by 1.2 MB (25%)
4.9 MB
3.7 MB
In fact, the total size of Botanicalgarden.berkeley.edu main page is 4.9 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. 50% of websites need less resources to load. Images take 3.4 MB which makes up the majority of the site volume.
Potential reduce by 60.9 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 60.9 kB or 83% of the original size.
Potential reduce by 145.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. Botanical Garden Berkeley images are well optimized though.
Potential reduce by 587.0 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 587.0 kB or 68% of the original size.
Potential reduce by 430.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. Botanicalgarden.berkeley.edu needs all CSS files to be minified and compressed as it can save up to 430.2 kB or 86% of the original size.
Number of requests can be reduced by 57 (70%)
81
24
The browser has sent 81 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Botanical Garden Berkeley. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 42 to 1 for JavaScripts and from 17 to 1 for CSS and as a result speed up the page load time.
botanicalgarden.berkeley.edu
979 ms
wp-emoji-release.min.js
307 ms
validationEngine.jquery.css
162 ms
layerslider.css
235 ms
layerslider.custom.css
159 ms
css
25 ms
styles.css
157 ms
font-awesome.min.css
385 ms
bwg_frontend.css
310 ms
sumoselect.css
311 ms
font-awesome.css
465 ms
jquery.mCustomScrollbar.css
458 ms
css
34 ms
magnific.css
459 ms
all.css
1048 ms
colorbox.min.css
492 ms
greensock.js
721 ms
jquery.js
874 ms
jquery-migrate.min.js
609 ms
layerslider.kreaturamedia.jquery.js
761 ms
layerslider.transitions.js
718 ms
front.js
763 ms
bwg_frontend.js
872 ms
jquery.sumoselect.min.js
875 ms
jquery.mobile.js
914 ms
jquery.mCustomScrollbar.concat.min.js
998 ms
jquery.fullscreen-0.4.1.js
1027 ms
bwg_gallery_box.js
896 ms
picturefill.min.js
901 ms
modernizr.min.js
1008 ms
site.js
39 ms
panopress.js
1098 ms
panopress.css
1047 ms
jquery.form.min.js
986 ms
scripts.js
903 ms
underscore.min.js
921 ms
backbone.min.js
1021 ms
push-menu.min.js
1007 ms
jquery.transit.min.js
1020 ms
jquery.matchheight.min.js
1022 ms
jquery.bxslider.js
1211 ms
core.min.js
1080 ms
effect.min.js
1131 ms
widget.min.js
1161 ms
accordion.min.js
1165 ms
tabs.min.js
1169 ms
all.min.js
1534 ms
jquery.colorbox.1.5.9-min.js
1240 ms
wp-embed.min.js
1199 ms
jquery.validationEngine-en.js
1203 ms
jquery.validationEngine.js
1442 ms
front-subscribers.js
1212 ms
widgets.css
37 ms
settings
45 ms
UCBG-rhodo-logotype.jpg
825 ms
Tropical-House-Heliconia-in-flower-3.jpg
1546 ms
Entrance-with-chamerops-nolina-6-8-2012-3-45-37-PM-e1445359537418.jpg
1250 ms
Facebook.jpg
824 ms
YouTube.jpg
859 ms
Twitter.jpg
885 ms
Pinterest.jpg
917 ms
Mark-Bittman-600x600.jpg
1209 ms
String-from-Sticks-e1457647134391-600x600.jpg
1240 ms
Spring-Plant-Sale2015-Yoni-8-600x600.jpg
1378 ms
FiberDyeSquare.jpg
1677 ms
3389290442_1096ee28d9_o-e1440615175285-600x600.jpg
1590 ms
foot_patt.png
27 ms
s-BiyweUPV0v-yRb-cjciC3USBnSvpkopQaUR-2r7iU.ttf
40 ms
EFpQQyG9GqCrobXxL-KRMfEr6Hm6RMS0v1dtXsGir4g.ttf
48 ms
theme-icons.ttf
1594 ms
icons.ttf
1678 ms
xkvoNo9fC8O2RDydKj12by3USBnSvpkopQaUR-2r7iU.ttf
60 ms
JbtMzqLaYbbbCL9X6EvaIy3USBnSvpkopQaUR-2r7iU.ttf
66 ms
bIcY3_3JNqUVRAQQRNVteQ.ttf
67 ms
-_Ctzj9b56b8RgXW8FAriS3USBnSvpkopQaUR-2r7iU.ttf
66 ms
foot_patt.png
42 ms
Mark-Bittman-300x300@2x.jpg
1461 ms
UC-Botanical-Garden-Bright-600x600.jpg
1780 ms
Spring-Plant-Sale2015-Yoni-8-300x300@2x.jpg
1773 ms
FiberDyeSquare-300x300@2x.jpg
2158 ms
skin.css
1092 ms
Draggable.min.js
1099 ms
ThrowPropsPlugin.min.js
1048 ms
TweenLite.min.js
1256 ms
CSSPlugin.min.js
1280 ms
blank.gif
275 ms
skin.png
308 ms
Draggable.min.js
377 ms
ThrowPropsPlugin.min.js
155 ms
botanicalgarden.berkeley.edu 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
Links do not have a discernible name
botanicalgarden.berkeley.edu 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
Page has valid source maps
Issues were logged in the Issues panel in Chrome Devtools
botanicalgarden.berkeley.edu SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Page is blocked from indexing
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 Botanicalgarden.berkeley.edu 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 Botanicalgarden.berkeley.edu 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.
botanicalgarden.berkeley.edu
Open Graph description is not detected on the main page of Botanical Garden Berkeley. 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: