4.2 sec in total
360 ms
3.5 sec
341 ms
Click here to check amazing FFE content for France. Otherwise, check out these important facts you probably never knew about ffe.com
Site officiel de la Fédération Française d'Équitation (FFE). Première activité sportive et de loisir proche de la nature.
Visit ffe.comWe analyzed Ffe.com page load time and found that the first response time was 360 ms and then it took 3.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
ffe.com performance score
name
value
score
weighting
Value15.8 s
0/100
10%
Value47.4 s
0/100
25%
Value30.4 s
0/100
10%
Value5,390 ms
0/100
30%
Value0.141
78/100
15%
Value48.1 s
0/100
10%
360 ms
430 ms
144 ms
275 ms
279 ms
Our browser made a total of 74 requests to load all elements on the main page. We found that 51% of them (38 requests) were addressed to the original Ffe.com, 9% (7 requests) were made to Platform.twitter.com and 9% (7 requests) were made to Static1.dmcdn.net. The less responsive or slowest element that took the longest time to load (1.9 sec) belongs to the original domain Ffe.com.
Page size can be reduced by 1.1 MB (31%)
3.6 MB
2.5 MB
In fact, the total size of Ffe.com main page is 3.6 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. Images take 2.2 MB which makes up the majority of the site volume.
Potential reduce by 46.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. This page needs HTML code to be minified as it can gain 12.3 kB, which is 21% 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 46.5 kB or 79% of the original size.
Potential reduce by 63.2 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. FFE images are well optimized though.
Potential reduce by 786.1 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 786.1 kB or 72% of the original size.
Potential reduce by 213.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. Ffe.com needs all CSS files to be minified and compressed as it can save up to 213.0 kB or 70% of the original size.
Number of requests can be reduced by 23 (34%)
68
45
The browser has sent 68 CSS, Javascripts, AJAX and image requests in order to completely render the main page of FFE. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 14 to 1 for JavaScripts and from 11 to 1 for CSS and as a result speed up the page load time.
ffe.com
360 ms
www.ffe.com
430 ms
css_screen.css
144 ms
websitetoolbar.css
275 ms
supersized.core.css
279 ms
theme-options.css
281 ms
survey.css
283 ms
libs.js
563 ms
cookiechoices.js
292 ms
sprite.png
419 ms
Debuter-l-equitation.jpg
290 ms
Frederic-David-3eme-du-Grand-Prix-CSI-5-d-Al-Rayyan-au-Qatar_tiers.jpg
406 ms
BORDEAUX-VACILLE-A-SAUMUR_tiers.jpg
321 ms
Au-Salon-international-de-l-agriculture-2016-le-poney-pour-tous_tiers.jpg
418 ms
SalonAgriculture2016.jpg
290 ms
encart-pub-LETTRE-FED-V2.jpg
847 ms
Acceder-Ressouces.jpg
1156 ms
encart-pub-poney-ecole.jpg
1427 ms
Generali-Assurances_tiers.png
576 ms
Point-P_small.gif
576 ms
PADD_small.gif
597 ms
EKKIA_small.gif
680 ms
Equiphorse_small.jpg
697 ms
Equistro_small.png
704 ms
GPA_small.png
811 ms
RMC_small.jpg
840 ms
Cheval-Nature-2016_deuxtiers.jpg
830 ms
Poney-Ecole_deuxtiers.jpg
1210 ms
Manuels-Galops-1-2_deuxtiers.jpg
1138 ms
Grand-National-CCE-Saumur_deuxtiers.jpg
969 ms
jukebox
300 ms
bouton_merialTV.png
964 ms
sdk.js
65 ms
widgets.js
98 ms
ga.js
10 ms
__utm.gif
26 ms
loadingAnimation.gif
1064 ms
Accueil.jpg
1879 ms
progress.gif
1167 ms
Jeux-Olympiques-Rio-2016_large.jpg
1176 ms
Amateur-Gold-Tour_large.jpg
1182 ms
73 ms
xd_arbiter.php
87 ms
xd_arbiter.php
82 ms
button.831500944bc3eb7ea5276ccdc3f71d2e.js
122 ms
timeline.1b43d11859b7663a2225b885f87704a5.js
148 ms
follow_button.6a78875565a912489e9aef879c881358.fr.html
44 ms
syndication
85 ms
494751597910429696
95 ms
jukebox.ltr.css.v31d9112f094ad6a89
103 ms
jukebox.js.v20d67366952fb8eb9
148 ms
all.js
144 ms
timeline.4d087f49a21e27038d9769d7c976b8fa.default.css
51 ms
timeline.4d087f49a21e27038d9769d7c976b8fa.default.css
164 ms
play.png.v11b2fefa92a0dc9b
137 ms
6q4w-Orw_normal.jpg
53 ms
embed
239 ms
928Jt8nM+GtmeigpYjhicsSU3xYvfKkAAAAAAVTl7msAAA==
18 ms
dvCbfJzPhrZnooKWI4YnLElN8WL3ypAAAAAAFU5e5vAAA=
18 ms
bjY8U5o5EzQBa8kFGMXJi63ckLWDRl76RW5JRfynJxbkPc5icjLhhIfmomyAz+XXQDjoPeiT0LbjRwFR3aNNymnkooNTSVPP6P03000kzRfmgur2cyCvNf7A5hf+W4AAAA=
17 ms
140x78-r3P.jpg
57 ms
140x78-b-d.jpg
134 ms
140x78-Bcv.jpg
58 ms
main.1f73167e52.css
28 ms
jquery.min.js
31 ms
playerv5-embed.js.v5b530410decb4d5f9
30 ms
dmp.831b5175769a4af67631.js
49 ms
css
65 ms
abaf7bb7ec529d2db26c.dmp.js
76 ms
cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf
25 ms
jot.html
26 ms
pebed.dm.gg
288 ms
Grand-National_large.jpg
187 ms
css_print.css
142 ms
ffe.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
button, link, and menuitem elements do not have accessible names.
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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
List items (<li>) are not contained within <ul> or <ol> parent elements.
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.
ffe.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Requests the geolocation permission on page load
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
ffe.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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 Ffe.com 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 Ffe.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.
ffe.com
Open Graph description is not detected on the main page of FFE. 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: