5.8 sec in total
339 ms
5.1 sec
446 ms
Click here to check amazing Botanologio content for Greece. Otherwise, check out these important facts you probably never knew about botanologio.com
Βότανολόγιο, ένα Blog που θα βρείτε τα πάντα για τα βότανα, και τα μπαχαρικά, τις θεραπευτικές και καλλυντικές ιδιότητες και χρήσεις τους!
Visit botanologio.comWe analyzed Botanologio.com page load time and found that the first response time was 339 ms and then it took 5.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
botanologio.com performance score
name
value
score
weighting
Value4.4 s
17/100
10%
Value6.1 s
13/100
25%
Value7.9 s
23/100
10%
Value1,530 ms
14/100
30%
Value0.004
100/100
15%
Value11.8 s
17/100
10%
339 ms
197 ms
194 ms
294 ms
219 ms
Our browser made a total of 129 requests to load all elements on the main page. We found that 53% of them (68 requests) were addressed to the original Botanologio.com, 6% (8 requests) were made to Static.xx.fbcdn.net and 4% (5 requests) were made to Googleads.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (2.4 sec) belongs to the original domain Botanologio.com.
Page size can be reduced by 422.9 kB (32%)
1.3 MB
891.4 kB
In fact, the total size of Botanologio.com main page is 1.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. 70% of websites need less resources to load. Images take 716.0 kB which makes up the majority of the site volume.
Potential reduce by 66.4 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 66.4 kB or 79% of the original size.
Potential reduce by 53.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. Botanologio images are well optimized though.
Potential reduce by 229.4 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 229.4 kB or 55% of the original size.
Potential reduce by 73.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. Botanologio.com needs all CSS files to be minified and compressed as it can save up to 73.1 kB or 77% of the original size.
Number of requests can be reduced by 69 (58%)
119
50
The browser has sent 119 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Botanologio. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 38 to 1 for JavaScripts and from 21 to 1 for CSS and as a result speed up the page load time.
botanologio.com
339 ms
language-selector.css
197 ms
styles.css
194 ms
jquery.js
294 ms
jquery-migrate.min.js
219 ms
js
24 ms
hashchange.js
218 ms
dpagination.js
217 ms
index.css
379 ms
style.css
382 ms
shortcode.css
384 ms
superfish.js
385 ms
smthemes.js
386 ms
jquery.cycle.all.js
483 ms
widgets.min.css
571 ms
nextgen_basic_thumbnails.min.css
570 ms
trigger_buttons.min.css
572 ms
jquery.fancybox-1.3.4.min.css
574 ms
font-awesome.min.css
576 ms
style.min.css
672 ms
nggallery.css
768 ms
adsbygoogle.js
17 ms
jquery.form.min.js
768 ms
scripts.js
770 ms
wp-embed.min.js
769 ms
sitepress.js
764 ms
ajax.min.js
863 ms
common.min.js
963 ms
nextgen_basic_thumbnails.min.js
962 ms
lightbox_context.min.js
964 ms
jquery.easing-1.3.pack.js
963 ms
jquery.fancybox-1.3.4.pack.js
964 ms
nextgen_fancybox_init.min.js
1056 ms
element.js
34 ms
wp-emoji-release.min.js
964 ms
0.jpg
21 ms
53 ms
186b4ec90b0cd3c2aea6bfd43ff9c4f7
56 ms
e2b69088aea5b0ef14a8a5f2d9eec792
80 ms
arrow-up.png
852 ms
logo_vot_140x264new.png
984 ms
herbs-banner5.jpg
1235 ms
slide2.jpg
949 ms
slide33.jpg
1049 ms
herbs-banner4.jpg
1329 ms
parnis.jpg
1049 ms
astragalus.jpg
1153 ms
epilobium-how-to-collect.jpg
1171 ms
herbsforeyes.jpg
1253 ms
d6c380e068f6b73d264f47fcb0ab2540
82 ms
epilobium_cosmetics.jpg
1252 ms
wide.css
1293 ms
css
26 ms
css
37 ms
css
45 ms
thumbs_levanta.jpg
1615 ms
thumbs_dentrolivano2.jpg
1613 ms
thumbs_maintanos.jpg
1613 ms
thumbs_fresh-oregano.jpg
1612 ms
thumbs_melissoxorto.jpg
1515 ms
thumbs_moloxa-2.jpg
1426 ms
facebook.png
1595 ms
googleplus-button.png
1593 ms
pinterest-button.png
1778 ms
youtube-icon.png
1599 ms
twitter-logo.png
1504 ms
top.jpg
507 ms
analytics.js
13 ms
fbds.js
8 ms
menu.png
661 ms
main-n.png
660 ms
shadow.png
673 ms
slide-right.png
673 ms
slide-left.png
677 ms
search.png
871 ms
UyYrYy3ltEffJV9QueSi4VLE0juxe_YrR4_5kH0wfhI.ttf
32 ms
top-r.png
2373 ms
2Tarv7Qs4oCEU-xItQ7PXSwlidHJgAgmTjOEEzwu1L8.ttf
28 ms
lXoKq2PC8Z_S1wl-BwvrB-vvDin1pK8aKteLpeZ5c0A.ttf
28 ms
collect
35 ms
402 ms
ca-pub-6757802697380850.js
355 ms
zrt_lookup.html
354 ms
show_ads_impl.js
264 ms
all.js
217 ms
separator.png
825 ms
nextpage.png
824 ms
bottom-r.png
2284 ms
collect
375 ms
translateelement.css
373 ms
main.js
383 ms
ads
317 ms
osd.js
28 ms
83 ms
xd_arbiter.php
61 ms
xd_arbiter.php
69 ms
ads
291 ms
ads
359 ms
element_main.js
39 ms
translate_24dp.png
39 ms
l
43 ms
cleardot.gif
50 ms
te_ctrl3.gif
46 ms
m_js_controller.js
27 ms
abg.js
41 ms
googlelogo_color_112x36dp.png
9 ms
17493185805111091500
67 ms
favicon
84 ms
nessie_icon_thin_arrow_big_white.png
35 ms
s
51 ms
x_button_blue2.png
45 ms
favicon
91 ms
favicon
34 ms
favicon
76 ms
Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js
6 ms
mobile.css
96 ms
tablet.css
187 ms
22 ms
ui
14 ms
like_box.php
130 ms
ebiMDO3r-8l.css
17 ms
jGc-59L_9lo.css
24 ms
q68gy-v_YMF.js
35 ms
FJmpeSpHpjS.js
34 ms
0wM5s1Khldu.js
32 ms
1bNoFZUdlYZ.js
33 ms
1979691_221440814722445_838025825_n.png
57 ms
wL6VQj7Ab77.png
6 ms
s7jcwEQH7Sx.png
11 ms
botanologio.com accessibility score
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-*] attributes do not match their roles
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
botanologio.com 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
Browser errors were logged to the console
botanologio.com 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
EL
EL
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Botanologio.com can be misinterpreted by Google and other search engines. Our service has detected that Greek is used on the page, and it matches the claimed language. Our system also found out that Botanologio.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.
botanologio.com
Open Graph description is not detected on the main page of Botanologio. 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: