12.4 sec in total
3.1 sec
8.5 sec
807 ms
Visit runinlille.fr now to see the best up-to-date Run In Lille content and also check out these interesting facts you probably never knew about runinlille.fr
Tribulations d'un coureur à Lille
Visit runinlille.frWe analyzed Runinlille.fr page load time and found that the first response time was 3.1 sec and then it took 9.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
runinlille.fr performance score
name
value
score
weighting
Value6.0 s
4/100
10%
Value6.3 s
10/100
25%
Value11.4 s
5/100
10%
Value110 ms
98/100
30%
Value0
100/100
15%
Value6.2 s
62/100
10%
3112 ms
2536 ms
175 ms
192 ms
180 ms
Our browser made a total of 190 requests to load all elements on the main page. We found that 33% of them (62 requests) were addressed to the original Runinlille.fr, 15% (29 requests) were made to Static.xx.fbcdn.net and 7% (14 requests) were made to Pbs.twimg.com. The less responsive or slowest element that took the longest time to load (3.1 sec) belongs to the original domain Runinlille.fr.
Page size can be reduced by 2.1 MB (42%)
5.1 MB
3.0 MB
In fact, the total size of Runinlille.fr main page is 5.1 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. 85% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 2.3 MB which makes up the majority of the site volume.
Potential reduce by 66.7 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 66.7 kB or 75% of the original size.
Potential reduce by 104.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. Run In Lille images are well optimized though.
Potential reduce by 1.5 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.5 MB or 68% of the original size.
Potential reduce by 408.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. Runinlille.fr needs all CSS files to be minified and compressed as it can save up to 408.3 kB or 81% of the original size.
Number of requests can be reduced by 88 (47%)
187
99
The browser has sent 187 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Run In Lille. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 52 to 1 for JavaScripts and from 29 to 1 for CSS and as a result speed up the page load time.
runinlille.fr
3112 ms
style.css
2536 ms
style.css
175 ms
styles.css
192 ms
fergcorp_milestone-style.css
180 ms
social_widget.css
182 ms
lightbox.min.css
193 ms
shortcodes.css
296 ms
font-awesome.min.css
388 ms
wzslider.css
298 ms
black.css
284 ms
custom.css
291 ms
jetpack.css
463 ms
race_calendar.css
389 ms
jquery.js
552 ms
jquery-migrate.min.js
411 ms
mailchimp-widget-min.js
491 ms
js
40 ms
highcharts.js
17 ms
WP-GPX-Maps.js
485 ms
init.js
515 ms
ai.js
629 ms
vertical-m.css
588 ms
jquery.form.min.js
528 ms
scripts.js
606 ms
wp-lightbox-2.min.js
551 ms
devicepx-jetpack.js
5 ms
gprofiles.js
60 ms
wpgroho.js
600 ms
jquery.flexslider-min.js
709 ms
dropdown.js
644 ms
galleria.js
745 ms
wzslider.js
695 ms
wp-embed.min.js
705 ms
e-201611.js
4 ms
wp-emoji-release.min.js
260 ms
xFaJDdyofiU
162 ms
LThKtHt4PF4
162 ms
fcQL3ta3ouw
642 ms
EqJ0WrTOQ-A
639 ms
20qfTnvj.png
879 ms
garmin-connect.png
879 ms
App_Nikeplus_Running.png
664 ms
img_logo_bluebg_2x.png
637 ms
membre_runhappy.png
1111 ms
RiL_964X145-1.png
635 ms
back-menu.png
148 ms
icon_form.png
147 ms
11825937_412060882312775_5126162493767730772_n-400x400.jpg
736 ms
running-the-race-400x400.jpg
634 ms
bluetens-1-400x400.jpg
635 ms
Package1-400x400.png
1441 ms
Garmin_Varia-400x400.jpg
635 ms
11825937_412060882312775_5126162493767730772_n-640x300.jpg
1294 ms
running-the-race-310x190.jpg
1108 ms
bluetens-1-310x190.jpg
1294 ms
Package1-310x190.png
1437 ms
Garmin_Varia-310x190.jpg
872 ms
Capture-d%E2%80%99%C3%A9cran-2015-07-22-%C3%A0-11.44.42-310x190.png
2149 ms
adidas-adizero-boost-new-2-310x190.jpg
1340 ms
1367273459keycoopt-310x190.png
1551 ms
Hexoskin_03-310x190.jpg
1551 ms
lemon-grass-310x190.png
1644 ms
facebook.png
1550 ms
twitter.png
1546 ms
instagram.png
1666 ms
googleplus.png
1666 ms
Encart-Blog-runinlille-1-e1455727007208.jpg
1784 ms
logo.png
1666 ms
topchrono-1-e1397656911691.jpg
1784 ms
logo-oxsitis-e1390914240909.jpg
1790 ms
Mule-Bar-Logo-JPEG-e1390914211962.jpg
1789 ms
Data-Vitae-e1390914279136.jpeg
1790 ms
logo-HD-e1390920004792.jpg
1994 ms
stars.png
1933 ms
widget.js
597 ms
widgets.js
68 ms
390dcaecec599e86e4276890a7738ea23b4c6430
579 ms
hovercard.css
527 ms
services.css
555 ms
g.gif
513 ms
timeline.d11f7a3b3287fb94220e8ee6d03cc772.js
561 ms
www-embed-player-vflfNyN_r.css
647 ms
www-embed-player.js
843 ms
base.js
967 ms
likebox.php
1288 ms
1f609.png
1054 ms
bullets-small.png
1315 ms
strava-widget-df7e9c9bf07b52d15d8a5992d76f16ee.css
107 ms
strava-head-e2dcbf12e93fb23d5530f39814fa1160.js
110 ms
mapbox-0fd71b6e080ef35cc068dfb9ab80c9b2.js
125 ms
en-US-8a0032b97f41c342fc74ac67b548864d.js
187 ms
application-db1db54ec4fecae20b1dd89d9fcad578.js
246 ms
manifest-72ea53976498e16ef4af5e264a576c5c.js
184 ms
wdg.css
17 ms
recent
901 ms
ajax-loader.gif
78 ms
syndication
603 ms
373029196844376064
837 ms
sprites-widget.png
353 ms
widgets.js
335 ms
175.png@2x
375 ms
175.png@2x
330 ms
172.png@2x
250 ms
Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js
120 ms
ad_status.js
120 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
55 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
58 ms
kyEKgjk51ZE.css
286 ms
xgj7bXhJNEH.css
338 ms
Czh0gDTFcBt.css
471 ms
kE_Z8j4XNUS.css
543 ms
N-k91nHCZS2.css
561 ms
ZeuPykSxSED.css
551 ms
q68gy-v_YMF.js
560 ms
FJmpeSpHpjS.js
604 ms
0wM5s1Khldu.js
542 ms
1bNoFZUdlYZ.js
641 ms
njO1TPvGzoR.js
635 ms
OloiM1PZafe.js
662 ms
LTv6ZK-5zxz.js
686 ms
1FCa-btixu2.js
681 ms
Oagsvfb4VWi.js
664 ms
pObvZSrFc_4.js
747 ms
Kt4tkgSRvHH.js
681 ms
H3EKDTObx05.js
682 ms
eR-qA8bp1RM.js
681 ms
1QuX41zDRrx.js
759 ms
1171082_1745109202377527_1741749095_n.jpg
744 ms
powered_by_ink_normal_200_27.png
27 ms
proxy.jpg
100 ms
1f1eb-1f1f7.png
120 ms
1f618.png
104 ms
1f6b4-1f3fc.png
104 ms
1f1ec-1f1e7.png
103 ms
1f3c3.png
107 ms
1f609.png
101 ms
1f44d.png
109 ms
1f6b5.png
108 ms
12818864_1691871001098724_1151314725_n.jpg
722 ms
12797909_908510519265858_1208075251_n.jpg
741 ms
12750064_1056434081066642_1332769280_n.jpg
835 ms
12751248_464682550390288_133454031_n.jpg
851 ms
12747677_1039875969412620_272020692_n.jpg
838 ms
10632120_241260412875113_961212164_n.jpg
874 ms
12747729_1501788380130354_1295976265_n.jpg
883 ms
proxy.jpg
229 ms
proxy.jpg
106 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.dark.ltr.css
22 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.dark.ltr.css
43 ms
qldhyEXR_normal.jpg
71 ms
Mv4fgDci_normal.jpg
172 ms
fc314bd1f4a31a63bf58e6a1299f089d_normal.png
247 ms
rQETe9Dz_normal.jpg
244 ms
UozxE23y_normal.png
336 ms
nZcQJ_4j_normal.png
296 ms
l04vVo8n_normal.png
335 ms
ROY3vUxY_normal.jpg
334 ms
z9KmsOw-_normal.jpg
385 ms
Cc83qI6WIAAPdAt.jpg:small
683 ms
CctcKoHVIAAX-uz.png:small
679 ms
CcpNQyvWIAEff8R.jpg:small
681 ms
CchzkQnXIAAQ_1f.jpg:small
388 ms
syndication_bundle_v1_64fcb3dd2f6da5b5f976d91a319ef73e329c1a5d.css
175 ms
syndication_bundle_v1_64fcb3dd2f6da5b5f976d91a319ef73e329c1a5d.css
169 ms
proxy.jpg
146 ms
proxy.jpg
144 ms
960008_182674785251587_1923561710_n.png
357 ms
safe_image.php
320 ms
safe_image.php
379 ms
1385148_182667718585627_1138632798_n.png
430 ms
1474469_10205120781685663_7701778861799460373_n.jpg
468 ms
10534693_136976823301116_7208682426435245291_n.jpg
499 ms
12814609_10153334040130766_1449714360895271427_n.jpg
630 ms
10406408_10152968849887367_8612930596998799291_n.jpg
501 ms
12592242_10153253987395966_6811180692246717715_n.jpg
465 ms
11225429_1028114767198778_8388775650363282640_n.jpg
467 ms
12821480_474852769367119_574224309268589350_n.jpg
567 ms
12821443_472287979623598_4543810843828952599_n.jpg
606 ms
1936285_468196316699431_4333702058409065734_n.jpg
559 ms
wL6VQj7Ab77.png
158 ms
s7jcwEQH7Sx.png
158 ms
pimRBh7B6ER.png
159 ms
QDwYpIaRyfG.png
159 ms
aeO1ik7i7-T.png
276 ms
K00K-UgnsKu.png
175 ms
gxbPuQdXIZP.png
65 ms
jot.html
2 ms
I6-MnjEovm5.js
42 ms
pQrUxxo5oQp.js
43 ms
runinlille.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.
runinlille.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
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
runinlille.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
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 Runinlille.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 Runinlille.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.
runinlille.fr
Open Graph data is detected on the main page of Run In Lille. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: