Tools & Wizards About Us
l4m.fr screenshot

Report Summary

  • 46

    Performance

    Renders faster than
    65% of other websites

  • 96

    Accessibility

    Visual factors better than
    that of 89% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 89

    SEO

    Google-friendlier than
    67% of websites

l4m.fr

L4M : Emploi Nord Pas de Calais, Stage, Intérim et Job étudiant

Page Load Speed

12.5 sec in total

First Response

974 ms

Resources Loaded

10.4 sec

Page Rendered

1 sec

l4m.fr screenshot

About Website

Visit l4m.fr now to see the best up-to-date L4M content for France and also check out these interesting facts you probably never knew about l4m.fr

L4M vous permet de consulter les offres d'emploi dans le nord pas de calais ainsi que les offres de stage, d’intérim et les jobs étudiants

Visit l4m.fr

Key Findings

We analyzed L4m.fr page load time and found that the first response time was 974 ms and then it took 11.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.

Performance Metrics

l4m.fr performance score

46

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.5 s

16/100

10%

LCP (Largest Contentful Paint)

Value7.0 s

6/100

25%

SI (Speed Index)

Value6.3 s

42/100

10%

TBT (Total Blocking Time)

Value440 ms

64/100

30%

CLS (Cumulative Layout Shift)

Value0.024

100/100

15%

TTI (Time to Interactive)

Value7.9 s

43/100

10%

Network Requests Diagram

www.l4m.fr

974 ms

prototype.js

638 ms

scriptaculous.js

597 ms

common.src.js

728 ms

lightbox.js

629 ms

Our browser made a total of 82 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original L4m.fr, 59% (48 requests) were made to Static.l4m.fr and 12% (10 requests) were made to Static.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (6.9 sec) relates to the external source Static.l4m.fr.

Page Optimization Overview & Recommendations

Page size can be reduced by 59.4 kB (6%)

Content Size

994.5 kB

After Optimization

935.1 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of L4m.fr main page is 994.5 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. 55% of websites need less resources to load. Images take 915.4 kB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 48.9 kB

  • Original 62.0 kB
  • After minification 57.5 kB
  • After compression 13.1 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 48.9 kB or 79% of the original size.

Image Optimization

-1%

Potential reduce by 10.5 kB

  • Original 915.4 kB
  • After minification 904.9 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. L4M images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 27 B

  • Original 17.1 kB
  • After minification 17.1 kB
  • After compression 17.1 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. This website has mostly compressed JavaScripts.

Requests Breakdown

Number of requests can be reduced by 40 (49%)

Requests Now

81

After Optimization

41

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 81 CSS, Javascripts, AJAX and image requests in order to completely render the main page of L4M. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 25 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

www.l4m.fr

www.l4m.fr

974 ms

prototype.js

prototype.js

638 ms

scriptaculous.js

scriptaculous.js

597 ms

common.src.js

common.src.js

728 ms

lightbox.js

lightbox.js

629 ms

carrousel.js

carrousel.js

630 ms

skyscraper.js

skyscraper.js

632 ms

global.css

global.css

755 ms

plusone.js

plusone.js

70 ms

cookies.js

cookies.js

719 ms

builder.js

builder.js

85 ms

effects.js

effects.js

84 ms

dragdrop.js

dragdrop.js

82 ms

controls.js

controls.js

89 ms

slider.js

slider.js

88 ms

sound.js

sound.js

109 ms

separation.jpg

separation.jpg

83 ms

l4m_sprite.png

l4m_sprite.png

165 ms

1481725.jpg

1481725.jpg

160 ms

1471849.jpg

1471849.jpg

332 ms

1481722.jpg

1481722.jpg

165 ms

1481724.jpg

1481724.jpg

164 ms

1481727.jpg

1481727.jpg

232 ms

1483948.jpg

1483948.jpg

238 ms

1452456.png

1452456.png

241 ms

1424000.jpg

1424000.jpg

245 ms

1320515.png

1320515.png

247 ms

1237896.jpg

1237896.jpg

318 ms

1409501.png

1409501.png

329 ms

1483998.jpg

1483998.jpg

330 ms

1483945.jpg

1483945.jpg

412 ms

1483931.jpg

1483931.jpg

478 ms

1483969.gif

1483969.gif

485 ms

683923.jpg

683923.jpg

493 ms

1026115.jpg

1026115.jpg

6898 ms

629080.jpg

629080.jpg

602 ms

1363586.jpg

1363586.jpg

602 ms

1420271.jpg

1420271.jpg

599 ms

1263757.jpg

1263757.jpg

597 ms

1447769.jpg

1447769.jpg

647 ms

1471852.jpg

1471852.jpg

811 ms

1481882.jpg

1481882.jpg

643 ms

1481854.jpg

1481854.jpg

647 ms

1481847.jpg

1481847.jpg

724 ms

ajs.php

ajs.php

507 ms

fan.php

fan.php

212 ms

up-carrousel.png

up-carrousel.png

176 ms

down-carrousel.png

down-carrousel.png

175 ms

more.jpg

more.jpg

206 ms

fleche.png

fleche.png

249 ms

f2daa471bb59c79ea5b5799c72bfd385.gif

f2daa471bb59c79ea5b5799c72bfd385.gif

252 ms

lg.php

lg.php

248 ms

ajs.php

ajs.php

267 ms

p_TUZUiNrjI.css

p_TUZUiNrjI.css

208 ms

CkaAj0ofVuQ.css

CkaAj0ofVuQ.css

251 ms

mm0vjjrXdxr.js

mm0vjjrXdxr.js

338 ms

Ta5YnQdNSFy.js

Ta5YnQdNSFy.js

394 ms

XXn49zk5GnD.js

XXn49zk5GnD.js

322 ms

OwNnuMlrnxQ.js

OwNnuMlrnxQ.js

334 ms

separation.png

separation.png

95 ms

a6faae11e7d1484192a3aed75a31ce70.gif

a6faae11e7d1484192a3aed75a31ce70.gif

94 ms

lg.php

lg.php

89 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

24 ms

dc.js

dc.js

74 ms

all.js

all.js

448 ms

__utm.gif

__utm.gif

20 ms

12742600_10154596825803508_6308336664361572243_n.jpg

12742600_10154596825803508_6308336664361572243_n.jpg

304 ms

12032152_10154250459973508_2295014397595620231_n.jpg

12032152_10154250459973508_2295014397595620231_n.jpg

308 ms

10354686_10150004552801856_220367501106153455_n.jpg

10354686_10150004552801856_220367501106153455_n.jpg

359 ms

12376701_10153451131714234_8610148733528212108_n.jpg

12376701_10153451131714234_8610148733528212108_n.jpg

398 ms

12366206_10208055053199925_1780084111240981401_n.jpg

12366206_10208055053199925_1780084111240981401_n.jpg

399 ms

1395998_660551420645408_1367818823_n.jpg

1395998_660551420645408_1367818823_n.jpg

392 ms

1379841_10150004552801901_469209496895221757_n.jpg

1379841_10150004552801901_469209496895221757_n.jpg

387 ms

12552625_104817439901290_4999991742778596842_n.jpg

12552625_104817439901290_4999991742778596842_n.jpg

389 ms

wL6VQj7Ab77.png

wL6VQj7Ab77.png

158 ms

s7jcwEQH7Sx.png

s7jcwEQH7Sx.png

156 ms

72 ms

xd_arbiter.php

xd_arbiter.php

261 ms

wBg80dBy2Ra.js

wBg80dBy2Ra.js

43 ms

WIQcBxwlOXr.js

WIQcBxwlOXr.js

38 ms

print.css

print.css

243 ms

xd_arbiter.php

xd_arbiter.php

82 ms

Accessibility Review

l4m.fr accessibility score

96

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

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

High

Links do not have a discernible name

Best Practices

l4m.fr best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

l4m.fr SEO score

89

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

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

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    FR

  • Language Claimed

    FR

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise L4m.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 L4m.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.

Social Sharing Optimization

l4m.fr

Open Graph data is detected on the main page of L4M. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: