9.1 sec in total
734 ms
8.1 sec
225 ms
Welcome to ecuagenera.com homepage info - get ready to check Ecuagenera best content for Germany right away, or after learning these important things about ecuagenera.com
Ecuagenera orchids from Ecuador, Orchids, Araceas, Aroids, Anthurium, Philodendron, Bromeliáceas and more tropical plants, propagated in vitro, available to be exported to all the world, flowering siz...
Visit ecuagenera.comWe analyzed Ecuagenera.com page load time and found that the first response time was 734 ms and then it took 8.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
ecuagenera.com performance score
name
value
score
weighting
Value4.6 s
14/100
10%
Value16.2 s
0/100
25%
Value11.5 s
5/100
10%
Value1,270 ms
19/100
30%
Value0.186
66/100
15%
Value19.6 s
2/100
10%
734 ms
1761 ms
296 ms
718 ms
1432 ms
Our browser made a total of 111 requests to load all elements on the main page. We found that 66% of them (73 requests) were addressed to the original Ecuagenera.com, 11% (12 requests) were made to Scontent.xx.fbcdn.net and 9% (10 requests) were made to Static.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (1.8 sec) belongs to the original domain Ecuagenera.com.
Page size can be reduced by 1.3 MB (55%)
2.4 MB
1.1 MB
In fact, the total size of Ecuagenera.com main page is 2.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. 50% of websites need less resources to load. Javascripts take 1.3 MB which makes up the majority of the site volume.
Potential reduce by 201.8 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. This page needs HTML code to be minified as it can gain 33.2 kB, which is 13% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 201.8 kB or 81% of the original size.
Potential reduce by 9.6 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. Ecuagenera images are well optimized though.
Potential reduce by 877.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 877.2 kB or 70% of the original size.
Potential reduce by 217.0 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. Ecuagenera.com needs all CSS files to be minified and compressed as it can save up to 217.0 kB or 82% of the original size.
Number of requests can be reduced by 60 (56%)
108
48
The browser has sent 108 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Ecuagenera. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 48 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
ecuagenera.com
734 ms
www.ecuagenera.com
1761 ms
296 ms
package-sf.min.css
718 ms
package-sf.min.js
1432 ms
StorefrontStyle_161.css
728 ms
addthis_widget.js
10 ms
style-ie.css
240 ms
en-GB.js
309 ms
USD.js
304 ms
string.js
304 ms
scope.js
472 ms
json.js
482 ms
base64.js
478 ms
inject-sec-token.js
478 ms
cookie.js
478 ms
storage.js
479 ms
button.js
695 ms
draggable.js
709 ms
resizable.js
708 ms
$pub.js
700 ms
class.js
713 ms
mime.js
704 ms
$dict.js
927 ms
core.js
941 ms
support.js
934 ms
$tmpl.js
933 ms
load.js
939 ms
touch.js
940 ms
version.js
1158 ms
validate.js
1168 ms
de_epages.js
1169 ms
ico_s_search.png
953 ms
de_DE.gif
954 ms
es_ES.gif
953 ms
fr_FR.gif
1171 ms
en_US.gif
1182 ms
en_GB.gif
1183 ms
en_AU.gif
1186 ms
ja_JP.gif
1183 ms
ico_l_basket.png
1184 ms
ecugenera-trans120.png
1642 ms
paypal_credit_card.gif
1417 ms
suggest.js
1358 ms
gadget_facebook.png
732 ms
bgr_content.png
1347 ms
img_content_separatorline.png
1348 ms
gadget_contentslider.png
1363 ms
ga.js
15 ms
300lo.json
45 ms
sh.8e5f85691f9aaa082472a194.html
23 ms
inpage_linkid.js
19 ms
__utm.gif
14 ms
layers.e5ea973510bf60b3db41.js
7 ms
pixel
17 ms
megamenu.js
1428 ms
$ready.js
1427 ms
cookiemessage.js
1440 ms
energylabel.js
1439 ms
bgr_bottom_floatin.png
1443 ms
utf8.js
1647 ms
pixel
15 ms
bgr_bottom.png
1432 ms
all.js
269 ms
dict.en.json
1196 ms
magnifier.tmpl.html
1194 ms
slides.tmpl.html
1196 ms
thumbbox.tmpl.html
1197 ms
datepicker.tmpl.html
1405 ms
67 ms
xd_arbiter.php
228 ms
xd_arbiter.php
450 ms
dictionary.en.json
706 ms
suggest.tmpl.html
706 ms
masonry.js
479 ms
contentslider.js
496 ms
facebook.js
496 ms
simpledialog.js
679 ms
cookiemessage.tmpl.html
690 ms
contentslider.tmpl.html
245 ms
cycle.js
248 ms
facebook.tmpl.html
238 ms
simpledialog.tmpl.html
238 ms
all.js
421 ms
web1.jpg
1213 ms
slider41.jpg
734 ms
slider73.JPG
987 ms
slider51.JPG
1246 ms
like_box.php
102 ms
410ucuAGgaJ.css
182 ms
tSbl8xBI27R.css
224 ms
q68gy-v_YMF.js
306 ms
FJmpeSpHpjS.js
380 ms
0wM5s1Khldu.js
304 ms
1bNoFZUdlYZ.js
302 ms
12075077_528476610661921_7608936940928734162_n.jpg
258 ms
6668_144901149019471_1984287811_n.png
297 ms
10424997_962031627145083_5304036356031770075_n.jpg
337 ms
12821564_511706465698597_3009744290985903619_n.jpg
374 ms
226915_10153605445301634_7536339336919287109_n.jpg
376 ms
64309_10200357526035942_2118097120_n.jpg
377 ms
11164820_707959719314395_7904015138741726278_n.jpg
377 ms
12003375_1090474357659881_6316981177884010174_n.jpg
379 ms
1916976_951105701611895_4860005882117112961_n.jpg
379 ms
1794786_1694317757494315_772529991603565558_n.jpg
414 ms
10258215_1490009007928709_6327332251869420624_n.jpg
416 ms
1459767_3721048281733_134091578_n.jpg
416 ms
wL6VQj7Ab77.png
47 ms
s7jcwEQH7Sx.png
47 ms
I6-MnjEovm5.js
44 ms
pQrUxxo5oQp.js
81 ms
ecuagenera.com 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.
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
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
ecuagenera.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
Browser errors were logged to the console
Page has valid source maps
ecuagenera.com SEO score
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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ecuagenera.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 Ecuagenera.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.
ecuagenera.com
Open Graph description is not detected on the main page of Ecuagenera. 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: