12.2 sec in total
4.3 sec
7.7 sec
252 ms
Click here to check amazing FFTRI content for France. Otherwise, check out these important facts you probably never knew about fftri.com
Site officiel de la Fédération Française de Triathlon (FFTRI).
Visit fftri.comWe analyzed Fftri.com page load time and found that the first response time was 4.3 sec and then it took 7.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
fftri.com performance score
name
value
score
weighting
Value6.7 s
2/100
10%
Value10.1 s
0/100
25%
Value59.6 s
0/100
10%
Value86,220 ms
0/100
30%
Value1.777
0/100
15%
Value129.5 s
0/100
10%
4327 ms
159 ms
160 ms
164 ms
166 ms
Our browser made a total of 290 requests to load all elements on the main page. We found that 36% of them (105 requests) were addressed to the original Fftri.com, 8% (23 requests) were made to Pbs.twimg.com and 8% (23 requests) were made to Ads.contextweb.com. The less responsive or slowest element that took the longest time to load (4.3 sec) belongs to the original domain Fftri.com.
Page size can be reduced by 971.0 kB (36%)
2.7 MB
1.7 MB
In fact, the total size of Fftri.com main page is 2.7 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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 1.5 MB which makes up the majority of the site volume.
Potential reduce by 83.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. This page needs HTML code to be minified as it can gain 45.1 kB, which is 48% 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 83.4 kB or 88% of the original size.
Potential reduce by 52.8 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. FFTRI images are well optimized though.
Potential reduce by 640.5 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 640.5 kB or 73% of the original size.
Potential reduce by 194.3 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. Fftri.com needs all CSS files to be minified and compressed as it can save up to 194.3 kB or 85% of the original size.
Number of requests can be reduced by 179 (66%)
272
93
The browser has sent 272 CSS, Javascripts, AJAX and image requests in order to completely render the main page of FFTRI. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 90 to 1 for JavaScripts and from 18 to 1 for CSS and as a result speed up the page load time.
fftri.com
4327 ms
linr.css
159 ms
system.css
160 ms
calendar.css
164 ms
epreuves-ria.css
166 ms
reset-min.css
173 ms
reset-fonts-grids.css
175 ms
style.css
243 ms
home-style.css
238 ms
template02-style.css
249 ms
performance-style.css
250 ms
centre-media.css
259 ms
championnat.css
260 ms
jquery-ui-1.8.11.custom.css
317 ms
search.css
325 ms
lionbars.css
326 ms
propal.css
327 ms
jquery.js
431 ms
drupal.js
347 ms
fr_c9df50c9b6cad66b053812592a7af21e.js
396 ms
jquery.js
501 ms
jquery.timelinr-0.9.5.js
406 ms
application.js
408 ms
swfobject.js
448 ms
fftri_epreuves_views.js
474 ms
fftri_epreuves_application.js
486 ms
json2.js
491 ms
ICanHaz.min.js
517 ms
ba-debug.min.js
519 ms
jquery-ui-1.8.11.custom.min.js
723 ms
jquery-thenewbrain.js
568 ms
quickpager.jquery.js
572 ms
slides.jquery.js
584 ms
firefox-swf-fix.js
602 ms
jquery.jgfeed-min.js
605 ms
dateFormat.js
648 ms
jquery.jtwitter.js
589 ms
underscore-min.js
516 ms
backbone-min.js
537 ms
soma-v1.0.1.min.js
537 ms
jquery.lionbars.0.3.js
587 ms
swfaddress-min.js
582 ms
fftri.js
585 ms
fftri-home.js
546 ms
fftri-mediacenter.js
540 ms
fftri-template02.js
558 ms
fftri-championships.js
570 ms
fftri-performance.js
566 ms
ga.js
32 ms
NICE130929_192A.jpg
251 ms
logo-fftri.gif
81 ms
facebook.png
88 ms
twit.png
83 ms
blocsearch.png
88 ms
loupe.png
83 ms
fond-club-a-fftri.jpg
159 ms
IMG_1846.JPG
406 ms
12742578_869032496528363_5297441003414232019_n.jpg
407 ms
partnership-526413_960_720.jpg
259 ms
150606-121329-1288-1DX.jpg
346 ms
bouton-flash-player.jpg
241 ms
logo-footer-ministeresport.jpg
317 ms
logoarc-150px.jpg
338 ms
logo-footer-adidas-150px.jpg
345 ms
logo-footer-isostar-150px.jpg
397 ms
logo-footer-mavic-150px.png
416 ms
logo-footer-lepape-150px.png
431 ms
santesportmag.png
431 ms
logo-footer-triathletemag.jpg
475 ms
logo-footer-rmc.jpg
493 ms
header-accueil.jpg
484 ms
header-degrade-roll.gif
495 ms
header-news.jpg
508 ms
header-clubfftri.jpg
509 ms
header-tripourtous.jpg
544 ms
header-reglementation.jpg
562 ms
header-evenements.jpg
563 ms
header-performance.jpg
590 ms
header-centremedia.jpg
605 ms
header-partenaire.jpg
605 ms
arrondi-header-gauche.png
622 ms
arrondi-header-droite.png
647 ms
207 ms
__utm.gif
24 ms
Cassandre%20Beaugrand.jpg
433 ms
arrondi-header-gauche-haut.png
441 ms
arrondi-header-droite-haut.png
465 ms
header-resultats-home.gif
466 ms
loop-picto.png
486 ms
footer-resultat-home.gif
513 ms
widgets.js
83 ms
header-site-partenaire.gif
508 ms
footer-evenement-approche.gif
516 ms
bouton-partager-triathlon.jpg
544 ms
100 ms
bouton-en-savoir-plus-triathlon.png
541 ms
bouton-licencier-triathlon.png
545 ms
fond-pub.png
567 ms
show5.asp
96 ms
bouton-video-home.gif
391 ms
bouton-photo-home.gif
397 ms
footer-player-video-home.gif
430 ms
arrow-player-left.png
431 ms
arrow-player-right.png
437 ms
encart-all-videos.gif
473 ms
bouton-play-player.png
472 ms
jsinfo.asp
85 ms
timeline.1b43d11859b7663a2225b885f87704a5.js
127 ms
logo-footer-new.png
470 ms
bouton-valider-recherche.gif
520 ms
bouton-facebook.gif
520 ms
adi
94 ms
bouton-twitter.gif
480 ms
bouton-rss.gif
547 ms
js
60 ms
pixel
21 ms
pixel
34 ms
match
19 ms
syndication
119 ms
378168958072791041
315 ms
match
15 ms
match
15 ms
match
17 ms
getjs.aspx
43 ms
match
16 ms
xrefid.xgi
15 ms
getjs.static.js
27 ms
GetAd.aspx
21 ms
getjs.aspx
15 ms
400066.gif
9 ms
GetAd.aspx
20 ms
getjs.aspx
14 ms
GetAd.aspx
19 ms
getjs.aspx
15 ms
GetAd.aspx
21 ms
getjs.aspx
15 ms
GetAd.aspx
20 ms
getjs.aspx
15 ms
GetAd.aspx
22 ms
match
5 ms
getjs.aspx
15 ms
GetAd.aspx
23 ms
timeline.4d087f49a21e27038d9769d7c976b8fa.default.css
30 ms
timeline.4d087f49a21e27038d9769d7c976b8fa.default.css
90 ms
getjs.aspx
12 ms
GetAd.aspx
34 ms
HbLg9A9p_normal.jpg
99 ms
Ec6WEkIV_normal.jpeg
98 ms
LIU07oY3_normal.jpg
136 ms
lTU4qgEz_normal.jpg
100 ms
a5011c442c75e6501252e9cad18676ac_normal.png
97 ms
dWbaCvz7_normal.jpeg
155 ms
xGgO0cs5_normal.png
99 ms
5UHbum3w_normal.jpg
99 ms
D7_u44ib_normal.jpg
103 ms
ni9fo61K_normal.jpg
102 ms
uSdPd7Tz_normal.jpg
100 ms
CcYJHuIXEAEgYX-.jpg:small
106 ms
CcElxvyWwAAeyrT.jpg:small
107 ms
Cb-3h5-WwAAR1j2.jpg:small
107 ms
Cb-GKNsWwAIUN0N.jpg:small
109 ms
Cb6eMETW8AE_Ebg.jpg:small
110 ms
Cb6AnTpWIAAOBvm.jpg:small
110 ms
Cb0KnLIWIAEf7eG.jpg:small
113 ms
Cb0D3hRW0AAHHYx.jpg:small
151 ms
CbvoJGGXIAEmXTI.jpg:small
135 ms
Cbwbm_uW8AUY2yM.jpg:small
131 ms
CbviJ4GWEAAgToa.jpg:small
116 ms
CbqqmTYWAAAc8jE.jpg:small
165 ms
getjs.aspx
64 ms
GetAd.aspx
42 ms
getjs.aspx
14 ms
GetAd.aspx
24 ms
getjs.aspx
15 ms
GetAd.aspx
24 ms
getjs.aspx
13 ms
GetAd.aspx
22 ms
getjs.aspx
14 ms
GetAd.aspx
22 ms
jot
26 ms
getjs.aspx
13 ms
GetAd.aspx
21 ms
getjs.aspx
14 ms
GetAd.aspx
22 ms
getjs.aspx
13 ms
GetAd.aspx
21 ms
getjs.aspx
14 ms
GetAd.aspx
17 ms
getjs.aspx
13 ms
GetAd.aspx
17 ms
getjs.aspx
15 ms
GetAd.aspx
16 ms
getjs.aspx
17 ms
GetAd.aspx
15 ms
getjs.aspx
15 ms
GetAd.aspx
15 ms
getjs.aspx
14 ms
GetAd.aspx
16 ms
300x250.html
41 ms
p-01-0VIaSjnOLg.gif
23 ms
visitormatch
22 ms
visitormatch
22 ms
visitormatch
31 ms
id.js
40 ms
cookiematch
7 ms
contextweb
17 ms
pp
77 ms
aceUAC.js
5 ms
pixel.htm
67 ms
dref=http%253A%252F%252Fad.360yield.com%252Ful_cb%252Fadi%253Fp%253D61413%2526w%253D300%2526h%253D250%2526tz%253D-180%2526click3rd%253D
30 ms
cw
20 ms
rtset
25 ms
contextweb
15 ms
contextmatch.php
26 ms
rtset
53 ms
dref=http%253A%252F%252Fad.360yield.com%252Ful_cb%252Fadi%253Fp%253D61413%2526w%253D300%2526h%253D250%2526tz%253D-180%2526click3rd%253D
40 ms
rtset
43 ms
cw_match
34 ms
context_sync
106 ms
ddc.htm
50 ms
rtset
55 ms
rtset
233 ms
CSG_TWW_MKT_20080513_01%20_photo_300x250.jpg
67 ms
moatad.js
69 ms
ecw
84 ms
cse
308 ms
pull_sync
82 ms
Pug
330 ms
pixel
99 ms
u.php
294 ms
245 ms
g.js
90 ms
7953210652398106471
150 ms
4499
147 ms
7953210652398106471
265 ms
pixel
131 ms
rtset
131 ms
7953210652398106471
245 ms
rtset
147 ms
rtset
149 ms
pixel
171 ms
n.js
145 ms
ecc
131 ms
sync
107 ms
xrefid.xgi
88 ms
mapuser
76 ms
merge
77 ms
92 ms
bd
141 ms
pixel.gif
151 ms
rum
93 ms
contextweb
93 ms
128 ms
match
145 ms
145 ms
bd
140 ms
127 ms
126c56d4-d245-4700-93e2-a059171dc249
143 ms
-8170206059683546334
138 ms
rtset
127 ms
NAX8752956450245272272
131 ms
cpush
125 ms
rtset
120 ms
rtset
119 ms
appnexus
114 ms
rtset
122 ms
rtset
117 ms
adsct
232 ms
0ad47b31-df3b-11e5-a88a-005056a27a0c
125 ms
cs
113 ms
lr.gif
123 ms
demconf.jpg
76 ms
appnexus
96 ms
usersync.yashi.com
116 ms
sd
126 ms
rtset
91 ms
blank.gif
70 ms
sync
86 ms
demconf.jpg
74 ms
cs.ashx
82 ms
ck-confirm
81 ms
match
66 ms
rtset
48 ms
pixel
46 ms
rtset
32 ms
beacon.js
19 ms
rtset
31 ms
TA0adabd52-df3b-11e5-8215-00163e219845
26 ms
tap.php
390 ms
Pug
19 ms
fftri.com accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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 IDs are not unique
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
Image elements do not have [alt] attributes
Links do not have a discernible name
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.
fftri.com 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
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
fftri.com 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
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 Fftri.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 Fftri.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.
fftri.com
Open Graph description is not detected on the main page of FFTRI. 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: