3.1 sec in total
258 ms
2.4 sec
461 ms
Welcome to lille.fr homepage info - get ready to check Lille best content for France right away, or after learning these important things about lille.fr
Site officiel de la Ville de Lille. Retrouvez toute l’actualité, l’agenda culturel, les démarches administratives et les grands projets en cours.
Visit lille.frWe analyzed Lille.fr page load time and found that the first response time was 258 ms and then it took 2.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
lille.fr performance score
name
value
score
weighting
Value3.5 s
34/100
10%
Value13.1 s
0/100
25%
Value5.7 s
51/100
10%
Value270 ms
82/100
30%
Value0.003
100/100
15%
Value8.6 s
37/100
10%
258 ms
357 ms
341 ms
254 ms
391 ms
Our browser made a total of 80 requests to load all elements on the main page. We found that 95% of them (76 requests) were addressed to the original Lille.fr, 3% (2 requests) were made to Google-analytics.com and 1% (1 request) were made to Sarbacane.com. The less responsive or slowest element that took the longest time to load (940 ms) belongs to the original domain Lille.fr.
Page size can be reduced by 185.8 kB (9%)
2.0 MB
1.8 MB
In fact, the total size of Lille.fr main page is 2.0 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. 65% of websites need less resources to load. Images take 1.8 MB which makes up the majority of the site volume.
Potential reduce by 153.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 72.5 kB, which is 43% 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 153.5 kB or 90% of the original size.
Potential reduce by 31.8 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. Lille images are well optimized though.
Potential reduce by 534 B
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. This website has mostly compressed JavaScripts.
Number of requests can be reduced by 15 (21%)
70
55
The browser has sent 70 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 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 4 to 1 for JavaScripts and as a result speed up the page load time.
lille.fr
258 ms
www.lille.fr
357 ms
4bc6a3d40ab90d2d032a01297d35ef0b_all.css
341 ms
jquery-1.11.0.min.js
254 ms
mailing_list.js
391 ms
fb8afa7d3c3e3fd9452fd7bd293b1748.js
429 ms
analytics.js
74 ms
ico-flux.png
87 ms
ico-fb.png
88 ms
ico-twitt.png
170 ms
ico-pint.png
178 ms
ico-insta.png
183 ms
ico-youtu.png
172 ms
logo.png
170 ms
monProfil.png
179 ms
profils.png
253 ms
quartier.png
254 ms
stamp.png
255 ms
fleur.png
255 ms
journee-femme_actualite01_homepage.jpg
257 ms
2015_0926_JS_Parade_Renaissance_GrandPlace_018.JPG-1024_actualite02_homepage.jpg
343 ms
Open-Tennis_actualite02_homepage.jpg
335 ms
Equipement-Stephane-Hessel_actualite02_homepage.jpg
336 ms
melcity_actualite02_homepage.jpg
624 ms
Figaro-divorce_actualite02_homepage.jpg
627 ms
L-air-de-rien_event_homepage.jpg
340 ms
open-du-nord_event_homepage.jpg
623 ms
Lille-neige_event_homepage.jpg
626 ms
Decouverte-de-l-architecture-et-du-patrimoine_event_homepage.jpg
623 ms
Beffrois-de-l-architecture_event_homepage.jpg
624 ms
Palais-des-Beaux-Arts_zoom_homepage.jpg
668 ms
Lille-Neige-bleu-1.jpg
756 ms
Le-defi-de-Fortunee.jpg
629 ms
Le-defi-de-Fortunee.jpg
772 ms
Lille-neige-2.jpg
749 ms
lille-neige-3.jpg
771 ms
la-patinoire-de-Lille-Neige.jpg
771 ms
Lille-neige-luge.jpg
922 ms
Lille-Neige-bleu-1_return_pictures_homepage.jpg
834 ms
Le-defi-de-Fortunee_return_pictures_homepage.jpg
839 ms
Le-defi-de-Fortunee_return_pictures_homepage.jpg
842 ms
Lille-neige-2_return_pictures_homepage.jpg
804 ms
mailing_list.js
349 ms
collect
27 ms
lato-regular-webfont.woff
768 ms
fontawesome-webfont.woff
940 ms
lato-bold-webfont.woff
850 ms
Lato-Black.woff
768 ms
Lato-BoldItalic.woff
766 ms
Lato-Italic.woff
806 ms
lille-neige-3_return_pictures_homepage.jpg
850 ms
la-patinoire-de-Lille-Neige_return_pictures_homepage.jpg
850 ms
Lille-neige-luge_return_pictures_homepage.jpg
848 ms
Facebook.png
778 ms
Twitter.png
779 ms
Pinterest.png
835 ms
Instagram.png
842 ms
You-Tube.png
841 ms
Google-Plus.png
767 ms
Appli-mobile_thumbnail_homepage.png
769 ms
Carte_thumbnail_homepage.png
768 ms
Mag_thumbnail_homepage.png
832 ms
siteListControl.png
557 ms
Palais-beaux-arts-Lille_site_homepage.jpg
556 ms
MFW_site_homepage.jpg
563 ms
musee-d-histoire-naturelle-de-Lille_site_homepage.jpg
561 ms
Espace-famille_site_homepage.jpg
567 ms
Bibliotheque-municipal-de-Lille_site_homepage.jpg
630 ms
Conservatoire-de-Lille_site_homepage.jpg
634 ms
Maison-des-associations_site_homepage.jpg
598 ms
Maison-de-l-habitat-durable_site_homepage.jpg
518 ms
logoFooter.png
502 ms
buttonClose.png
505 ms
newsletter.png
569 ms
ico-location.png
569 ms
ico-tel.png
514 ms
ico-mail.png
513 ms
bx_loader.gif
513 ms
rue-faidherbe_diapo_homepage.jpg
600 ms
controls.png
557 ms
lille.fr accessibility score
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
Buttons do not have an accessible name
Image elements do not have [alt] attributes
Links do not have a discernible name
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
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.
lille.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
Missing source maps for large first-party JavaScript
lille.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
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 Lille.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 Lille.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.
lille.fr
Open Graph description is not detected on the main page of Lille. 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: