3.2 sec in total
275 ms
2 sec
891 ms
Welcome to lundi.am homepage info - get ready to check Lundi best content for France right away, or after learning these important things about lundi.am
lundimatin paraît toutes les semaines. : Le manifeste afro-décolonial. Un orage prêt à éclater. Le génocide des « Nomades » : Figures du déni. Prévoir en stratèges, agir en primitives. « Ils ne p...
Visit lundi.amWe analyzed Lundi.am page load time and found that the first response time was 275 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 50% of websites can load faster. This domain responded with an error, which can significantly jeopardize Lundi.am rating and web reputation
lundi.am performance score
name
value
score
weighting
Value3.1 s
48/100
10%
Value9.3 s
1/100
25%
Value5.2 s
60/100
10%
Value330 ms
76/100
30%
Value0.001
100/100
15%
Value5.1 s
75/100
10%
275 ms
490 ms
61 ms
74 ms
85 ms
Our browser made a total of 62 requests to load all elements on the main page. We found that 27% of them (17 requests) were addressed to the original Lundi.am, 11% (7 requests) were made to Apis.google.com and 10% (6 requests) were made to Ssl.gstatic.com. The less responsive or slowest element that took the longest time to load (787 ms) belongs to the original domain Lundi.am.
Page size can be reduced by 584.9 kB (19%)
3.0 MB
2.4 MB
In fact, the total size of Lundi.am main page is 3.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. 55% of websites need less resources to load. Images take 2.3 MB which makes up the majority of the site volume.
Potential reduce by 69.0 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 69.0 kB or 85% of the original size.
Potential reduce by 63.4 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. Lundi images are well optimized though.
Potential reduce by 268.9 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 268.9 kB or 68% of the original size.
Potential reduce by 183.6 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. Lundi.am needs all CSS files to be minified and compressed as it can save up to 183.6 kB or 83% of the original size.
Number of requests can be reduced by 34 (62%)
55
21
The browser has sent 55 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Lundi. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 19 to 1 for JavaScripts and from 10 to 1 for CSS and as a result speed up the page load time.
lundi.am
275 ms
lundi.am
490 ms
bootstrap.min.css
61 ms
font-awesome.min.css
74 ms
css
85 ms
css
97 ms
css
110 ms
css
114 ms
c27c12a0fc8296221240a9ceb37b4fa1.css
137 ms
24eeedbd2a536abfc49f7d62eb85c6a7.js
446 ms
fluidbox.css
87 ms
bootstrap.min.js
68 ms
jquery.fitvids.js
237 ms
search.js
246 ms
platform.js
92 ms
mixpanel-2-latest.min.js
177 ms
sdk.js
232 ms
arton365.jpg
132 ms
arton360.jpg
574 ms
arton361.jpg
533 ms
arton357.jpg
533 ms
arton359.jpg
614 ms
arton358.jpg
787 ms
arton364.jpg
754 ms
arton363.jpg
755 ms
arton362.jpg
677 ms
83169847_o.jpg
714 ms
widgets.js
300 ms
G0XvmuebhPCfCq4YdUpRgALUuEpTyoUstqEm5AMlJo4.ttf
114 ms
SLchCroJwYIfYhi7deprmCZ2oysoEQEeKwjgmXLRnTc.ttf
208 ms
ahqA-Qx4hCXuev49rpJH9uvvDin1pK8aKteLpeZ5c0A.ttf
265 ms
DXI1ORHCpsQm3Vp6mXoaTZS3E-kSBmtLoNJPDtbj2Pk.ttf
265 ms
piwik.js
548 ms
cb=gapi.loaded_0
44 ms
cb=gapi.loaded_1
165 ms
subscribe_embed
223 ms
overlay.png
666 ms
230 ms
230 ms
280 ms
postmessageRelay
150 ms
xd_arbiter.php
200 ms
www-subscribe-embed-vflTum1sJ.css
97 ms
www-subscribe-embed.js
105 ms
button.0308b81ff1714e446f674b5b9793f2cd.js
41 ms
www-hitchhiker-vflvB63an.png
20 ms
cb=gapi.loaded_0
10 ms
3193398744-postmessagerelay.js
50 ms
rpc:shindig_random.js
43 ms
follow_button.b9740740e0bcf9b0657c5b11bd4388da.en.html
61 ms
cb=gapi.loaded_0
12 ms
info.json
86 ms
cb=gapi.loaded_2
12 ms
border_3.gif
8 ms
subscribe_embed
51 ms
spacer.gif
9 ms
bubbleSprite_3.png
4 ms
bubbleDropR_3.png
9 ms
bubbleDropB_3.png
11 ms
www-subscribe-embed-card-vflqARhQ4.css
3 ms
www-subscribe-embed-card.js
7 ms
jot
81 ms
lundi.am 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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
[id] attributes on active, focusable elements are not unique
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 IDs are not unique
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
Form elements do not have associated labels
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
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
lundi.am 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
lundi.am SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Lundi.am can be misinterpreted by Google and other search engines. Our service has detected that French is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Lundi.am 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.
lundi.am
Open Graph data is detected on the main page of Lundi. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: