5.6 sec in total
198 ms
3.3 sec
2.2 sec
Visit cherie.fr now to see the best up-to-date Cherie content and also check out these interesting facts you probably never knew about cherie.fr
Chérie FM, la musique la plus variée : écoute en direct, podcasts programmes, vidéos, fréquences, webradios, actualités people, horoscope...
Visit cherie.frWe analyzed Cherie.fr page load time and found that the first response time was 198 ms and then it took 5.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
cherie.fr performance score
name
value
score
weighting
Value2.5 s
69/100
10%
Value16.2 s
0/100
25%
Value6.8 s
34/100
10%
Value1,280 ms
18/100
30%
Value0.203
61/100
15%
Value17.3 s
4/100
10%
198 ms
727 ms
161 ms
165 ms
1091 ms
Our browser made a total of 40 requests to load all elements on the main page. We found that 3% of them (1 request) were addressed to the original Cherie.fr, 30% (12 requests) were made to Cheriefm.fr and 28% (11 requests) were made to Img.nrj.fr. The less responsive or slowest element that took the longest time to load (2.1 sec) relates to the external source Players.nrjaudio.fm.
Page size can be reduced by 167.2 kB (51%)
329.3 kB
162.1 kB
In fact, the total size of Cherie.fr main page is 329.3 kB. 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. HTML takes 187.1 kB which makes up the majority of the site volume.
Potential reduce by 147.5 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 147.5 kB or 79% of the original size.
Potential reduce by 19.7 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. Obviously, Cherie needs image optimization as it can save up to 19.7 kB or 23% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 0 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. Cherie.fr has all CSS files already compressed.
Number of requests can be reduced by 8 (44%)
18
10
The browser has sent 18 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Cherie. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 9 to 1 for JavaScripts and as a result speed up the page load time.
cherie.fr
198 ms
www.cheriefm.fr
727 ms
54.4b2f9272.css
161 ms
app.1edf6dde.css
165 ms
621516f26dfb8_621516f412477.svg
1091 ms
logo-cheriefm-premium-player.png
2065 ms
facebook-svgrepo-com_60db0c5f83cc9.svg
1463 ms
6215170b9444c_6215170ceb406.svg
1446 ms
twitter-svgrepo-com_60db0c94238fe.svg
1445 ms
youtube-svgrepo-com_60db0cb481878.svg
1437 ms
medias%2F2022%2F09%2F6319c25ed6b44_6319c268d56d6.jpg
1437 ms
medias%2F2022%2F09%2F63330b787ec53_63330b83e7988.jpg
1464 ms
medias%2F2022%2F09%2F632884614aedb_6328846b8d469.jpg
1516 ms
medias%2F2022%2F09%2F632d84f1077bf_632d84f207703.png
1515 ms
medias%2F2022%2F09%2F6329d42597dbf_6329d428d1cdc.png
1514 ms
medias%2F2022%2F09%2F63288ffa0a4bb_6328901f3ef55.png
1518 ms
P_CHERIE_ZEN_3.png
2052 ms
P_CHERIE_FRENCHY_3.png
2053 ms
P_CHERIE_NOUVEAUTES.png
2052 ms
P_CHERIE_LOVE_SONGS_3.png
2052 ms
P_CHERIE_HAPPY_3.png
2034 ms
badge-google-play-20201221.svg
1393 ms
5.eabde2.js
949 ms
37.eabde2.js
948 ms
app.eabde2.js
948 ms
1.eabde2.js
1049 ms
2.eabde2.js
1049 ms
search-modal.eabde2.js
1047 ms
account-modal.eabde2.js
1191 ms
webradio-player.eabde2.js
1323 ms
logo-cherie-fm-monochrome.svg
1320 ms
badge-apple-store-fr-fr.svg
1451 ms
badge-ask-amazon-alexa-3.svg
1940 ms
pattern-noisy.png
1474 ms
lato-regular.woff
856 ms
lato-bold.woff
657 ms
lato-black.woff
836 ms
montserrat-bold.woff
1172 ms
enrj-sdfsdf.woff
1314 ms
gtm.js
588 ms
cherie.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-*] attributes do not match their roles
[aria-hidden="true"] elements contain focusable descendents
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
Heading elements are not in a sequentially-descending order
cherie.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
Browser errors were logged to the console
Page has valid source maps
cherie.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 Cherie.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 Cherie.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.
cherie.fr
Open Graph data is detected on the main page of Cherie. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: