55
Progressive Web App
51
Performance
80
Accessibility
62
Best Practices
55
Progressive Web App
These audits validate the aspects of a Progressive Web App, as specified by the baseline PWA Checklist.
5 failed audits
0
Does not register a Service Worker
The service worker is the technology that enables your app to use many Progressive Web App features, such as offline, add to homescreen, and push notifications. Learn more.
0
Does not respond with a 200 when offline
If you're building a Progressive Web App, consider using a service worker so that your app can work offline. Learn more.
0
User will not be prompted to Install the Web App
Browsers can proactively prompt users to add your app to their homescreen, which can lead to higher engagement. Learn more.
Failures: No manifest was fetched, Site does not register a Service Worker, Manifest start_url is not cached by a Service Worker.
0
Is not configured for a custom splash screen
A default splash screen will be constructed for your app, but satisfying these requirements guarantee a high-quality splash screen that transitions the user from tapping the home screen icon to your app's first paint
Failures: No manifest was fetched.
0
Address bar does not match brand colors
The browser address bar can be themed to match your site. Learn more.
Failures: No manifest was fetched.
6 Passed Audits
100
Contains some content when JavaScript is not available
Your app should display some content when JavaScript is disabled, even if it's just a warning to the user that JavaScript is required to use the app. Learn more.
100
Uses HTTPS
All sites should be protected with HTTPS, even ones that don't handle sensitive data. HTTPS prevents intruders from tampering with or passively listening in on the communications between your app and your users, and is a prerequisite for HTTP/2 and many new web platform APIs. Learn more.
100
Redirects HTTP traffic to HTTPS
If you've already set up HTTPS, make sure that you redirect all HTTP traffic to HTTPS. Learn more.
100
Page load is fast enough on 3G
A fast page load over a 3G network ensures a good mobile user experience. Learn more.
100
Has a <meta name="viewport"> tag with width or initial-scale
Add a viewport meta tag to optimize your app for mobile screens. Learn more.
100
Content is sized correctly for the viewport
If the width of your app's content doesn't match the width of the viewport, your app might not be optimized for mobile screens. Learn more.
Manual checks to verify
These audits are required by the baseline PWA Checklist but are not automatically checked by Lighthouse. They do not affect your score but it's important that you verify them manually.
0
Site works cross-browser
To reach the most number of users, sites should work across every major browser. Learn more.
0
Page transitions don't feel like they block on the network
Transitions should feel snappy as you tap around, even on a slow network, a key to perceived performance. Learn more.
0
Each page has a URL
Ensure individual pages are deep linkable via the URLs and that URLs are unique for the purpose of shareability on social media. Learn more.
51
Performance
These encapsulate your app's performance.
Metrics
These metrics encapsulate your app's performance across a number of dimensions.
1,7 s
Screenshot at 1,7 s
3,4 s
Screenshot at 3,4 s
5,1 s
Screenshot at 5,1 s
6,7 s
Screenshot at 6,7 s
8,4 s
Screenshot at 8,4 s
10,1 s
Screenshot at 10,1 s
11,8 s
Screenshot at 11,8 s
13,5 s
Screenshot at 13,5 s
15,2 s
Screenshot at 15,2 s
16,9 s
Screenshot at 16,9 s
3 210 ms
First meaningful paint
First meaningful paint measures when the primary content of a page is visible. Learn more.
9 800 ms
First Interactive (beta)
The first point at which necessary scripts of the page have loaded and the CPU is idle enough to handle most user input.
16 860 ms
Consistently Interactive (beta)
The point at which most network resources have finished loading and the CPU is idle for a prolonged period.
77
Perceptual Speed Index: 3 268 (target: < 1 250)
Speed Index shows how quickly the contents of a page are visibly populated. Learn more.
70
Estimated Input Latency: 80 ms (target: < 50 ms)
The score above is an estimate of how long your app takes to respond to user input, in milliseconds. There is a 90% probability that a user encounters this amount of latency, or less. 10% of the time a user can expect additional latency. If your score is higher than Lighthouse's target score, users may perceive your app as laggy. Learn more.
Opportunities
These are opportunities to speed up your application by optimizing the following resources.
Reduce render-blocking scripts
1 850 ms
Script elements are blocking the first paint of your page. Consider inlining critical scripts and deferring non-critical ones. Learn more.
View Details
URL
Size (KB)
Delayed Paint By (ms)
/js/mobile-detect.min.js
14,84 KB
1 004 ms
/js/beta_base_70959.js
147,25 KB
1 846 ms
Reduce render-blocking stylesheets
1 170 ms
Link elements are blocking the first paint of your page. Consider inlining critical links and deferring non-critical ones. Learn more.
View Details
URL
Size (KB)
Delayed Paint By (ms)
/css/beta_layout_70959.css
28,5 KB
1 172 ms
/css/beta_styles_70959.css
15,1 KB
989 ms
Enable text compression
380 ms
55 KB
Text-based responses should be served with compression (gzip, deflate or brotli) to minimize total network bytes. Learn more.
View Details
Uncompressed resource URL
Original
GZIP Savings
…102/trk.js
68 KB
43 KB (63%)
/CSS_PREPROD/appnexus.css
14 KB
12 KB (82%)
Properly size images
130 ms
19 KB
Serve images that are appropriately-sized to save cellular data and improve load time. Learn more.
View Details
URL
Original
Potential Savings
/img/favicon-beta-touch.png
18 KB
12 KB (66%)
/img/download_on_google_play.png
4 KB
4 KB (100%)
/img/download_on_app_store.png
4 KB
4 KB (100%)
Offscreen images
50 ms
7 KB
Consider lazy-loading offscreen images to improve page load speed and time to interactive. Learn more.
View Details
URL
Original
Potential Savings
/img/download_on_google_play.png
4 KB
4 KB (100%)
/img/download_on_app_store.png
4 KB
4 KB (100%)
Diagnostics
More information about the performance of your application.
0
Critical Request Chains: 12
The Critical Request Chains below show you what resources are required for first render of this page. Improve page load by reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources. Learn more.
Longest chain: 8 642,5ms over 1 requests, totalling 0,62 KB
View critical network waterfall:
Initial Navigation
/ (www.leboncoin.fr)
/css/beta_layout_70959.css (static.leboncoin.fr) - 1 171,5ms, 28,5 KB
/css/beta_styles_70959.css (static.leboncoin.fr) - 988,7ms, 15,1 KB
/js/mobile-detect.min.js (static.leboncoin.fr) - 1 003,9ms, 14,84 KB
/js/beta_base_70959.js (static.leboncoin.fr)
/fonts/opensans-regular-webfont.woff (static.leboncoin.fr) - 810,5ms, 24,62 KB
/js/datalayer-functions.js (static.leboncoin.fr) - 604,4ms, 0,84 KB
…prod/utag.js (tags.tiqcdn.com) - 1 081,2ms, 20,5 KB
/js/jquery.mobile-1.4.5.min.js (static.leboncoin.fr) - 611,5ms, 3,28 KB
/ (advertising.leboncoin.fr) - 957,8ms, 0,1 KB
/ (hit.leboncoin.fr) - 814,7ms, 0,1 KB
/fonts/opensans-semibold-webfont.woff2 (static.leboncoin.fr) - 1 745,7ms, 19,01 KB
/fonts/opensans-bold-webfont.woff2 (static.leboncoin.fr) - 1 609,8ms, 19,36 KB
/fonts/icomoon.ttf (static.leboncoin.fr) - 1 702,1ms, 11,76 KB
/rd_log?e=… (ams1-ib.adnxs.com) - 969,4ms, 0,62 KB
/CSS_PREPROD/appnexus.css (img8.leboncoin.fr) - 937ms, 14,51 KB
/rd_log?e=… (ams1-ib.adnxs.com) - 987,7ms, 0,62 KB
5 Passed Audits
100
Optimize images
Optimized images load faster and consume less cellular data. Learn more.
100
Serve images as WebP
WebP provides better lossy and lossless compression than PNG or JPEG, which means faster downloads and less data consumption. Learn more.
100
Avoids enormous network payloads: Total size was 821 KB (target: < 1 600 KB)
Network transfer size costs users real money and is highly correlated with long load times. Try to find ways to reduce the size of required files.
View Details
URL
Total Size
Transfer Time
/js/beta_base_70959.js
147 KB
1 020 ms
/
137 KB
950 ms
…a1/04fd57a1-7088-4e03-b7d6-74ad27258093.jpg
77 KB
540 ms
…102/trk.js
69 KB
480 ms
/css/beta_layout_70959.css
29 KB
200 ms
/fonts/opensans-regular-webfont.woff
25 KB
170 ms
…0.7.3/ast.js
24 KB
170 ms
…prod/utag.js
21 KB
140 ms
/fonts/opensans-bold-webfont.woff2
19 KB
130 ms
/fonts/opensans-semibold-webfont.woff2
19 KB
130 ms
100
Avoids an excessive DOM size: 736 nodes (target: < 1 500 nodes)
Browser engineers recommend pages contain fewer than ~1 500 DOM nodes. The sweet spot is a tree depth < 32 elements and fewer than 60 children/parent element. A large DOM can increase memory usage, cause longer style calculations, and produce costly layout reflows. Learn more.
View details
Total DOM Nodes
736
target: < 1 500 nodes
DOM Depth
13
target: < 32
Maximum Children
33
target: < 60 nodes
100
User Timing marks and measures: 0
Consider instrumenting your app with the User Timing API to create custom, real-world measurements of key user experiences. Learn more.
80
Accessibility
These checks highlight opportunities to improve the accessibility of your app.
Elements Use Attributes Correctly
Screen readers and other assistive technologies require annotations to understand otherwise ambiguous content.
0
Image elements do not have [alt] attributes.
Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute.Learn more.
View failing elements
<img class="fl" id="logoApp" src="//static.leboncoin.fr/img/favicon-beta-touch.png"><img id="full0" src="//static.leboncoin.fr/img/star.svg"><img id="full1" src="//static.leboncoin.fr/img/star.svg"><img id="full2" src="//static.leboncoin.fr/img/star.svg"><img id="full3" src="//static.leboncoin.fr/img/star.svg"><img src="//static.leboncoin.fr/img/star-half.svg">
Elements Have Discernable Names
Screen readers and other assistive technologies require annotations to understand otherwise ambiguous content.
0
Links do not have a discernable name.
Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn more.
View failing elements
<a href="//www.leboncoin.fr/" class="logo-site trackable" data-info="{&quot;event_name&quot; : &quot;header::logo::accueil&quot;, &quot;event_type&quot; : &quot;click&quot;, &quot;event_s2&quot; : &quot;9&quot;, &quot;click_type&quot; : &quot;N&quot;}"><a href="" class="logo-site trackable custom-large-hidden" data-info="{&quot;event_name&quot; : &quot;header::logo::accueil&quot;, &quot;event_type&quot; : &quot;click&quot;, &quot;event_s2&quot; : &quot;9&quot;, &quot;click_type&quot; : &quot;N&quot;}"><a href="" class="closeFs">
Elements Describe Contents Well
Screen readers and other assistive technologies require annotations to understand otherwise ambiguous content.
0
<frame> or <iframe> elements do not have a title.
Screen reader users rely on frame titles to describe the contents of frames. Learn more.
View failing elements
<iframe id="utif_hbh-s_6f2359b6-2a65-4867-a9a2-e40cb3984e78" name="utif_hbh-s_6f2359b6-2a65-4867-a9a2-e40cb3984e78" height="110px" width="480px" tabindex="-1" marginwidth="0" marginheight="0" scrolling="no" frameborder="0" style="border: 0px; left: 50%; position: relative; margin-left: -240px;"><iframe id="utif_be-s_91a875b3-0af3-4351-87d0-a6c2194a5b2e" name="utif_be-s_91a875b3-0af3-4351-87d0-a6c2194a5b2e" height="159px" width="159px" tabindex="-1" marginwidth="0" marginheight="0" scrolling="no" frameborder="0" style="border: 0px;">
0
Form elements do not have associated labels.
Labels ensure that form controls are announced properly by assistive technologies, like screen readers. Learn more.
View failing elements
<select id="selectRegion" class="select" onchange="xt_click('this','C','1','accueil::selection_region::lien_textuel::'+this.options[this.selectedIndex].getAttribute('data-region'),'N');this.options[this.selectedIndex].value &amp;&amp; (window.location = this.options[this.selectedIndex].value);">
Color Contrast Is Satisfactory
Screen readers and other assistive technologies require annotations to understand otherwise ambiguous content.
0
Background and foreground colors do not have a sufficient contrast ratio.
Low-contrast text is difficult or impossible for many users to read. Learn more.
View failing elements
<a id="appRedirect" target="_blank" class="button-blue fr trackable" data-info="{&quot;event_name&quot; : &quot;bandeau::accueil::utiliser&quot;, &quot;event_type&quot; : &quot;click&quot;, &quot;click_type&quot; : &quot;N&quot;, &quot;event_s2&quot; : &quot;1&quot;}" href="https://play.google.com/store/apps/details?id=fr.leboncoin&amp;hl=en"><a class="displayMenu button-white-mobile custom-large-hidden"><a href="//www.leboncoin.fr/ai" class="button-blue full mlw trackable" data-info="{&quot;event_name&quot; : &quot;accueil::depot_annonce&quot;, &quot;event_type&quot; : &quot;click&quot;, &quot;event_s2&quot; : &quot;1&quot;, &quot;click_type&quot; : &quot;N&quot;}"><button data-url="//www.leboncoin.fr/annonces/offres/" id="geolocMain" class="button-blue button-secondary launchGeoloc full mlw trackable" data-info="{&quot;event_name&quot; : &quot;accueil::autour_de_moi&quot;, &quot;event_type&quot; : &quot;click&quot;, &quot;event_s2&quot; : &quot;1&quot;, &quot;click_type&quot; : &quot;N&quot;}">
Page Specifies Valid Language
Screen readers and other assistive technologies require annotations to understand otherwise ambiguous content.
0
<html> element does not have a [lang] attribute.
If a page doesn't specify a lang attribute, a screen reader assumes that the page is in the default language that the user chose when setting up the screen reader. If the page isn't actually in the default language, then the screen reader might not announce the page's text correctly. Learn more.
View failing elements
<html class=" js flexbox flexboxlegacy canvas canvastext webgl touch geolocation postmessage websqldatabase indexeddb hashchange history draganddrop websockets rgba hsla multiplebgs backgroundsize borderimage borderradius boxshadow textshadow opacity cssanimations csscolumns cssgradients cssreflections csstransforms csstransforms3d csstransitions fontface generatedcontent video audio localstorage sessionstorage webworkers applicationcache svg inlinesvg smil svgclippaths" style="">
Meta Tags Used Properly
Screen readers and other assistive technologies require annotations to understand otherwise ambiguous content.
0
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a web page. Learn more.
View failing elements
<meta name="viewport" content="width=device-width, initial-scale=1.0, maximum-scale=1.0, user-scalable=0">
7 Passed Audits
Elements Use Attributes Correctly
Screen readers and other assistive technologies require annotations to understand otherwise ambiguous content.
100
[accesskey] values are unique.
Access keys let users quickly focus a part of the page. For proper navigation, each access key must be unique. Learn more.
100
<audio> elements contain a <track> element with [kind="captions"].
Captions make audio elements usable for deaf or hearing-impaired users, providing critical information such as who is talking, what they're saying, and other non-speech information. Learn more.
100
<input type="image"> elements have [alt] text.
When an image is being used as an `<input>` button, providing alternative text can help screen reader users understand the purpose of the button. Learn more.
100
No element has a [tabindex] value greater than 0.
A value greater than 0 implies an explicit navigation ordering. Although technically valid, this often creates frustrating experiences for users who rely on assistive technologies. Learn more.
100
Cells in a <table> element that use the [headers] attribute only refer to other cells of that same table.
Screen readers have features to make navigating tables easier. Ensuring `<td>` cells using the `headers]` attribute only refer to other cells in the same table may improve the experience for screen reader users. [Learn more.
100
<th> elements and elements with [role="columnheader"/"rowheader"] have data cells they describe.
Screen readers have features to make navigating tables easier. Ensuring table headers always refer to some set of cells may improve the experience for screen reader users. Learn more.
ARIA Attributes Follow Best Practices
Screen readers and other assistive technologies require annotations to understand otherwise ambiguous content.
100
[aria-*] attributes match their roles.
Each ARIA `role` supports a specific subset of `aria-*` attributes. Mismatching these invalidates the `aria-*` attributes. Learn more.
100
[role]s have all required [aria-*] attributes.
Some ARIA roles have required attributes that describe the state of the element to screen readers. Learn more.
100
Elements with [role] that require specific children [role]s, are present.
Some ARIA parent roles must contain specific child roles to perform their intended accessibility functions. Learn more.
100
[role]s are contained by their required parent element.
Some ARIA child roles must be contained by specific parent roles to properly perform their intended accessibility functions. Learn more.
100
[role] values are valid.
ARIA roles must have valid values in order to perform their intended accessibility functions. Learn more.
100
[aria-*] attributes have valid values.
Assistive technologies, like screen readers, can't interpret ARIA attributes with invalid values. Learn more.
100
[aria-*] attributes are valid and not misspelled.
Assistive technologies, like screen readers, can't interpret ARIA attributes with invalid names. Learn more.
Elements Have Discernable Names
Screen readers and other assistive technologies require annotations to understand otherwise ambiguous content.
100
Buttons have an accessible name.
When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn more.
Elements Describe Contents Well
Screen readers and other assistive technologies require annotations to understand otherwise ambiguous content.
100
The page contains a heading, skip link, or landmark region.
Adding ways to bypass repetitive content lets keyboard users navigate the page more efficiently. Learn more.
100
Document has a <title> element.
Screen reader users use page titles to get an overview of the contents of the page. Learn more.
100
Presentational <table> elements avoid using <th>, <caption> or the [summary] attribute.
A table being used for layout purposes should not include data elements, such as the th or caption elements or the summary attribute, because this can create a confusing experience for screen reader users. Learn more.
100
<object> elements have [alt] text.
Screen readers cannot translate non-text content. Adding alt text to `<object>` elements helps screen readers convey meaning to users. Learn more.
100
<video> elements contain a <track> element with [kind="captions"].
When a video provides a caption it is easier for deaf and hearing impaired users to access its information. Learn more.
100
<video> elements contain a <track> element with [kind="description"].
Audio descriptions provide relevant information for videos that dialogue cannot, such as facial expressions and scenes. Learn more.
Elements Are Well Structured
Screen readers and other assistive technologies require annotations to understand otherwise ambiguous content.
100
<dl>'s contain only properly-ordered <dt> and <dd> groups, <script> or <template> elements.
When definition lists are not properly marked up, screen readers may produce confusing or inaccurate output. Learn more.
100
Definition list items are wrapped in <dl> elements.
Definition list items (`<dt>` and `<dd>`) must be wrapped in a parent `<dl>` element to ensure that screen readers can properly announce them. Learn more.
100
[id] attributes on the page are unique.
The value of an id attribute must be unique to prevent other instances from being overlooked by assistive technologies. Learn more.
100
Lists contain only <li> elements and script supporting elements (<script> and <template>).
Screen readers have a specific way of announcing lists. Ensuring proper list structure aids screen reader output. Learn more.
100
List items (<li>) are contained within <ul> or <ol> parent elements.
Screen readers require list items (`<li>`) to be contained within a parent `<ul>` or `<ol>` to be announced properly. Learn more.
Page Specifies Valid Language
Screen readers and other assistive technologies require annotations to understand otherwise ambiguous content.
100
<html> element has a valid value for its [lang] attribute.
Specifying a valid BCP 47 language helps screen readers announce text properly. Learn more.
100
[lang] attributes have a valid value.
Specifying a valid BCP 47 language on elements helps ensure that text is pronounced correctly by a screen reader. Learn more.
Meta Tags Used Properly
Screen readers and other assistive technologies require annotations to understand otherwise ambiguous content.
100
The document does not use <meta http-equiv="refresh">.
Users do not expect a page to refresh automatically, and doing so will move focus back to the top of the page. This may create a frustrating or confusing experience. Learn more.
62
Best Practices
We've compiled some recommendations for modernizing your web app and avoiding performance pitfalls. These audits do not affect your score but are worth a look.
5 failed audits
0
Does not use HTTP/2 for all of its resources: 1 request was not handled over HTTP/2
HTTP/2 offers many benefits over HTTP/1.1, including binary headers, multiplexing, and server push. Learn more.
View Details
URL
Protocol
/
http/1.1
0
Does not use passive listeners to improve scrolling performance
Consider marking your touch and wheel event listeners as `passive` to improve your page's scroll performance. Learn more.
View Details
URL
Location
/js/beta_base_70959.js
line: 6
0
Uses document.write()
For users on slow connections, external scripts dynamically injected via `document.write()` can delay page load by tens of seconds. Learn more.
View Details
URL
Location
…0.7.3/ast.js
line: 2
…0.7.3/ast.js
line: 2
/
line: 0
/
line: 0
0
Does not open external anchors using rel="noopener"
Open new tabs using `rel="noopener"` to improve performance and prevent security vulnerabilities. Learn more.
View Details
URL
Target
Rel
…apps/details?id=fr.leboncoin&hl=en
_blank
/
_blank
/
_blank
//www.leboncoin.fr/
_blank
/
_blank
…leboncoin/id484115113?mt=8
_blank
…apps/details?id=fr.leboncoin
_blank
/
_blank
/
_blank
/
_blank
/
_blank
/
_blank
/
_blank
/
_blank
/
_blank
/
_blank
/
_blank
/
_blank
/
_blank
/
_blank
/
_blank
/
_blank
/
_blank
/
_blank
/
_blank
/
_blank
/
_blank
/
_blank
/
_blank
/
_blank
/
_blank
/
_blank
/
_blank
/?utm_source=partner_lbc
_blank
/?utm_source=partner_lbc
_blank
/
_blank
…leboncoin/1565057520410527
_blank
/leboncoin/
_blank
Lighthouse was unable to determine the destination of some anchor tags. If they are not used as hyperlinks, consider removing the _blank target.
0
Manifest's short_name will be truncated when displayed on homescreen
Make your app's `short_name` fewer than 12 characters to ensure that it's not truncated on homescreens. Learn more.
8 Passed Audits
100
Avoids Application Cache
Application Cache is deprecated. Learn more.
100
Avoids WebSQL DB
Web SQL is deprecated. Consider using IndexedDB instead. Learn more.
100
Uses HTTPS
All sites should be protected with HTTPS, even ones that don't handle sensitive data. HTTPS prevents intruders from tampering with or passively listening in on the communications between your app and your users, and is a prerequisite for HTTP/2 and many new web platform APIs. Learn more.
100
Avoids Mutation Events in its own scripts
Mutation Events are deprecated and harm performance. Consider using Mutation Observers instead. Learn more.
100
Avoids requesting the geolocation permission on page load
Users are mistrustful of or confused by sites that request their location without context. Consider tying the request to user gestures instead. Learn more.
100
Avoids requesting the notification permission on page load
Users are mistrustful of or confused by sites that request to send notifications without context. Consider tying the request to user gestures instead. Learn more.
100
Avoids deprecated APIs
Deprecated APIs will eventually be removed from the browser. Learn more.
100
Allows users to paste into password fields