4.1 sec in total
285 ms
3.3 sec
491 ms
Click here to check amazing Yolly content. Otherwise, check out these important facts you probably never knew about yolly.net
Découvrez le groupe Edenred, la plateforme de service et de paiements qui accompagne au quotidien les acteurs du monde du travail dans 45 pays.
Visit yolly.netWe analyzed Yolly.net page load time and found that the first response time was 285 ms and then it took 3.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
yolly.net performance score
name
value
score
weighting
Value7.4 s
1/100
10%
Value31.6 s
0/100
25%
Value19.2 s
0/100
10%
Value13,140 ms
0/100
30%
Value0.072
96/100
15%
Value22.9 s
1/100
10%
285 ms
176 ms
162 ms
244 ms
262 ms
Our browser made a total of 59 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Yolly.net, 7% (4 requests) were made to Fonts.googleapis.com and 7% (4 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1.1 sec) relates to the external source Edenred.com.
Page size can be reduced by 429.4 kB (10%)
4.3 MB
3.8 MB
In fact, the total size of Yolly.net main page is 4.3 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. 55% of websites need less resources to load. Images take 3.9 MB which makes up the majority of the site volume.
Potential reduce by 124.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 124.4 kB or 86% of the original size.
Potential reduce by 255.9 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. Yolly images are well optimized though.
Potential reduce by 49.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 49.0 kB or 36% of the original size.
Potential reduce by 151 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. Yolly.net has all CSS files already compressed.
Number of requests can be reduced by 19 (37%)
52
33
The browser has sent 52 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Yolly. 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 10 to 1 for CSS and as a result speed up the page load time.
www.edenred.com
285 ms
en
176 ms
css_xE-rWrJf-fncB6ztZfd2huxqgxu4WO-qwma6Xer30m4.css
162 ms
css_ZwQ4JegYk9_vB7LtvEKjfjeVcLzDAa88SNWeshZo5Jw.css
244 ms
css_ipx8FJ1R3Eg-emayGk6ASEXxojhUNPy8jr4NF0bqG9w.css
262 ms
css_l5O0L_r1DLdXYfy8Uik38MZRuDju1cISs036ojBkehM.css
270 ms
css_eadGSuGZXMHgP8ZjqMBetY9C8a9c3Hg6E8bWwCpJgPw.css
450 ms
js_4WkLGZTP5OIov__I_0P6NGPWl2bSTfTiZ5H47BqcLsg.js
495 ms
js_x_l9sNc8PgAVP16YEoylO9WB8rT3vBIWFZXAshN4lmI.js
310 ms
js_rsGiM5M1ffe6EhN-RnhM5f3pDyJ8ZAPFJNKpfjtepLk.js
326 ms
js_pl5TENeYWYYyZ_HlNxZKlVwqjgdmCX2JfUttMnceeWM.js
346 ms
js_9_fnNj3OeBRSK1s5OyGJLS9cnv0V_shX-pa9I74VxcI.js
554 ms
js_7Ukqb3ierdBEL0eowfOKzTkNu-Le97OPm-UqTS5NENU.js
326 ms
OtAutoBlock.js
28 ms
otSDKStub.js
46 ms
css
57 ms
css
69 ms
css
72 ms
css
75 ms
analytics.js
555 ms
gtm.js
613 ms
edenred_logo_new.svg
577 ms
figaro-edenred_0.jpg
929 ms
eye_white.svg
565 ms
purpose-hp-com_1.gif
578 ms
essentialscard.png
688 ms
h1-static_1.jpg
864 ms
blue_notes_button.svg
615 ms
edenred-rapport-integre_0.png
617 ms
white_download.svg
616 ms
kadeosedenred.jpg
992 ms
vibewithus_0.png
763 ms
4_0.png
685 ms
blocfocusboursev2_0.png
783 ms
view_solutions_front_bg.jpg
783 ms
card_1.png
852 ms
notepad_1.png
865 ms
star_1.png
857 ms
essentialscard.png
1041 ms
h1-static_1.jpg
1032 ms
kadeosedenred.jpg
1048 ms
idealday2022.png
1146 ms
VivaTech-min.png
1023 ms
edenred_footer_logo.svg
1074 ms
instagram-logo.png
1106 ms
twitter.png
1115 ms
linkedin.png
1143 ms
youtube.png
1145 ms
7cfa46e2-ef2c-41a6-8106-d1841c5c2456.json
417 ms
ajax-loader.gif
687 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw5aX8.ttf
123 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aX8.ttf
186 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Hw5aX8.ttf
192 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Xw5aX8.ttf
226 ms
Edenred-Regular.woff
701 ms
collect
124 ms
collect
58 ms
collect
78 ms
css_qSTpoWfuNRUhoQEIOBNTw8HN614XXBKjYHr5rXqt5YQ.css
90 ms
yolly.net accessibility score
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
Image elements do not have [alt] attributes
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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
[id] attributes on active, focusable elements are not unique
Heading elements are not in a sequentially-descending order
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
yolly.net 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
General
Impact
Issue
Detected JavaScript libraries
yolly.net 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
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
Tap targets are not sized appropriately
FR
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Yolly.net can be misinterpreted by Google and other search engines. Our service has detected that French is used on the page, and it does not match the claimed English language. Our system also found out that Yolly.net 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.
yolly.net
Open Graph description is not detected on the main page of Yolly. 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: