3.7 sec in total
571 ms
2.8 sec
254 ms
Welcome to viverobotanik.com homepage info - get ready to check Vivero Botanik best content right away, or after learning these important things about viverobotanik.com
Vivero Botanik
Visit viverobotanik.comWe analyzed Viverobotanik.com page load time and found that the first response time was 571 ms and then it took 3.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
viverobotanik.com performance score
name
value
score
weighting
Value5.0 s
10/100
10%
Value7.7 s
3/100
25%
Value5.0 s
64/100
10%
Value20 ms
100/100
30%
Value0.169
70/100
15%
Value6.4 s
60/100
10%
571 ms
574 ms
117 ms
314 ms
119 ms
Our browser made a total of 85 requests to load all elements on the main page. We found that 41% of them (35 requests) were addressed to the original Viverobotanik.com, 13% (11 requests) were made to Static.xx.fbcdn.net and 9% (8 requests) were made to Apis.google.com. The less responsive or slowest element that took the longest time to load (1.5 sec) belongs to the original domain Viverobotanik.com.
Page size can be reduced by 601.9 kB (65%)
919.2 kB
317.3 kB
In fact, the total size of Viverobotanik.com main page is 919.2 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 50% of websites need less resources to load. Javascripts take 670.4 kB which makes up the majority of the site volume.
Potential reduce by 141.6 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 141.6 kB or 77% of the original size.
Potential reduce by 2.1 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. Vivero Botanik images are well optimized though.
Potential reduce by 457.8 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 457.8 kB or 68% of the original size.
Potential reduce by 326 B
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. Viverobotanik.com needs all CSS files to be minified and compressed as it can save up to 326 B or 24% of the original size.
Number of requests can be reduced by 33 (40%)
82
49
The browser has sent 82 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Vivero Botanik. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 27 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
viverobotanik.com
571 ms
template.css
574 ms
frontend.css
117 ms
frontend.js
314 ms
mdcr.js
119 ms
droplinebar.css
186 ms
jquery.min.js
30 ms
droplinemenu.js
594 ms
jquery-1.4.2.js
152 ms
coin-slider.min.js
694 ms
coin-slider-styles.css
224 ms
addthis_widget.js
10 ms
anynews.css
59 ms
print.css
62 ms
lg5.jpg
122 ms
anios.jpg
181 ms
qs2.jpg
118 ms
pr2.jpg
172 ms
nb2.jpg
118 ms
ct2.jpg
115 ms
iflor.jpg
179 ms
1.jpg
176 ms
2.jpg
238 ms
3.jpg
178 ms
4.jpg
316 ms
ff.jpg
237 ms
fondo.jpg
388 ms
portada1.jpg
388 ms
portada2.jpg
269 ms
portada3.jpg
228 ms
portada4.jpg
1487 ms
portada5.jpg
754 ms
portada6.jpg
378 ms
portada7.jpg
378 ms
portada8.jpg
490 ms
portada9.jpg
490 ms
portada10.jpg
545 ms
300lo.json
54 ms
all.js&version=v2.0
409 ms
widgets.js
165 ms
plusone.js
48 ms
counter.5524cceca805eb4b9b2b.js
7 ms
likebox.php
225 ms
sh.8e5f85691f9aaa082472a194.html
27 ms
shares.json
35 ms
cb=gapi.loaded_0
75 ms
cb=gapi.loaded_1
71 ms
fastbutton
128 ms
layers.e5ea973510bf60b3db41.js
19 ms
postmessageRelay
58 ms
button.0308b81ff1714e446f674b5b9793f2cd.js
124 ms
cb=gapi.loaded_0
27 ms
cb=gapi.loaded_1
22 ms
pJeswbKZO4XwVR0035gpgvesZW2xOQ-xsNqO47m55DA.ttf
34 ms
ebiMDO3r-8l.css
180 ms
jGc-59L_9lo.css
230 ms
q68gy-v_YMF.js
307 ms
FJmpeSpHpjS.js
376 ms
0wM5s1Khldu.js
298 ms
1bNoFZUdlYZ.js
307 ms
3193398744-postmessagerelay.js
20 ms
rpc:shindig_random.js
34 ms
cb=gapi.loaded_0
18 ms
tweet_button.b9740740e0bcf9b0657c5b11bd4388da.en.html
72 ms
40 ms
xd_arbiter.php
129 ms
xd_arbiter.php
252 ms
jot
113 ms
12670221_770169506450271_3210409308076109776_n.jpg
225 ms
10934046_600098046790752_1701581356172673665_n.png
265 ms
10806410_10152809287526311_120961628621394992_n.jpg
306 ms
1661452_10153168485110448_3064566514790177359_n.jpg
345 ms
12821516_938435589610068_9070181069924375991_n.jpg
347 ms
10383535_345991805603291_4110099447519368969_n.jpg
348 ms
1001979_1675473752699300_3696217899821607348_n.jpg
396 ms
wL6VQj7Ab77.png
47 ms
s7jcwEQH7Sx.png
47 ms
I6-MnjEovm5.js
46 ms
pQrUxxo5oQp.js
41 ms
fql
40 ms
count.json
27 ms
shares.json
18 ms
ping
46 ms
like.php
77 ms
LVx-xkvaJ0b.png
46 ms
viverobotanik.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
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
Image elements do not have [alt] attributes
viverobotanik.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
viverobotanik.com SEO score
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
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
ES
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Viverobotanik.com can be misinterpreted by Google and other search engines. Our service has detected that Spanish is used on the page, and it does not match the claimed English language. Our system also found out that Viverobotanik.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.
viverobotanik.com
Open Graph description is not detected on the main page of Vivero Botanik. 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: