8.6 sec in total
3.2 sec
5.1 sec
342 ms
Visit athle.com now to see the best up-to-date Athle content for France and also check out these interesting facts you probably never knew about athle.com
Fédération Française d'Athlétisme
Visit athle.comWe analyzed Athle.com page load time and found that the first response time was 3.2 sec 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.
athle.com performance score
name
value
score
weighting
Value4.9 s
10/100
10%
Value8.1 s
2/100
25%
Value7.3 s
29/100
10%
Value180 ms
91/100
30%
Value0.056
98/100
15%
Value10.7 s
23/100
10%
3205 ms
728 ms
8 ms
333 ms
167 ms
Our browser made a total of 72 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Athle.com, 93% (67 requests) were made to Athle.fr and 3% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (3.2 sec) belongs to the original domain Athle.com.
Page size can be reduced by 308.7 kB (31%)
995.7 kB
687.0 kB
In fact, the total size of Athle.com main page is 995.7 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. 35% of websites need less resources to load. Images take 633.9 kB which makes up the majority of the site volume.
Potential reduce by 25.8 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 3.5 kB, which is 11% 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 25.8 kB or 80% of the original size.
Potential reduce by 47.0 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. Athle images are well optimized though.
Potential reduce by 204.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 204.8 kB or 70% of the original size.
Potential reduce by 31.1 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. Athle.com needs all CSS files to be minified and compressed as it can save up to 31.1 kB or 84% of the original size.
Number of requests can be reduced by 18 (29%)
62
44
The browser has sent 62 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Athle. 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 9 to 1 for CSS and as a result speed up the page load time.
athle.com
3205 ms
index.aspx
728 ms
analytics.js
8 ms
suggest.js.php
333 ms
main.js
167 ms
frontend.smenus.js
170 ms
main.js
170 ms
jquery-1.11.1.min.js
334 ms
jquery.nivo.slider.js
221 ms
jquery.fancybox.pack.js
280 ms
jquery.fancybox-media.js
277 ms
jquery-ffa.js
280 ms
jquery.fancybox.css
281 ms
main.css
302 ms
fonts.css
363 ms
main.css
363 ms
css.aspx
530 ms
jquery.simplyscroll.js
364 ms
jquery_simplyscroll.css
386 ms
nivo-slider-home.css
414 ms
nivo-slider-default.css
446 ms
home.css
447 ms
collect
13 ms
background.portail.jpg
339 ms
background.wrapper.png
89 ms
medaillon.portail.png
90 ms
medaillon.sante.png
87 ms
medaillon.evenements.png
93 ms
medaillon.jeunesse.png
93 ms
medaillon.performance.png
171 ms
medaillon.federation.png
175 ms
medaillon.clubs.png
173 ms
logo.ffa.png
176 ms
logo.athle.png
177 ms
shop.gif
254 ms
social.png
256 ms
menuseparator.gif
256 ms
titre_alaune.png
258 ms
13288_big.jpg
257 ms
13290_big.jpg
380 ms
titre_evenement.png
340 ms
lemans2016.jpg
342 ms
aubiere2016.jpg
422 ms
titre_jaimecourir.png
343 ms
jaimecourir.png
420 ms
titre_performance.png
420 ms
titre_jeunesse.png
422 ms
13092_small.jpg
424 ms
titre_federation.png
461 ms
titre_sante.png
508 ms
13114_small.jpg
509 ms
titre_trouverSmall.png
509 ms
carteSmall.png
509 ms
titre_filacces.png
514 ms
logo.asics.png
544 ms
logo.ministere.png
592 ms
logo.iaaf.png
593 ms
logo.eaa.png
595 ms
logo.ffa.png
537 ms
proximanova-regular-webfont.woff
518 ms
faktslabconpro-light-webfont.woff
556 ms
faktslabconpro-semibold-webfont.woff
594 ms
proximanova-light-webfont.woff
598 ms
faktslabpro-semibold-webfont.woff
598 ms
proximanova-bold-webfont.woff
527 ms
faktslabconpro-bold-webfont.woff
527 ms
faktslabconpro-normal-webfont.woff
556 ms
traitInfoVert.png
592 ms
320x240-HPz.jpg
87 ms
loading.gif
594 ms
trait.png
518 ms
traitInfo.png
517 ms
athle.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.
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
<input type="image"> elements do not have [alt] text
Form elements do not have associated labels
Links do not have a discernible name
athle.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
athle.com 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
FR
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Athle.com 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 Athle.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.
athle.com
Open Graph description is not detected on the main page of Athle. 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: