3.4 sec in total
671 ms
2.4 sec
310 ms
Visit ae.ecover.com now to see the best up-to-date Ae Ecover content for United States and also check out these interesting facts you probably never knew about ae.ecover.com
CLEAN. It’s the five-letter word we’ve lived by for the best part of 40 years. You see clean means much more to us than washing the dishes or doing the laundry. We are Ecover. #LETSLIVECLEAN
Visit ae.ecover.comWe analyzed Ae.ecover.com page load time and found that the first response time was 671 ms and then it took 2.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
ae.ecover.com performance score
name
value
score
weighting
Value3.6 s
33/100
10%
Value4.0 s
50/100
25%
Value6.7 s
35/100
10%
Value2,320 ms
5/100
30%
Value0
100/100
15%
Value10.6 s
23/100
10%
671 ms
185 ms
463 ms
642 ms
27 ms
Our browser made a total of 35 requests to load all elements on the main page. We found that 86% of them (30 requests) were addressed to the original Ae.ecover.com, 9% (3 requests) were made to Google-analytics.com and 3% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain Ae.ecover.com.
Page size can be reduced by 344.4 kB (12%)
2.8 MB
2.5 MB
In fact, the total size of Ae.ecover.com main page is 2.8 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. Images take 2.5 MB which makes up the majority of the site volume.
Potential reduce by 41.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. This page needs HTML code to be minified as it can gain 16.3 kB, which is 34% 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 41.7 kB or 87% of the original size.
Potential reduce by 66.8 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. Ae Ecover images are well optimized though.
Potential reduce by 124.0 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 124.0 kB or 69% of the original size.
Potential reduce by 111.8 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. Ae.ecover.com needs all CSS files to be minified and compressed as it can save up to 111.8 kB or 85% of the original size.
Number of requests can be reduced by 10 (38%)
26
16
The browser has sent 26 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Ae 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 6 to 1 for JavaScripts and as a result speed up the page load time.
ae.ecover.com
671 ms
normalize.css
185 ms
main.css
463 ms
modernizr-2.6.2.min.js
642 ms
css
27 ms
forms.css
733 ms
jquery.min.js
51 ms
plugins.js
187 ms
main.js
95 ms
packery.pkgd.min.js
1167 ms
149 ms
analytics.js
72 ms
sprite.png
94 ms
ecover_logo.png
96 ms
192en.png
549 ms
194en.png
742 ms
199en.png
944 ms
1439463797.6a285ebb2abe90a80e68b2a459c3ec59.png
561 ms
Ecover-flower.png
187 ms
dots-green.svg
280 ms
2en.png
655 ms
9en.png
840 ms
10en.png
732 ms
14en.png
658 ms
dots-cyan.svg
745 ms
gotham-book.woff
696 ms
icomoon.woff
770 ms
Florence-medium-webfont.woff
786 ms
Florence-semibold-webfont.woff
787 ms
florence-regular-webfont.woff
806 ms
gotham-medium.woff
861 ms
collect
11 ms
collect
20 ms
dots-white.svg
426 ms
dots-lavender.svg
94 ms
ae.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
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
Links do not have a discernible name
ae.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
ae.ecover.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
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
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ae.ecover.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Ae.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.
ae.ecover.com
Open Graph description is not detected on the main page of Ae 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: