16.9 sec in total
5.5 sec
11.1 sec
368 ms
Visit botanical.bg now to see the best up-to-date Botanical content and also check out these interesting facts you probably never knew about botanical.bg
Натурални чайове и билки Ботаникъл. Здраве от природата, предоставено ви чрез специално разработени серии чайове, плод на семейна традиция.
Visit botanical.bgWe analyzed Botanical.bg page load time and found that the first response time was 5.5 sec and then it took 11.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
botanical.bg performance score
name
value
score
weighting
Value1.9 s
87/100
10%
Value6.7 s
7/100
25%
Value11.9 s
4/100
10%
Value7,220 ms
0/100
30%
Value0.364
29/100
15%
Value15.4 s
7/100
10%
5473 ms
30 ms
27 ms
471 ms
462 ms
Our browser made a total of 78 requests to load all elements on the main page. We found that 64% of them (50 requests) were addressed to the original Botanical.bg, 22% (17 requests) were made to Fonts.gstatic.com and 4% (3 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (5.5 sec) belongs to the original domain Botanical.bg.
Page size can be reduced by 2.6 MB (49%)
5.4 MB
2.7 MB
In fact, the total size of Botanical.bg main page is 5.4 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. 70% of websites need less resources to load. CSS take 2.6 MB which makes up the majority of the site volume.
Potential reduce by 169.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 169.2 kB or 81% of the original size.
Potential reduce by 7.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. Botanical images are well optimized though.
Potential reduce by 170.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 170.7 kB or 62% of the original size.
Potential reduce by 2.3 MB
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. Botanical.bg needs all CSS files to be minified and compressed as it can save up to 2.3 MB or 87% of the original size.
Number of requests can be reduced by 39 (70%)
56
17
The browser has sent 56 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Botanical. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 12 to 1 for JavaScripts and from 29 to 1 for CSS and as a result speed up the page load time.
5473 ms
webfont.js
30 ms
analytics.js
27 ms
wp-emoji-release.min.js
471 ms
layerslider.css
462 ms
styles.css
310 ms
go_pricing_styles.css
499 ms
mediaelementplayer.min.css
501 ms
mediaelementplayer.css
620 ms
optinforms.css
617 ms
tp_twitter_plugin.css
624 ms
settings.css
995 ms
form-basic.min.css
665 ms
js_composer.css
2003 ms
main.min.css
1846 ms
font-awesome.min.css
771 ms
fontello.css
782 ms
main-d80cb47028.css
1164 ms
custom-d80cb47028.css
1979 ms
wc-dt-custom-d80cb47028.css
1104 ms
media-d80cb47028.css
1160 ms
style.css
1266 ms
ubermenu.min.css
1326 ms
blackwhite2.css
1330 ms
cleanwhite.css
1427 ms
font-awesome.min.css
1493 ms
ultimate.min.css
2490 ms
Defaults.css
1660 ms
addtoany.min.css
1729 ms
font-awesome.min.css
20 ms
qb.css
1881 ms
jquery.js
2469 ms
jquery-migrate.min.js
1997 ms
collect
27 ms
css
24 ms
2771 ms
2093 ms
2941 ms
3208 ms
js
40 ms
kAYTUNvBOXlHHqglRQ0Nlg.woff
25 ms
kU6VHbqMAZhaN_nXCmLQsQ.woff
7 ms
1bHRUMxmJHoup12DnI9XmQ.woff
11 ms
I1Pn3gihk5vyP0Yw5GqKsQ.woff
14 ms
7DI7Kjvwfuz8m3ExKe6m-Q.woff
11 ms
DXI1ORHCpsQm3Vp6mXoaTRsxEYwM7FgeyaSgU71cLG0.woff
14 ms
10JVD_humAd5zP2yrFqw6nhCUOGz7vYGh680lGh-uXM.woff
11 ms
l1cOQ90roY9yC7voEhngDD8E0i7KZn-EPnyo3HZu7kw.woff
18 ms
PyqsDANUgLi2UsdO-d4iZQ.woff
18 ms
dI-qzxlKVQA6TUC5RKSb3z8E0i7KZn-EPnyo3HZu7kw.woff
18 ms
yunJt0R8tCvMyj_V4xSjafesZW2xOQ-xsNqO47m55DA.woff
18 ms
grlryt2bdKIyfMSOhzd1eA.woff
26 ms
7KXg6nyyqN8gyMoNwQ7aOQ.woff
23 ms
biUEjW7P-lfzIZFXrcy-wQ.woff
23 ms
XE-CQUm9nMnSxYSbi8LNmQ.woff
21 ms
zhcz-_WihjSQC0oHJ9TCYBsxEYwM7FgeyaSgU71cLG0.woff
18 ms
3__ulTNA7unv0UtplybPij8E0i7KZn-EPnyo3HZu7kw.woff
24 ms
gb.png
194 ms
bg.png
195 ms
submenu-001-1.png
1269 ms
submenu-002.png
344 ms
Happy-Holidays.jpg
1575 ms
products-tea.png
1270 ms
products-herbs.png
1270 ms
online-shop.png
1499 ms
botanical-simbol.png
1270 ms
page.js
28 ms
fontawesome-webfont.woff
4 ms
fontawesome-webfont.woff
1381 ms
fontawesome-webfont.woff
1457 ms
Defaults.woff
1645 ms
sm13.html
37 ms
icons.15.svg.css
45 ms
ga.js
32 ms
logo.png
199 ms
ifs.png
355 ms
sgs.png
366 ms
logo-buttom-white.png
503 ms
botanical.bg 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
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.
botanical.bg 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
botanical.bg SEO score
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
BG
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Botanical.bg can be misinterpreted by Google and other search engines. Our service has detected that Bulgarian is used on the page, and it does not match the claimed English language. Our system also found out that Botanical.bg 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.
botanical.bg
Open Graph data is detected on the main page of Botanical. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: