5.6 sec in total
730 ms
4.3 sec
565 ms
Click here to check amazing AJ A content for France. Otherwise, check out these important facts you probably never knew about aja.fr
Actus, matchs, classements, vidéos... retrouvez toute l'actualité de l'AJ Auxerre sur notre site officiel.
Visit aja.frWe analyzed Aja.fr page load time and found that the first response time was 730 ms and then it took 4.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
aja.fr performance score
name
value
score
weighting
Value5.4 s
6/100
10%
Value10.3 s
0/100
25%
Value10.2 s
8/100
10%
Value1,440 ms
15/100
30%
Value0.195
63/100
15%
Value10.9 s
21/100
10%
730 ms
165 ms
417 ms
754 ms
338 ms
Our browser made a total of 92 requests to load all elements on the main page. We found that 54% of them (50 requests) were addressed to the original Aja.fr, 7% (6 requests) were made to Idsync.rlcdn.com and 5% (5 requests) were made to Tag.leadplace.fr. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain Aja.fr.
Page size can be reduced by 1.4 MB (43%)
3.3 MB
1.9 MB
In fact, the total size of Aja.fr main page is 3.3 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. 70% of websites need less resources to load. Images take 1.5 MB which makes up the majority of the site volume.
Potential reduce by 39.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 5.4 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 39.5 kB or 79% of the original size.
Potential reduce by 94.3 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. AJ A images are well optimized though.
Potential reduce by 1.0 MB
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 1.0 MB or 73% of the original size.
Potential reduce by 254.6 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. Aja.fr needs all CSS files to be minified and compressed as it can save up to 254.6 kB or 83% of the original size.
Number of requests can be reduced by 53 (62%)
85
32
The browser has sent 85 CSS, Javascripts, AJAX and image requests in order to completely render the main page of AJ A. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 28 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
aja.fr
730 ms
Site.css
165 ms
jquery-ui-1.8.18.custom.css
417 ms
jquery-1.7.1.min.js
754 ms
modernizr-1.7.min.js
338 ms
jquery-ui-1.8.11.min.js
745 ms
jquery.unobtrusive-ajax.js
312 ms
jquery.validate.js
410 ms
jquery.validate.unobtrusive.js
474 ms
fckeditor.js
417 ms
jquery-ui-timepicker-addon.js
560 ms
jquery.limit-1.2.source.js
476 ms
grid.css
482 ms
mainPage.css
537 ms
menuCSS.css
541 ms
fond.jpg
353 ms
logo.png
173 ms
spinLoader_white.gif
175 ms
IMG_2027.JPG
354 ms
bullet-toggle-minus-icon.png
174 ms
WILLY%20BOLY%20Copie%20de%20IMG_1538.jpg
175 ms
IMG_8667%20(300x225).jpg
178 ms
cotret_4.JPG
248 ms
Auxerre.png
182 ms
Dijon.png
182 ms
jeReserve.png
245 ms
jeReserveGradin.png
255 ms
nouvelles48x48.png
253 ms
Trophy-bronze-icon30x30.png
344 ms
agenda48x48.png
344 ms
twitter.png
346 ms
facebook.png
347 ms
airness.png
392 ms
boutique.jpg
576 ms
F58D5056.JPG
575 ms
F58D4998.JPG
974 ms
F58D4756.JPG
574 ms
F58D4755.JPG
1208 ms
F58D4745.JPG
566 ms
F58D4738.JPG
591 ms
Sponsors.jpg
1049 ms
js
187 ms
ga.js
51 ms
__utm.gif
43 ms
library-1.47.3.js
100 ms
amzn_ads.js
49 ms
bid
82 ms
controltag
101 ms
megatag.js
149 ms
libJsLP.js
531 ms
headerMenu-separator.png
401 ms
articles-separator.png
402 ms
btnArticle-separator.png
401 ms
menuMiddleBar-separator.png
479 ms
middleBar-separator.png
483 ms
fondTabNews.png
481 ms
400466.html
86 ms
sWLSbZCjS6g
558 ms
pixel
323 ms
304 ms
activity;src=1901398;type=lrmp;cat=dmp02;u2=041b912bea1d2c64879d552195073df8502ada412cac047801f1999542bb39d8a6704fcfe29d7ba7
303 ms
iframe_api
303 ms
controltag.js.f8e94fa978cc2569e4b4423df4245d7e
98 ms
footerHeader.png
210 ms
xrefid.xgi
82 ms
blank.gif
79 ms
pixel
82 ms
378348.gif
88 ms
ui-bg_inset-hard_100_fcfdfd_1x100.png
165 ms
ui-icons_469bdd_256x240.png
165 ms
px
127 ms
362248.gif
115 ms
www-widgetapi.js
147 ms
wckr.php
164 ms
cookie2json
110 ms
52154.gif
74 ms
www-embed-player-vflRGs1ko.css
175 ms
www-embed-player.js
269 ms
base.js
365 ms
362358.gif
76 ms
47154.gif
54 ms
mtj
64 ms
362708.gif
50 ms
wappad.php
829 ms
wappbk.php
664 ms
Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js
187 ms
ad_status.js
195 ms
wappweb.php
566 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
391 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
409 ms
optout_check
578 ms
get
577 ms
aja.fr 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.
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
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.
aja.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
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
aja.fr SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
FR
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Aja.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 Aja.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.
aja.fr
Open Graph description is not detected on the main page of AJ A. 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: