PageSpeed Insights logo
PageSpeed Insights
PageSpeed Insights
This site uses cookies from Google to deliver its services and to analyze traffic.
Report from Feb 17, 2025, 8:00:27 AM
Discover what your real users are experiencing
Core Web Vitals Assessment: Failed
Largest Contentful Paint (LCP)
2.7 s
Page LoadsGood (≤ 2.5 s)70%Needs Improvement (2.5 s - 4 s)19%Poor (> 4 s)11%75th Percentile - 2.7 sCore Web Vital
Interaction to Next Paint (INP)
469 ms
Page LoadsGood (≤ 200 ms)30%Needs Improvement (200 ms - 500 ms)47%Poor (> 500 ms)23%75th Percentile - 469 msCore Web Vital
Cumulative Layout Shift (CLS)
0.02
Page LoadsGood (≤ 0.1)81%Needs Improvement (0.1 - 0.25)12%Poor (> 0.25)6%75th Percentile - 0.02Core Web Vital
Other Notable Metrics
First Contentful Paint (FCP)
2.2 s
Page LoadsGood (≤ 1.8 s)61%Needs Improvement (1.8 s - 3 s)26%Poor (> 3 s)13%75th Percentile - 2.2 s 
Time to First Byte (TTFB)
1.4 s
Page LoadsGood (≤ 0.8 s)31%Needs Improvement (0.8 s - 1.8 s)58%Poor (> 1.8 s)12%75th Percentile - 1.4 sExperimental
Latest 28-day collection period
Various mobile devicesMany samples (Chrome UX Report)Full visit durationsVarious network connectionsAll Chrome versions
Core Web Vitals Assessment: Failed
Largest Contentful Paint (LCP)
2.5 s
Page LoadsGood (≤ 2.5 s)74%Needs Improvement (2.5 s - 4 s)17%Poor (> 4 s)8%75th Percentile - 2.5 sCore Web Vital
Interaction to Next Paint (INP)
426 ms
Page LoadsGood (≤ 200 ms)42%Needs Improvement (200 ms - 500 ms)38%Poor (> 500 ms)20%75th Percentile - 426 msCore Web Vital
Cumulative Layout Shift (CLS)
0.02
Page LoadsGood (≤ 0.1)85%Needs Improvement (0.1 - 0.25)8%Poor (> 0.25)6%75th Percentile - 0.02Core Web Vital
Other Notable Metrics
First Contentful Paint (FCP)
2.2 s
Page LoadsGood (≤ 1.8 s)62%Needs Improvement (1.8 s - 3 s)27%Poor (> 3 s)11%75th Percentile - 2.2 s 
Time to First Byte (TTFB)
1.4 s
Page LoadsGood (≤ 0.8 s)33%Needs Improvement (0.8 s - 1.8 s)54%Poor (> 1.8 s)12%75th Percentile - 1.4 sExperimental
Latest 28-day collection period
Various mobile devicesMany samples (Chrome UX Report)Full visit durationsVarious network connectionsAll Chrome versions
Diagnose performance issues
53
Performance
74
Accessibility
100
Best Practices
100
SEO
53
Performance
74
Accessibility
100
Best Practices
100
SEO
53 FCP+0LCP+0TBT+24CLS+25SI+3 Performance
Values are estimated and may vary. The performance score is calculated directly from these metrics.See calculator.
0–49 50–89 90–100
Final Screenshot
Metrics
First Contentful Paint
7.1 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more about the First Contentful Paint metric.
Largest Contentful Paint
8.8 s
Largest Contentful Paint marks the time at which the largest text or image is painted. Learn more about the Largest Contentful Paint metric
Total Blocking Time
280 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds. Learn more about the Total Blocking Time metric.
Cumulative Layout Shift
0
Cumulative Layout Shift measures the movement of visible elements within the viewport. Learn more about the Cumulative Layout Shift metric.
Speed Index
7.1 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more about the Speed Index metric.
  • Captured at Feb 17, 2025, 8:00 AM UTC
  • Emulated Moto G Power with Lighthouse 12.2.3
    Unthrottled CPU/Memory Power: 533 CPU throttling: 1.2x slowdown (Simulated) Screen emulation: 412x823, DPR 1.75 Axe version: 4.10.2
  • Single page session
    This data is taken from a single page session, as opposed to field data summarizing many sessions.
  • Initial page load
  • Slow 4G throttling
    Network throttling: 150 ms TCP RTT, 1,638.4 kb/s throughput (Simulated) Browser location: North America
  • Using HeadlessChromium 133.0.6943.53 with lr
    User agent (network): "Mozilla/5.0 (Linux; Android 11; moto g power (2022)) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/119.0.0.0 Mobile Safari/537.36"
Screenshot
Screenshot
Screenshot
Screenshot
Screenshot
Screenshot
Screenshot
Screenshot
Show audits relevant to:
Diagnostics
Largest Contentful Paint element 8,810 ms
This is the largest contentful element painted within the viewport. Learn more about the Largest Contentful Paint elementLCP
Element
En sélectionnant « Tout accepter », vous autorisez Back Market et nos partenair…
<p class="body-2 mb-16 text-center">
Phase
% of LCP
Timing
TTFB
7%
600 ms
Load Delay
0%
0 ms
Load Time
0%
0 ms
Render Delay
93%
8,210 ms
Reduce JavaScript execution time 1.4 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to reduce Javascript execution time.TBT
URL
Total CPU Time
Script Evaluation
Script Parse
Unattributable
965 ms
650 ms
0 ms
Unattributable
965 ms
650 ms
0 ms
backmarket.fr
1st party
509 ms
17 ms
62 ms
/fr-fr
(www.backmarket.fr)
509 ms
17 ms
62 ms
Google Tag Manager
tag-manager
431 ms
398 ms
12 ms
/gtm.js?auth=C_TrFGuRx…&id=GTM-N6P9JCF&preview=env-1
(www.googletagmanager.com)
431 ms
398 ms
12 ms
backmarket.com
396 ms
304 ms
0 ms
…_nuxt/ModularCa….BCfz8sCZ.js
(front-office.statics.backmarket.com)
285 ms
201 ms
0 ms
…_nuxt/TrustpilotWidget.DFlucsDh.js
(front-office.statics.backmarket.com)
111 ms
103 ms
0 ms
Minimize main-thread work 2.4 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to minimize main-thread workTBT
Category
Time Spent
Script Evaluation
1,432 ms
Other
366 ms
Style & Layout
268 ms
Parse HTML & CSS
137 ms
Script Parsing & Compilation
88 ms
Garbage Collection
82 ms
Rendering
49 ms
Reduce unused JavaScript Potential savings of 252 KiB
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.LCPFCP
URL
Transfer Size
Potential Savings
backmarket.com
387.4 KiB
131.9 KiB
…_nuxt/entry.Bs2bIzRW.js
(front-office.statics.backmarket.com)
329.8 KiB
81.8 KiB
…../../../node_modules/@backmarket/front-logger/dist/esm/index.js
16.9 KiB
7.5 KiB
…../../../node_modules/@vue/runtime-core/dist/runtime-core.esm-bundler.js
15.5 KiB
3.3 KiB
…../../../node_modules/intl-messageformat/node_modules/@formatjs/icu-messageformat-parser/lib/parser.js
4.7 KiB
3.0 KiB
…../../../node_modules/@amplitude/analytics-browser/lib/esm/config.js
2.0 KiB
1.7 KiB
…../../../node_modules/@amplitude/analytics-core/lib/esm/plugins/destination.js
1.7 KiB
1.6 KiB
…_nuxt/index.CqFBXIJu.js
(front-office.statics.backmarket.com)
57.6 KiB
50.1 KiB
…rc/ui/js/iam-css.js
9.8 KiB
9.8 KiB
…rc/ui/js/feed-css.js
2.2 KiB
2.2 KiB
…rc/Push/push-manager.js
2.1 KiB
2.1 KiB
…rc/managers/network-manager.js
1.6 KiB
1.6 KiB
…rc/triggers/triggers-provider.js
1.6 KiB
1.6 KiB
Google Tag Manager
tag-manager
262.6 KiB
120.3 KiB
/gtm.js?id=GTM-WB77QG&l=dataLayer&gtm=45He52d0v855…za200
(www.googletagmanager.com)
108.8 KiB
68.9 KiB
/gtm.js?auth=C_TrFGuRx…&id=GTM-N6P9JCF&preview=env-1
(www.googletagmanager.com)
153.7 KiB
51.4 KiB
Eliminate render-blocking resources Potential savings of 240 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles. Learn how to eliminate render-blocking resources.LCPFCP
URL
Transfer Size
Potential Savings
backmarket.com
2.2 KiB
910 ms
…_nuxt/entry.BYTEDdIC.css
(front-office.statics.backmarket.com)
0.7 KiB
750 ms
…_nuxt/RichText.BYuM95KO.css
(front-office.statics.backmarket.com)
1.5 KiB
150 ms
Serve images in next-gen formats Potential savings of 315 KiB
Image formats like WebP and AVIF often provide better compression than PNG or JPEG, which means faster downloads and less data consumption. Learn more about modern image formats.LCPFCP
NuxtUse the nuxt/image component and set format="webp". Learn more.
URL
Resource Size
Potential Savings
ctfassets.net
469.0 KiB
315.2 KiB
…2ed061d…/Thumbnail-9_16-FR.jpg
(images.ctfassets.net)
305.5 KiB
212.4 KiB
…a28cdea…/PROCESSOR….jpg
(images.ctfassets.net)
40.0 KiB
25.1 KiB
…4e3008e…/NEW-BATTERY-FR-verticale-thumbnail.jpg
(images.ctfassets.net)
35.6 KiB
22.8 KiB
…390fd72…/VDEF-Thumbail-verticale-FR.jpg
(images.ctfassets.net)
30.3 KiB
19.6 KiB
…ea71742…/Myths_about_your_tech_-_Thumbnail_-_FR.jpg
(images.ctfassets.net)
29.9 KiB
18.4 KiB
…4daf0ed…/Tips_for_laptops_-_Thumbnail_-_FR.jpg
(images.ctfassets.net)
27.6 KiB
16.9 KiB
Serve static assets with an efficient cache policy 11 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more about efficient cache policies.
URL
Cache TTL
Transfer Size
backmarket.com
86 KiB
…latest/IvarSoft-SemiBold.woff2
(static-ds.backmarket.com)
1d
28 KiB
…latest/BMDupletT….woff2
(static-ds.backmarket.com)
1d
20 KiB
…latest/BMDupletD….woff2
(static-ds.backmarket.com)
1d
20 KiB
…latest/BMDupletT….woff2
(static-ds.backmarket.com)
1d
19 KiB
backmarket.fr
1st party
24 KiB
…d2e6ccujb3mkqf.cloudfront.net/d61d0800-a563-4e5c-a1e6-652f….jpg
(www.backmarket.fr)
1d
5 KiB
…d2e6ccujb3mkqf.cloudfront.net/338165eb-e7d5-4145-8786-234d….jpg
(www.backmarket.fr)
1d
5 KiB
…d2e6ccujb3mkqf.cloudfront.net/2fd60d82-0348-4944-9734-9fb4….jpg
(www.backmarket.fr)
1d
4 KiB
…d2e6ccujb3mkqf.cloudfront.net/ef5660d2-6883-4b81-b47d-86e5….jpg
(www.backmarket.fr)
1d
3 KiB
…d2e6ccujb3mkqf.cloudfront.net/b1c177ac-ef78-4c4e-8a77-b888….jpg
(www.backmarket.fr)
1d
3 KiB
…d2e6ccujb3mkqf.cloudfront.net/afb7c00c-b020-43af-a5de-5d43….jpg
(www.backmarket.fr)
1d
3 KiB
appsflyer.com
14 KiB
/?st=banners&
(websdk.appsflyer.com)
None
14 KiB
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 about adopting passive event listeners.
Source
backmarket.com
../../../../../../node_modules/@backmarket/design-system/dist/src/components/Carousel/Carousel.vue2.js:118:33
../../../../../../node_modules/@backmarket/design-system/dist/src/components/Carousel/Carousel.vue2.js:118:98
Efficiently encode images Potential savings of 121 KiB
Optimized images load faster and consume less cellular data. Learn how to efficiently encode images.LCPFCP
NuxtUse the nuxt/image component and set the appropriate quality. Learn more.
URL
Resource Size
Potential Savings
ctfassets.net
469.0 KiB
120.7 KiB
…2ed061d…/Thumbnail-9_16-FR.jpg
(images.ctfassets.net)
305.5 KiB
82.5 KiB
…a28cdea…/PROCESSOR….jpg
(images.ctfassets.net)
40.0 KiB
10.3 KiB
…4e3008e…/NEW-BATTERY-FR-verticale-thumbnail.jpg
(images.ctfassets.net)
35.6 KiB
9.1 KiB
…390fd72…/VDEF-Thumbail-verticale-FR.jpg
(images.ctfassets.net)
30.3 KiB
8.0 KiB
…ea71742…/Myths_about_your_tech_-_Thumbnail_-_FR.jpg
(images.ctfassets.net)
29.9 KiB
5.6 KiB
…4daf0ed…/Tips_for_laptops_-_Thumbnail_-_FR.jpg
(images.ctfassets.net)
27.6 KiB
5.2 KiB
Remove duplicate modules in JavaScript bundles Potential savings of 2 KiB
Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity. LCPFCP
Source
Transfer Size
Potential Savings
Other
0 KiB
…_nuxt/entry.Bs2bIzRW.js
(front-office.statics.backmarket.com)
…_nuxt/TrustpilotWidget.DFlucsDh.js
(front-office.statics.backmarket.com)
…_nuxt/ModularCa….BCfz8sCZ.js
(front-office.statics.backmarket.com)
…_nuxt/Faq.As4M2F0b.js
(front-office.statics.backmarket.com)
…_nuxt/index.D8ZxCYCV.js
(front-office.statics.backmarket.com)
Avoid serving legacy JavaScript to modern browsers Potential savings of 25 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. However, many aren't necessary for modern browsers. For your bundled JavaScript, adopt a modern script deployment strategy using module/nomodule feature detection to reduce the amount of code shipped to modern browsers, while retaining support for legacy browsers. Learn how to use modern JavaScriptLCPFCP
URL
Potential Savings
backmarket.com
18.3 KiB
…_nuxt/Form.vue2.afXhp2pQ.js
(front-office.statics.backmarket.com)
10.8 KiB
../../../../../../node_modules/@backmarket/design-system/node_modules/core-js-pure/modules/es.object.keys.js:11:2
Object.keys
…_nuxt/entry.Bs2bIzRW.js
(front-office.statics.backmarket.com)
7.5 KiB
../../../../../../node_modules/@amplitude/analytics-connector/dist/analytics-connector.esm.js:188:4
Object.entries
…_nuxt/ArticleCardsList.EtuQa7DX.js
(front-office.statics.backmarket.com)
0.0 KiB
../../../../../../node_modules/libphonenumber-js/es6/ParseError.js:7:112
@babel/plugin-transform-classes
appsflyer.com
6.6 KiB
/?st=banners&
(websdk.appsflyer.com)
6.6 KiB
/?st=banners&:4:3745
(websdk.appsflyer.com)
Object.keys
Reduce unused CSS Potential savings of 27 KiB
Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity. Learn how to reduce unused CSS.LCPFCP
URL
Transfer Size
Potential Savings
*,:after,:before{--tw-border-spacing-x:0;--tw-border-spacing-y:0;--tw-translate-x:0;--tw-translate-…
33.6 KiB
27.2 KiB
Avoid an excessive DOM size 2,841 elements
A large DOM will increase memory usage, cause longer style calculations, and produce costly layout reflows. Learn how to avoid an excessive DOM size.TBT
Statistic
Element
Value
Total DOM Elements
2,841
Maximum DOM Depth
div.text-action-default-hi > div.flex > svg > path
<path d="M13.154 3.65c-.427-1.026-1.881-1.026-2.308 0L8.838 8.478l-5.21.418C2.519 8…">
30
Maximum Child Elements
Emplacement actuelFrancefrançais (FR)PaysAutricheDeutsch (AT)AustralieEnglish (…
<ul class="divide-static-default-low divide-y border-static-default-low border-y body…">
18
Avoid long main-thread tasks 11 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay. Learn how to avoid long main-thread tasksTBT
URL
Start Time
Duration
Unattributable
575 ms
Unattributable
12,057 ms
409 ms
Unattributable
3,067 ms
107 ms
Unattributable
2,551 ms
59 ms
Google Tag Manager
tag-manager
341 ms
/gtm.js?auth=C_TrFGuRx…&id=GTM-N6P9JCF&preview=env-1
(www.googletagmanager.com)
10,960 ms
112 ms
/gtm.js?auth=C_TrFGuRx…&id=GTM-N6P9JCF&preview=env-1
(www.googletagmanager.com)
7,502 ms
96 ms
/gtm.js?auth=C_TrFGuRx…&id=GTM-N6P9JCF&preview=env-1
(www.googletagmanager.com)
10,850 ms
81 ms
/gtm.js?auth=C_TrFGuRx…&id=GTM-N6P9JCF&preview=env-1
(www.googletagmanager.com)
7,450 ms
52 ms
backmarket.fr
1st party
139 ms
/fr-fr
(www.backmarket.fr)
2,610 ms
72 ms
/fr-fr
(www.backmarket.fr)
2,714 ms
67 ms
backmarket.com
115 ms
…_nuxt/TrustpilotWidget.DFlucsDh.js
(front-office.statics.backmarket.com)
13,774 ms
58 ms
…_nuxt/ModularCa….BCfz8sCZ.js
(front-office.statics.backmarket.com)
13,717 ms
57 ms
Minimize third-party usage Third-party code blocked the main thread for 160 ms
Third-party code can significantly impact load performance. Limit the number of redundant third-party providers and try to load third-party code after your page has primarily finished loading. Learn how to minimize third-party impact.TBT
Third-Party
Transfer Size
Main-Thread Blocking Time
Google Tag Manager
tag-manager
265 KiB
141 ms
/gtm.js?auth=C_TrFGuRx…&id=GTM-N6P9JCF&preview=env-1
(www.googletagmanager.com)
155 KiB
141 ms
/gtm.js?id=GTM-WB77QG&l=dataLayer&gtm=45He52d0v855…za200
(www.googletagmanager.com)
110 KiB
0 ms
backmarket.com
862 KiB
15 ms
…_nuxt/TrustpilotWidget.DFlucsDh.js
(front-office.statics.backmarket.com)
8 KiB
8 ms
…_nuxt/ModularCa….BCfz8sCZ.js
(front-office.statics.backmarket.com)
13 KiB
7 ms
…_nuxt/SocialMediaEmbed.BmAIYN8L.js
(front-office.statics.backmarket.com)
5 KiB
0 ms
…_nuxt/entry.Bs2bIzRW.js
(front-office.statics.backmarket.com)
339 KiB
0 ms
…_nuxt/index.CqFBXIJu.js
(front-office.statics.backmarket.com)
59 KiB
0 ms
…_nuxt/default.BvJTZVXQ.js
(front-office.statics.backmarket.com)
42 KiB
0 ms
…_nuxt/Categories.Beq3oKCm.js
(front-office.statics.backmarket.com)
40 KiB
0 ms
…_nuxt/ArticleCardsList.EtuQa7DX.js
(front-office.statics.backmarket.com)
32 KiB
0 ms
…latest/IvarSoft-SemiBold.woff2
(static-ds.backmarket.com)
28 KiB
0 ms
…latest/BMDupletT….woff2
(static-ds.backmarket.com)
20 KiB
0 ms
…latest/BMDupletD….woff2
(static-ds.backmarket.com)
20 KiB
0 ms
…_nuxt/SectionBanner.DKAl42QZ.js
(front-office.statics.backmarket.com)
19 KiB
0 ms
…latest/BMDupletT….woff2
(static-ds.backmarket.com)
19 KiB
0 ms
…_nuxt/InputSelectItem.vue.1xOyxAWy.js
(front-office.statics.backmarket.com)
19 KiB
0 ms
…_nuxt/IconMoreVertical.B3hyVza0.js
(front-office.statics.backmarket.com)
19 KiB
0 ms
…_nuxt/IconSunFace.DguFtgLq.js
(front-office.statics.backmarket.com)
17 KiB
0 ms
…_nuxt/Form.vue2.afXhp2pQ.js
(front-office.statics.backmarket.com)
17 KiB
0 ms
…_nuxt/el-GR.B0HUlPw2.js
(front-office.statics.backmarket.com)
11 KiB
0 ms
…_nuxt/ar.GHrHWN67.js
(front-office.statics.backmarket.com)
10 KiB
0 ms
…_nuxt/index.DKXniy5T.js
(front-office.statics.backmarket.com)
10 KiB
0 ms
…_nuxt/useAlgolia.BFi66Qj7.js
(front-office.statics.backmarket.com)
10 KiB
0 ms
…_nuxt/constants.DfcgOMTc.js
(front-office.statics.backmarket.com)
9 KiB
0 ms
…_nuxt/useFetchPageContent.BCCBGDsn.js
(front-office.statics.backmarket.com)
7 KiB
0 ms
…_nuxt/useFooter….Bfua1zZY.js
(front-office.statics.backmarket.com)
6 KiB
0 ms
…_nuxt/UserCommentModal.t54Dksp_.js
(front-office.statics.backmarket.com)
6 KiB
0 ms
…_nuxt/Faq.As4M2F0b.js
(front-office.statics.backmarket.com)
6 KiB
0 ms
…_nuxt/Cookies.D0NQjIDM.js
(front-office.statics.backmarket.com)
6 KiB
0 ms
…_nuxt/ProductCardCarousel.vue.qeFbQcvn.js
(front-office.statics.backmarket.com)
6 KiB
0 ms
…_nuxt/VideosBlock.B4dAMETN.js
(front-office.statics.backmarket.com)
5 KiB
0 ms
…_nuxt/Home.Dh0SfaEg.js
(front-office.statics.backmarket.com)
4 KiB
0 ms
…_nuxt/Recommendations.CmXpKmQD.js
(front-office.statics.backmarket.com)
3 KiB
0 ms
…_nuxt/Carousel.CHgz4WAQ.js
(front-office.statics.backmarket.com)
3 KiB
0 ms
…_nuxt/EnhancedCarousel.CY-p7yHT.js
(front-office.statics.backmarket.com)
3 KiB
0 ms
…_nuxt/Products.BBT9btKm.js
(front-office.statics.backmarket.com)
3 KiB
0 ms
…_nuxt/EmailCollector.ny0BrYFD.js
(front-office.statics.backmarket.com)
3 KiB
0 ms
…_nuxt/RichText.BqcuRBkr.js
(front-office.statics.backmarket.com)
3 KiB
0 ms
…_nuxt/index.D8ZxCYCV.js
(front-office.statics.backmarket.com)
3 KiB
0 ms
…_nuxt/recommend….DDeUi7cy.js
(front-office.statics.backmarket.com)
3 KiB
0 ms
…_nuxt/Reviews.BoNLJ5AQ.js
(front-office.statics.backmarket.com)
3 KiB
0 ms
…_nuxt/ModularCardImage.DDnj35Vm.js
(front-office.statics.backmarket.com)
2 KiB
0 ms
…_nuxt/algoliaFunctions.DY2th9gi.js
(front-office.statics.backmarket.com)
2 KiB
0 ms
…_nuxt/MobileAppBanner.vue.CmpP_UJm.js
(front-office.statics.backmarket.com)
2 KiB
0 ms
…_nuxt/Media.CYxgitS-.js
(front-office.statics.backmarket.com)
2 KiB
0 ms
…header/Logo.svg
(front-office.statics.backmarket.com)
2 KiB
0 ms
…_nuxt/SkinnyBanner.vue.C_t3iY7Z.js
(front-office.statics.backmarket.com)
2 KiB
0 ms
…_nuxt/RichText.BYuM95KO.css
(front-office.statics.backmarket.com)
1 KiB
0 ms
…v8.6.0/backmarket.fontface.css
(static-ds.backmarket.com)
1 KiB
0 ms
…_nuxt/useLogout.DME5LXjP.js
(front-office.statics.backmarket.com)
1 KiB
0 ms
…meta/6c3f9c32-276c-4c20-9915-4882d132d2b9.json
(front-office.statics.backmarket.com)
1 KiB
0 ms
…_nuxt/UserCommentModal.OMJl9RBk.css
(front-office.statics.backmarket.com)
1 KiB
0 ms
…_nuxt/default.C26oZ689.css
(front-office.statics.backmarket.com)
1 KiB
0 ms
…_nuxt/Media.CwEUDodq.css
(front-office.statics.backmarket.com)
1 KiB
0 ms
…_nuxt/Reviews.Dl7AnzoM.css
(front-office.statics.backmarket.com)
1 KiB
0 ms
…_nuxt/EnhancedCarousel.DqqW-XG_.css
(front-office.statics.backmarket.com)
1 KiB
0 ms
…_nuxt/entry.BYTEDdIC.css
(front-office.statics.backmarket.com)
1 KiB
0 ms
ctfassets.net
472 KiB
0 ms
…2ed061d…/Thumbnail-9_16-FR.jpg
(images.ctfassets.net)
306 KiB
0 ms
…a28cdea…/PROCESSOR….jpg
(images.ctfassets.net)
41 KiB
0 ms
…4e3008e…/NEW-BATTERY-FR-verticale-thumbnail.jpg
(images.ctfassets.net)
36 KiB
0 ms
…390fd72…/VDEF-Thumbail-verticale-FR.jpg
(images.ctfassets.net)
31 KiB
0 ms
…ea71742…/Myths_about_your_tech_-_Thumbnail_-_FR.jpg
(images.ctfassets.net)
30 KiB
0 ms
…4daf0ed…/Tips_for_laptops_-_Thumbnail_-_FR.jpg
(images.ctfassets.net)
28 KiB
0 ms
appsflyer.com
14 KiB
0 ms
/?st=banners&
(websdk.appsflyer.com)
14 KiB
0 ms
backmarket.io
0 KiB
0 ms
https://noodle.backmarket.io
0 KiB
0 ms
Initial server response time was short Root document took 280 ms
Keep the server response time for the main document short because all other requests depend on it. Learn more about the Time to First Byte metric.LCPFCP
URL
Time Spent
backmarket.fr
1st party
280 ms
/fr-fr
(www.backmarket.fr)
280 ms
Avoid large layout shifts 1 layout shift found
These are the largest layout shifts observed on the page. Each table item represents a single layout shift, and shows the element that shifted the most. Below each item are possible root causes that led to the layout shift. Some of these layout shifts may not be included in the CLS metric value due to windowing. Learn how to improve CLSCLS
Element
Layout shift score
Achetez et revendez vos appareils à des pros du reconditionné.
<div class="heading-2 text-center md:line-clamp-2">
0.000
…latest/BMDupletD….woff2
(static-ds.backmarket.com)
Web font loaded
…latest/IvarSoft-SemiBold.woff2
(static-ds.backmarket.com)
Web font loaded
…latest/BMDupletT….woff2
(static-ds.backmarket.com)
Web font loaded
…latest/BMDupletT….woff2
(static-ds.backmarket.com)
Web font loaded
…_nuxt/Reviews.Dl7AnzoM.css
(front-office.statics.backmarket.com)
A late network request adjusted the page layout
…_nuxt/UserCommentModal.OMJl9RBk.css
(front-office.statics.backmarket.com)
A late network request adjusted the page layout
…_nuxt/RichText.BYuM95KO.css
(front-office.statics.backmarket.com)
A late network request adjusted the page layout
…_nuxt/entry.BYTEDdIC.css
(front-office.statics.backmarket.com)
A late network request adjusted the page layout
Avoid non-composited animations 2 animated elements found
Animations which are not composited can be janky and increase CLS. Learn how to avoid non-composited animationsCLS
Element
Name
Tout accepter
<button aria-disabled="false" class="focus-visible-outline-default-hi rounded-sm relative max-w-full select-non…" data-qa="accept-cta" type="button">
Unsupported CSS Property: background-color
background-color
Unsupported CSS Property: color
color
Définir les préférences
<button aria-disabled="false" class="focus-visible-outline-default-hi rounded-sm relative max-w-full select-non…" type="button">
Unsupported CSS Property: border-right-color
border-right-color
Unsupported CSS Property: border-top-color
border-top-color
Unsupported CSS Property: background-color
background-color
Unsupported CSS Property: color
color
Unsupported CSS Property: border-bottom-color
border-bottom-color
Unsupported CSS Property: border-left-color
border-left-color
Avoids enormous network payloads Total size was 2,306 KiB
Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.
URL
Transfer Size
backmarket.fr
1st party
455.7 KiB
/fr-fr
(www.backmarket.fr)
367.9 KiB
…15019d2…/App_incentive_translations_-_HP_Banner_-_Mobile_-….jpg
(www.backmarket.fr)
45.9 KiB
…7f3640a…/Mobile.jpg
(www.backmarket.fr)
42.0 KiB
backmarket.com
440.0 KiB
…_nuxt/entry.Bs2bIzRW.js
(front-office.statics.backmarket.com)
338.9 KiB
…_nuxt/index.CqFBXIJu.js
(front-office.statics.backmarket.com)
58.8 KiB
…_nuxt/default.BvJTZVXQ.js
(front-office.statics.backmarket.com)
42.4 KiB
ctfassets.net
346.5 KiB
…2ed061d…/Thumbnail-9_16-FR.jpg
(images.ctfassets.net)
306.0 KiB
…a28cdea…/PROCESSOR….jpg
(images.ctfassets.net)
40.5 KiB
Google Tag Manager
tag-manager
264.7 KiB
/gtm.js?auth=C_TrFGuRx…&id=GTM-N6P9JCF&preview=env-1
(www.googletagmanager.com)
154.8 KiB
/gtm.js?id=GTM-WB77QG&l=dataLayer&gtm=45He52d0v855…za200
(www.googletagmanager.com)
109.9 KiB
Avoid chaining critical requests 4 chains found
The Critical Request Chains below show you what resources are loaded with a high priority. Consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load. Learn how to avoid chaining critical requests.
Maximum critical path latency: 509.993 ms
Initial Navigation
/fr-fr
(www.backmarket.fr)
…_nuxt/entry.BYTEDdIC.css
(front-office.statics.backmarket.com)
- 25.887 ms, 0.69 KiB
…_nuxt/RichText.BYuM95KO.css
(front-office.statics.backmarket.com)
- 26.896 ms, 1.48 KiB
…_nuxt/Reviews.Dl7AnzoM.css
(front-office.statics.backmarket.com)
- 46.931 ms, 0.75 KiB
…_nuxt/UserCommentModal.OMJl9RBk.css
(front-office.statics.backmarket.com)
- 28.433 ms, 0.91 KiB
More information about the performance of your application. These numbers don't directly affect the Performance score.
Passed audits (16)
Show Hide
Properly size images
Serve images that are appropriately-sized to save cellular data and improve load time. Learn how to size images.LCPFCP
NuxtUse the nuxt/image component and set the appropriate sizes. Learn more.
Defer offscreen images
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive. Learn how to defer offscreen images.LCPFCP
NuxtUse the nuxt/image component and set loading="lazy" for offscreen images. Learn more.
Minify CSS
Minifying CSS files can reduce network payload sizes. Learn how to minify CSS.LCPFCP
Minify JavaScript
Minifying JavaScript files can reduce payload sizes and script parse time. Learn how to minify JavaScript.LCPFCP
Enable text compression
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. Learn more about text compression.LCPFCP
Preconnect to required origins
Consider adding preconnect or dns-prefetch resource hints to establish early connections to important third-party origins. Learn how to preconnect to required origins.LCPFCP
Avoid multiple page redirects
Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.LCPFCP
Use video formats for animated content
Large GIFs are inefficient for delivering animated content. Consider using MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF to save network bytes. Learn more about efficient video formatsLCPFCP
Preload Largest Contentful Paint image
If the LCP element is dynamically added to the page, you should preload the image in order to improve LCP. Learn more about preloading LCP elements.LCP
NuxtUse the nuxt/image component and specify preload for LCP image. Learn more.
User Timing marks and measures
Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences. Learn more about User Timing marks.
All text remains visible during webfont loads
Leverage the font-display CSS feature to ensure text is user-visible while webfonts are loading. Learn more about font-display.
Lazy load third-party resources with facades
Some third-party embeds can be lazy loaded. Consider replacing them with a facade until they are required. Learn how to defer third-parties with a facade.TBT
Largest Contentful Paint image was not lazily loaded
Above-the-fold images that are lazily loaded render later in the page lifecycle, which can delay the largest contentful paint. Learn more about optimal lazy loading.LCP
Avoids document.write()
For users on slow connections, external scripts dynamically injected via document.write() can delay page load by tens of seconds. Learn how to avoid document.write().
Image elements have explicit width and height
Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensionsCLS
NuxtUse the nuxt/image component and specify explicit width and height. Learn more.
Has a <meta name="viewport"> tag with width or initial-scale
A <meta name="viewport"> not only optimizes your app for mobile screen sizes, but also prevents a 300 millisecond delay to user input. Learn more about using the viewport meta tag.
74
Accessibility
These checks highlight opportunities to improve the accessibility of your web app. Automatic detection can only detect a subset of issues and does not guarantee the accessibility of your web app, so manual testing is also encouraged.
ARIA
[aria-*] attributes do not match their roles
Each ARIA role supports a specific subset of aria-* attributes. Mismatching these invalidates the aria-* attributes. Learn how to match ARIA attributes to their roles.
Failing Elements
div.z-[1] > form.border-action-default-low > div.text-action-default-hi > input#searchBar-input
<input id="searchBar-input" aria-describedby="resultsListBoxAlert" aria-expanded="false" autocomplete="off" autocorrect="off" class="text-action-default-hi peer body-1 h-[38px] flex-1 appearance-none outline…" data-qa="search-bar-input" name="q" placeholder="Que cherchez-vous ?" role="searchbox" type="text" value="">
Elements with role="dialog" or role="alertdialog" do not have accessible names.
ARIA dialog elements without accessible names may prevent screen readers users from discerning the purpose of these elements. Learn how to make ARIA dialog elements more accessible.
Failing Elements
En sélectionnant « Tout accepter », vous autorisez Back Market et nos partenair…
<div aria-labelledby="modalTitle" aria-modal="true" class="bg-surface-default-hi rounded-t-lg fixed bottom-0 left-0 max-h-full w-full…" role="dialog" tabindex="0">
Elements use prohibited ARIA attributes
Using ARIA attributes in roles where they are prohibited can mean that important information is not communicated to users of assistive technologies. Learn more about prohibited ARIA roles.
Failing Elements
div.relative > div.relative > div.sr-only > span
<span aria-labelledby="cms-carousel">
div.relative > div.relative > div.sr-only > span
<span aria-labelledby="cms-carousel">
ARIA IDs are unique
The value of an ARIA ID must be unique to prevent other instances from being overlooked by assistive technologies. Learn how to fix duplicate ARIA IDs.
Failing Elements
FR - Samsung Galaxy
<li aria-hidden="false" class="flex w-full list-none justify-center motion-safe:animate-fade-in block" id="cms-carousel">
What is Verified Refurbished
<li id="cms-carousel" aria-hidden="false" class="flex w-full list-none justify-center motion-safe:animate-fade-in block">
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.
Names and labels
Buttons do not 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 how to make buttons more accessible.
Failing Elements
div > header#header > div.flex > button.block
<button class="block flex-1 grow md:hidden" type="button">
div.flex > div._invisibleScrollBar_nw9fi_2 > div.flex > button.bg-surface-default-low
<button class="bg-surface-default-low rounded-lg h-48 w-72 cursor-pointer border hover:bo…" data-test="recommendation-thumbnail" type="button">
div.flex > div._invisibleScrollBar_nw9fi_2 > div.flex > button.bg-surface-default-low
<button class="bg-surface-default-low rounded-lg h-48 w-72 cursor-pointer border hover:bo…" data-test="recommendation-thumbnail" type="button">
Image elements have [alt] attributes that are redundant text.
Informative elements should aim for short, descriptive alternative text. Alternative text that is exactly the same as the text adjacent to the link or image is potentially confusing for screen reader users, because the text will be read twice. Learn more about the alt attribute.
Failing Elements
Macbook
<img class="block w-full object-cover rounded-lg h-auto max-h-full max-w-full leading-…" alt="Macbook" decoding="async" height="180" loading="eager" sizes="100vw" src="https://www.backmarket.fr/cdn-cgi/image/format%3Dauto%2Cquality%3D75%2Cwid…" srcset="/cdn-cgi/image/format%3Dauto%2Cquality%3D75%2Cwidth%3D260/https://images.c…" width="268">
iPad
<img class="block w-full object-cover rounded-lg h-auto max-h-full max-w-full leading-…" alt="iPad" decoding="async" height="180" loading="eager" sizes="100vw" src="https://www.backmarket.fr/cdn-cgi/image/format%3Dauto%2Cquality%3D75%2Cwid…" srcset="/cdn-cgi/image/format%3Dauto%2Cquality%3D75%2Cwidth%3D260/https://images.c…" width="268">
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.
Best practices
[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 about the viewport meta tag.
Failing Elements
head > meta
<meta name="viewport" content="width=device-width, initial-scale=1, maximum-scale=1">
Touch targets do not have sufficient size or spacing.
Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.
Failing Elements
Diapositive 1
<button aria-current="false" aria-label="Diapositive 1" class="focus-visible-outline-default-hi relative cursor-pointer appearance-none o…" data-slide="0" type="button">
Diapositive 2
<button aria-current="true" aria-label="Diapositive 2" class="focus-visible-outline-default-hi relative cursor-pointer appearance-none o…" data-slide="1" type="button">
Diapositive 2
<button aria-current="true" aria-label="Diapositive 2" class="focus-visible-outline-default-hi relative cursor-pointer appearance-none o…" data-slide="1" type="button">
Diapositive 1
<button aria-current="false" aria-label="Diapositive 1" class="focus-visible-outline-default-hi relative cursor-pointer appearance-none o…" data-slide="0" type="button">
Diapositive 3
<button aria-current="false" aria-label="Diapositive 3" class="focus-visible-outline-default-hi relative cursor-pointer appearance-none o…" data-slide="2" type="button">
Diapositive 3
<button aria-current="false" aria-label="Diapositive 3" class="focus-visible-outline-default-hi relative cursor-pointer appearance-none o…" data-slide="2" type="button">
Diapositive 2
<button aria-current="true" aria-label="Diapositive 2" class="focus-visible-outline-default-hi relative cursor-pointer appearance-none o…" data-slide="1" type="button">
Diapositive 4
<button aria-current="false" aria-label="Diapositive 4" class="focus-visible-outline-default-hi relative cursor-pointer appearance-none o…" data-slide="3" type="button">
Diapositive 4
<button aria-current="false" aria-label="Diapositive 4" class="focus-visible-outline-default-hi relative cursor-pointer appearance-none o…" data-slide="3" type="button">
Diapositive 3
<button aria-current="false" aria-label="Diapositive 3" class="focus-visible-outline-default-hi relative cursor-pointer appearance-none o…" data-slide="2" type="button">
Diapositive 5
<button aria-current="false" aria-label="Diapositive 5" class="focus-visible-outline-default-hi relative cursor-pointer appearance-none o…" data-slide="4" type="button">
Diapositive 5
<button aria-current="false" aria-label="Diapositive 5" class="focus-visible-outline-default-hi relative cursor-pointer appearance-none o…" data-slide="4" type="button">
Diapositive 4
<button aria-current="false" aria-label="Diapositive 4" class="focus-visible-outline-default-hi relative cursor-pointer appearance-none o…" data-slide="3" type="button">
Diapositive 6
<button aria-current="false" aria-label="Diapositive 6" class="focus-visible-outline-default-hi relative cursor-pointer appearance-none o…" data-slide="5" type="button">
Diapositive 6
<button aria-current="false" aria-label="Diapositive 6" class="focus-visible-outline-default-hi relative cursor-pointer appearance-none o…" data-slide="5" type="button">
Diapositive 5
<button aria-current="false" aria-label="Diapositive 5" class="focus-visible-outline-default-hi relative cursor-pointer appearance-none o…" data-slide="4" type="button">
Diapositive 7
<button aria-current="false" aria-label="Diapositive 7" class="focus-visible-outline-default-hi relative cursor-pointer appearance-none o…" data-slide="6" type="button">
Diapositive 7
<button aria-current="false" aria-label="Diapositive 7" class="focus-visible-outline-default-hi relative cursor-pointer appearance-none o…" data-slide="6" type="button">
Diapositive 6
<button aria-current="false" aria-label="Diapositive 6" class="focus-visible-outline-default-hi relative cursor-pointer appearance-none o…" data-slide="5" type="button">
Diapositive 1
<button aria-current="true" aria-label="Diapositive 1" class="focus-visible-outline-default-hi relative cursor-pointer appearance-none o…" data-slide="0" type="button">
Diapositive 2
<button aria-current="false" aria-label="Diapositive 2" class="focus-visible-outline-default-hi relative cursor-pointer appearance-none o…" data-slide="1" type="button">
Diapositive 2
<button aria-current="false" aria-label="Diapositive 2" class="focus-visible-outline-default-hi relative cursor-pointer appearance-none o…" data-slide="1" type="button">
Diapositive 1
<button aria-current="true" aria-label="Diapositive 1" class="focus-visible-outline-default-hi relative cursor-pointer appearance-none o…" data-slide="0" type="button">
Diapositive 3
<button aria-current="false" aria-label="Diapositive 3" class="focus-visible-outline-default-hi relative cursor-pointer appearance-none o…" data-slide="2" type="button">
Diapositive 3
<button aria-current="false" aria-label="Diapositive 3" class="focus-visible-outline-default-hi relative cursor-pointer appearance-none o…" data-slide="2" type="button">
Diapositive 2
<button aria-current="false" aria-label="Diapositive 2" class="focus-visible-outline-default-hi relative cursor-pointer appearance-none o…" data-slide="1" type="button">
Diapositive 4
<button aria-current="false" aria-label="Diapositive 4" class="focus-visible-outline-default-hi relative cursor-pointer appearance-none o…" data-slide="3" type="button">
Diapositive 4
<button aria-current="false" aria-label="Diapositive 4" class="focus-visible-outline-default-hi relative cursor-pointer appearance-none o…" data-slide="3" type="button">
Diapositive 3
<button aria-current="false" aria-label="Diapositive 3" class="focus-visible-outline-default-hi relative cursor-pointer appearance-none o…" data-slide="2" type="button">
Diapositive 5
<button aria-current="false" aria-label="Diapositive 5" class="focus-visible-outline-default-hi relative cursor-pointer appearance-none o…" data-slide="4" type="button">
Diapositive 5
<button aria-current="false" aria-label="Diapositive 5" class="focus-visible-outline-default-hi relative cursor-pointer appearance-none o…" data-slide="4" type="button">
Diapositive 4
<button aria-current="false" aria-label="Diapositive 4" class="focus-visible-outline-default-hi relative cursor-pointer appearance-none o…" data-slide="3" type="button">
These items highlight common accessibility best practices.
Additional items to manually check (10)
Show Hide
Interactive controls are keyboard focusable
Custom interactive controls are keyboard focusable and display a focus indicator. Learn how to make custom controls focusable.
Interactive elements indicate their purpose and state
Interactive elements, such as links and buttons, should indicate their state and be distinguishable from non-interactive elements. Learn how to decorate interactive elements with affordance hints.
The page has a logical tab order
Tabbing through the page follows the visual layout. Users cannot focus elements that are offscreen. Learn more about logical tab ordering.
Visual order on the page follows DOM order
DOM order matches the visual order, improving navigation for assistive technology. Learn more about DOM and visual ordering.
User focus is not accidentally trapped in a region
A user can tab into and out of any control or region without accidentally trapping their focus. Learn how to avoid focus traps.
The user's focus is directed to new content added to the page
If new content, such as a dialog, is added to the page, the user's focus is directed to it. Learn how to direct focus to new content.
HTML5 landmark elements are used to improve navigation
Landmark elements (<main>, <nav>, etc.) are used to improve the keyboard navigation of the page for assistive technology. Learn more about landmark elements.
Offscreen content is hidden from assistive technology
Offscreen content is hidden with display: none or aria-hidden=true. Learn how to properly hide offscreen content.
Custom controls have associated labels
Custom interactive controls have associated labels, provided by aria-label or aria-labelledby. Learn more about custom controls and labels.
Custom controls have ARIA roles
Custom interactive controls have appropriate ARIA roles. Learn how to add roles to custom controls.
These items address areas which an automated testing tool cannot cover. Learn more in our guide on conducting an accessibility review.
Passed audits (21)
Show Hide
[aria-hidden="true"] is not present on the document <body>
Assistive technologies, like screen readers, work inconsistently when aria-hidden="true" is set on the document <body>. Learn how aria-hidden affects the document body.
[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 about roles and required attributes.
[aria-*] attributes have valid values
Assistive technologies, like screen readers, can't interpret ARIA attributes with invalid values. Learn more about valid values for ARIA attributes.
[aria-*] attributes are valid and not misspelled
Assistive technologies, like screen readers, can't interpret ARIA attributes with invalid names. Learn more about valid ARIA attributes.
Image elements have [alt] attributes
Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the alt attribute.
ARIA attributes are used as specified for the element's role
Some ARIA attributes are only allowed on an element under certain conditions. Learn more about conditional ARIA attributes.
[aria-hidden="true"] elements do not contain focusable descendents
Focusable descendents within an [aria-hidden="true"] element prevent those interactive elements from being available to users of assistive technologies like screen readers. Learn how aria-hidden affects focusable elements.
[role] values are valid
ARIA roles must have valid values in order to perform their intended accessibility functions. Learn more about valid ARIA roles.
Background and foreground colors have a sufficient contrast ratio
Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.
Document has a <title> element
The title gives screen reader users an overview of the page, and search engine users rely on it heavily to determine if a page is relevant to their search. Learn more about document titles.
<html> element has 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 about the lang attribute.
<html> element has a valid value for its [lang] attribute
Specifying a valid BCP 47 language helps screen readers announce text properly. Learn how to use the lang attribute.
Form elements have associated labels
Labels ensure that form controls are announced properly by assistive technologies, like screen readers. Learn more about form element labels.
Links are distinguishable without relying on color.
Low-contrast text is difficult or impossible for many users to read. Link text that is discernible improves the experience for users with low vision. Learn how to make links distinguishable.
Links have a discernible 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 how to make links accessible.
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 about proper list structure.
List items (<li>) are contained within <ul>, <ol> or <menu> parent elements
Screen readers require list items (<li>) to be contained within a parent <ul>, <ol> or <menu> to be announced properly. Learn more about proper list structure.
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 about the tabindex attribute.
Heading elements appear in a sequentially-descending order
Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.
Uses ARIA roles only on compatible elements
Many HTML elements can only be assigned certain ARIA roles. Using ARIA roles where they are not allowed can interfere with the accessibility of the web page. Learn more about ARIA roles.
Deprecated ARIA roles were not used
Deprecated ARIA roles may not be processed correctly by assistive technology. Learn more about deprecated ARIA roles.
Not applicable (28)
Show Hide
[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 about access keys.
button, link, and menuitem elements have accessible names
When an element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn how to make command elements more accessible.
ARIA input fields have accessible names
When an input field doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn more about input field labels.
ARIA meter elements have accessible names
When a meter element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn how to name meter elements.
ARIA progressbar elements have accessible names
When a progressbar element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn how to label progressbar elements.
Elements with an ARIA [role] that require children to contain a specific [role] have all required children.
Some ARIA parent roles must contain specific child roles to perform their intended accessibility functions. Learn more about roles and required children elements.
[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 about ARIA roles and required parent element.
Elements with the role=text attribute do not have focusable descendents.
Adding role=text around a text node split by markup enables VoiceOver to treat it as one phrase, but the element's focusable descendents will not be announced. Learn more about the role=text attribute.
ARIA toggle fields have accessible names
When a toggle field doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn more about toggle fields.
ARIA tooltip elements have accessible names
When a tooltip element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn how to name tooltip elements.
ARIA treeitem elements have accessible names
When a treeitem element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn more about labeling treeitem elements.
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 about bypass blocks.
<dl>'s contain only properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements.
When definition lists are not properly marked up, screen readers may produce confusing or inaccurate output. Learn how to structure definition lists correctly.
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 how to structure definition lists correctly.
No form fields have multiple labels
Form fields with multiple labels can be confusingly announced by assistive technologies like screen readers which use either the first, the last, or all of the labels. Learn how to use form labels.
<frame> or <iframe> elements have a title
Screen reader users rely on frame titles to describe the contents of frames. Learn more about frame titles.
<html> element has an [xml:lang] attribute with the same base language as the [lang] attribute.
If the webpage does not specify a consistent language, then the screen reader might not announce the page's text correctly. Learn more about the lang attribute.
Input buttons have discernible text.
Adding discernable and accessible text to input buttons may help screen reader users understand the purpose of the input button. Learn more about input buttons.
<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 about input image alt text.
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 about the refresh meta tag.
<object> elements have alternate text
Screen readers cannot translate non-text content. Adding alternate text to <object> elements helps screen readers convey meaning to users. Learn more about alt text for object elements.
Select elements have associated label elements.
Form elements without effective labels can create frustrating experiences for screen reader users. Learn more about the select element.
Tables have different content in the summary attribute and <caption>.
The summary attribute should describe the table structure, while <caption> should have the onscreen title. Accurate table mark-up helps users of screen readers. Learn more about summary and caption.
Cells in a <table> element that use the [headers] attribute refer to table cells within the 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 about the headers attribute.
<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 about table headers.
[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 how to use the lang attribute.
<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 about video captions.
100
Best Practices
Trust and Safety
Ensure CSP is effective against XSS attacks
A strong Content Security Policy (CSP) significantly reduces the risk of cross-site scripting (XSS) attacks. Learn how to use a CSP to prevent XSS
Description
Directive
Severity
No CSP found in enforcement mode
High
General
Detected JavaScript libraries
All front-end JavaScript libraries detected on the page. Learn more about this JavaScript library detection diagnostic audit.
Name
Version
Nuxt.js
core-js
core-js-pure@3.40.0
Missing source maps for large first-party JavaScript
Source maps translate minified code to the original source code. This helps developers debug in production. In addition, Lighthouse is able to provide further insights. Consider deploying source maps to take advantage of these benefits. Learn more about source maps.
URL
Map URL
backmarket.fr
1st party
/fr-fr
(www.backmarket.fr)
Large JavaScript file is missing a source map
backmarket.com
…_nuxt/VideosBlock.B4dAMETN.js
(front-office.statics.backmarket.com)
…_nuxt/VideosBlock.B4dAMETN.js.map
(front-office.statics.backmarket.com)
…_nuxt/UserCommentModal.t54Dksp_.js
(front-office.statics.backmarket.com)
…_nuxt/UserCommentModal.t54Dksp_.js.map
(front-office.statics.backmarket.com)
…_nuxt/useLogout.DME5LXjP.js
(front-office.statics.backmarket.com)
…_nuxt/useLogout.DME5LXjP.js.map
(front-office.statics.backmarket.com)
…_nuxt/useFooter….Bfua1zZY.js
(front-office.statics.backmarket.com)
…_nuxt/useFooter….Bfua1zZY.js.map
(front-office.statics.backmarket.com)
…_nuxt/useFetchPageContent.BCCBGDsn.js
(front-office.statics.backmarket.com)
…_nuxt/useFetchPageContent.BCCBGDsn.js.map
(front-office.statics.backmarket.com)
…_nuxt/useAlgolia.BFi66Qj7.js
(front-office.statics.backmarket.com)
…_nuxt/useAlgolia.BFi66Qj7.js.map
(front-office.statics.backmarket.com)
…_nuxt/TrustpilotWidget.DFlucsDh.js
(front-office.statics.backmarket.com)
…_nuxt/TrustpilotWidget.DFlucsDh.js.map
(front-office.statics.backmarket.com)
…_nuxt/SocialMediaEmbed.BmAIYN8L.js
(front-office.statics.backmarket.com)
…_nuxt/SocialMediaEmbed.BmAIYN8L.js.map
(front-office.statics.backmarket.com)
…_nuxt/SkinnyBanner.vue.C_t3iY7Z.js
(front-office.statics.backmarket.com)
…_nuxt/SkinnyBanner.vue.C_t3iY7Z.js.map
(front-office.statics.backmarket.com)
…_nuxt/SectionBanner.DKAl42QZ.js
(front-office.statics.backmarket.com)
…_nuxt/SectionBanner.DKAl42QZ.js.map
(front-office.statics.backmarket.com)
…_nuxt/RichText.BqcuRBkr.js
(front-office.statics.backmarket.com)
…_nuxt/RichText.BqcuRBkr.js.map
(front-office.statics.backmarket.com)
…_nuxt/Reviews.BoNLJ5AQ.js
(front-office.statics.backmarket.com)
…_nuxt/Reviews.BoNLJ5AQ.js.map
(front-office.statics.backmarket.com)
…_nuxt/Recommendations.CmXpKmQD.js
(front-office.statics.backmarket.com)
…_nuxt/Recommendations.CmXpKmQD.js.map
(front-office.statics.backmarket.com)
…_nuxt/recommend….DDeUi7cy.js
(front-office.statics.backmarket.com)
…_nuxt/recommend….DDeUi7cy.js.map
(front-office.statics.backmarket.com)
…_nuxt/Products.BBT9btKm.js
(front-office.statics.backmarket.com)
…_nuxt/Products.BBT9btKm.js.map
(front-office.statics.backmarket.com)
…_nuxt/ProductCardCarousel.vue.qeFbQcvn.js
(front-office.statics.backmarket.com)
…_nuxt/ProductCardCarousel.vue.qeFbQcvn.js.map
(front-office.statics.backmarket.com)
…_nuxt/ModularCa….BCfz8sCZ.js
(front-office.statics.backmarket.com)
…_nuxt/ModularCa….BCfz8sCZ.js.map
(front-office.statics.backmarket.com)
…_nuxt/ModularCardImage.DDnj35Vm.js
(front-office.statics.backmarket.com)
…_nuxt/ModularCardImage.DDnj35Vm.js.map
(front-office.statics.backmarket.com)
…_nuxt/MobileAppBanner.vue.CmpP_UJm.js
(front-office.statics.backmarket.com)
…_nuxt/MobileAppBanner.vue.CmpP_UJm.js.map
(front-office.statics.backmarket.com)
…_nuxt/Media.CYxgitS-.js
(front-office.statics.backmarket.com)
…_nuxt/Media.CYxgitS-.js.map
(front-office.statics.backmarket.com)
…_nuxt/InputSelectItem.vue.1xOyxAWy.js
(front-office.statics.backmarket.com)
…_nuxt/InputSelectItem.vue.1xOyxAWy.js.map
(front-office.statics.backmarket.com)
…_nuxt/index.DKXniy5T.js
(front-office.statics.backmarket.com)
…_nuxt/index.DKXniy5T.js.map
(front-office.statics.backmarket.com)
…_nuxt/index.D8ZxCYCV.js
(front-office.statics.backmarket.com)
…_nuxt/index.D8ZxCYCV.js.map
(front-office.statics.backmarket.com)
…_nuxt/index.CqFBXIJu.js
(front-office.statics.backmarket.com)
…_nuxt/index.CqFBXIJu.js.map
(front-office.statics.backmarket.com)
…_nuxt/IconSunFace.DguFtgLq.js
(front-office.statics.backmarket.com)
…_nuxt/IconSunFace.DguFtgLq.js.map
(front-office.statics.backmarket.com)
…_nuxt/IconMoreVertical.B3hyVza0.js
(front-office.statics.backmarket.com)
…_nuxt/IconMoreVertical.B3hyVza0.js.map
(front-office.statics.backmarket.com)
…_nuxt/Home.Dh0SfaEg.js
(front-office.statics.backmarket.com)
…_nuxt/Home.Dh0SfaEg.js.map
(front-office.statics.backmarket.com)
…_nuxt/Form.vue2.afXhp2pQ.js
(front-office.statics.backmarket.com)
…_nuxt/Form.vue2.afXhp2pQ.js.map
(front-office.statics.backmarket.com)
…_nuxt/Faq.As4M2F0b.js
(front-office.statics.backmarket.com)
…_nuxt/Faq.As4M2F0b.js.map
(front-office.statics.backmarket.com)
…_nuxt/entry.Bs2bIzRW.js
(front-office.statics.backmarket.com)
…_nuxt/entry.Bs2bIzRW.js.map
(front-office.statics.backmarket.com)
…_nuxt/EnhancedCarousel.CY-p7yHT.js
(front-office.statics.backmarket.com)
…_nuxt/EnhancedCarousel.CY-p7yHT.js.map
(front-office.statics.backmarket.com)
…_nuxt/EmailCollector.ny0BrYFD.js
(front-office.statics.backmarket.com)
…_nuxt/EmailCollector.ny0BrYFD.js.map
(front-office.statics.backmarket.com)
…_nuxt/el-GR.B0HUlPw2.js
(front-office.statics.backmarket.com)
…_nuxt/el-GR.B0HUlPw2.js.map
(front-office.statics.backmarket.com)
…_nuxt/default.BvJTZVXQ.js
(front-office.statics.backmarket.com)
…_nuxt/default.BvJTZVXQ.js.map
(front-office.statics.backmarket.com)
…_nuxt/Cookies.D0NQjIDM.js
(front-office.statics.backmarket.com)
…_nuxt/Cookies.D0NQjIDM.js.map
(front-office.statics.backmarket.com)
…_nuxt/constants.DfcgOMTc.js
(front-office.statics.backmarket.com)
…_nuxt/constants.DfcgOMTc.js.map
(front-office.statics.backmarket.com)
…_nuxt/Categories.Beq3oKCm.js
(front-office.statics.backmarket.com)
…_nuxt/Categories.Beq3oKCm.js.map
(front-office.statics.backmarket.com)
…_nuxt/Carousel.CHgz4WAQ.js
(front-office.statics.backmarket.com)
…_nuxt/Carousel.CHgz4WAQ.js.map
(front-office.statics.backmarket.com)
…_nuxt/ArticleCardsList.EtuQa7DX.js
(front-office.statics.backmarket.com)
…_nuxt/ArticleCardsList.EtuQa7DX.js.map
(front-office.statics.backmarket.com)
…_nuxt/ar.GHrHWN67.js
(front-office.statics.backmarket.com)
…_nuxt/ar.GHrHWN67.js.map
(front-office.statics.backmarket.com)
…_nuxt/algoliaFunctions.DY2th9gi.js
(front-office.statics.backmarket.com)
…_nuxt/algoliaFunctions.DY2th9gi.js.map
(front-office.statics.backmarket.com)
Passed audits (14)
Show Hide
Uses HTTPS
All sites should be protected with HTTPS, even ones that don't handle sensitive data. This includes avoiding mixed content, where some resources are loaded over HTTP despite the initial request being served over HTTPS. 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 about HTTPS.
Avoids deprecated APIs
Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs.
Avoids third-party cookies
Chrome is moving towards a new experience that allows users to choose to browse without third-party cookies. Learn more about third-party cookies.
Allows users to paste into input fields
Preventing input pasting is a bad practice for the UX, and weakens security by blocking password managers.Learn more about user-friendly input fields.
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 a user action instead. Learn more about the geolocation permission.
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 about responsibly getting permission for notifications.
Displays images with correct aspect ratio
Image display dimensions should match natural aspect ratio. Learn more about image aspect ratio.
Serves images with appropriate resolution
Image natural dimensions should be proportional to the display size and the pixel ratio to maximize image clarity. Learn how to provide responsive images.
Has a <meta name="viewport"> tag with width or initial-scale
A <meta name="viewport"> not only optimizes your app for mobile screen sizes, but also prevents a 300 millisecond delay to user input. Learn more about using the viewport meta tag.
Document uses legible font sizes 100% legible text
Font sizes less than 12px are too small to be legible and require mobile visitors to “pinch to zoom” in order to read. Strive to have >60% of page text ≥12px. Learn more about legible font sizes.
Source
Selector
% of Page Text
Font Size
Legible text
100.00%
≥ 12px
Page has the HTML doctype
Specifying a doctype prevents the browser from switching to quirks-mode. Learn more about the doctype declaration.
Properly defines charset
A character encoding declaration is required. It can be done with a <meta> tag in the first 1024 bytes of the HTML or in the Content-Type HTTP response header. Learn more about declaring the character encoding.
No browser errors logged to the console
Errors logged to the console indicate unresolved problems. They can come from network request failures and other browser concerns. Learn more about this errors in console diagnostic audit
No issues in the Issues panel in Chrome Devtools
Issues logged to the Issues panel in Chrome Devtools indicate unresolved problems. They can come from network request failures, insufficient security controls, and other browser concerns. Open up the Issues panel in Chrome DevTools for more details on each issue.
Not applicable (1)
Show Hide
Redirects HTTP traffic to HTTPS
Make sure that you redirect all HTTP traffic to HTTPS in order to enable secure web features for all your users. Learn more.
100
SEO
These checks ensure that your page is following basic search engine optimization advice. There are many additional factors Lighthouse does not score here that may affect your search ranking, including performance on Core Web Vitals. Learn more about Google Search Essentials.
Additional items to manually check (1)
Show Hide
Structured data is valid
Run the Structured Data Testing Tool and the Structured Data Linter to validate structured data. Learn more about Structured Data.
Run these additional validators on your site to check additional SEO best practices.
Passed audits (10)
Show Hide
Page isn’t blocked from indexing
Search engines are unable to include your pages in search results if they don't have permission to crawl them. Learn more about crawler directives.
Document has a <title> element
The title gives screen reader users an overview of the page, and search engine users rely on it heavily to determine if a page is relevant to their search. Learn more about document titles.
Document has a meta description
Meta descriptions may be included in search results to concisely summarize page content. Learn more about the meta description.
Page has successful HTTP status code
Pages with unsuccessful HTTP status codes may not be indexed properly. Learn more about HTTP status codes.
Links have descriptive text
Descriptive link text helps search engines understand your content. Learn how to make links more accessible.
Links are crawlable
Search engines may use href attributes on links to crawl websites. Ensure that the href attribute of anchor elements links to an appropriate destination, so more pages of the site can be discovered. Learn how to make links crawlable
robots.txt is valid
If your robots.txt file is malformed, crawlers may not be able to understand how you want your website to be crawled or indexed. Learn more about robots.txt.
Image elements have [alt] attributes
Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the alt attribute.
Document has a valid hreflang
hreflang links tell search engines what version of a page they should list in search results for a given language or region. Learn more about hreflang.
Document has a valid rel=canonical
Canonical links suggest which URL to show in search results. Learn more about canonical links.
Discover what your real users are experiencing
Core Web Vitals Assessment: Failed
Largest Contentful Paint (LCP)
2.4 s
Page LoadsGood (≤ 2.5 s)77%Needs Improvement (2.5 s - 4 s)13%Poor (> 4 s)10%75th Percentile - 2.4 sCore Web Vital
Interaction to Next Paint (INP)
227 ms
Page LoadsGood (≤ 200 ms)71%Needs Improvement (200 ms - 500 ms)22%Poor (> 500 ms)7%75th Percentile - 227 msCore Web Vital
Cumulative Layout Shift (CLS)
0.06
Page LoadsGood (≤ 0.1)80%Needs Improvement (0.1 - 0.25)7%Poor (> 0.25)12%75th Percentile - 0.06Core Web Vital
Other Notable Metrics
First Contentful Paint (FCP)
1.7 s
Page LoadsGood (≤ 1.8 s)78%Needs Improvement (1.8 s - 3 s)15%Poor (> 3 s)7%75th Percentile - 1.7 s 
Time to First Byte (TTFB)
1 s
Page LoadsGood (≤ 0.8 s)54%Needs Improvement (0.8 s - 1.8 s)40%Poor (> 1.8 s)6%75th Percentile - 1 sExperimental
Latest 28-day collection period
Various desktop devicesMany samples (Chrome UX Report)Full visit durationsVarious network connectionsAll Chrome versions
Core Web Vitals Assessment: Passed
Largest Contentful Paint (LCP)
2.2 s
Page LoadsGood (≤ 2.5 s)80%Needs Improvement (2.5 s - 4 s)13%Poor (> 4 s)7%75th Percentile - 2.2 sCore Web Vital
Interaction to Next Paint (INP)
161 ms
Page LoadsGood (≤ 200 ms)81%Needs Improvement (200 ms - 500 ms)14%Poor (> 500 ms)5%75th Percentile - 161 msCore Web Vital
Cumulative Layout Shift (CLS)
0.04
Page LoadsGood (≤ 0.1)86%Needs Improvement (0.1 - 0.25)6%Poor (> 0.25)8%75th Percentile - 0.04Core Web Vital
Other Notable Metrics
First Contentful Paint (FCP)
1.9 s
Page LoadsGood (≤ 1.8 s)72%Needs Improvement (1.8 s - 3 s)20%Poor (> 3 s)8%75th Percentile - 1.9 s 
Time to First Byte (TTFB)
1.3 s
Page LoadsGood (≤ 0.8 s)41%Needs Improvement (0.8 s - 1.8 s)48%Poor (> 1.8 s)11%75th Percentile - 1.3 sExperimental
Latest 28-day collection period
Various desktop devicesMany samples (Chrome UX Report)Full visit durationsVarious network connectionsAll Chrome versions
Diagnose performance issues
70
Performance
74
Accessibility
100
Best Practices
100
SEO
70
Performance
74
Accessibility
100
Best Practices
100
SEO
70 FCP+7LCP+16TBT+15CLS+25SI+8 Performance
Values are estimated and may vary. The performance score is calculated directly from these metrics.See calculator.
0–49 50–89 90–100
Final Screenshot
Metrics
First Contentful Paint
1.3 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more about the First Contentful Paint metric.
Largest Contentful Paint
2.0 s
Largest Contentful Paint marks the time at which the largest text or image is painted. Learn more about the Largest Contentful Paint metric
Total Blocking Time
340 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds. Learn more about the Total Blocking Time metric.
Cumulative Layout Shift
0.023
Cumulative Layout Shift measures the movement of visible elements within the viewport. Learn more about the Cumulative Layout Shift metric.
Speed Index
1.7 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more about the Speed Index metric.
  • Captured at Feb 17, 2025, 8:00 AM UTC
  • Emulated Desktop with Lighthouse 12.2.3
    Unthrottled CPU/Memory Power: 328 CPU throttling: 1x slowdown (Simulated) Screen emulation: 1350x940, DPR 1 Axe version: 4.10.2
  • Single page session
    This data is taken from a single page session, as opposed to field data summarizing many sessions.
  • Initial page load
  • Custom throttling
    Network throttling: 40 ms TCP RTT, 10,240 kb/s throughput (Simulated) Browser location: North America
  • Using HeadlessChromium 133.0.6943.53 with lr
    User agent (network): "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/119.0.0.0 Safari/537.36"
Screenshot
Screenshot
Screenshot
Screenshot
Screenshot
Screenshot
Screenshot
Screenshot
Show audits relevant to:
Diagnostics
Reduce JavaScript execution time 1.3 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to reduce Javascript execution time.TBT
URL
Total CPU Time
Script Evaluation
Script Parse
Unattributable
959 ms
560 ms
0 ms
Unattributable
959 ms
560 ms
0 ms
Google Tag Manager
tag-manager
419 ms
369 ms
13 ms
/gtm.js?auth=C_TrFGuRx…&id=GTM-N6P9JCF&preview=env-1
(www.googletagmanager.com)
419 ms
369 ms
13 ms
backmarket.fr
1st party
414 ms
19 ms
51 ms
/fr-fr
(www.backmarket.fr)
414 ms
19 ms
51 ms
backmarket.com
382 ms
289 ms
0 ms
…_nuxt/ModularCa….BCfz8sCZ.js
(front-office.statics.backmarket.com)
280 ms
194 ms
0 ms
…_nuxt/TrustpilotWidget.DFlucsDh.js
(front-office.statics.backmarket.com)
102 ms
95 ms
0 ms
Minimize main-thread work 2.3 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to minimize main-thread workTBT
Category
Time Spent
Script Evaluation
1,284 ms
Other
293 ms
Garbage Collection
246 ms
Style & Layout
221 ms
Parse HTML & CSS
100 ms
Script Parsing & Compilation
78 ms
Rendering
58 ms
Largest Contentful Paint element 2,030 ms
This is the largest contentful element painted within the viewport. Learn more about the Largest Contentful Paint elementLCP
Element
GLO - HP Banner - Q1 Incentive
<img class="block w-full object-cover h-auto max-h-full max-w-full leading-none" alt="GLO - HP Banner - Q1 Incentive" decoding="async" height="343" loading="eager" sizes="100vw" src="https://www.backmarket.fr/cdn-cgi/image/format%3Dauto%2Cquality%3D75%2Cwid…" srcset="/cdn-cgi/image/format%3Dauto%2Cquality%3D75%2Cwidth%3D260/https://images.c…" width="1440">
Phase
% of LCP
Timing
TTFB
8%
160 ms
Load Delay
49%
990 ms
Load Time
8%
170 ms
Render Delay
35%
710 ms
Reduce unused JavaScript Potential savings of 252 KiB
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.LCPFCP
URL
Transfer Size
Potential Savings
backmarket.com
387.4 KiB
131.9 KiB
…_nuxt/entry.Bs2bIzRW.js
(front-office.statics.backmarket.com)
329.8 KiB
81.8 KiB
…../../../node_modules/@backmarket/front-logger/dist/esm/index.js
16.9 KiB
7.5 KiB
…../../../node_modules/@vue/runtime-core/dist/runtime-core.esm-bundler.js
15.5 KiB
3.3 KiB
…../../../node_modules/intl-messageformat/node_modules/@formatjs/icu-messageformat-parser/lib/parser.js
4.7 KiB
3.0 KiB
…../../../node_modules/@amplitude/analytics-browser/lib/esm/config.js
2.0 KiB
1.7 KiB
…../../../node_modules/@amplitude/analytics-core/lib/esm/plugins/destination.js
1.7 KiB
1.6 KiB
…_nuxt/index.CqFBXIJu.js
(front-office.statics.backmarket.com)
57.6 KiB
50.1 KiB
…rc/ui/js/iam-css.js
9.8 KiB
9.8 KiB
…rc/ui/js/feed-css.js
2.2 KiB
2.2 KiB
…rc/Push/push-manager.js
2.1 KiB
2.1 KiB
…rc/managers/network-manager.js
1.6 KiB
1.6 KiB
…rc/triggers/triggers-provider.js
1.6 KiB
1.6 KiB
Google Tag Manager
tag-manager
263.1 KiB
120.2 KiB
/gtm.js?id=GTM-WB77QG&l=dataLayer&gtm=45He52d0v855…za200
(www.googletagmanager.com)
108.9 KiB
68.9 KiB
/gtm.js?auth=C_TrFGuRx…&id=GTM-N6P9JCF&preview=env-1
(www.googletagmanager.com)
154.2 KiB
51.3 KiB
Serve images in next-gen formats Potential savings of 315 KiB
Image formats like WebP and AVIF often provide better compression than PNG or JPEG, which means faster downloads and less data consumption. Learn more about modern image formats.LCPFCP
NuxtUse the nuxt/image component and set format="webp". Learn more.
URL
Resource Size
Potential Savings
ctfassets.net
469.0 KiB
315.2 KiB
…2ed061d…/Thumbnail-9_16-FR.jpg
(images.ctfassets.net)
305.5 KiB
212.4 KiB
…a28cdea…/PROCESSOR….jpg
(images.ctfassets.net)
40.0 KiB
25.1 KiB
…4e3008e…/NEW-BATTERY-FR-verticale-thumbnail.jpg
(images.ctfassets.net)
35.6 KiB
22.8 KiB
…390fd72…/VDEF-Thumbail-verticale-FR.jpg
(images.ctfassets.net)
30.3 KiB
19.6 KiB
…ea71742…/Myths_about_your_tech_-_Thumbnail_-_FR.jpg
(images.ctfassets.net)
29.9 KiB
18.4 KiB
…4daf0ed…/Tips_for_laptops_-_Thumbnail_-_FR.jpg
(images.ctfassets.net)
27.6 KiB
16.9 KiB
Serve static assets with an efficient cache policy 24 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more about efficient cache policies.
URL
Cache TTL
Transfer Size
backmarket.fr
1st party
2,075 KiB
…1f0JyDRFa…/original.jpeg
(www.backmarket.fr)
4h
466 KiB
…91w7PsUgq…/original.jpeg
(www.backmarket.fr)
4h
275 KiB
…gPGaBH3va…/original.jpeg
(www.backmarket.fr)
4h
239 KiB
…QOp7iR98p…/original.jpeg
(www.backmarket.fr)
4h
227 KiB
…FrMrYXgxp…/original.jpeg
(www.backmarket.fr)
4h
181 KiB
…G0WKsGTcN…/original.jpeg
(www.backmarket.fr)
4h
164 KiB
…pQ6f1XCUp…/original.jpeg
(www.backmarket.fr)
4h
149 KiB
…7IDtgTYkB…/original.jpeg
(www.backmarket.fr)
4h
144 KiB
…P0ZUq7zfL…/original.jpeg
(www.backmarket.fr)
4h
115 KiB
…w8P0764jr…/original.jpg
(www.backmarket.fr)
4h
83 KiB
…d2e6ccujb3mkqf.cloudfront.net/d61d0800-a563-4e5c-a1e6-652f….jpg
(www.backmarket.fr)
1d
5 KiB
…d2e6ccujb3mkqf.cloudfront.net/338165eb-e7d5-4145-8786-234d….jpg
(www.backmarket.fr)
1d
5 KiB
…d2e6ccujb3mkqf.cloudfront.net/2fd60d82-0348-4944-9734-9fb4….jpg
(www.backmarket.fr)
1d
4 KiB
…d2e6ccujb3mkqf.cloudfront.net/ef5660d2-6883-4b81-b47d-86e5….jpg
(www.backmarket.fr)
1d
3 KiB
…d2e6ccujb3mkqf.cloudfront.net/b1c177ac-ef78-4c4e-8a77-b888….jpg
(www.backmarket.fr)
1d
3 KiB
…d2e6ccujb3mkqf.cloudfront.net/5e00cb64-a460-4975-a515-5fa9….jpg
(www.backmarket.fr)
1d
3 KiB
…d2e6ccujb3mkqf.cloudfront.net/afb7c00c-b020-43af-a5de-5d43….jpg
(www.backmarket.fr)
1d
3 KiB
…d2e6ccujb3mkqf.cloudfront.net/e3d83ef6-ca98-456b-bfeb-653f….jpg
(www.backmarket.fr)
1d
3 KiB
…d2e6ccujb3mkqf.cloudfront.net/4b323a83-4579-4cec-9478-90f9….jpg
(www.backmarket.fr)
1d
2 KiB
backmarket.com
86 KiB
…latest/IvarSoft-SemiBold.woff2
(static-ds.backmarket.com)
1d
28 KiB
…latest/BMDupletT….woff2
(static-ds.backmarket.com)
1d
20 KiB
…latest/BMDupletD….woff2
(static-ds.backmarket.com)
1d
20 KiB
…latest/BMDupletT….woff2
(static-ds.backmarket.com)
1d
19 KiB
appsflyer.com
14 KiB
/?st=banners&
(websdk.appsflyer.com)
None
14 KiB
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 about adopting passive event listeners.
Source
backmarket.com
../../../../../../node_modules/@backmarket/design-system/dist/src/components/Carousel/Carousel.vue2.js:118:33
../../../../../../node_modules/@backmarket/design-system/dist/src/components/Carousel/Carousel.vue2.js:118:98
Eliminate render-blocking resources Potential savings of 10 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles. Learn how to eliminate render-blocking resources.LCPFCP
URL
Transfer Size
Potential Savings
backmarket.com
0.7 KiB
200 ms
…_nuxt/entry.BYTEDdIC.css
(front-office.statics.backmarket.com)
0.7 KiB
200 ms
Properly size images Potential savings of 26 KiB
Serve images that are appropriately-sized to save cellular data and improve load time. Learn how to size images.LCPFCP
NuxtUse the nuxt/image component and set the appropriate sizes. Learn more.
URL
Resource Size
Potential Savings
backmarket.fr
1st party
58.4 KiB
25.5 KiB
GLO - HP Banner - Q1 Incentive
<img class="block w-full object-cover h-auto max-h-full max-w-full leading-none" alt="GLO - HP Banner - Q1 Incentive" decoding="async" height="343" loading="eager" sizes="100vw" src="https://www.backmarket.fr/cdn-cgi/image/format%3Dauto%2Cquality%3D75%2Cwid…" srcset="/cdn-cgi/image/format%3Dauto%2Cquality%3D75%2Cwidth%3D260/https://images.c…" width="1440">
…f517d38…/App_incentive_translations_-_HP_Banner_-_Desktop_….jpg
(www.backmarket.fr)
58.4 KiB
25.5 KiB
Efficiently encode images Potential savings of 121 KiB
Optimized images load faster and consume less cellular data. Learn how to efficiently encode images.LCPFCP
NuxtUse the nuxt/image component and set the appropriate quality. Learn more.
URL
Resource Size
Potential Savings
ctfassets.net
469.0 KiB
120.7 KiB
…2ed061d…/Thumbnail-9_16-FR.jpg
(images.ctfassets.net)
305.5 KiB
82.5 KiB
…a28cdea…/PROCESSOR….jpg
(images.ctfassets.net)
40.0 KiB
10.3 KiB
…4e3008e…/NEW-BATTERY-FR-verticale-thumbnail.jpg
(images.ctfassets.net)
35.6 KiB
9.1 KiB
…390fd72…/VDEF-Thumbail-verticale-FR.jpg
(images.ctfassets.net)
30.3 KiB
8.0 KiB
…ea71742…/Myths_about_your_tech_-_Thumbnail_-_FR.jpg
(images.ctfassets.net)
29.9 KiB
5.6 KiB
…4daf0ed…/Tips_for_laptops_-_Thumbnail_-_FR.jpg
(images.ctfassets.net)
27.6 KiB
5.2 KiB
Remove duplicate modules in JavaScript bundles Potential savings of 2 KiB
Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity. LCPFCP
Source
Transfer Size
Potential Savings
Other
0 KiB
…_nuxt/entry.Bs2bIzRW.js
(front-office.statics.backmarket.com)
…_nuxt/TrustpilotWidget.DFlucsDh.js
(front-office.statics.backmarket.com)
…_nuxt/ModularCa….BCfz8sCZ.js
(front-office.statics.backmarket.com)
…_nuxt/Faq.As4M2F0b.js
(front-office.statics.backmarket.com)
…_nuxt/index.D8ZxCYCV.js
(front-office.statics.backmarket.com)
Avoid serving legacy JavaScript to modern browsers Potential savings of 25 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. However, many aren't necessary for modern browsers. For your bundled JavaScript, adopt a modern script deployment strategy using module/nomodule feature detection to reduce the amount of code shipped to modern browsers, while retaining support for legacy browsers. Learn how to use modern JavaScriptLCPFCP
URL
Potential Savings
backmarket.com
18.3 KiB
…_nuxt/Form.vue2.afXhp2pQ.js
(front-office.statics.backmarket.com)
10.8 KiB
../../../../../../node_modules/@backmarket/design-system/node_modules/core-js-pure/modules/es.object.keys.js:11:2
Object.keys
…_nuxt/entry.Bs2bIzRW.js
(front-office.statics.backmarket.com)
7.5 KiB
../../../../../../node_modules/@amplitude/analytics-connector/dist/analytics-connector.esm.js:188:4
Object.entries
…_nuxt/ArticleCardsList.EtuQa7DX.js
(front-office.statics.backmarket.com)
0.0 KiB
../../../../../../node_modules/libphonenumber-js/es6/ParseError.js:7:112
@babel/plugin-transform-classes
appsflyer.com
6.6 KiB
/?st=banners&
(websdk.appsflyer.com)
6.6 KiB
/?st=banners&:4:3745
(websdk.appsflyer.com)
Object.keys
Reduce unused CSS Potential savings of 26 KiB
Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity. Learn how to reduce unused CSS.LCPFCP
URL
Transfer Size
Potential Savings
*,:after,:before{--tw-border-spacing-x:0;--tw-border-spacing-y:0;--tw-translate-x:0;--tw-translate-…
33.6 KiB
26.3 KiB
Avoid enormous network payloads Total size was 4,516 KiB
Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.
URL
Transfer Size
backmarket.fr
1st party
1,920.4 KiB
…1f0JyDRFa…/original.jpeg
(www.backmarket.fr)
465.9 KiB
/fr-fr
(www.backmarket.fr)
367.9 KiB
…91w7PsUgq…/original.jpeg
(www.backmarket.fr)
275.5 KiB
…gPGaBH3va…/original.jpeg
(www.backmarket.fr)
239.0 KiB
…QOp7iR98p…/original.jpeg
(www.backmarket.fr)
227.1 KiB
…FrMrYXgxp…/original.jpeg
(www.backmarket.fr)
180.6 KiB
…G0WKsGTcN…/original.jpeg
(www.backmarket.fr)
164.4 KiB
backmarket.com
338.9 KiB
…_nuxt/entry.Bs2bIzRW.js
(front-office.statics.backmarket.com)
338.9 KiB
ctfassets.net
306.0 KiB
…2ed061d…/Thumbnail-9_16-FR.jpg
(images.ctfassets.net)
306.0 KiB
Google Tag Manager
tag-manager
155.3 KiB
/gtm.js?auth=C_TrFGuRx…&id=GTM-N6P9JCF&preview=env-1
(www.googletagmanager.com)
155.3 KiB
Avoid an excessive DOM size 2,834 elements
A large DOM will increase memory usage, cause longer style calculations, and produce costly layout reflows. Learn how to avoid an excessive DOM size.TBT
Statistic
Element
Value
Total DOM Elements
2,834
Maximum DOM Depth
div.text-action-default-hi > div.flex > svg > path
<path d="M13.154 3.65c-.427-1.026-1.881-1.026-2.308 0L8.838 8.478l-5.21.418C2.519 8…">
30
Maximum Child Elements
Emplacement actuelFrancefrançais (FR)PaysAutricheDeutsch (AT)AustralieEnglish (…
<ul class="divide-static-default-low divide-y border-static-default-low border-y body…">
18
Avoid long main-thread tasks 9 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay. Learn how to avoid long main-thread tasksTBT
URL
Start Time
Duration
Unattributable
588 ms
Unattributable
2,252 ms
390 ms
Unattributable
2,642 ms
147 ms
Unattributable
975 ms
51 ms
Google Tag Manager
tag-manager
272 ms
/gtm.js?auth=C_TrFGuRx…&id=GTM-N6P9JCF&preview=env-1
(www.googletagmanager.com)
1,539 ms
114 ms
/gtm.js?auth=C_TrFGuRx…&id=GTM-N6P9JCF&preview=env-1
(www.googletagmanager.com)
2,086 ms
85 ms
/gtm.js?auth=C_TrFGuRx…&id=GTM-N6P9JCF&preview=env-1
(www.googletagmanager.com)
1,952 ms
73 ms
backmarket.com
104 ms
…_nuxt/TrustpilotWidget.DFlucsDh.js
(front-office.statics.backmarket.com)
2,861 ms
54 ms
…_nuxt/ModularCa….BCfz8sCZ.js
(front-office.statics.backmarket.com)
2,811 ms
50 ms
backmarket.fr
1st party
60 ms
/fr-fr
(www.backmarket.fr)
622 ms
60 ms
Minimize third-party usage Third-party code blocked the main thread for 130 ms
Third-party code can significantly impact load performance. Limit the number of redundant third-party providers and try to load third-party code after your page has primarily finished loading. Learn how to minimize third-party impact.TBT
Third-Party
Transfer Size
Main-Thread Blocking Time
Google Tag Manager
tag-manager
265 KiB
122 ms
/gtm.js?auth=C_TrFGuRx…&id=GTM-N6P9JCF&preview=env-1
(www.googletagmanager.com)
155 KiB
122 ms
/gtm.js?id=GTM-WB77QG&l=dataLayer&gtm=45He52d0v855…za200
(www.googletagmanager.com)
110 KiB
0 ms
backmarket.com
862 KiB
4 ms
…_nuxt/TrustpilotWidget.DFlucsDh.js
(front-office.statics.backmarket.com)
8 KiB
4 ms
…_nuxt/SocialMediaEmbed.BmAIYN8L.js
(front-office.statics.backmarket.com)
5 KiB
0 ms
…_nuxt/entry.Bs2bIzRW.js
(front-office.statics.backmarket.com)
339 KiB
0 ms
…_nuxt/ModularCa….BCfz8sCZ.js
(front-office.statics.backmarket.com)
13 KiB
0 ms
…_nuxt/index.CqFBXIJu.js
(front-office.statics.backmarket.com)
59 KiB
0 ms
…_nuxt/default.BvJTZVXQ.js
(front-office.statics.backmarket.com)
42 KiB
0 ms
…_nuxt/Categories.Beq3oKCm.js
(front-office.statics.backmarket.com)
40 KiB
0 ms
…_nuxt/ArticleCardsList.EtuQa7DX.js
(front-office.statics.backmarket.com)
32 KiB
0 ms
…latest/IvarSoft-SemiBold.woff2
(static-ds.backmarket.com)
28 KiB
0 ms
…latest/BMDupletT….woff2
(static-ds.backmarket.com)
20 KiB
0 ms
…latest/BMDupletD….woff2
(static-ds.backmarket.com)
20 KiB
0 ms
…_nuxt/SectionBanner.DKAl42QZ.js
(front-office.statics.backmarket.com)
19 KiB
0 ms
…latest/BMDupletT….woff2
(static-ds.backmarket.com)
19 KiB
0 ms
…_nuxt/InputSelectItem.vue.1xOyxAWy.js
(front-office.statics.backmarket.com)
19 KiB
0 ms
…_nuxt/IconMoreVertical.B3hyVza0.js
(front-office.statics.backmarket.com)
19 KiB
0 ms
…_nuxt/IconSunFace.DguFtgLq.js
(front-office.statics.backmarket.com)
17 KiB
0 ms
…_nuxt/Form.vue2.afXhp2pQ.js
(front-office.statics.backmarket.com)
17 KiB
0 ms
…_nuxt/el-GR.B0HUlPw2.js
(front-office.statics.backmarket.com)
11 KiB
0 ms
…_nuxt/ar.GHrHWN67.js
(front-office.statics.backmarket.com)
10 KiB
0 ms
…_nuxt/index.DKXniy5T.js
(front-office.statics.backmarket.com)
10 KiB
0 ms
…_nuxt/useAlgolia.BFi66Qj7.js
(front-office.statics.backmarket.com)
10 KiB
0 ms
…_nuxt/constants.DfcgOMTc.js
(front-office.statics.backmarket.com)
9 KiB
0 ms
…_nuxt/useFetchPageContent.BCCBGDsn.js
(front-office.statics.backmarket.com)
7 KiB
0 ms
…_nuxt/useFooter….Bfua1zZY.js
(front-office.statics.backmarket.com)
6 KiB
0 ms
…_nuxt/UserCommentModal.t54Dksp_.js
(front-office.statics.backmarket.com)
6 KiB
0 ms
…_nuxt/Faq.As4M2F0b.js
(front-office.statics.backmarket.com)
6 KiB
0 ms
…_nuxt/Cookies.D0NQjIDM.js
(front-office.statics.backmarket.com)
6 KiB
0 ms
…_nuxt/ProductCardCarousel.vue.qeFbQcvn.js
(front-office.statics.backmarket.com)
6 KiB
0 ms
…_nuxt/VideosBlock.B4dAMETN.js
(front-office.statics.backmarket.com)
5 KiB
0 ms
…_nuxt/Home.Dh0SfaEg.js
(front-office.statics.backmarket.com)
4 KiB
0 ms
…_nuxt/Recommendations.CmXpKmQD.js
(front-office.statics.backmarket.com)
3 KiB
0 ms
…_nuxt/Carousel.CHgz4WAQ.js
(front-office.statics.backmarket.com)
3 KiB
0 ms
…_nuxt/EnhancedCarousel.CY-p7yHT.js
(front-office.statics.backmarket.com)
3 KiB
0 ms
…_nuxt/Products.BBT9btKm.js
(front-office.statics.backmarket.com)
3 KiB
0 ms
…_nuxt/EmailCollector.ny0BrYFD.js
(front-office.statics.backmarket.com)
3 KiB
0 ms
…_nuxt/RichText.BqcuRBkr.js
(front-office.statics.backmarket.com)
3 KiB
0 ms
…_nuxt/index.D8ZxCYCV.js
(front-office.statics.backmarket.com)
3 KiB
0 ms
…_nuxt/recommend….DDeUi7cy.js
(front-office.statics.backmarket.com)
3 KiB
0 ms
…_nuxt/Reviews.BoNLJ5AQ.js
(front-office.statics.backmarket.com)
3 KiB
0 ms
…_nuxt/ModularCardImage.DDnj35Vm.js
(front-office.statics.backmarket.com)
2 KiB
0 ms
…_nuxt/algoliaFunctions.DY2th9gi.js
(front-office.statics.backmarket.com)
2 KiB
0 ms
…_nuxt/MobileAppBanner.vue.CmpP_UJm.js
(front-office.statics.backmarket.com)
2 KiB
0 ms
…_nuxt/Media.CYxgitS-.js
(front-office.statics.backmarket.com)
2 KiB
0 ms
…header/Logo.svg
(front-office.statics.backmarket.com)
2 KiB
0 ms
…_nuxt/SkinnyBanner.vue.C_t3iY7Z.js
(front-office.statics.backmarket.com)
2 KiB
0 ms
…_nuxt/RichText.BYuM95KO.css
(front-office.statics.backmarket.com)
1 KiB
0 ms
…v8.6.0/backmarket.fontface.css
(static-ds.backmarket.com)
1 KiB
0 ms
…_nuxt/useLogout.DME5LXjP.js
(front-office.statics.backmarket.com)
1 KiB
0 ms
…meta/6c3f9c32-276c-4c20-9915-4882d132d2b9.json
(front-office.statics.backmarket.com)
1 KiB
0 ms
…_nuxt/UserCommentModal.OMJl9RBk.css
(front-office.statics.backmarket.com)
1 KiB
0 ms
…_nuxt/default.C26oZ689.css
(front-office.statics.backmarket.com)
1 KiB
0 ms
…_nuxt/Media.CwEUDodq.css
(front-office.statics.backmarket.com)
1 KiB
0 ms
…_nuxt/Reviews.Dl7AnzoM.css
(front-office.statics.backmarket.com)
1 KiB
0 ms
…_nuxt/EnhancedCarousel.DqqW-XG_.css
(front-office.statics.backmarket.com)
1 KiB
0 ms
…_nuxt/entry.BYTEDdIC.css
(front-office.statics.backmarket.com)
1 KiB
0 ms
ctfassets.net
472 KiB
0 ms
…2ed061d…/Thumbnail-9_16-FR.jpg
(images.ctfassets.net)
306 KiB
0 ms
…a28cdea…/PROCESSOR….jpg
(images.ctfassets.net)
41 KiB
0 ms
…4e3008e…/NEW-BATTERY-FR-verticale-thumbnail.jpg
(images.ctfassets.net)
36 KiB
0 ms
…390fd72…/VDEF-Thumbail-verticale-FR.jpg
(images.ctfassets.net)
31 KiB
0 ms
…ea71742…/Myths_about_your_tech_-_Thumbnail_-_FR.jpg
(images.ctfassets.net)
30 KiB
0 ms
…4daf0ed…/Tips_for_laptops_-_Thumbnail_-_FR.jpg
(images.ctfassets.net)
28 KiB
0 ms
appsflyer.com
14 KiB
0 ms
/?st=banners&
(websdk.appsflyer.com)
14 KiB
0 ms
backmarket.io
0 KiB
0 ms
https://noodle.backmarket.io
0 KiB
0 ms
Initial server response time was short Root document took 340 ms
Keep the server response time for the main document short because all other requests depend on it. Learn more about the Time to First Byte metric.LCPFCP
URL
Time Spent
backmarket.fr
1st party
340 ms
/fr-fr
(www.backmarket.fr)
340 ms
Avoid large layout shifts 4 layout shifts found
These are the largest layout shifts observed on the page. Each table item represents a single layout shift, and shows the element that shifted the most. Below each item are possible root causes that led to the layout shift. Some of these layout shifts may not be included in the CLS metric value due to windowing. Learn how to improve CLSCLS
Element
Layout shift score
En sélectionnant « Tout accepter », vous autorisez Back Market et nos partenair…
<div aria-labelledby="modalTitle" aria-modal="true" class="bg-surface-default-hi rounded-t-lg fixed bottom-0 left-0 max-h-full w-full…" role="dialog" tabindex="0">
0.018
…_nuxt/UserCommentModal.OMJl9RBk.css
(front-office.statics.backmarket.com)
A late network request adjusted the page layout
…_nuxt/RichText.BYuM95KO.css
(front-office.statics.backmarket.com)
A late network request adjusted the page layout
…_nuxt/entry.BYTEDdIC.css
(front-office.statics.backmarket.com)
A late network request adjusted the page layout
…_nuxt/Reviews.Dl7AnzoM.css
(front-office.statics.backmarket.com)
A late network request adjusted the page layout
En sélectionnant « Tout accepter », vous autorisez Back Market et nos partenair…
<div aria-labelledby="modalTitle" aria-modal="true" class="bg-surface-default-hi rounded-t-lg fixed bottom-0 left-0 max-h-full w-full…" role="dialog" tabindex="0">
0.007
…latest/BMDupletT….woff2
(static-ds.backmarket.com)
Web font loaded
…latest/BMDupletT….woff2
(static-ds.backmarket.com)
Web font loaded
…_nuxt/UserCommentModal.OMJl9RBk.css
(front-office.statics.backmarket.com)
A late network request adjusted the page layout
…_nuxt/RichText.BYuM95KO.css
(front-office.statics.backmarket.com)
A late network request adjusted the page layout
…_nuxt/entry.BYTEDdIC.css
(front-office.statics.backmarket.com)
A late network request adjusted the page layout
…_nuxt/Reviews.Dl7AnzoM.css
(front-office.statics.backmarket.com)
A late network request adjusted the page layout
Bons plans Smartphones Ordinateurs portables Tablettes Consoles Montres connect…
<ul class="flex flex-row gap-32 overflow-x-auto scrollbar-none md:h-48" data-v-e6cce1bf="">
0.003
…latest/BMDupletD….woff2
(static-ds.backmarket.com)
Web font loaded
…latest/IvarSoft-SemiBold.woff2
(static-ds.backmarket.com)
Web font loaded
…latest/BMDupletT….woff2
(static-ds.backmarket.com)
Web font loaded
…latest/BMDupletT….woff2
(static-ds.backmarket.com)
Web font loaded
…_nuxt/UserCommentModal.OMJl9RBk.css
(front-office.statics.backmarket.com)
A late network request adjusted the page layout
…_nuxt/RichText.BYuM95KO.css
(front-office.statics.backmarket.com)
A late network request adjusted the page layout
…_nuxt/entry.BYTEDdIC.css
(front-office.statics.backmarket.com)
A late network request adjusted the page layout
…_nuxt/Reviews.Dl7AnzoM.css
(front-office.statics.backmarket.com)
A late network request adjusted the page layout
La circularité recommence ici. Achetez et revendez vos appareils à des pros du …
<div class="px-24 md:px-72 py-0 flex flex-col gap-24">
0.002
…_nuxt/EnhancedCarousel.DqqW-XG_.css
(front-office.statics.backmarket.com)
A late network request adjusted the page layout
…_nuxt/Media.CwEUDodq.css
(front-office.statics.backmarket.com)
A late network request adjusted the page layout
Avoid non-composited animations 2 animated elements found
Animations which are not composited can be janky and increase CLS. Learn how to avoid non-composited animationsCLS
Element
Name
Tout accepter
<button aria-disabled="false" class="focus-visible-outline-default-hi rounded-sm relative max-w-full select-non…" data-qa="accept-cta" type="button">
Unsupported CSS Property: background-color
background-color
Unsupported CSS Property: color
color
Définir les préférences
<button aria-disabled="false" class="focus-visible-outline-default-hi rounded-sm relative max-w-full select-non…" type="button">
Unsupported CSS Property: border-right-color
border-right-color
Unsupported CSS Property: border-top-color
border-top-color
Unsupported CSS Property: background-color
background-color
Unsupported CSS Property: color
color
Unsupported CSS Property: border-bottom-color
border-bottom-color
Unsupported CSS Property: border-left-color
border-left-color
Avoid chaining critical requests 4 chains found
The Critical Request Chains below show you what resources are loaded with a high priority. Consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load. Learn how to avoid chaining critical requests.
Maximum critical path latency: 580.215 ms
Initial Navigation
/fr-fr
(www.backmarket.fr)
…_nuxt/entry.BYTEDdIC.css
(front-office.statics.backmarket.com)
- 70.627 ms, 0.69 KiB
…_nuxt/RichText.BYuM95KO.css
(front-office.statics.backmarket.com)
- 71.674 ms, 1.48 KiB
…_nuxt/Reviews.Dl7AnzoM.css
(front-office.statics.backmarket.com)
- 65.509 ms, 0.75 KiB
…_nuxt/UserCommentModal.OMJl9RBk.css
(front-office.statics.backmarket.com)
- 92.766 ms, 0.91 KiB
More information about the performance of your application. These numbers don't directly affect the Performance score.
Passed audits (15)
Show Hide
Defer offscreen images
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive. Learn how to defer offscreen images.LCPFCP
NuxtUse the nuxt/image component and set loading="lazy" for offscreen images. Learn more.
Minify CSS
Minifying CSS files can reduce network payload sizes. Learn how to minify CSS.LCPFCP
Minify JavaScript
Minifying JavaScript files can reduce payload sizes and script parse time. Learn how to minify JavaScript.LCPFCP
Enable text compression
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. Learn more about text compression.LCPFCP
Preconnect to required origins
Consider adding preconnect or dns-prefetch resource hints to establish early connections to important third-party origins. Learn how to preconnect to required origins.LCPFCP
Avoid multiple page redirects
Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.LCPFCP
Use video formats for animated content
Large GIFs are inefficient for delivering animated content. Consider using MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF to save network bytes. Learn more about efficient video formatsLCPFCP
Preload Largest Contentful Paint image
If the LCP element is dynamically added to the page, you should preload the image in order to improve LCP. Learn more about preloading LCP elements.LCP
NuxtUse the nuxt/image component and specify preload for LCP image. Learn more.
User Timing marks and measures
Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences. Learn more about User Timing marks.
All text remains visible during webfont loads
Leverage the font-display CSS feature to ensure text is user-visible while webfonts are loading. Learn more about font-display.
Lazy load third-party resources with facades
Some third-party embeds can be lazy loaded. Consider replacing them with a facade until they are required. Learn how to defer third-parties with a facade.TBT
Largest Contentful Paint image was not lazily loaded
Above-the-fold images that are lazily loaded render later in the page lifecycle, which can delay the largest contentful paint. Learn more about optimal lazy loading.LCP
Element
GLO - HP Banner - Q1 Incentive
<img class="block w-full object-cover h-auto max-h-full max-w-full leading-none" alt="GLO - HP Banner - Q1 Incentive" decoding="async" height="343" loading="eager" sizes="100vw" src="https://www.backmarket.fr/cdn-cgi/image/format%3Dauto%2Cquality%3D75%2Cwid…" srcset="/cdn-cgi/image/format%3Dauto%2Cquality%3D75%2Cwidth%3D260/https://images.c…" width="1440">
Avoids document.write()
For users on slow connections, external scripts dynamically injected via document.write() can delay page load by tens of seconds. Learn how to avoid document.write().
Image elements have explicit width and height
Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensionsCLS
NuxtUse the nuxt/image component and specify explicit width and height. Learn more.
Has a <meta name="viewport"> tag with width or initial-scale
A <meta name="viewport"> not only optimizes your app for mobile screen sizes, but also prevents a 300 millisecond delay to user input. Learn more about using the viewport meta tag.
74
Accessibility
These checks highlight opportunities to improve the accessibility of your web app. Automatic detection can only detect a subset of issues and does not guarantee the accessibility of your web app, so manual testing is also encouraged.
ARIA
[aria-*] attributes do not match their roles
Each ARIA role supports a specific subset of aria-* attributes. Mismatching these invalidates the aria-* attributes. Learn how to match ARIA attributes to their roles.
Failing Elements
div.z-[1] > form.border-action-default-low > div.text-action-default-hi > input#searchBar-input
<input id="searchBar-input" aria-describedby="resultsListBoxAlert" aria-expanded="false" autocomplete="off" autocorrect="off" class="text-action-default-hi peer body-1 h-[38px] flex-1 appearance-none outline…" data-qa="search-bar-input" name="q" placeholder="Que cherchez-vous ?" role="searchbox" type="text" value="">
FR
<span id="trigger-j3i3c3okiwwcgicucbxnc" aria-controls="content-72juyh72ma4ayrkvd2bcv5" aria-expanded="false" aria-haspopup="true">
Elements with role="dialog" or role="alertdialog" do not have accessible names.
ARIA dialog elements without accessible names may prevent screen readers users from discerning the purpose of these elements. Learn how to make ARIA dialog elements more accessible.
Failing Elements
En sélectionnant « Tout accepter », vous autorisez Back Market et nos partenair…
<div aria-labelledby="modalTitle" aria-modal="true" class="bg-surface-default-hi rounded-t-lg fixed bottom-0 left-0 max-h-full w-full…" role="dialog" tabindex="0">
Elements use prohibited ARIA attributes
Using ARIA attributes in roles where they are prohibited can mean that important information is not communicated to users of assistive technologies. Learn more about prohibited ARIA roles.
Failing Elements
div.relative > div.relative > div.sr-only > span
<span aria-labelledby="cms-carousel">
div.relative > div.relative > div.sr-only > span
<span aria-labelledby="cms-carousel">
ARIA IDs are unique
The value of an ARIA ID must be unique to prevent other instances from being overlooked by assistive technologies. Learn how to fix duplicate ARIA IDs.
Failing Elements
FR - Samsung Galaxy
<li aria-hidden="false" class="flex w-full list-none justify-center motion-safe:animate-fade-in block" id="cms-carousel">
What is Verified Refurbished
<li id="cms-carousel" aria-hidden="false" class="flex w-full list-none justify-center motion-safe:animate-fade-in block">
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.
Names and labels
Buttons do not 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 how to make buttons more accessible.
Failing Elements
div.flex > div._invisibleScrollBar_nw9fi_2 > div.flex > button.bg-surface-default-low
<button class="bg-surface-default-low rounded-lg h-48 w-72 cursor-pointer border hover:bo…" data-test="recommendation-thumbnail" type="button">
div.flex > div._invisibleScrollBar_nw9fi_2 > div.flex > button.bg-surface-default-low
<button class="bg-surface-default-low rounded-lg h-48 w-72 cursor-pointer border hover:bo…" data-test="recommendation-thumbnail" type="button">
Image elements have [alt] attributes that are redundant text.
Informative elements should aim for short, descriptive alternative text. Alternative text that is exactly the same as the text adjacent to the link or image is potentially confusing for screen reader users, because the text will be read twice. Learn more about the alt attribute.
Failing Elements
FR
<img class="w-24 rounded-xs h-auto max-h-full max-w-full leading-none" alt="FR" decoding="async" height="16" loading="lazy" sizes="100vw" src="data:image/svg+xml,%3csvg%20width='36'%20height='24'%20viewBox='0%200%2036…" srcset="data:image/svg+xml,%3csvg%20width='36'%20height='24'%20viewBox='0%200%2036…" width="24">
Macbook
<img class="block w-full object-cover rounded-lg h-auto max-h-full max-w-full leading-…" alt="Macbook" decoding="async" height="180" loading="eager" sizes="100vw" src="https://www.backmarket.fr/cdn-cgi/image/format%3Dauto%2Cquality%3D75%2Cwid…" srcset="/cdn-cgi/image/format%3Dauto%2Cquality%3D75%2Cwidth%3D260/https://images.c…" width="268">
iPad
<img class="block w-full object-cover rounded-lg h-auto max-h-full max-w-full leading-…" alt="iPad" decoding="async" height="180" loading="eager" sizes="100vw" src="https://www.backmarket.fr/cdn-cgi/image/format%3Dauto%2Cquality%3D75%2Cwid…" srcset="/cdn-cgi/image/format%3Dauto%2Cquality%3D75%2Cwidth%3D260/https://images.c…" width="268">
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.
Best practices
[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 about the viewport meta tag.
Failing Elements
head > meta
<meta name="viewport" content="width=device-width, initial-scale=1, maximum-scale=1">
Touch targets do not have sufficient size or spacing.
Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.
Failing Elements
Diapositive 1
<button aria-current="false" aria-label="Diapositive 1" class="focus-visible-outline-default-hi relative cursor-pointer appearance-none o…" data-slide="0" type="button">
Diapositive 2
<button aria-current="true" aria-label="Diapositive 2" class="focus-visible-outline-default-hi relative cursor-pointer appearance-none o…" data-slide="1" type="button">
Diapositive 2
<button aria-current="true" aria-label="Diapositive 2" class="focus-visible-outline-default-hi relative cursor-pointer appearance-none o…" data-slide="1" type="button">
Diapositive 1
<button aria-current="false" aria-label="Diapositive 1" class="focus-visible-outline-default-hi relative cursor-pointer appearance-none o…" data-slide="0" type="button">
Diapositive 3
<button aria-current="false" aria-label="Diapositive 3" class="focus-visible-outline-default-hi relative cursor-pointer appearance-none o…" data-slide="2" type="button">
Diapositive 3
<button aria-current="false" aria-label="Diapositive 3" class="focus-visible-outline-default-hi relative cursor-pointer appearance-none o…" data-slide="2" type="button">
Diapositive 2
<button aria-current="true" aria-label="Diapositive 2" class="focus-visible-outline-default-hi relative cursor-pointer appearance-none o…" data-slide="1" type="button">
Diapositive 4
<button aria-current="false" aria-label="Diapositive 4" class="focus-visible-outline-default-hi relative cursor-pointer appearance-none o…" data-slide="3" type="button">
Diapositive 4
<button aria-current="false" aria-label="Diapositive 4" class="focus-visible-outline-default-hi relative cursor-pointer appearance-none o…" data-slide="3" type="button">
Diapositive 3
<button aria-current="false" aria-label="Diapositive 3" class="focus-visible-outline-default-hi relative cursor-pointer appearance-none o…" data-slide="2" type="button">
Diapositive 5
<button aria-current="false" aria-label="Diapositive 5" class="focus-visible-outline-default-hi relative cursor-pointer appearance-none o…" data-slide="4" type="button">
Diapositive 5
<button aria-current="false" aria-label="Diapositive 5" class="focus-visible-outline-default-hi relative cursor-pointer appearance-none o…" data-slide="4" type="button">
Diapositive 4
<button aria-current="false" aria-label="Diapositive 4" class="focus-visible-outline-default-hi relative cursor-pointer appearance-none o…" data-slide="3" type="button">
Diapositive 6
<button aria-current="false" aria-label="Diapositive 6" class="focus-visible-outline-default-hi relative cursor-pointer appearance-none o…" data-slide="5" type="button">
Diapositive 6
<button aria-current="false" aria-label="Diapositive 6" class="focus-visible-outline-default-hi relative cursor-pointer appearance-none o…" data-slide="5" type="button">
Diapositive 5
<button aria-current="false" aria-label="Diapositive 5" class="focus-visible-outline-default-hi relative cursor-pointer appearance-none o…" data-slide="4" type="button">
Diapositive 7
<button aria-current="false" aria-label="Diapositive 7" class="focus-visible-outline-default-hi relative cursor-pointer appearance-none o…" data-slide="6" type="button">
Diapositive 7
<button aria-current="false" aria-label="Diapositive 7" class="focus-visible-outline-default-hi relative cursor-pointer appearance-none o…" data-slide="6" type="button">
Diapositive 6
<button aria-current="false" aria-label="Diapositive 6" class="focus-visible-outline-default-hi relative cursor-pointer appearance-none o…" data-slide="5" type="button">
Diapositive 1
<button aria-current="true" aria-label="Diapositive 1" class="focus-visible-outline-default-hi relative cursor-pointer appearance-none o…" data-slide="0" type="button">
Diapositive 2
<button aria-current="false" aria-label="Diapositive 2" class="focus-visible-outline-default-hi relative cursor-pointer appearance-none o…" data-slide="1" type="button">
Diapositive 2
<button aria-current="false" aria-label="Diapositive 2" class="focus-visible-outline-default-hi relative cursor-pointer appearance-none o…" data-slide="1" type="button">
Diapositive 1
<button aria-current="true" aria-label="Diapositive 1" class="focus-visible-outline-default-hi relative cursor-pointer appearance-none o…" data-slide="0" type="button">
Diapositive 3
<button aria-current="false" aria-label="Diapositive 3" class="focus-visible-outline-default-hi relative cursor-pointer appearance-none o…" data-slide="2" type="button">
Diapositive 3
<button aria-current="false" aria-label="Diapositive 3" class="focus-visible-outline-default-hi relative cursor-pointer appearance-none o…" data-slide="2" type="button">
Diapositive 2
<button aria-current="false" aria-label="Diapositive 2" class="focus-visible-outline-default-hi relative cursor-pointer appearance-none o…" data-slide="1" type="button">
Diapositive 4
<button aria-current="false" aria-label="Diapositive 4" class="focus-visible-outline-default-hi relative cursor-pointer appearance-none o…" data-slide="3" type="button">
Diapositive 4
<button aria-current="false" aria-label="Diapositive 4" class="focus-visible-outline-default-hi relative cursor-pointer appearance-none o…" data-slide="3" type="button">
Diapositive 3
<button aria-current="false" aria-label="Diapositive 3" class="focus-visible-outline-default-hi relative cursor-pointer appearance-none o…" data-slide="2" type="button">
Diapositive 5
<button aria-current="false" aria-label="Diapositive 5" class="focus-visible-outline-default-hi relative cursor-pointer appearance-none o…" data-slide="4" type="button">
Diapositive 5
<button aria-current="false" aria-label="Diapositive 5" class="focus-visible-outline-default-hi relative cursor-pointer appearance-none o…" data-slide="4" type="button">
Diapositive 4
<button aria-current="false" aria-label="Diapositive 4" class="focus-visible-outline-default-hi relative cursor-pointer appearance-none o…" data-slide="3" type="button">
These items highlight common accessibility best practices.
Additional items to manually check (10)
Show Hide
Interactive controls are keyboard focusable
Custom interactive controls are keyboard focusable and display a focus indicator. Learn how to make custom controls focusable.
Interactive elements indicate their purpose and state
Interactive elements, such as links and buttons, should indicate their state and be distinguishable from non-interactive elements. Learn how to decorate interactive elements with affordance hints.
The page has a logical tab order
Tabbing through the page follows the visual layout. Users cannot focus elements that are offscreen. Learn more about logical tab ordering.
Visual order on the page follows DOM order
DOM order matches the visual order, improving navigation for assistive technology. Learn more about DOM and visual ordering.
User focus is not accidentally trapped in a region
A user can tab into and out of any control or region without accidentally trapping their focus. Learn how to avoid focus traps.
The user's focus is directed to new content added to the page
If new content, such as a dialog, is added to the page, the user's focus is directed to it. Learn how to direct focus to new content.
HTML5 landmark elements are used to improve navigation
Landmark elements (<main>, <nav>, etc.) are used to improve the keyboard navigation of the page for assistive technology. Learn more about landmark elements.
Offscreen content is hidden from assistive technology
Offscreen content is hidden with display: none or aria-hidden=true. Learn how to properly hide offscreen content.
Custom controls have associated labels
Custom interactive controls have associated labels, provided by aria-label or aria-labelledby. Learn more about custom controls and labels.
Custom controls have ARIA roles
Custom interactive controls have appropriate ARIA roles. Learn how to add roles to custom controls.
These items address areas which an automated testing tool cannot cover. Learn more in our guide on conducting an accessibility review.
Passed audits (21)
Show Hide
[aria-hidden="true"] is not present on the document <body>
Assistive technologies, like screen readers, work inconsistently when aria-hidden="true" is set on the document <body>. Learn how aria-hidden affects the document body.
[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 about roles and required attributes.
[aria-*] attributes have valid values
Assistive technologies, like screen readers, can't interpret ARIA attributes with invalid values. Learn more about valid values for ARIA attributes.
[aria-*] attributes are valid and not misspelled
Assistive technologies, like screen readers, can't interpret ARIA attributes with invalid names. Learn more about valid ARIA attributes.
Image elements have [alt] attributes
Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the alt attribute.
ARIA attributes are used as specified for the element's role
Some ARIA attributes are only allowed on an element under certain conditions. Learn more about conditional ARIA attributes.
[aria-hidden="true"] elements do not contain focusable descendents
Focusable descendents within an [aria-hidden="true"] element prevent those interactive elements from being available to users of assistive technologies like screen readers. Learn how aria-hidden affects focusable elements.
[role] values are valid
ARIA roles must have valid values in order to perform their intended accessibility functions. Learn more about valid ARIA roles.
Background and foreground colors have a sufficient contrast ratio
Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.
Document has a <title> element
The title gives screen reader users an overview of the page, and search engine users rely on it heavily to determine if a page is relevant to their search. Learn more about document titles.
<html> element has 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 about the lang attribute.
<html> element has a valid value for its [lang] attribute
Specifying a valid BCP 47 language helps screen readers announce text properly. Learn how to use the lang attribute.
Form elements have associated labels
Labels ensure that form controls are announced properly by assistive technologies, like screen readers. Learn more about form element labels.
Links are distinguishable without relying on color.
Low-contrast text is difficult or impossible for many users to read. Link text that is discernible improves the experience for users with low vision. Learn how to make links distinguishable.
Links have a discernible 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 how to make links accessible.
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 about proper list structure.
List items (<li>) are contained within <ul>, <ol> or <menu> parent elements
Screen readers require list items (<li>) to be contained within a parent <ul>, <ol> or <menu> to be announced properly. Learn more about proper list structure.
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 about the tabindex attribute.
Heading elements appear in a sequentially-descending order
Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.
Uses ARIA roles only on compatible elements
Many HTML elements can only be assigned certain ARIA roles. Using ARIA roles where they are not allowed can interfere with the accessibility of the web page. Learn more about ARIA roles.
Deprecated ARIA roles were not used
Deprecated ARIA roles may not be processed correctly by assistive technology. Learn more about deprecated ARIA roles.
Not applicable (28)
Show Hide
[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 about access keys.
button, link, and menuitem elements have accessible names
When an element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn how to make command elements more accessible.
ARIA input fields have accessible names
When an input field doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn more about input field labels.
ARIA meter elements have accessible names
When a meter element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn how to name meter elements.
ARIA progressbar elements have accessible names
When a progressbar element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn how to label progressbar elements.
Elements with an ARIA [role] that require children to contain a specific [role] have all required children.
Some ARIA parent roles must contain specific child roles to perform their intended accessibility functions. Learn more about roles and required children elements.
[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 about ARIA roles and required parent element.
Elements with the role=text attribute do not have focusable descendents.
Adding role=text around a text node split by markup enables VoiceOver to treat it as one phrase, but the element's focusable descendents will not be announced. Learn more about the role=text attribute.
ARIA toggle fields have accessible names
When a toggle field doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn more about toggle fields.
ARIA tooltip elements have accessible names
When a tooltip element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn how to name tooltip elements.
ARIA treeitem elements have accessible names
When a treeitem element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn more about labeling treeitem elements.
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 about bypass blocks.
<dl>'s contain only properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements.
When definition lists are not properly marked up, screen readers may produce confusing or inaccurate output. Learn how to structure definition lists correctly.
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 how to structure definition lists correctly.
No form fields have multiple labels
Form fields with multiple labels can be confusingly announced by assistive technologies like screen readers which use either the first, the last, or all of the labels. Learn how to use form labels.
<frame> or <iframe> elements have a title
Screen reader users rely on frame titles to describe the contents of frames. Learn more about frame titles.
<html> element has an [xml:lang] attribute with the same base language as the [lang] attribute.
If the webpage does not specify a consistent language, then the screen reader might not announce the page's text correctly. Learn more about the lang attribute.
Input buttons have discernible text.
Adding discernable and accessible text to input buttons may help screen reader users understand the purpose of the input button. Learn more about input buttons.
<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 about input image alt text.
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 about the refresh meta tag.
<object> elements have alternate text
Screen readers cannot translate non-text content. Adding alternate text to <object> elements helps screen readers convey meaning to users. Learn more about alt text for object elements.
Select elements have associated label elements.
Form elements without effective labels can create frustrating experiences for screen reader users. Learn more about the select element.
Tables have different content in the summary attribute and <caption>.
The summary attribute should describe the table structure, while <caption> should have the onscreen title. Accurate table mark-up helps users of screen readers. Learn more about summary and caption.
Cells in a <table> element that use the [headers] attribute refer to table cells within the 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 about the headers attribute.
<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 about table headers.
[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 how to use the lang attribute.
<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 about video captions.
100
Best Practices
Trust and Safety
Ensure CSP is effective against XSS attacks
A strong Content Security Policy (CSP) significantly reduces the risk of cross-site scripting (XSS) attacks. Learn how to use a CSP to prevent XSS
Description
Directive
Severity
No CSP found in enforcement mode
High
General
Detected JavaScript libraries
All front-end JavaScript libraries detected on the page. Learn more about this JavaScript library detection diagnostic audit.
Name
Version
Nuxt.js
core-js
core-js-pure@3.40.0
Missing source maps for large first-party JavaScript
Source maps translate minified code to the original source code. This helps developers debug in production. In addition, Lighthouse is able to provide further insights. Consider deploying source maps to take advantage of these benefits. Learn more about source maps.
URL
Map URL
backmarket.fr
1st party
/fr-fr
(www.backmarket.fr)
Large JavaScript file is missing a source map
backmarket.com
…_nuxt/VideosBlock.B4dAMETN.js
(front-office.statics.backmarket.com)
…_nuxt/VideosBlock.B4dAMETN.js.map
(front-office.statics.backmarket.com)
…_nuxt/UserCommentModal.t54Dksp_.js
(front-office.statics.backmarket.com)
…_nuxt/UserCommentModal.t54Dksp_.js.map
(front-office.statics.backmarket.com)
…_nuxt/useLogout.DME5LXjP.js
(front-office.statics.backmarket.com)
…_nuxt/useLogout.DME5LXjP.js.map
(front-office.statics.backmarket.com)
…_nuxt/useFooter….Bfua1zZY.js
(front-office.statics.backmarket.com)
…_nuxt/useFooter….Bfua1zZY.js.map
(front-office.statics.backmarket.com)
…_nuxt/useFetchPageContent.BCCBGDsn.js
(front-office.statics.backmarket.com)
…_nuxt/useFetchPageContent.BCCBGDsn.js.map
(front-office.statics.backmarket.com)
…_nuxt/useAlgolia.BFi66Qj7.js
(front-office.statics.backmarket.com)
…_nuxt/useAlgolia.BFi66Qj7.js.map
(front-office.statics.backmarket.com)
…_nuxt/TrustpilotWidget.DFlucsDh.js
(front-office.statics.backmarket.com)
…_nuxt/TrustpilotWidget.DFlucsDh.js.map
(front-office.statics.backmarket.com)
…_nuxt/SocialMediaEmbed.BmAIYN8L.js
(front-office.statics.backmarket.com)
…_nuxt/SocialMediaEmbed.BmAIYN8L.js.map
(front-office.statics.backmarket.com)
…_nuxt/SkinnyBanner.vue.C_t3iY7Z.js
(front-office.statics.backmarket.com)
…_nuxt/SkinnyBanner.vue.C_t3iY7Z.js.map
(front-office.statics.backmarket.com)
…_nuxt/SectionBanner.DKAl42QZ.js
(front-office.statics.backmarket.com)
…_nuxt/SectionBanner.DKAl42QZ.js.map
(front-office.statics.backmarket.com)
…_nuxt/RichText.BqcuRBkr.js
(front-office.statics.backmarket.com)
…_nuxt/RichText.BqcuRBkr.js.map
(front-office.statics.backmarket.com)
…_nuxt/Reviews.BoNLJ5AQ.js
(front-office.statics.backmarket.com)
…_nuxt/Reviews.BoNLJ5AQ.js.map
(front-office.statics.backmarket.com)
…_nuxt/Recommendations.CmXpKmQD.js
(front-office.statics.backmarket.com)
…_nuxt/Recommendations.CmXpKmQD.js.map
(front-office.statics.backmarket.com)
…_nuxt/recommend….DDeUi7cy.js
(front-office.statics.backmarket.com)
…_nuxt/recommend….DDeUi7cy.js.map
(front-office.statics.backmarket.com)
…_nuxt/Products.BBT9btKm.js
(front-office.statics.backmarket.com)
…_nuxt/Products.BBT9btKm.js.map
(front-office.statics.backmarket.com)
…_nuxt/ProductCardCarousel.vue.qeFbQcvn.js
(front-office.statics.backmarket.com)
…_nuxt/ProductCardCarousel.vue.qeFbQcvn.js.map
(front-office.statics.backmarket.com)
…_nuxt/ModularCa….BCfz8sCZ.js
(front-office.statics.backmarket.com)
…_nuxt/ModularCa….BCfz8sCZ.js.map
(front-office.statics.backmarket.com)
…_nuxt/ModularCardImage.DDnj35Vm.js
(front-office.statics.backmarket.com)
…_nuxt/ModularCardImage.DDnj35Vm.js.map
(front-office.statics.backmarket.com)
…_nuxt/MobileAppBanner.vue.CmpP_UJm.js
(front-office.statics.backmarket.com)
…_nuxt/MobileAppBanner.vue.CmpP_UJm.js.map
(front-office.statics.backmarket.com)
…_nuxt/Media.CYxgitS-.js
(front-office.statics.backmarket.com)
…_nuxt/Media.CYxgitS-.js.map
(front-office.statics.backmarket.com)
…_nuxt/InputSelectItem.vue.1xOyxAWy.js
(front-office.statics.backmarket.com)
…_nuxt/InputSelectItem.vue.1xOyxAWy.js.map
(front-office.statics.backmarket.com)
…_nuxt/index.DKXniy5T.js
(front-office.statics.backmarket.com)
…_nuxt/index.DKXniy5T.js.map
(front-office.statics.backmarket.com)
…_nuxt/index.D8ZxCYCV.js
(front-office.statics.backmarket.com)
…_nuxt/index.D8ZxCYCV.js.map
(front-office.statics.backmarket.com)
…_nuxt/index.CqFBXIJu.js
(front-office.statics.backmarket.com)
…_nuxt/index.CqFBXIJu.js.map
(front-office.statics.backmarket.com)
…_nuxt/IconSunFace.DguFtgLq.js
(front-office.statics.backmarket.com)
…_nuxt/IconSunFace.DguFtgLq.js.map
(front-office.statics.backmarket.com)
…_nuxt/IconMoreVertical.B3hyVza0.js
(front-office.statics.backmarket.com)
…_nuxt/IconMoreVertical.B3hyVza0.js.map
(front-office.statics.backmarket.com)
…_nuxt/Home.Dh0SfaEg.js
(front-office.statics.backmarket.com)
…_nuxt/Home.Dh0SfaEg.js.map
(front-office.statics.backmarket.com)
…_nuxt/Form.vue2.afXhp2pQ.js
(front-office.statics.backmarket.com)
…_nuxt/Form.vue2.afXhp2pQ.js.map
(front-office.statics.backmarket.com)
…_nuxt/Faq.As4M2F0b.js
(front-office.statics.backmarket.com)
…_nuxt/Faq.As4M2F0b.js.map
(front-office.statics.backmarket.com)
…_nuxt/entry.Bs2bIzRW.js
(front-office.statics.backmarket.com)
…_nuxt/entry.Bs2bIzRW.js.map
(front-office.statics.backmarket.com)
…_nuxt/EnhancedCarousel.CY-p7yHT.js
(front-office.statics.backmarket.com)
…_nuxt/EnhancedCarousel.CY-p7yHT.js.map
(front-office.statics.backmarket.com)
…_nuxt/EmailCollector.ny0BrYFD.js
(front-office.statics.backmarket.com)
…_nuxt/EmailCollector.ny0BrYFD.js.map
(front-office.statics.backmarket.com)
…_nuxt/el-GR.B0HUlPw2.js
(front-office.statics.backmarket.com)
…_nuxt/el-GR.B0HUlPw2.js.map
(front-office.statics.backmarket.com)
…_nuxt/default.BvJTZVXQ.js
(front-office.statics.backmarket.com)
…_nuxt/default.BvJTZVXQ.js.map
(front-office.statics.backmarket.com)
…_nuxt/Cookies.D0NQjIDM.js
(front-office.statics.backmarket.com)
…_nuxt/Cookies.D0NQjIDM.js.map
(front-office.statics.backmarket.com)
…_nuxt/constants.DfcgOMTc.js
(front-office.statics.backmarket.com)
…_nuxt/constants.DfcgOMTc.js.map
(front-office.statics.backmarket.com)
…_nuxt/Categories.Beq3oKCm.js
(front-office.statics.backmarket.com)
…_nuxt/Categories.Beq3oKCm.js.map
(front-office.statics.backmarket.com)
…_nuxt/Carousel.CHgz4WAQ.js
(front-office.statics.backmarket.com)
…_nuxt/Carousel.CHgz4WAQ.js.map
(front-office.statics.backmarket.com)
…_nuxt/ArticleCardsList.EtuQa7DX.js
(front-office.statics.backmarket.com)
…_nuxt/ArticleCardsList.EtuQa7DX.js.map
(front-office.statics.backmarket.com)
…_nuxt/ar.GHrHWN67.js
(front-office.statics.backmarket.com)
…_nuxt/ar.GHrHWN67.js.map
(front-office.statics.backmarket.com)
…_nuxt/algoliaFunctions.DY2th9gi.js
(front-office.statics.backmarket.com)
…_nuxt/algoliaFunctions.DY2th9gi.js.map
(front-office.statics.backmarket.com)
Passed audits (13)
Show Hide
Uses HTTPS
All sites should be protected with HTTPS, even ones that don't handle sensitive data. This includes avoiding mixed content, where some resources are loaded over HTTP despite the initial request being served over HTTPS. 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 about HTTPS.
Avoids deprecated APIs
Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs.
Avoids third-party cookies
Chrome is moving towards a new experience that allows users to choose to browse without third-party cookies. Learn more about third-party cookies.
Allows users to paste into input fields
Preventing input pasting is a bad practice for the UX, and weakens security by blocking password managers.Learn more about user-friendly input fields.
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 a user action instead. Learn more about the geolocation permission.
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 about responsibly getting permission for notifications.
Displays images with correct aspect ratio
Image display dimensions should match natural aspect ratio. Learn more about image aspect ratio.
Serves images with appropriate resolution
Image natural dimensions should be proportional to the display size and the pixel ratio to maximize image clarity. Learn how to provide responsive images.
Has a <meta name="viewport"> tag with width or initial-scale
A <meta name="viewport"> not only optimizes your app for mobile screen sizes, but also prevents a 300 millisecond delay to user input. Learn more about using the viewport meta tag.
Page has the HTML doctype
Specifying a doctype prevents the browser from switching to quirks-mode. Learn more about the doctype declaration.
Properly defines charset
A character encoding declaration is required. It can be done with a <meta> tag in the first 1024 bytes of the HTML or in the Content-Type HTTP response header. Learn more about declaring the character encoding.
No browser errors logged to the console
Errors logged to the console indicate unresolved problems. They can come from network request failures and other browser concerns. Learn more about this errors in console diagnostic audit
No issues in the Issues panel in Chrome Devtools
Issues logged to the Issues panel in Chrome Devtools indicate unresolved problems. They can come from network request failures, insufficient security controls, and other browser concerns. Open up the Issues panel in Chrome DevTools for more details on each issue.
Not applicable (2)
Show Hide
Redirects HTTP traffic to HTTPS
Make sure that you redirect all HTTP traffic to HTTPS in order to enable secure web features for all your users. Learn more.
Document uses legible font sizes
Font sizes less than 12px are too small to be legible and require mobile visitors to “pinch to zoom” in order to read. Strive to have >60% of page text ≥12px. Learn more about legible font sizes.
100
SEO
These checks ensure that your page is following basic search engine optimization advice. There are many additional factors Lighthouse does not score here that may affect your search ranking, including performance on Core Web Vitals. Learn more about Google Search Essentials.
Additional items to manually check (1)
Show Hide
Structured data is valid
Run the Structured Data Testing Tool and the Structured Data Linter to validate structured data. Learn more about Structured Data.
Run these additional validators on your site to check additional SEO best practices.
Passed audits (10)
Show Hide
Page isn’t blocked from indexing
Search engines are unable to include your pages in search results if they don't have permission to crawl them. Learn more about crawler directives.
Document has a <title> element
The title gives screen reader users an overview of the page, and search engine users rely on it heavily to determine if a page is relevant to their search. Learn more about document titles.
Document has a meta description
Meta descriptions may be included in search results to concisely summarize page content. Learn more about the meta description.
Page has successful HTTP status code
Pages with unsuccessful HTTP status codes may not be indexed properly. Learn more about HTTP status codes.
Links have descriptive text
Descriptive link text helps search engines understand your content. Learn how to make links more accessible.
Links are crawlable
Search engines may use href attributes on links to crawl websites. Ensure that the href attribute of anchor elements links to an appropriate destination, so more pages of the site can be discovered. Learn how to make links crawlable
robots.txt is valid
If your robots.txt file is malformed, crawlers may not be able to understand how you want your website to be crawled or indexed. Learn more about robots.txt.
Image elements have [alt] attributes
Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the alt attribute.
Document has a valid hreflang
hreflang links tell search engines what version of a page they should list in search results for a given language or region. Learn more about hreflang.
Document has a valid rel=canonical
Canonical links suggest which URL to show in search results. Learn more about canonical links.