5.4 sec in total
326 ms
4.8 sec
272 ms
Visit l3fr.org now to see the best up-to-date L3FR content and also check out these interesting facts you probably never knew about l3fr.org
Généalogie
Visit l3fr.orgWe analyzed L3fr.org page load time and found that the first response time was 326 ms and then it took 5 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
l3fr.org performance score
name
value
score
weighting
Value2.0 s
83/100
10%
Value3.4 s
66/100
25%
Value3.6 s
86/100
10%
Value280 ms
81/100
30%
Value0.118
85/100
15%
Value3.2 s
94/100
10%
326 ms
564 ms
202 ms
393 ms
212 ms
Our browser made a total of 71 requests to load all elements on the main page. We found that 99% of them (70 requests) were addressed to the original L3fr.org, 1% (1 request) were made to Appelgenealogielibre.free.fr. The less responsive or slowest element that took the longest time to load (2.1 sec) belongs to the original domain L3fr.org.
Page size can be reduced by 130.7 kB (29%)
446.8 kB
316.1 kB
In fact, the total size of L3fr.org main page is 446.8 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. 20% of websites need less resources to load. Images take 358.5 kB which makes up the majority of the site volume.
Potential reduce by 36.3 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 36.3 kB or 80% of the original size.
Potential reduce by 59.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. Obviously, L3FR needs image optimization as it can save up to 59.3 kB or 17% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 24.3 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 24.3 kB or 82% of the original size.
Potential reduce by 10.8 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. L3fr.org needs all CSS files to be minified and compressed as it can save up to 10.8 kB or 81% of the original size.
Number of requests can be reduced by 40 (58%)
69
29
The browser has sent 69 CSS, Javascripts, AJAX and image requests in order to completely render the main page of L3FR. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 4 to 1 for JavaScripts and as a result speed up the page load time.
l3fr.org
326 ms
forum.php
564 ms
e107.js
202 ms
sleight_js.php
393 ms
style.css
212 ms
nav_menu_alt.js
213 ms
clock.js
212 ms
genealogielibre.png
255 ms
s_nav.png
186 ms
s_left_cap.png
336 ms
bullet2.gif
338 ms
postedby_16.png
328 ms
bar.jpg
340 ms
s_left_bevel_.png
336 ms
Europcar_navigation_bg.gif
498 ms
button3dBlue.gif
567 ms
arrow.png
570 ms
pgBandeauGauche.gif
570 ms
polls.png
568 ms
print_16.png
572 ms
pgBandeauRemplir.gif
700 ms
email_16.png
770 ms
s_main_cap.png
774 ms
s_body_.png
777 ms
pgButtonGrey.gif
779 ms
forumheader.gif
792 ms
button3dGreyA.gif
984 ms
blank.gif
993 ms
pgBandeauDroite.gif
989 ms
Europcar_nav_separator.gif
1060 ms
button.png
989 ms
s_left_cap_.png
998 ms
buttonover.png
1197 ms
comments_16.png
1197 ms
s_body.png
1198 ms
s_main_cap_.png
1224 ms
button%202009-10-02.png
1222 ms
s_nav_.png
1262 ms
pgBandeauPetitDroite.gif
1456 ms
button3dGrey.gif
1462 ms
button3dWhite.gif
1428 ms
pgBandeauPetitGauche.gif
1454 ms
button3dGreyB.gif
1459 ms
pgTextBandeau.gif
1461 ms
s_left_bevel.png
1526 ms
l3fr_00001.png
2077 ms
fleche003.png
1467 ms
logocrl.gif
1454 ms
mozilla.gif
1370 ms
archivespubliqueslibres.jpg
1375 ms
openoffice.jpg
1450 ms
framasoft.jpg
1359 ms
nonew.png
1349 ms
post2.png
1441 ms
e.png
1462 ms
new_small.png
1566 ms
nonew_small.png
1433 ms
closed_small.png
1385 ms
button_passe_oublie.gif
1513 ms
bouton_inscription.gif
1574 ms
republicain_lorrain.jpg
1587 ms
am_metz.jpg
1562 ms
lorraine_centenaire14_18.jpg
1378 ms
mission_centenaire.jpg
1506 ms
memoire_des_hommes.jpg
1574 ms
logo_gallica.png
1569 ms
eluxemburgensia.jpg
1575 ms
kiosque_lorrain.jpg
1588 ms
windows-10-lead.jpg
1422 ms
drapeau_France.jpg
1497 ms
europe.jpg
1579 ms
l3fr.org 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.
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
Image elements do not have [alt] attributes
Form elements do not have associated labels
Links do not have a discernible name
l3fr.org best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
Serves images with low resolution
l3fr.org 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
FR
FR
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise L3fr.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 L3fr.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.
l3fr.org
Open Graph description is not detected on the main page of L3FR. 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: