3.6 sec in total
566 ms
1.9 sec
1.1 sec
Visit fff.fr now to see the best up-to-date Fff content for France and also check out these interesting facts you probably never knew about fff.fr
fff
Visit fff.frWe analyzed Fff.fr page load time and found that the first response time was 566 ms and then it took 3.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
fff.fr performance score
name
value
score
weighting
Value3.5 s
35/100
10%
Value19.2 s
0/100
25%
Value10.5 s
7/100
10%
Value2,550 ms
4/100
30%
Value0
100/100
15%
Value29.6 s
0/100
10%
566 ms
81 ms
108 ms
113 ms
113 ms
Our browser made a total of 188 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Fff.fr, 74% (139 requests) were made to Web-statics.fff.fr and 14% (26 requests) were made to Fff.twic.pics. The less responsive or slowest element that took the longest time to load (935 ms) relates to the external source Feeds.frgimages.com.
Page size can be reduced by 2.7 MB (15%)
17.8 MB
15.1 MB
In fact, the total size of Fff.fr main page is 17.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. Only a small number of websites need less resources to load. Images take 16.4 MB which makes up the majority of the site volume.
Potential reduce by 194.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 194.4 kB or 85% of the original size.
Potential reduce by 2.5 MB
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, Fff needs image optimization as it can save up to 2.5 MB or 15% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 1.8 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. This website has mostly compressed JavaScripts.
Potential reduce by 11.0 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. Fff.fr needs all CSS files to be minified and compressed as it can save up to 11.0 kB or 12% of the original size.
Number of requests can be reduced by 135 (74%)
183
48
The browser has sent 183 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Fff. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 43 to 1 for JavaScripts and from 86 to 1 for CSS and as a result speed up the page load time.
www.fff.fr
566 ms
loader.js
81 ms
nav_article.7ca6a691.css
108 ms
agents_sportifs.819eac86.css
113 ms
aside_classement.2e23c67c.css
113 ms
aside_resultat.228fc84a.css
112 ms
autocomplete.1645ffb7.css
107 ms
blockquote.19f6e64d.css
117 ms
card_contextualise.a1e9fc47.css
113 ms
carousel-css.eff03096.css
116 ms
carrousel_arrows.9838e44a.css
115 ms
carte_ligueetdistrict.43f8980b.css
115 ms
chiffre_cle.f0bf42af.css
118 ms
classement.c632a9ef.css
118 ms
competition.f9c92def.css
119 ms
competition_resultat.4b3d313f.css
121 ms
derniere_selection_joueur.f4c8e857.css
122 ms
edf_derniere_selection.5e596d87.css
118 ms
encadre.fb082f09.css
119 ms
etapeScss.7557d9c0.css
208 ms
faq.bf908267.css
222 ms
fff_tv_contexte.b844abb0.css
210 ms
general.05d5ad85.css
213 ms
header-etendu.ef67be00.css
216 ms
header-full.a4d7beea.css
218 ms
header-home-minisite.b03c1e7c.css
216 ms
header-regular.c0ea0f83.css
221 ms
header_match_edf.cfb35944.css
223 ms
historique.06a44aac.css
224 ms
iff_contexte.7742b7f5.css
224 ms
footalecole_contexte.0e9ecd48.css
227 ms
info_club.bbbcf5c8.css
228 ms
installation_club.c12dd981.css
231 ms
joueurs.c93eb635.css
228 ms
lame-catalogue.55ccc5b6.css
231 ms
lame-partenaire.78b81f02.css
232 ms
lame_4_carrousel.e7d7e6c7.css
233 ms
lame_5_link.90554918.css
246 ms
all.css
99 ms
all.min.css
83 ms
smart.js
78 ms
sha256.min.js
133 ms
sha256.js
145 ms
sdk.13baec1685caf5c6eeacde774570aa8c3314ba71.js
33 ms
lame_base.9df0a55a.css
133 ms
lame_category.7647ac43.css
130 ms
lame_focus.298c0420.css
130 ms
lame_live.9429d6a4.css
130 ms
lame_masonry_10.6baafcc9.css
131 ms
lame_masonry_3.540990b2.css
130 ms
lame_masonry_6.dbba2e2c.css
139 ms
lame_masonry_9.280f2733.css
130 ms
lame_playlist.4b20627c.css
132 ms
lieu_rencontre.bc1f0f3c.css
131 ms
match_results_after-before.4fa94da3.css
128 ms
module_description.eefc206d.css
132 ms
moteur_competition.35d8621b.css
139 ms
nav-home-minisite.2b30290d.css
133 ms
nav_competition.22b03ecc.css
134 ms
nav_master.6486b1c6.css
133 ms
officiel.3b1e9ffa.css
61 ms
palmares.e66ff305.css
61 ms
partenaire.fb1fb198.css
58 ms
quick-access.53e0e309.css
55 ms
referee.f0c95d21.css
56 ms
reset.568fc5c2.css
55 ms
resultat_calendrier_club.55d2fe8f.css
56 ms
resultat_compet.44dd8597.css
56 ms
resultat_saison.3a578707.css
56 ms
slick.b7063800.css
58 ms
social-media.cd28f624.css
53 ms
stat_rencontre.df797950.css
54 ms
style.39d3b5c6.css
54 ms
temps_forts_match.026952c3.css
55 ms
top_chrono.16a01974.css
56 ms
tous_les_matchs.bf2a7fb6.css
56 ms
upload_document.1023b242.css
56 ms
variables_contextes.941ba703.css
58 ms
prehome.661b046f.css
55 ms
trouver_club_module.63f1860a.css
56 ms
trouver-club.d7bcd968.css
57 ms
lame_base_fff.18442c07.css
58 ms
lame_live_fff.82af285f.css
58 ms
playlist.fe77bd21.css
59 ms
podcast.7efed8de.css
57 ms
statistiques.692f2a7f.css
58 ms
evolution_classement.09e078a4.css
59 ms
home_header.abeb0d8a.css
78 ms
tag.c7cbc5bf.css
90 ms
subheader.5e13be8b.js
90 ms
fff_connexion.7765d39b.js
90 ms
home_carousel.37ef8a7f.js
86 ms
billetterie_featured.f8dcbc87.js
160 ms
topchrono.0984d53c.js
86 ms
billetterie.147a7564.css
86 ms
icon
301 ms
jquery.min.js
224 ms
script
301 ms
miseenavant.dce48a80.css
156 ms
display_article.fa9dbbe2.js
153 ms
carousel.e2eb9222.js
150 ms
derniere_selection.afb172fc.js
150 ms
faq_js.c0a887d4.js
148 ms
download_js.bd63b248.js
147 ms
ffftv_script.55694c6c.js
203 ms
img-ie.e86dae5a.js
202 ms
instagram.caa5281e.js
200 ms
main.fd299d2d.js
201 ms
map-pin-unique.2f4fd177.js
200 ms
match.d161ae75.js
196 ms
nav_minisite.e6b4af70.js
276 ms
parcours_en_bleu.09207110.js
275 ms
player_profile.ff99ea35.js
273 ms
poule_data_carousel.615d485e.js
273 ms
ranking.4a708b4e.js
271 ms
results-and-calendar-load-part.4d5c5ec2.js
270 ms
search_clubs.2e540551.js
576 ms
season-load-part.173a932f.js
574 ms
stats_joueur_js.abf1311f.js
590 ms
svg.cd04d493.js
589 ms
tous_les_joueurs.0f2dba83.js
587 ms
tous_les_matchs_edf.ebe1bedb.js
586 ms
twitter.a5e685e5.js
679 ms
prehome.ae544d49.js
699 ms
gtm.js
894 ms
flag-400.png
653 ms
_ss5_p-201015263+u-5cmtgyftlx5a3btgkopx+v-nk5nzgngqvwwipq6t4ku.jpg
932 ms
1df8eae9109d27c685c4b1ec440ca46f.png
705 ms
statistiques_js.5302afcf.js
705 ms
0f3827bdff24e823afa5ceaee090ace5.png
725 ms
93aaa920ab6c46cb08a914ac2cc703c4.png
721 ms
aed298e711eaa4b70560cb05dee52914.png
705 ms
a6f12a7907d696531d78fde664aa635d.png
726 ms
_ss5_p-201015309+u-zgleojrkejaxjp3pbbmm+v-eaeds1ikbeordslwb2xp.jpg
919 ms
_ss5_p-201015274+u-ndi7ne5pcxmvhx4ppand+v-0rrdox0fyxitlcqilsvr.jpg
924 ms
_ss5_p-201015273+u-jk2mdy4lxcuj08f3idor+v-kdl2tm4iyju23lz5rfsv.jpg
935 ms
9ec238951a54c6dfe5140db87477100a.jpeg
320 ms
fd4bb5499742e2bedc9a65334a9e51ef.png
895 ms
18d1a7d18b235c537747b73e6f439afd.png
897 ms
584436f5cbdad24c3fa59e07a00c6c90.png
901 ms
ae61f9b4bae744f583e0aaea420cfd6e.png
886 ms
b221ee3f11d17d2d30847dd188899669.png
904 ms
cebc67b77be79b29998250a7d4dae7e1.jpeg
648 ms
6a5f9773fea88242349ab80ae56e08e1.jpeg
724 ms
0b69c2185ae55f43c797661adaf4fa8d.png
736 ms
3e5a4cac47e6640c371445ea81c7941b.png
742 ms
2b06c788ff1c1861c7ad9c035ec1abf7.png
887 ms
c9ab1fd4ece75ebee7cf3e7e60545274.png
892 ms
48ae279ed166375042a0a8df0175f7a8.png
898 ms
d99f2e6f46f4b880aee45bf1cc90ccef.png
903 ms
2b4849aecff2ec1cef0ca654205bc799.png
900 ms
cd28a25598955dec74bf5c592d75d395.png
906 ms
a2b900333201ef79ff1aee90fdc29170.jpeg
906 ms
e5d89a1feca191bd5d2d4deb98c2a918.jpeg
907 ms
52f77915f48b9c8f2b86fc7c3156703a.jpeg
907 ms
0f191daf57332091523af8d8752c870e.png
921 ms
bd5d07eccaaa499fa6c0ecfbfd336e19.png
911 ms
ebcd907f54fc19033145fc2c09ff92c8.png
909 ms
45e7fb16edb0cacd553cdf3051bc4354.png
908 ms
0701beac9b85887df82a3313c7607431.png
912 ms
9e9b956180962fb64356bb29da99b22d.png
921 ms
equipe_statistiques_js.bc8f7a7d.js
666 ms
article_mobile_js.5ec8de54.js
680 ms
map-final.ab1d8e47.js
641 ms
fff_plan_taggage.b5b2237a.js
701 ms
logo.png
701 ms
mic.svg
702 ms
play.svg
697 ms
credit-agricole.png
629 ms
edf.png
625 ms
nike.png
629 ms
orange.png
628 ms
uber-eats.png
627 ms
vw.png
632 ms
connexion-login.ccfa1e00.svg
628 ms
fff-equipe-news.335c7394.woff
631 ms
fff-equipe-bold.aab4e46a.woff
579 ms
fff-hero-bold.ec97c54f.woff
577 ms
fff-hero-regular.fc82003d.woff
578 ms
search_blanc.0b75a077.svg
582 ms
slide%20down.6ea48eed.svg
719 ms
arrowRight.90680367.svg
577 ms
ff47bc8bd0b5783153090a2d7f8bcc30.png
660 ms
f8ba3f93835813767ff2769e9a7e7be9.png
653 ms
arrow_right_icon.c4369423.svg
638 ms
star-solid.e01e0fce.svg
645 ms
playlist_icon.b680575b.svg
642 ms
partenaires-bkg.6b18951b.png
582 ms
fff.fr 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
Heading elements are not in a sequentially-descending order
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
fff.fr 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
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
Issues were logged in the Issues panel in Chrome Devtools
fff.fr SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
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
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Fff.fr can be misinterpreted by Google and other search engines. Our service has detected that French 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 Fff.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.
fff.fr
Open Graph description is not detected on the main page of Fff. 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: