3.3 sec in total
301 ms
2.8 sec
258 ms
Click here to check amazing Envy content. Otherwise, check out these important facts you probably never knew about envy.fr
Le Site de toutes les Envy
Visit envy.frWe analyzed Envy.fr page load time and found that the first response time was 301 ms and then it took 3 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
envy.fr performance score
name
value
score
weighting
Value5.7 s
5/100
10%
Value8.9 s
1/100
25%
Value10.8 s
6/100
10%
Value150 ms
95/100
30%
Value0.419
23/100
15%
Value8.8 s
35/100
10%
301 ms
54 ms
88 ms
97 ms
109 ms
Our browser made a total of 27 requests to load all elements on the main page. We found that 19% of them (5 requests) were addressed to the original Envy.fr, 30% (8 requests) were made to Ajax.googleapis.com and 22% (6 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (2.1 sec) relates to the external source Google-analytics.com.
Page size can be reduced by 976.7 kB (88%)
1.1 MB
139.1 kB
In fact, the total size of Envy.fr main page is 1.1 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. 65% of websites need less resources to load. HTML takes 721.7 kB which makes up the majority of the site volume.
Potential reduce by 675.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 675.6 kB or 94% of the original size.
Potential reduce by 129.4 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 129.4 kB or 63% of the original size.
Potential reduce by 171.6 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. Envy.fr needs all CSS files to be minified and compressed as it can save up to 171.6 kB or 90% of the original size.
Number of requests can be reduced by 17 (85%)
20
3
The browser has sent 20 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Envy. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 11 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
envy.fr
301 ms
angular-material.min.css
54 ms
icon
88 ms
css
97 ms
css
109 ms
font-awesome.min.css
9 ms
flag-icon.min.css
17 ms
0-vendor.min.3196.css
21 ms
1-app.min.48e1.css
70 ms
angular.min.js
85 ms
angular-route.min.js
83 ms
angular-aria.min.js
86 ms
angular-animate.min.js
84 ms
angular-sanitize.min.js
85 ms
angular-messages.js
86 ms
angular-material.min.js
150 ms
d3.min.js
18 ms
0-vendor.min.832a.js
200 ms
1-app.min.917d.js
267 ms
analytics.js
2135 ms
collect
16 ms
IczWvq5y_Cwwv_rBjOtT0w.woff
34 ms
CcKI4k9un7TZVWzRVT-T8xsxEYwM7FgeyaSgU71cLG0.woff
46 ms
-_Ctzj9b56b8RgXW8FAriRsxEYwM7FgeyaSgU71cLG0.woff
61 ms
8KhZd3VQBtXTAznvKjw-kxsxEYwM7FgeyaSgU71cLG0.woff
68 ms
xkvoNo9fC8O2RDydKj12bxsxEYwM7FgeyaSgU71cLG0.woff
66 ms
JbtMzqLaYbbbCL9X6EvaIxsxEYwM7FgeyaSgU71cLG0.woff
65 ms
envy.fr 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 input fields do not have accessible names
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
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
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.
envy.fr 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
Missing source maps for large first-party JavaScript
envy.fr 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
FR
FR
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Envy.fr can be misinterpreted by Google and other search engines. Our service has detected that French is used on the page, and it matches the claimed language. Our system also found out that Envy.fr 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.
envy.fr
Open Graph data is detected on the main page of Envy. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: