12.5 sec in total
2.5 sec
9.8 sec
308 ms
Click here to check amazing Botanicalme content for United States. Otherwise, check out these important facts you probably never knew about botanicalme.com
Visit botanicalme.comWe analyzed Botanicalme.com page load time and found that the first response time was 2.5 sec and then it took 10.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
botanicalme.com performance score
name
value
score
weighting
Value0.8 s
100/100
10%
Value1.5 s
100/100
25%
Value0.8 s
100/100
10%
Value0 ms
100/100
30%
Value0
100/100
15%
Value0.8 s
100/100
10%
2477 ms
81 ms
32 ms
37 ms
44 ms
Our browser made a total of 116 requests to load all elements on the main page. We found that 55% of them (64 requests) were addressed to the original Botanicalme.com, 16% (19 requests) were made to Static.xx.fbcdn.net and 7% (8 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (4.1 sec) belongs to the original domain Botanicalme.com.
Page size can be reduced by 869.0 kB (32%)
2.7 MB
1.9 MB
In fact, the total size of Botanicalme.com main page is 2.7 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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 1.7 MB which makes up the majority of the site volume.
Potential reduce by 32.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. 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 32.2 kB or 80% of the original size.
Potential reduce by 44.2 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. Botanicalme images are well optimized though.
Potential reduce by 387.5 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 387.5 kB or 68% of the original size.
Potential reduce by 405.1 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. Botanicalme.com needs all CSS files to be minified and compressed as it can save up to 405.1 kB or 84% of the original size.
Number of requests can be reduced by 64 (60%)
106
42
The browser has sent 106 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Botanicalme. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 39 to 1 for JavaScripts and from 27 to 1 for CSS and as a result speed up the page load time.
botanicalme.com
2477 ms
style.css
81 ms
css
32 ms
css
37 ms
css
44 ms
css
55 ms
css
55 ms
css
55 ms
css
54 ms
css
53 ms
validationEngine.jquery.css
70 ms
styles.css
83 ms
prettyPhoto.css
65 ms
style.css
83 ms
woocommerce-layout.css
55 ms
woocommerce.css
105 ms
superfish.css
114 ms
prettyPhoto.css
111 ms
flexslider.css
121 ms
colour.css
114 ms
responsive.css
121 ms
jquery.js
208 ms
jquery-migrate.min.js
154 ms
jquery.prettyPhoto.js
162 ms
ajax.js
2866 ms
jquery.form.min.js
190 ms
scripts.js
172 ms
add-to-cart.min.js
197 ms
jquery.blockUI.min.js
233 ms
woocommerce.min.js
233 ms
jquery.cookie.min.js
239 ms
cart-fragments.min.js
241 ms
jquery-ui.min.js
44 ms
jquery.prettyPhoto.js
243 ms
superfish.js
237 ms
jquery.flexslider-min.js
242 ms
jquery.fitvid.js
258 ms
froogaloop.js
265 ms
jquery.jcarousel.min.js
263 ms
cloud-zoom.1.0.2.js
282 ms
selectivizr-min.js
276 ms
scripts.js
294 ms
jquery.validationEngine-en.js
297 ms
jquery.validationEngine.js
338 ms
front-subscribers.js
307 ms
ga.js
94 ms
icon-free.jpg
75 ms
icon-gc.png
91 ms
lock-icon.png
89 ms
arrow-icon.png
90 ms
cart-icon.png
88 ms
header-bkg.jpg
90 ms
main-logo.png
167 ms
header-main-img1.png
328 ms
bkg-weave.jpg
221 ms
slider-ie-675x420.png
680 ms
slider-shea-675x420.png
653 ms
slider-rr-675x420.jpg
327 ms
mnm-bug.jpg
180 ms
widget-fb-icon.jpg
319 ms
img-co-meetme.jpg
325 ms
img-co-ourcause.jpg
345 ms
img-co-newprods.jpg
345 ms
img-co-buzzblog.jpg
344 ms
bkg-footer.jpg
423 ms
footer-weave.jpg
484 ms
dot.png
483 ms
icon-fb.png
483 ms
icon-twitter.png
483 ms
icon-utube.png
630 ms
list-icon-ig.png
648 ms
RvE3-RmMouE
249 ms
ODelI1aHBYDBqgeIAH2zlEY6Fu39Tt9XkmtSosaMoEA.ttf
94 ms
RXTgOOQ9AAtaVOHxx0IUBF5f9YK0z_CKegLiCihVlJo.ttf
94 ms
bVp4nhwFIXU-r3LqUR8DSO4_8dNFM_-5wVGTcpuxfTE.ttf
101 ms
gDxHeefcXIo-lOuZFCn2xYkPW4j7ieGPU4sFV2kAxjrr7w4p9aSvGirXi6XmeXNA.ttf
126 ms
jXlXpULVZtk2Rzpy5O18QwLUuEpTyoUstqEm5AMlJo4.ttf
125 ms
GCgb7bssGpwp7V5ynxmWy2nGvBZA8xlFy_N6JGBgUeo.ttf
94 ms
__utm.gif
64 ms
slide-arrows.png
468 ms
likebox.php
497 ms
admin-ajax.php
4076 ms
www-embed-player-vflfNyN_r.css
47 ms
www-embed-player.js
112 ms
base.js
171 ms
fBnyGA8Aionz5086-mElmoOSPUuyQ1M9Un647_EjucU.js
88 ms
ad_status.js
87 ms
ebiMDO3r-8l.css
101 ms
jGc-59L_9lo.css
113 ms
6qHpHChjY_J.css
141 ms
ztINr5qMqM_.css
134 ms
uVjHKJ0glvg.css
162 ms
q68gy-v_YMF.js
142 ms
FJmpeSpHpjS.js
142 ms
0wM5s1Khldu.js
160 ms
1bNoFZUdlYZ.js
141 ms
njO1TPvGzoR.js
160 ms
1QuX41zDRrx.js
237 ms
Oagsvfb4VWi.js
238 ms
LTv6ZK-5zxz.js
245 ms
1FCa-btixu2.js
244 ms
CrYjSnGjrRCn0pd9VQsnFOvvDin1pK8aKteLpeZ5c0A.woff
90 ms
RxZJdnzeo3R5zSexge8UUbO3LdcAZYWl9Si6vvxL-qU.woff
90 ms
996981_575735669186207_449002841_n.jpg
206 ms
1380000_529451453814629_939683446_n.jpg
223 ms
12744342_1055319861227783_2150583340353452576_n.jpg
248 ms
12243162_997826576948644_8914037915402598100_n.jpg
187 ms
11947456_962696973823406_6701076694890107513_n.jpg
183 ms
11698561_946045322155238_5878200182569818498_n.jpg
201 ms
11752505_943700169056420_590604124307767593_n.jpg
193 ms
wL6VQj7Ab77.png
179 ms
s7jcwEQH7Sx.png
178 ms
QDwYpIaRyfG.png
178 ms
I6-MnjEovm5.js
9 ms
pQrUxxo5oQp.js
4 ms
woocommerce-smallscreen.css
79 ms
botanicalme.com accessibility score
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
botanicalme.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Browser errors were logged to the console
botanicalme.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Page is blocked from indexing
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Botanicalme.com 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 Botanicalme.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.
botanicalme.com
Open Graph description is not detected on the main page of Botanicalme. 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: