2 sec in total
114 ms
1.2 sec
713 ms
Welcome to ecover.com homepage info - get ready to check Ecover best content for United States right away, or after learning these important things about ecover.com
From the way we do business to how we source our ingredients to our war on plastic waste – it’s all about finding new ways to put our values into practice. Even if it might take a while to get there
Visit ecover.comWe analyzed Ecover.com page load time and found that the first response time was 114 ms and then it took 1.9 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.
ecover.com performance score
name
value
score
weighting
Value4.5 s
15/100
10%
Value5.7 s
17/100
25%
Value6.9 s
34/100
10%
Value2,050 ms
8/100
30%
Value0.272
45/100
15%
Value9.2 s
33/100
10%
114 ms
80 ms
19 ms
20 ms
22 ms
Our browser made a total of 72 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Ecover.com, 14% (10 requests) were made to Fast.fonts.net and 4% (3 requests) were made to Us.ecover.com. The less responsive or slowest element that took the longest time to load (303 ms) relates to the external source Static.addtoany.com.
Page size can be reduced by 686.6 kB (23%)
3.0 MB
2.3 MB
In fact, the total size of Ecover.com main page is 3.0 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. 85% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 2.2 MB which makes up the majority of the site volume.
Potential reduce by 38.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 38.4 kB or 78% of the original size.
Potential reduce by 103.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. Ecover images are well optimized though.
Potential reduce by 239.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 239.2 kB or 65% of the original size.
Potential reduce by 305.4 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. Ecover.com needs all CSS files to be minified and compressed as it can save up to 305.4 kB or 92% of the original size.
Number of requests can be reduced by 22 (36%)
61
39
The browser has sent 61 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Ecover. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 15 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.
us.ecover.com
114 ms
ab0e94f7-241f-4476-bc3f-99c609734b44.js
80 ms
gdsr.css.php
19 ms
rating.css
20 ms
main.css
22 ms
responsive-tabs.css
24 ms
jquery.mmenu.css
19 ms
jquery.mmenu.positioning.css
23 ms
widget.subscribe.css
23 ms
tablepress-combined.min.css
36 ms
addtoany.min.css
23 ms
jquery.js
26 ms
jquery-migrate.min.js
29 ms
gdsr.js
22 ms
jquery.mmenu.min.js
22 ms
widget.subscribe.js
24 ms
jquery.responsiveTabs.js
21 ms
jquery.ddslick.min.js
24 ms
built.min.js
24 ms
wp-embed.min.js
23 ms
wp-emoji-release.min.js
204 ms
analytics.js
160 ms
ecover-logo.png
158 ms
page.js
303 ms
v1.js
147 ms
all.js
228 ms
shopping-cart.png
34 ms
search-icon.png
35 ms
hamburger_icon.png
35 ms
logo.jpg
34 ms
ecover_header_background.jpg
48 ms
ecover_Homepage_Header_Flower_Hand_0818.gif
52 ms
hero_text_balloon3a.png
35 ms
hp-bottles-line.png
36 ms
home_product_line_1.png
36 ms
home_product_line_2.png
35 ms
home_product_line_3.png
37 ms
home_product_line_4.png
38 ms
home_product_line_5.png
37 ms
home_product_line_6.png
38 ms
homepage_products_mobile_image.png
43 ms
product_bubble_bg.png
39 ms
pioneering_clean_bg.png
38 ms
homepage_icon_science.gif
39 ms
homepage_icon_animal.gif
40 ms
homepage_icon_anatomy.gif
38 ms
homepage_icon_bottle.gif
40 ms
hp_plantplastic_v2b_blinks_1800x589.gif
180 ms
at_home_flower.png
40 ms
laundry_home1.png
44 ms
homecare_home1.png
41 ms
dish_home1.png
48 ms
facebook-icon.png
41 ms
twitter-icon.png
45 ms
footer-flower.png
45 ms
cart_icon_mobile.png
25 ms
collect
47 ms
fontawesome-webfont.woff
41 ms
7aa9b54d-99a5-4935-8cb9-655f66538358.woff
43 ms
1759dc85-8914-40ba-b188-15e4edaab18d.woff
77 ms
e937312f-f992-4563-affa-034e72695042.woff
131 ms
6aeea65d-70ff-4c78-8519-926e58dac386.woff
145 ms
338dcca2-6eb6-4622-bf9c-7d52a954d95c.woff
148 ms
3e29b28a-4c46-4e97-8770-c4d7bb8edc49.woff
144 ms
70ae52ec-d89b-4c6a-9402-854ebe423c54.woff
64 ms
d999c07b-a049-4eb5-b8a6-4f36ae25e67e.woff
88 ms
e56ecb6d-da41-4bd9-982d-2d295bec9ab0.woff
110 ms
68 ms
xd_arbiter.php
124 ms
xd_arbiter.php
276 ms
track
131 ms
xd_arbiter.php
87 ms
ecover.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
[role] values are not valid
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
ecover.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
Uses deprecated APIs
ecover.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 Ecover.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 Ecover.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.
ecover.com
Open Graph description is not detected on the main page of Ecover. 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: