3.5 sec in total
172 ms
2.8 sec
546 ms
Welcome to lnr.fr homepage info - get ready to check LNR best content for France right away, or after learning these important things about lnr.fr
La Ligue Nationale de Rugby fait peau neuve ! Découvrez le nouveau site de la LNR
Visit lnr.frWe analyzed Lnr.fr page load time and found that the first response time was 172 ms and then it took 3.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
lnr.fr performance score
name
value
score
weighting
Value4.8 s
11/100
10%
Value9.0 s
1/100
25%
Value8.2 s
20/100
10%
Value3,260 ms
2/100
30%
Value0.168
71/100
15%
Value14.9 s
8/100
10%
172 ms
270 ms
168 ms
163 ms
174 ms
Our browser made a total of 147 requests to load all elements on the main page. We found that 95% of them (139 requests) were addressed to the original Lnr.fr, 1% (2 requests) were made to Google-analytics.com and 1% (1 request) were made to Ajax.googleapis.com. The less responsive or slowest element that took the longest time to load (686 ms) belongs to the original domain Lnr.fr.
Page size can be reduced by 1.2 MB (64%)
1.9 MB
676.0 kB
In fact, the total size of Lnr.fr main page is 1.9 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. 60% of websites need less resources to load. Images take 560.7 kB which makes up the majority of the site volume.
Potential reduce by 265.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 79.2 kB, which is 28% 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 265.8 kB or 93% of the original size.
Potential reduce by 94.2 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, LNR needs image optimization as it can save up to 94.2 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 367.0 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 367.0 kB or 74% of the original size.
Potential reduce by 470.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. Lnr.fr needs all CSS files to be minified and compressed as it can save up to 470.3 kB or 89% of the original size.
Number of requests can be reduced by 39 (28%)
141
102
The browser has sent 141 CSS, Javascripts, AJAX and image requests in order to completely render the main page of LNR. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 31 to 1 for JavaScripts and from 10 to 1 for CSS and as a result speed up the page load time.
lnr.fr
172 ms
www.lnr.fr
270 ms
system.base.css
168 ms
date.css
163 ms
datepicker.1.7.css
174 ms
field.css
175 ms
views.css
175 ms
ctools.css
175 ms
eu_cookie_compliance.css
240 ms
normalize.css
251 ms
jquery.smartbanner.css
257 ms
lnr.css
516 ms
jquery.min.js
31 ms
jquery.once.js
258 ms
drupal.js
259 ms
admin_devel.js
316 ms
fr_HOYApLN2injq87d4XFgAGyiNB8-j2EoXA_ik93y5wfo.js
336 ms
lnr-gtm-jquery-plugin.js
343 ms
modernizr.js
346 ms
fastclick.js
344 ms
foundation.js
395 ms
foundation.alert.js
421 ms
foundation.equalizer.js
428 ms
foundation.reveal.js
430 ms
foundation.tab.js
431 ms
foundation.topbar.js
475 ms
jquery.sticky.js
506 ms
jquery.socialSharers.js
596 ms
responsiveCarousel.js
596 ms
slick.min.js
597 ms
stupidtable.js
599 ms
jquery.smartbanner.js
598 ms
jquery.reject.js
599 ms
circles.js
600 ms
lnr.js
686 ms
scripts.js
607 ms
eu_cookie_compliance.js
568 ms
lnr-gtm.js
614 ms
gpt.js
5 ms
pubads_impl_81.js
10 ms
container.html
16 ms
logo-lnr-inverted.png
88 ms
hub-pro-d2.png
185 ms
hub-top-14.png
185 ms
img_lnr_default.png
186 ms
img_billets_default.png
185 ms
img_store_default.png
188 ms
img_international_default.png
604 ms
logo_toulon_rct_2015_2016_3_etoiles_hd.png
186 ms
logo_racing92_2015.png
188 ms
Club-Rugby-Clermont-auvergne-ASM.png
603 ms
Club-Rugby-Union-bordeaux-Belges_0.png
604 ms
s.png
605 ms
Club-rugby-montpellier-herault.png
605 ms
Club-Rugby-castres-olympique.png
605 ms
Club-Rugby-Brive-Correze-limousin.png
606 ms
Club-rugby-FC-grenoble-rugby.png
607 ms
Club-Rugby-Atlantique-stade-rochelais-la-rochelle_0.png
608 ms
LogParis-d1b84_0.png
609 ms
rugby-club-section-paloise-bearn-pyrenees.png
609 ms
rugby-club-sporting-union-agen-lot-et-garonne.png
609 ms
Club-Rugby-Oyonnax.png
610 ms
Club-Rugby-Lyon-lou-rugby.png
611 ms
Club-rugby-aviron-bayonnais.png
612 ms
rugby-club-AS-beziers-herault.png
613 ms
rugby-club-stade-aurillacois.png
612 ms
rugby-club-colomiers-rugby.png
613 ms
rugby-club-sporting-club-albigeois.png
614 ms
rugby-club-union-sportive-arlequins-perpignan.png
615 ms
rcnm-logo_2015-2016.png
615 ms
rugby-club-stade-montois-rugby.png
617 ms
rugby-club-union-sportive-montalbanaise.png
615 ms
rr.png
617 ms
rugby-club-biarritz-olympique-pays-basque.png
618 ms
rugby-club-US-carcassonne.png
624 ms
rugby-club-tarbes-pyrenees.png
625 ms
rugby-club-union-sportive-dax-rugby-landes.png
626 ms
gtm.js
41 ms
ads
66 ms
analytics.js
117 ms
pl-logo-provence-rugby_0.png
549 ms
Embleme_Angleterre_0.png
460 ms
Embleme_Galles_0.png
511 ms
Embleme_France_0.png
520 ms
Embleme_Ecosse_0.png
514 ms
Embleme_Irlande_0.png
514 ms
FrutigerLTStd-Cn.otf
516 ms
collect
403 ms
FrutigerLTStd-BlackCn.otf
222 ms
icons-3f3d582baad812f0ba80df816d6ca87b.woff
321 ms
Embleme_Italie_0.png
216 ms
Nouvelle_Zelande_0.png
216 ms
Australie_0.png
217 ms
Logo_saracens_0.gif
217 ms
Ulster_0.gif
318 ms
120px-Exeter_Chiefs_logo_0.png
318 ms
Ospreys_0.gif
319 ms
Northampton_0.jpg
319 ms
Glasgow_0.gif
320 ms
Llanelli_0.jpg
423 ms
150px-Leicester_tigers_badge_0.png
424 ms
Munster_0.gif
424 ms
120px-Benetton_Rugby_0.jpg
424 ms
500px-London_Wasps_svg_0.png
425 ms
Bath_0.gif
420 ms
Leinster_0.gif
430 ms
Connacht_0.gif
426 ms
NewcastleFalcons_logo_0.jpg
429 ms
120px-Salesharks_logo_0.png
431 ms
Newport_Dragons_0.gif
431 ms
100px-Harlequins_logo_0.png
432 ms
Cardiff_0.gif
497 ms
FrutigerLTStd-LightCn.otf
509 ms
calvisano_0.jpg
568 ms
Gloucesterrugby_0.gif
568 ms
zebre_0.png
567 ms
Worcester_warriors_logo_0.png
567 ms
150px-Londonirish_logo_0.png
575 ms
Edimbourg_0.gif
576 ms
partenaire-lnr-orange_0.png
524 ms
societe-generale-partenaires_0.png
524 ms
partenaire-lnr-GMF.png
525 ms
sddd.png
523 ms
land_rover-logo_2015.png
460 ms
partenaire-lnr-les-opticiens-mutualistes.png
486 ms
Partenaires%20LNR%20-%20logo%20Gedimat.png
490 ms
partenaire-lnr-Tissot_0.png
488 ms
partenaire-lnr-canal-plus.png
488 ms
ss.png
393 ms
c_sport.png
433 ms
partenaire-lnr-FR3-france-television.png
467 ms
logolp_q.jpg
472 ms
footer-lnr.png
557 ms
footer-google-play.png
468 ms
footer-app-store.png
370 ms
hub-bg.jpg
562 ms
bg-lnr.png
446 ms
bg-ticket.png
448 ms
bg-shop.png
449 ms
bg-international.png
450 ms
logo-top-14.png
528 ms
logo-pro-d2.png
527 ms
t-6-nations.png
527 ms
rwc-2015.png
526 ms
champions-cup.png
613 ms
challenge-cup.png
606 ms
ajax-loader.gif
606 ms
lnr.fr accessibility score
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-hidden="true"] elements contain focusable descendents
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
<dl>'s do not contain only properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements.
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.
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
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.
lnr.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
Browser errors were logged to the console
lnr.fr 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
FR
FR
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Lnr.fr 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 Lnr.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.
lnr.fr
Open Graph description is not detected on the main page of LNR. 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: