7.4 sec in total
1.8 sec
5.2 sec
433 ms
Visit voodland.com now to see the best up-to-date Voodland content for Russia and also check out these interesting facts you probably never knew about voodland.com
декоративные-растения-для-ландшафтного-дизайна, купить-растения, большой-выбор-саженцев-растений-собственного-производства, посадочный-материал-для-городского-и-загородного-озеленения, вудлэнд, маркет...
Visit voodland.comWe analyzed Voodland.com page load time and found that the first response time was 1.8 sec and then it took 5.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
voodland.com performance score
name
value
score
weighting
Value2.3 s
75/100
10%
Value2.8 s
84/100
25%
Value6.3 s
42/100
10%
Value920 ms
30/100
30%
Value0.478
18/100
15%
Value13.8 s
10/100
10%
1799 ms
276 ms
280 ms
283 ms
284 ms
Our browser made a total of 157 requests to load all elements on the main page. We found that 76% of them (120 requests) were addressed to the original Voodland.com, 6% (9 requests) were made to Mc.yandex.ru and 3% (4 requests) were made to Translate.googleapis.com. The less responsive or slowest element that took the longest time to load (1.8 sec) belongs to the original domain Voodland.com.
Page size can be reduced by 1.4 MB (57%)
2.5 MB
1.1 MB
In fact, the total size of Voodland.com main page is 2.5 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. Javascripts take 1.3 MB which makes up the majority of the site volume.
Potential reduce by 341.7 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 341.7 kB or 83% of the original size.
Potential reduce by 39.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. Voodland images are well optimized though.
Potential reduce by 889.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 889.2 kB or 67% of the original size.
Potential reduce by 153.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. Voodland.com needs all CSS files to be minified and compressed as it can save up to 153.2 kB or 82% of the original size.
Number of requests can be reduced by 113 (73%)
154
41
The browser has sent 154 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Voodland. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 36 to 1 for JavaScripts and from 50 to 1 for CSS and as a result speed up the page load time.
voodland.com
1799 ms
soccomments.css
276 ms
vmsite-ltr.css
280 ms
modal.css
283 ms
style.css
284 ms
facebox.css
286 ms
mod_vm_login.css.php
289 ms
rokajaxsearch.css
414 ms
rokajaxsearch-theme.css
418 ms
calendar-jos.css
419 ms
style.css
421 ms
acd47dbe9cf32bc7099e6b6ad7f7e132.css
429 ms
moo_maximenuhck.css
432 ms
maximenuhck.php
553 ms
beez_20-position1.css
557 ms
maximenuresponsiveck.css
559 ms
jquery.min.js
706 ms
jquery-ui-1.8.16.custom.min.js
571 ms
jsoccomments.js
572 ms
jquery.noConflict.js
690 ms
vmsite.js
693 ms
mootools-core.js
839 ms
core.js
723 ms
modal.js
724 ms
mootools-more.js
1119 ms
facebox.js
859 ms
vmprices.js
859 ms
rokajaxsearch.js
860 ms
calendar.js
860 ms
calendar-setup.js
977 ms
general.js
981 ms
28d4ede308591515c374495b0f99c507.js
1145 ms
moomaximenuck.js
997 ms
fancymenuck.js
998 ms
style.css
1115 ms
details.css
1143 ms
element.js
38 ms
74gygyjz52a.gif
198 ms
watch.js
172 ms
share.js
18 ms
logo88x31.gif
346 ms
top100.jcn
367 ms
88x31_wm_v_blue_on_white_ru.png
524 ms
out.php
497 ms
1kdigital88_31.gif
397 ms
2159
470 ms
gplus-16.png
11 ms
16418
430 ms
editor.css
1013 ms
layout.css
881 ms
menus.css
985 ms
modules.css
982 ms
reset.css
985 ms
template.css
996 ms
vm.css
1006 ms
watch.js
564 ms
cufon-yui.js
890 ms
PT_Serif_400-PT_Serif_700-PT_Serif_italic_400-PT_Serif_italic_700.font.js
1166 ms
set_height.js
983 ms
change_bg.js
1023 ms
css
27 ms
logo-mini2.png
1015 ms
tel.png
1016 ms
opros.gif
893 ms
glauca-globosapa38_120x120.jpg
983 ms
inversa13_120x120.jpg
1203 ms
hvoy5_120x120.jpg
1043 ms
oak114_120x120.jpg
1193 ms
ctr133.png
144 ms
bush18_120x120.jpg
1076 ms
krupnomery_120x120.jpg
990 ms
plody_120x120.jpg
1041 ms
kom_rast_120x120.jpg
1040 ms
kaktusy_120x120.jpg
1136 ms
rosa15_120x120.jpg
1221 ms
zashita4_120x120.jpg
1011 ms
spec_120x120.jpg
1010 ms
vvoodland1.jpg
1238 ms
soccomments.css
720 ms
vmsite-ltr.css
891 ms
modal.css
896 ms
style.css
907 ms
facebox.css
916 ms
mod_vm_login.css.php
970 ms
rokajaxsearch.css
982 ms
rokajaxsearch-theme.css
993 ms
calendar-jos.css
1005 ms
style.css
1037 ms
acd47dbe9cf32bc7099e6b6ad7f7e132.css
1050 ms
moo_maximenuhck.css
1019 ms
maximenuhck.php
1026 ms
beez_20-position1.css
1057 ms
maximenuresponsiveck.css
1046 ms
all.js
30 ms
top_bg.png
705 ms
top.png
812 ms
top_shadow.png
750 ms
hover_li.png
783 ms
translateelement.css
55 ms
main.js
124 ms
header_green_center.jpg
717 ms
header_green_bottom.jpg
726 ms
banner_3.png
1023 ms
catalog_readon.png
819 ms
main_gradient.png
850 ms
leaves_2.png
1131 ms
module_top.png
866 ms
advert.gif
117 ms
analytics.js
15 ms
module_bot.png
827 ms
search-icon.png
899 ms
arrows_exp.png
931 ms
6539a506ff7b6b5514680aa3ccb6f685.png
949 ms
element_main.js
43 ms
71e25f34d43b1fd798147fd5cbb67c15.png
959 ms
collect
15 ms
top100.scn
138 ms
collect
97 ms
67702dea9c80d8f7a37a6c9678bafba6.png
942 ms
8540115308a05693df9308bbee7f757a.png
963 ms
4caaeb6fbf6ceeae4d9caaf8813ce1b3.png
953 ms
username_bg.png
960 ms
support.js
1028 ms
1
169 ms
b-share-icon.png
81 ms
style.css
796 ms
details.css
852 ms
editor.css
883 ms
layout.css
893 ms
menus.css
925 ms
modules.css
931 ms
counter2
174 ms
20715859
209 ms
136588
130 ms
20715859
209 ms
136588
317 ms
26812653
128 ms
132 ms
reset.css
873 ms
template.css
894 ms
vm.css
918 ms
password_bg.png
924 ms
button_bg.png
910 ms
lost_password_bg.png
889 ms
lost_username_bg.png
881 ms
registration_bg.png
902 ms
content_top_scheme2_l.png
918 ms
content_in_scheme2_l.png
918 ms
category_bg.png
922 ms
translate_24dp.png
30 ms
l
41 ms
cleardot.gif
40 ms
separator.png
918 ms
content_bot_scheme2_l.png
887 ms
footer_shadow.png
940 ms
footer_sep.png
963 ms
module_bot_short.png
141 ms
voodland.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
Buttons do not have an accessible name
<frame> or <iframe> elements do not have a title
Links do not have a discernible name
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
voodland.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
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
voodland.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
Tap targets are not sized appropriately
RU
RU
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Voodland.com can be misinterpreted by Google and other search engines. Our service has detected that Russian is used on the page, and it matches the claimed language. Our system also found out that Voodland.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.
voodland.com
Open Graph description is not detected on the main page of Voodland. 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: