4.7 sec in total
1.1 sec
3.4 sec
188 ms
Visit afev.org now to see the best up-to-date Afev content for France and also check out these interesting facts you probably never knew about afev.org
L'association Afev accompagne les lycéens et étudiants qui souhaitent s'engager dans la lutte contre les inégalités scolaires et sociales !
Visit afev.orgWe analyzed Afev.org page load time and found that the first response time was 1.1 sec and then it took 3.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
afev.org performance score
name
value
score
weighting
Value4.7 s
12/100
10%
Value6.5 s
9/100
25%
Value5.7 s
51/100
10%
Value1,240 ms
19/100
30%
Value0.113
86/100
15%
Value8.9 s
34/100
10%
1088 ms
21 ms
322 ms
222 ms
364 ms
Our browser made a total of 55 requests to load all elements on the main page. We found that 82% of them (45 requests) were addressed to the original Afev.org, 7% (4 requests) were made to Fonts.gstatic.com and 4% (2 requests) were made to Maxcdn.bootstrapcdn.com. The less responsive or slowest element that took the longest time to load (1.6 sec) belongs to the original domain Afev.org.
Page size can be reduced by 299.7 kB (43%)
697.9 kB
398.2 kB
In fact, the total size of Afev.org main page is 697.9 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. 30% of websites need less resources to load. Images take 316.2 kB which makes up the majority of the site volume.
Potential reduce by 31.6 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 31.6 kB or 82% of the original size.
Potential reduce by 8.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. Afev images are well optimized though.
Potential reduce by 45.4 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 45.4 kB or 74% of the original size.
Potential reduce by 214.7 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. Afev.org needs all CSS files to be minified and compressed as it can save up to 214.7 kB or 76% of the original size.
Number of requests can be reduced by 20 (41%)
49
29
The browser has sent 49 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Afev. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 9 to 1 for JavaScripts and from 13 to 1 for CSS and as a result speed up the page load time.
afev.org
1088 ms
bootstrap.min.css
21 ms
wp-emoji-release.min.js
322 ms
advanced-responsive-video-embedder-public.css
222 ms
dashicons.min.css
364 ms
style.css
297 ms
juiz_last_tweet.css
175 ms
chosen.css
294 ms
frontend.css
459 ms
style.css
519 ms
style-map.css
466 ms
style-newsletter.css
469 ms
style-paypal.css
499 ms
thickbox.css
554 ms
jquery-latest.min.js
11 ms
script-map.js
626 ms
jquery.maphilight.min.js
776 ms
script-newsletter.js
639 ms
script-paypal.js
666 ms
script.js
816 ms
public.min.js
823 ms
thickbox.js
923 ms
css
24 ms
x60-DF6.jpg
64 ms
x60-uJ-.jpg
64 ms
Logo_Afev_site_corporate.jpg
527 ms
facebook.png
429 ms
twitter.png
536 ms
dailymotion.png
581 ms
newsletter.png
579 ms
presse.png
675 ms
flags.jpg
707 ms
alarm.png
699 ms
Benevolat.jpg
1366 ms
engager1.png
867 ms
engager2.png
870 ms
engager3.png
966 ms
nosactions1.png
994 ms
nosactions2.png
995 ms
nosactions3.png
1158 ms
nosactions4.png
1161 ms
partenaire1.png
1219 ms
partenaire2.png
1285 ms
partenaire3.png
1244 ms
engager4.png
1433 ms
nosactions5.png
1434 ms
facebook_32.png
1456 ms
twitter.png
1512 ms
dailymotion_32.png
1568 ms
kpI87QY2ce-mk2ZnKb-r0g.ttf
24 ms
TttUCfJ272GBgSKaOaD7KqCWcynf_cDxXwCLxiixG1c.ttf
23 ms
y7lebkjgREBJK96VQi37Zp0EAVxt0G0biEntp43Qt6E.ttf
24 ms
dazS1PrQQuCxC3iOAJFEJZ_TkvowlIOtbR7ePgFOpF4.ttf
24 ms
glyphicons-halflings-regular.woff
3 ms
loadingAnimation.gif
1317 ms
afev.org accessibility score
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
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
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
List items (<li>) are not contained within <ul> or <ol> parent elements.
afev.org 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
Page has valid source maps
afev.org SEO score
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 Afev.org 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 Afev.org 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.
afev.org
Open Graph data is detected on the main page of PARSED_DOMAIN, but there is no image specified in description. It would be a good idea for the website admin to select a nice image that can properly represent the website in Open Graph data, otherwise the first found image will be taken for this purpose and social media information block will look like this: