2.6 sec in total
179 ms
2.3 sec
160 ms
Click here to check amazing Botanicare content for United States. Otherwise, check out these important facts you probably never knew about botanicare.com
Visit botanicare.comWe analyzed Botanicare.com page load time and found that the first response time was 179 ms and then it took 2.4 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.
botanicare.com performance score
name
value
score
weighting
Value5.0 s
9/100
10%
Value11.0 s
0/100
25%
Value13.5 s
2/100
10%
Value2,980 ms
3/100
30%
Value0.004
100/100
15%
Value17.9 s
4/100
10%
179 ms
834 ms
77 ms
193 ms
165 ms
Our browser made a total of 66 requests to load all elements on the main page. We found that 82% of them (54 requests) were addressed to the original Botanicare.com, 8% (5 requests) were made to Translate.googleapis.com and 3% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (834 ms) belongs to the original domain Botanicare.com.
Page size can be reduced by 637.8 kB (28%)
2.3 MB
1.6 MB
In fact, the total size of Botanicare.com main page is 2.3 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. 55% of websites need less resources to load. Images take 1.6 MB which makes up the majority of the site volume.
Potential reduce by 34.8 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 34.8 kB or 77% of the original size.
Potential reduce by 176.9 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. Obviously, Botanicare needs image optimization as it can save up to 176.9 kB or 11% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 295.2 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 295.2 kB or 61% of the original size.
Potential reduce by 130.8 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. Botanicare.com needs all CSS files to be minified and compressed as it can save up to 130.8 kB or 84% of the original size.
Number of requests can be reduced by 38 (59%)
64
26
The browser has sent 64 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Botanicare. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 26 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
botanicare.com
179 ms
www.botanicare.com
834 ms
jquery.min.js
77 ms
jquery.fancybox-1.3.4.css
193 ms
ComponentArt.css
165 ms
print.css
214 ms
style.css
529 ms
webparts.css
149 ms
WebResource.axd
129 ms
WebResource.axd
151 ms
ScriptResource.axd
227 ms
ScriptResource.axd
257 ms
ScriptResource.axd
257 ms
WebKitFix.js
211 ms
common.js
222 ms
stuHover.js
284 ms
cufon-yui.js
384 ms
ITC_Franklin_Gothic_Std_600.font.js
411 ms
cufon-selectors.js
319 ms
jquery.jcarousel.min.js
362 ms
main.js
430 ms
jquery.mousewheel-3.0.4.pack.js
391 ms
jquery.easing-1.3.pack.js
448 ms
jquery.fancybox-1.3.4.pack.js
494 ms
swfobject.js
493 ms
nutrient_calculator.js
613 ms
jquery.labelify.js
503 ms
element.js
47 ms
ga.js
32 ms
logo.png
75 ms
0000000Hydroplex.jpg
524 ms
00000Hydroplex.jpg
396 ms
0000Hydroplex.jpg
405 ms
0001RhizoBlastBanner2.jpg
470 ms
0002PureBlendTeaBanner.jpg
424 ms
0004PureBlendTeaBanner2.jpg
404 ms
001RhizoGelBanner.jpg
534 ms
002GrowillaNewBanner.jpg
568 ms
02BotanicarePreResBanner2.jpg
557 ms
2CNS17familygraphic.jpg
665 ms
3KINDfamilygrapihc.jpg
632 ms
4PBPROfamilygrapihc.jpg
705 ms
New-Trays.jpg
604 ms
BlogBanner.png
644 ms
PremiumResBanner2.jpg
645 ms
NewCatalogButton2.png
681 ms
logo-footer.png
705 ms
0891.js
46 ms
__utm.gif
12 ms
bgr-header.png
568 ms
bgr-social.png
566 ms
twitter.png
586 ms
facebook.png
601 ms
instagram_small.png
644 ms
translateelement.css
54 ms
main.js
70 ms
bgr-search.png
564 ms
bgr-btn-go.png
578 ms
bgr-navigation_new.png
573 ms
bgr-overlay-blue-single-header.png
608 ms
bgr-footer.png
613 ms
element_main.js
42 ms
translate_24dp.png
50 ms
l
38 ms
cleardot.gif
55 ms
te_ctrl3.gif
13 ms
botanicare.com 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
<frame> or <iframe> elements do not have a title
Links do not have a discernible name
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
botanicare.com 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
Missing source maps for large first-party JavaScript
botanicare.com SEO score
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
N/A
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Botanicare.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else) and no language is claimed in <html> or <meta> tags either. Our system also found out that Botanicare.com 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.
botanicare.com
Open Graph description is not detected on the main page of Botanicare. 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: