PageSpeed Insights logo
PageSpeed Insights
PageSpeed Insights
This site uses cookies from Google to deliver its services and to analyze traffic.
Report from Mar 4, 2025, 8:00:28 AM
Discover what your real users are experiencing
Core Web Vitals Assessment: Passed
Largest Contentful Paint (LCP)
1.8 s
Page LoadsGood (≤ 2.5 s)87%Needs Improvement (2.5 s - 4 s)8%Poor (> 4 s)6%75th Percentile - 1.8 sCore Web Vital
Interaction to Next Paint (INP)
200 ms
Page LoadsGood (≤ 200 ms)75%Needs Improvement (200 ms - 500 ms)17%Poor (> 500 ms)8%75th Percentile - 200 msCore Web Vital
Cumulative Layout Shift (CLS)
0
Page LoadsGood (≤ 0.1)96%Needs Improvement (0.1 - 0.25)3%Poor (> 0.25)2%75th Percentile - 0Core Web Vital
Other Notable Metrics
First Contentful Paint (FCP)
1.2 s
Page LoadsGood (≤ 1.8 s)88%Needs Improvement (1.8 s - 3 s)7%Poor (> 3 s)5%75th Percentile - 1.2 s 
Time to First Byte (TTFB)
0.9 s
Page LoadsGood (≤ 0.8 s)72%Needs Improvement (0.8 s - 1.8 s)21%Poor (> 1.8 s)8%75th Percentile - 0.9 sExperimental
Latest 28-day collection period
Various mobile devicesMany samples (Chrome UX Report)Full visit durationsVarious network connectionsAll Chrome versions
Core Web Vitals Assessment: Passed
Largest Contentful Paint (LCP)
1.2 s
Page LoadsGood (≤ 2.5 s)93%Needs Improvement (2.5 s - 4 s)5%Poor (> 4 s)3%75th Percentile - 1.2 sCore Web Vital
Interaction to Next Paint (INP)
144 ms
Page LoadsGood (≤ 200 ms)85%Needs Improvement (200 ms - 500 ms)11%Poor (> 500 ms)4%75th Percentile - 144 msCore Web Vital
Cumulative Layout Shift (CLS)
0.06
Page LoadsGood (≤ 0.1)87%Needs Improvement (0.1 - 0.25)8%Poor (> 0.25)5%75th Percentile - 0.06Core Web Vital
Other Notable Metrics
First Contentful Paint (FCP)
1 s
Page LoadsGood (≤ 1.8 s)90%Needs Improvement (1.8 s - 3 s)6%Poor (> 3 s)3%75th Percentile - 1 s 
Time to First Byte (TTFB)
0.7 s
Page LoadsGood (≤ 0.8 s)79%Needs Improvement (0.8 s - 1.8 s)15%Poor (> 1.8 s)6%75th Percentile - 0.7 sExperimental
Latest 28-day collection period
Various mobile devicesMany samples (Chrome UX Report)Full visit durationsVarious network connectionsAll Chrome versions
Diagnose performance issues
45 FCP+10LCP+0TBT+8CLS+25SI+1 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.5 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.5 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
980 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.018
Cumulative Layout Shift measures the movement of visible elements within the viewport. Learn more about the Cumulative Layout Shift metric.
Speed Index
9.3 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more about the Speed Index metric.
  • Captured at Mar 4, 2025, 8:00 AM UTC
  • Emulated Moto G Power with Lighthouse 12.4.0
    Unthrottled CPU/Memory Power: 467 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.126 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,520 ms
This is the largest contentful element painted within the viewport. Learn more about the Largest Contentful Paint elementLCP
Element
Style Urbain
<img width="260" height="260" loading="lazy" src="/medias/cross-sell-fl-e25-look-essentiels-MIXTE-parka-alliance.jpg?context…" alt="Style Urbain">
Phase
% of LCP
Timing
TTFB
7%
600 ms
Load Delay
49%
4,140 ms
Load Time
4%
310 ms
Render Delay
41%
3,460 ms
Reduce JavaScript execution time 3.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
jacadi.fr
1st party
2,034 ms
914 ms
25 ms
1,121 ms
497 ms
6 ms
565 ms
145 ms
2 ms
124 ms
108 ms
13 ms
112 ms
66 ms
0 ms
111 ms
97 ms
3 ms
Unattributable
960 ms
276 ms
0 ms
Unattributable
650 ms
172 ms
0 ms
(program):2
310 ms
105 ms
0 ms
Dailymotion
content
840 ms
636 ms
45 ms
290 ms
268 ms
12 ms
152 ms
143 ms
6 ms
146 ms
75 ms
13 ms
96 ms
81 ms
3 ms
80 ms
2 ms
3 ms
76 ms
66 ms
8 ms
Google Tag Manager
tag-manager
441 ms
393 ms
18 ms
/gtm.js?id=GTM-THZXBP
(www.googletagmanager.com)
441 ms
393 ms
18 ms
Amazon Web Services
other
434 ms
248 ms
15 ms
…prod/velou.min.js
(velou-cloudfront.s3.amazonaws.com)
434 ms
248 ms
15 ms
JSDelivr CDN
cdn
306 ms
274 ms
31 ms
…umd/identity-ui.min.js
(cdn.jsdelivr.net)
306 ms
274 ms
31 ms
Forter
utility
201 ms
188 ms
8 ms
…afd1ebd5256b/script.js
(afd1ebd5256b.cdn4.forter.com)
201 ms
188 ms
8 ms
AB Tasty
analytics
154 ms
143 ms
7 ms
154 ms
143 ms
7 ms
mPulse
analytics
65 ms
59 ms
5 ms
65 ms
59 ms
5 ms
Minimize main-thread work 5.9 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
3,499 ms
Other
929 ms
Style & Layout
742 ms
Garbage Collection
272 ms
Script Parsing & Compilation
201 ms
Parse HTML & CSS
160 ms
Rendering
123 ms
Reduce the impact of third-party code Third-party code blocked the main thread for 680 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
97 KiB
267 ms
/gtm.js?id=GTM-THZXBP
(www.googletagmanager.com)
97 KiB
267 ms
Amazon Web Services
other
382 KiB
153 ms
…prod/velou.min.js
(velou-cloudfront.s3.amazonaws.com)
382 KiB
153 ms
JSDelivr CDN
cdn
288 KiB
120 ms
…umd/identity-ui.min.js
(cdn.jsdelivr.net)
288 KiB
120 ms
Dailymotion
content
698 KiB
91 ms
75 KiB
57 ms
142 KiB
21 ms
129 KiB
12 ms
8 KiB
1 ms
8 KiB
0 ms
/ABCFavorit-Regular.woff2
(static1.dmcdn.net)
99 KiB
0 ms
64 KiB
0 ms
/DailySans-Bulky.woff2
(static1.dmcdn.net)
39 KiB
0 ms
35 KiB
0 ms
29 KiB
0 ms
25 KiB
0 ms
21 KiB
0 ms
7 KiB
0 ms
…video/x9e5ewm?embedder=…
(www.dailymotion.com)
6 KiB
0 ms
6 KiB
0 ms
…video/x9e5ewo?embedder=…
(www.dailymotion.com)
6 KiB
0 ms
1 KiB
0 ms
AB Tasty
analytics
97 KiB
43 ms
65 KiB
43 ms
/shared/me.0c0baf9….js
(try.abtasty.com)
4 KiB
0 ms
/de369e8….js
(try.abtasty.com)
3 KiB
0 ms
7 KiB
0 ms
4 KiB
0 ms
/de369e8…/paypal.svg
(assets-manager.abtasty.com)
3 KiB
0 ms
/de369e8…/applepay.svg
(assets-manager.abtasty.com)
2 KiB
0 ms
/de369e8…/maestro.svg
(assets-manager.abtasty.com)
1 KiB
0 ms
/de369e8…/klarna.svg
(assets-manager.abtasty.com)
1 KiB
0 ms
1 KiB
0 ms
/de369e8…/visa.svg
(assets-manager.abtasty.com)
1 KiB
0 ms
/de369e8…/amex.svg
(assets-manager.abtasty.com)
1 KiB
0 ms
/de369e8…/mastercard.svg
(assets-manager.abtasty.com)
1 KiB
0 ms
/v1/geoip?weather=false
(dcinfos-cache.abtasty.com)
1 KiB
0 ms
/v1/ua-parser
(dcinfos-cache.abtasty.com)
1 KiB
0 ms
XiTi
analytics
26 KiB
7 ms
/piano-analytics.js
(tag.aticdn.net)
26 KiB
7 ms
mPulse
analytics
47 KiB
2 ms
47 KiB
2 ms
/api/config.json?key=…
(c.go-mpulse.net)
0 KiB
0 ms
Forter
utility
155 KiB
0 ms
…afd1ebd5256b/script.js
(afd1ebd5256b.cdn4.forter.com)
153 KiB
0 ms
…b5fdd3f…/wpt.json
(cdn0.euw.forter.com)
1 KiB
0 ms
0 KiB
0 ms
0 KiB
0 ms
0 KiB
0 ms
/prop.json
(b5fdd3f159154816b61b1652a6ad45b5-afd1ebd5256b.cdn.euw.forter.com)
0 KiB
0 ms
/events
(cdn3.euw.forter.com)
0 KiB
0 ms
get-potions.com
65 KiB
0 ms
/jacadi-fr/potions.js
(client.get-potions.com)
35 KiB
0 ms
/80/recos-tag.js
(client.get-potions.com)
19 KiB
0 ms
…80/recos
(client.experiences.get-potions.com)
7 KiB
0 ms
…multiply/rules.json
(client.get-potions.com)
1 KiB
0 ms
…page_enricher/rules.json
(client.get-potions.com)
1 KiB
0 ms
…cart_recorder/rules.json
(client.get-potions.com)
1 KiB
0 ms
TagCommander
tag-manager
17 KiB
0 ms
/6846/tc_jacadi_1.js
(cdn.tagcommander.com)
17 KiB
0 ms
SpeedCurve RUM
analytics
11 KiB
0 ms
/js/lux.js?id=445…
(cdn.speedcurve.com)
11 KiB
0 ms
dm-event.net
4 KiB
0 ms
4 KiB
0 ms
reach5.co
4 KiB
0 ms
…sdk/fr.json
(assets.reach5.co)
4 KiB
0 ms
botmind.ai
2 KiB
0 ms
/public/widget.js
(widget.botmind.ai)
2 KiB
0 ms
velou.com
1 KiB
0 ms
/tracking
(api-analytics.velou.com)
1 KiB
0 ms
/popular-searches
(api-search-jacadi.velou.com)
1 KiB
0 ms
axept.io
1 KiB
0 ms
/sdk.js
(static.axept.io)
1 KiB
0 ms
cloudfront.net
1 KiB
0 ms
/events
(dz8rit8v72mig.cloudfront.net)
1 KiB
0 ms
pa-cd.com
0 KiB
0 ms
0 KiB
0 ms
Enable text compression Potential savings of 272 KiB
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. Learn more about text compression.LCPFCP
URL
Transfer Size
Potential Savings
Amazon Web Services
other
382.0 KiB
267.2 KiB
…prod/velou.min.js
(velou-cloudfront.s3.amazonaws.com)
382.0 KiB
267.2 KiB
get-potions.com
6.2 KiB
5.0 KiB
…80/recos
(client.experiences.get-potions.com)
6.2 KiB
5.0 KiB
Largest Contentful Paint image was 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
Style Urbain
<img width="260" height="260" loading="lazy" src="/medias/cross-sell-fl-e25-look-essentiels-MIXTE-parka-alliance.jpg?context…" alt="Style Urbain">
Reduce unused JavaScript Potential savings of 750 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
Dailymotion
content
327.5 KiB
233.2 KiB
70.6 KiB
47.1 KiB
70.6 KiB
47.1 KiB
61.5 KiB
45.5 KiB
61.5 KiB
45.5 KiB
31.6 KiB
24.0 KiB
31.6 KiB
24.0 KiB
JSDelivr CDN
cdn
281.0 KiB
135.3 KiB
…umd/identity-ui.min.js
(cdn.jsdelivr.net)
281.0 KiB
135.3 KiB
…node_modules/@reachfive/identity-core/es/main.js
76.1 KiB
49.1 KiB
…node_modules/react-dom/cjs/react-dom.production.min.js
35.3 KiB
15.3 KiB
…node_modules/marked/lib/marked.esm.js
10.6 KiB
7.1 KiB
…node_modules/react-phone-number-input/modules/PhoneInputWithCountry.js
3.0 KiB
2.1 KiB
…src/icons/webauthn/keepassxc.svg
1.9 KiB
1.9 KiB
Amazon Web Services
other
382.0 KiB
131.0 KiB
…prod/velou.min.js
(velou-cloudfront.s3.amazonaws.com)
382.0 KiB
131.0 KiB
jacadi.fr
1st party
186.9 KiB
119.2 KiB
131.2 KiB
69.4 KiB
55.8 KiB
49.8 KiB
Forter
utility
152.3 KiB
43.4 KiB
…afd1ebd5256b/script.js
(afd1ebd5256b.cdn4.forter.com)
152.3 KiB
43.4 KiB
Google Tag Manager
tag-manager
96.2 KiB
33.7 KiB
/gtm.js?id=GTM-THZXBP
(www.googletagmanager.com)
96.2 KiB
33.7 KiB
mPulse
analytics
46.7 KiB
30.8 KiB
46.7 KiB
30.8 KiB
get-potions.com
34.6 KiB
23.3 KiB
/jacadi-fr/potions.js
(client.get-potions.com)
34.6 KiB
23.3 KiB
Avoid an excessive DOM size 1,569 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
1,569
Maximum DOM Depth
Lookbook
<span class="jac-nav-panel-list-item-link-label">
18
Maximum Child Elements
body.page-homepage
<body class="page-homepage pageType-ContentPage template-pages-layout-homepageLayout pa…" data-frz-flags="{&quot;lazyload&quot;:false,&quot;unlazyload&quot;:false,&quot;deferjs&quot;:false,&quot;cssontop&quot;:true,&quot;mini…" data-frz-version="2" data-frz-target-key="homepage" data-frz-target-label="Homepage">
100
Reduce initial server response time Root document took 660 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
jacadi.fr
1st party
660 ms
660 ms
Reduce unused CSS Potential savings of 89 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
jacadi.fr
1st party
69.5 KiB
66.8 KiB
…css/jacadi-R93.css
(www.jacadi.fr)
69.5 KiB
66.8 KiB
Unattributable
22.0 KiB
21.9 KiB
@charset "utf-8";.vl-root{max-width:100%;position:relative;overflow:hidden} …
22.0 KiB
21.9 KiB
Properly size images Potential savings of 40 KiB
Serve images that are appropriately-sized to save cellular data and improve load time. Learn how to size images.LCPFCP
URL
Resource Size
Potential Savings
jacadi.fr
1st party
132.8 KiB
39.8 KiB
Nouvelle collection Sport Chic
<img width="1147" height="714" loading="lazy" src="https://www.jacadi.fr/medias/Mineur-atelier-design-be-be-mobile-750x860-.j…" alt="Nouvelle collection Sport Chic">
82.0 KiB
21.5 KiB
Preppy chic
<img width="260" height="260" loading="lazy" src="/medias/cross-sell-fl-e25-look-essentiels-MIXTE-pull-conquete.jpg?context=…" alt="Preppy chic ">
19.2 KiB
6.9 KiB
Style Urbain
<img width="260" height="260" loading="lazy" src="/medias/cross-sell-fl-e25-look-essentiels-MIXTE-parka-alliance.jpg?context…" alt="Style Urbain">
19.1 KiB
6.9 KiB
Graphique et coloré
<img width="260" height="260" loading="lazy" src="/medias/cross-sell-fl-e25-look-essentiels-LF-robe-gabrielle2.jpg?context=b…" alt="Graphique et coloré">
12.5 KiB
4.5 KiB
Image elements do not 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
URL
AB Tasty
analytics
div.jac-col-12 > header.jac-title-center > div > img
<img src="https://assets-manager.abtasty.com/de369e82f81db8ce0e285db1fdf1118e/visa.s…" width="35">
/de369e8…/visa.svg
(assets-manager.abtasty.com)
div.jac-col-12 > header.jac-title-center > div > img
<img src="https://assets-manager.abtasty.com/de369e82f81db8ce0e285db1fdf1118e/master…" width="35">
/de369e8…/mastercard.svg
(assets-manager.abtasty.com)
div.jac-col-12 > header.jac-title-center > div > img
<img src="https://assets-manager.abtasty.com/de369e82f81db8ce0e285db1fdf1118e/maestr…" width="35">
/de369e8…/maestro.svg
(assets-manager.abtasty.com)
div.jac-col-12 > header.jac-title-center > div > img
<img src="https://assets-manager.abtasty.com/de369e82f81db8ce0e285db1fdf1118e/amex.s…" width="35">
/de369e8…/amex.svg
(assets-manager.abtasty.com)
div.jac-col-12 > header.jac-title-center > div > img
<img src="https://assets-manager.abtasty.com/de369e82f81db8ce0e285db1fdf1118e/klarna…" width="35">
/de369e8…/klarna.svg
(assets-manager.abtasty.com)
div.jac-col-12 > header.jac-title-center > div > img
<img src="https://assets-manager.abtasty.com/de369e82f81db8ce0e285db1fdf1118e/paypal…" width="35">
/de369e8…/paypal.svg
(assets-manager.abtasty.com)
div.jac-col-12 > header.jac-title-center > div > img
<img src="https://assets-manager.abtasty.com/de369e82f81db8ce0e285db1fdf1118e/applep…" width="35">
/de369e8…/applepay.svg
(assets-manager.abtasty.com)
Serve images in next-gen formats Potential savings of 61 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
URL
Resource Size
Potential Savings
jacadi.fr
1st party
82.0 KiB
39.2 KiB
Nouvelle collection Sport Chic
<img width="1147" height="714" loading="lazy" src="https://www.jacadi.fr/medias/Mineur-atelier-design-be-be-mobile-750x860-.j…" alt="Nouvelle collection Sport Chic">
82.0 KiB
39.2 KiB
Dailymotion
content
44.2 KiB
21.6 KiB
24.1 KiB
11.4 KiB
20.1 KiB
10.3 KiB
Serve static assets with an efficient cache policy 16 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
Amazon Web Services
other
382 KiB
…prod/velou.min.js
(velou-cloudfront.s3.amazonaws.com)
None
382 KiB
JSDelivr CDN
cdn
288 KiB
…umd/identity-ui.min.js
(cdn.jsdelivr.net)
7d
288 KiB
get-potions.com
54 KiB
/jacadi-fr/potions.js
(client.get-potions.com)
1h
35 KiB
/80/recos-tag.js
(client.get-potions.com)
1h
19 KiB
mPulse
analytics
47 KiB
7d
47 KiB
XiTi
analytics
26 KiB
/piano-analytics.js
(tag.aticdn.net)
4h
26 KiB
AB Tasty
analytics
14 KiB
/de369e8…/paypal.svg
(assets-manager.abtasty.com)
None
3 KiB
/de369e8…/applepay.svg
(assets-manager.abtasty.com)
None
2 KiB
/de369e8…/maestro.svg
(assets-manager.abtasty.com)
None
1 KiB
/de369e8…/klarna.svg
(assets-manager.abtasty.com)
None
1 KiB
/de369e8…/visa.svg
(assets-manager.abtasty.com)
None
1 KiB
/de369e8…/amex.svg
(assets-manager.abtasty.com)
None
1 KiB
/de369e8…/mastercard.svg
(assets-manager.abtasty.com)
None
1 KiB
/de369e8….js
(try.abtasty.com)
30s
3 KiB
SpeedCurve RUM
analytics
11 KiB
/js/lux.js?id=445…
(cdn.speedcurve.com)
7d
11 KiB
axept.io
1 KiB
/sdk.js
(static.axept.io)
None
1 KiB
Defer offscreen images Potential savings of 3 KiB
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
URL
Resource Size
Potential Savings
AB Tasty
analytics
3.4 KiB
3.4 KiB
div.jac-col-12 > header.jac-title-center > div > img
<img src="https://assets-manager.abtasty.com/de369e82f81db8ce0e285db1fdf1118e/paypal…" width="35">
/de369e8…/paypal.svg
(assets-manager.abtasty.com)
3.4 KiB
3.4 KiB
Avoid serving legacy JavaScript to modern browsers Potential savings of 20 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 serve modern JavaScriptLCPFCP
URL
Potential Savings
JSDelivr CDN
cdn
20.1 KiB
…umd/identity-ui.min.js
(cdn.jsdelivr.net)
20.1 KiB
../node_modules/@reachfive/identity-core/es/main.js:2336:8
Array.prototype.fill
../node_modules/@reachfive/identity-core/es/main.js:2351:8
Array.prototype.filter
../node_modules/@reachfive/identity-core/es/main.js:2369:8
Array.prototype.find
../node_modules/@reachfive/identity-core/es/main.js:2390:8
Array.prototype.findIndex
../node_modules/@reachfive/identity-core/es/main.js:2526:8
Array.prototype.forEach
../node_modules/@reachfive/identity-core/es/main.js:2620:8
Array.from
../node_modules/@reachfive/identity-core/es/main.js:2670:8
Array.isArray
../node_modules/@reachfive/identity-core/es/main.js:2934:8
Array.prototype.map
../node_modules/@reachfive/identity-core/es/main.js:2951:8
Array.of
../node_modules/@reachfive/identity-core/es/main.js:3157:8
Array.prototype.some
../node_modules/@reachfive/identity-core/es/main.js:4223:8
Date.now
../node_modules/@reachfive/identity-core/es/main.js:4342:8
Date.prototype.toISOString
../node_modules/@reachfive/identity-core/es/main.js:4353:8
Date.prototype.toJSON
../node_modules/@reachfive/identity-core/es/main.js:5413:8
Number.isInteger
../node_modules/@reachfive/identity-core/es/main.js:5430:8
Number.isSafeInteger
../node_modules/@reachfive/identity-core/es/main.js:5830:8
Object.defineProperties
../node_modules/@reachfive/identity-core/es/main.js:5839:8
Object.defineProperty
../node_modules/@reachfive/identity-core/es/main.js:5900:8
Object.entries
../node_modules/@reachfive/identity-core/es/main.js:5914:8
Object.freeze
../node_modules/@reachfive/identity-core/es/main.js:5947:8
Object.getOwnPropertyDescriptors
../node_modules/@reachfive/identity-core/es/main.js:5978:8
Object.getPrototypeOf
../node_modules/@reachfive/identity-core/es/main.js:6022:8
Object.isExtensible
../node_modules/@reachfive/identity-core/es/main.js:6040:8
Object.isFrozen
../node_modules/@reachfive/identity-core/es/main.js:6055:8
Object.isSealed
../node_modules/@reachfive/identity-core/es/main.js:6067:8
Object.keys
../node_modules/@reachfive/identity-core/es/main.js:6117:8
Object.preventExtensions
../node_modules/@reachfive/identity-core/es/main.js:6157:8
Object.seal
../node_modules/@reachfive/identity-core/es/main.js:6165:8
Object.setPrototypeOf
../node_modules/@reachfive/identity-core/es/main.js:6185:8
Object.values
../node_modules/@reachfive/identity-core/es/main.js:7031:8
Reflect.apply
../node_modules/@reachfive/identity-core/es/main.js:7056:8
Reflect.construct
../node_modules/@reachfive/identity-core/es/main.js:7092:8
Reflect.defineProperty
../node_modules/@reachfive/identity-core/es/main.js:7110:8
Reflect.deleteProperty
../node_modules/@reachfive/identity-core/es/main.js:7134:8
Reflect.get
../node_modules/@reachfive/identity-core/es/main.js:7140:8
Reflect.getOwnPropertyDescriptor
../node_modules/@reachfive/identity-core/es/main.js:7148:8
Reflect.getPrototypeOf
../node_modules/@reachfive/identity-core/es/main.js:7156:8
Reflect.has
../node_modules/@reachfive/identity-core/es/main.js:7164:8
Reflect.isExtensible
../node_modules/@reachfive/identity-core/es/main.js:7173:8
Reflect.ownKeys
../node_modules/@reachfive/identity-core/es/main.js:7179:8
Reflect.preventExtensions
../node_modules/@reachfive/identity-core/es/main.js:7233:34
Reflect.setPrototypeOf
../node_modules/@reachfive/identity-core/es/main.js:7857:8
String.prototype.codePointAt
../node_modules/@reachfive/identity-core/es/main.js:8279:8
String.raw
../node_modules/@reachfive/identity-core/es/main.js:8297:8
String.prototype.repeat
../node_modules/libphonenumber-js/es6/ParseError.js:7:112
@babel/plugin-transform-classes
Amazon Web Services
other
0.2 KiB
…prod/velou.min.js
(velou-cloudfront.s3.amazonaws.com)
0.2 KiB
…prod/velou.min.js:399:9075
(velou-cloudfront.s3.amazonaws.com)
@babel/plugin-transform-classes
jacadi.fr
1st party
0.1 KiB
0.1 KiB
@babel/plugin-transform-classes
0.0 KiB
@babel/plugin-transform-classes
Avoid enormous network payloads Total size was 2,949 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
Amazon Web Services
other
382.4 KiB
…prod/velou.min.js
(velou-cloudfront.s3.amazonaws.com)
382.4 KiB
JSDelivr CDN
cdn
288.3 KiB
…umd/identity-ui.min.js
(cdn.jsdelivr.net)
288.3 KiB
jacadi.fr
1st party
287.8 KiB
133.0 KiB
83.4 KiB
…css/jacadi-R93.css
(www.jacadi.fr)
71.4 KiB
Dailymotion
content
209.6 KiB
71.2 KiB
71.2 KiB
67.2 KiB
Forter
utility
153.1 KiB
…afd1ebd5256b/script.js
(afd1ebd5256b.cdn4.forter.com)
153.1 KiB
Google Tag Manager
tag-manager
97.3 KiB
/gtm.js?id=GTM-THZXBP
(www.googletagmanager.com)
97.3 KiB
Avoid long main-thread tasks 20 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
Amazon Web Services
other
413 ms
…prod/velou.min.js
(velou-cloudfront.s3.amazonaws.com)
11,324 ms
413 ms
Google Tag Manager
tag-manager
363 ms
/gtm.js?id=GTM-THZXBP
(www.googletagmanager.com)
19,187 ms
297 ms
/gtm.js?id=GTM-THZXBP
(www.googletagmanager.com)
14,646 ms
66 ms
jacadi.fr
1st party
362 ms
8,763 ms
96 ms
11,851 ms
83 ms
19,120 ms
67 ms
8,701 ms
62 ms
19,051 ms
54 ms
Unattributable
350 ms
(program):2
1,370 ms
200 ms
Unattributable
1,592 ms
95 ms
Unattributable
1,051 ms
55 ms
JSDelivr CDN
cdn
347 ms
…umd/identity-ui.min.js
(cdn.jsdelivr.net)
11,934 ms
173 ms
…umd/identity-ui.min.js
(cdn.jsdelivr.net)
21,409 ms
97 ms
…umd/identity-ui.min.js
(cdn.jsdelivr.net)
21,332 ms
77 ms
Dailymotion
content
283 ms
12,117 ms
83 ms
12,200 ms
80 ms
14,327 ms
65 ms
13,506 ms
55 ms
AB Tasty
analytics
93 ms
21,191 ms
93 ms
XiTi
analytics
61 ms
/piano-analytics.js
(tag.aticdn.net)
20,685 ms
61 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
Style Urbain Style Urbain - Ajouter à mes favoris Graphique et coloré Graphique…
<div class="jac-viewport">
0.018
Nouvelle collection Sport Chic
<img width="1147" height="714" loading="lazy" src="https://www.jacadi.fr/medias/Mineur-atelier-design-be-be-mobile-750x860-.j…" alt="Nouvelle collection Sport Chic">
Media element lacking an explicit size
Web font loaded
Web font loaded
Web font loaded
Web font loaded
Web font loaded
Web font loaded
User Timing marks and measures 14 user timings
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.
Name
Type
Start Time
Duration
vital_player_enter
Measure
1,454.81 ms
1,722.12 ms
vital_player_enter
Measure
1,454.81 ms
1,748.33 ms
vital_first_ui_displayed
Measure
3,176.93 ms
4.32 ms
vital_first_ui_displayed
Measure
3,203.14 ms
3.72 ms
vital_first_meaningful_content
Measure
3,206.86 ms
451.35 ms
vital_first_meaningful_content
Measure
3,206.86 ms
526.52 ms
vital_origin
Mark
1,452.86 ms
vital_origin
Mark
1,454.81 ms
vital_player_enter
Mark
3,176.93 ms
vital_first_ui_displayed
Mark
3,181.25 ms
vital_player_enter
Mark
3,203.14 ms
vital_first_ui_displayed
Mark
3,206.86 ms
vital_first_meaningful_content
Mark
3,658.21 ms
vital_first_meaningful_content
Mark
3,733.38 ms
Avoid non-composited animations 1 animated element found
Animations which are not composited can be janky and increase CLS. Learn how to avoid non-composited animationsCLS
Element
Name
div.spinner > div.spinner_image > svg.spinner_circle > circle.path
<circle class="path" cx="25" cy="25" r="20" fill="none" stroke="#fff" stroke-width="4" transform="rotate(-90 25 25)">
Unsupported CSS Property: stroke-dashoffset
dash
Avoid chaining critical requests 2 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: 3,919.642 ms
Initial Navigation
/ABCFavorit-Regular.woff2
(static1.dmcdn.net)
- 0.466 ms, 49.33 KiB
- 27.413 ms, 29.19 KiB
More information about the performance of your application. These numbers don't directly affect the Performance score.
Passed audits (14)
Show Hide
Eliminate render-blocking resources
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
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
Efficiently encode images
Optimized images load faster and consume less cellular data. Learn how to efficiently encode images.LCPFCP
Preconnect to required origins
Warnings:
  • A `<link rel=preconnect>` was found for "https://vod3.cf.dmcdn.net" but was not used by the browser. Only use `preconnect` for important origins that the page will certainly request.
  • More than 2 `<link rel=preconnect>` connections were found. These should be used sparingly and only to the most important 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
Remove duplicate modules in JavaScript bundles
Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity. LCPFCP
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
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
Uses 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.
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().
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.
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.
Names and labels
Image elements do not have [alt] attributes
Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the alt attribute.
Failing Elements
div.jac-col-12 > header.jac-title-center > div > img
<img src="https://assets-manager.abtasty.com/de369e82f81db8ce0e285db1fdf1118e/visa.s…" width="35">
div.jac-col-12 > header.jac-title-center > div > img
<img src="https://assets-manager.abtasty.com/de369e82f81db8ce0e285db1fdf1118e/master…" width="35">
div.jac-col-12 > header.jac-title-center > div > img
<img src="https://assets-manager.abtasty.com/de369e82f81db8ce0e285db1fdf1118e/maestr…" width="35">
div.jac-col-12 > header.jac-title-center > div > img
<img src="https://assets-manager.abtasty.com/de369e82f81db8ce0e285db1fdf1118e/amex.s…" width="35">
div.jac-col-12 > header.jac-title-center > div > img
<img src="https://assets-manager.abtasty.com/de369e82f81db8ce0e285db1fdf1118e/klarna…" width="35">
div.jac-col-12 > header.jac-title-center > div > img
<img src="https://assets-manager.abtasty.com/de369e82f81db8ce0e285db1fdf1118e/paypal…" width="35">
div.jac-col-12 > header.jac-title-center > div > img
<img src="https://assets-manager.abtasty.com/de369e82f81db8ce0e285db1fdf1118e/applep…" width="35">
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
Style Urbain
<img width="260" height="260" loading="lazy" src="/medias/cross-sell-fl-e25-look-essentiels-MIXTE-parka-alliance.jpg?context…" alt="Style Urbain">
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.
ARIA
Uses ARIA roles on incompatible 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.
Failing Elements
Le service client À votre écoute
<li class="splide__slide jac-footer-reassurance-list-item is-active is-visible" id="splide04-slide01" role="group" aria-roledescription="diapositive" aria-label="1 sur 4" style="width: calc(66.6667%);">
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.
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 (26)
Show Hide
[aria-*] attributes 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.
[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.
Buttons have an accessible name
When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.
[user-scalable="no"] is not used in the <meta name="viewport"> element and the [maximum-scale] attribute is not 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.
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.
Elements use only permitted 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.
[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.
<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 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.
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.
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.
Touch targets have sufficient size and 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.
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.
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.
Elements with role="dialog" or role="alertdialog" 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.
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.
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.
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.
<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.
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.
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.
General
Uses deprecated APIs 2 warnings found
Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs.
Deprecation / Warning
Source
jacadi.fr
1st party
Synchronous `XMLHttpRequest` on the main thread is deprecated because of its detrimental effects to the end user's experience. For more help, check https://xhr.spec.whatwg.org/.
Unattributable
Unload event listeners are deprecated and will be removed.
Uses third-party cookies 3 cookies found
Chrome is moving towards a new experience that allows users to choose to browse without third-party cookies. Learn more about third-party cookies.
Name
URL
Dailymotion
content
_TEST_
ts
v1st
Browser errors were 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
Source
Description
jacadi.fr
1st party
…browser/infos:1:0
(www.jacadi.fr)
Failed to load resource: the server responded with a status of 403 (Forbidden)
botmind.ai
/public/widget.js:1:0
(widget.botmind.ai)
Failed to load resource: the server responded with a status of 403 (Forbidden)
Issues were logged 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.
Issue type
Cookie
Detected JavaScript libraries
All front-end JavaScript libraries detected on the page. Learn more about this JavaScript library detection diagnostic audit.
Name
Version
jQuery
3.5.1
jQuery UI
1.12.1
Modernizr
2.8.3
Underscore
1.7.0
boomerang.js
1.571.0
core-js
core-js-global@3.35.0
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
Use a strong HSTS policy
Deployment of the HSTS header significantly reduces the risk of downgrading HTTP connections and eavesdropping attacks. A rollout in stages, starting with a low max-age is recommended. Learn more about using a strong HSTS policy.
Description
Directive
Severity
`max-age` is too low
max-age
High
Ensure proper origin isolation with COOP
The Cross-Origin-Opener-Policy (COOP) can be used to isolate the top-level window from other documents such as pop-ups. Learn more about deploying the COOP header.
Description
Directive
Severity
No COOP header found
High
Passed audits (11)
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.
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.
Page has valid source maps
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
jacadi.fr
1st party
SyntaxError: Unexpected token '<', "<!DOCTYPE "... is not valid JSON
Forter
utility
…afd1ebd5256b/script.js
(afd1ebd5256b.cdn4.forter.com)
Could not resolve map url: https://cdn4.forter.com/map/suid/afd1ebd5256b/13030253103
SpeedCurve RUM
analytics
/js/lux.js?id=445…
(cdn.speedcurve.com)
/js/lux.min.js.map
(cdn.speedcurve.com)
JSDelivr CDN
cdn
…umd/identity-ui.min.js
(cdn.jsdelivr.net)
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.
Mitigate clickjacking with XFO or CSP
The X-Frame-Options (XFO) header or the frame-ancestors directive in the Content-Security-Policy (CSP) header control where a page can be embedded. These can mitigate clickjacking attacks by blocking some or all sites from embedding the page. Learn more about mitigating clickjacking.
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.
Crawling and Indexing
robots.txt is not valid 1 error found
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.
Line #
Content
Error
34
Sitemap: /sitemap.xml
Invalid sitemap URL
To appear in search results, crawlers need access to your app.
Content Best Practices
Image elements do not have [alt] attributes
Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the alt attribute.
Failing Elements
div.jac-col-12 > header.jac-title-center > div > img
<img src="https://assets-manager.abtasty.com/de369e82f81db8ce0e285db1fdf1118e/visa.s…" width="35">
div.jac-col-12 > header.jac-title-center > div > img
<img src="https://assets-manager.abtasty.com/de369e82f81db8ce0e285db1fdf1118e/master…" width="35">
div.jac-col-12 > header.jac-title-center > div > img
<img src="https://assets-manager.abtasty.com/de369e82f81db8ce0e285db1fdf1118e/maestr…" width="35">
div.jac-col-12 > header.jac-title-center > div > img
<img src="https://assets-manager.abtasty.com/de369e82f81db8ce0e285db1fdf1118e/amex.s…" width="35">
div.jac-col-12 > header.jac-title-center > div > img
<img src="https://assets-manager.abtasty.com/de369e82f81db8ce0e285db1fdf1118e/klarna…" width="35">
div.jac-col-12 > header.jac-title-center > div > img
<img src="https://assets-manager.abtasty.com/de369e82f81db8ce0e285db1fdf1118e/paypal…" width="35">
div.jac-col-12 > header.jac-title-center > div > img
<img src="https://assets-manager.abtasty.com/de369e82f81db8ce0e285db1fdf1118e/applep…" width="35">
Format your HTML in a way that enables crawlers to better understand your app’s content.
Additional items to manually check (1)
Show Hide
Structured data is valid
Run these additional validators on your site to check additional SEO best practices.
Passed audits (8)
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 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
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: Passed
Largest Contentful Paint (LCP)
1.6 s
Page LoadsGood (≤ 2.5 s)88%Needs Improvement (2.5 s - 4 s)7%Poor (> 4 s)5%75th Percentile - 1.6 sCore Web Vital
Interaction to Next Paint (INP)
106 ms
Page LoadsGood (≤ 200 ms)85%Needs Improvement (200 ms - 500 ms)8%Poor (> 500 ms)7%75th Percentile - 106 msCore Web Vital
Cumulative Layout Shift (CLS)
0.02
Page LoadsGood (≤ 0.1)95%Needs Improvement (0.1 - 0.25)2%Poor (> 0.25)3%75th Percentile - 0.02Core Web Vital
Other Notable Metrics
First Contentful Paint (FCP)
0.9 s
Page LoadsGood (≤ 1.8 s)94%Needs Improvement (1.8 s - 3 s)4%Poor (> 3 s)2%75th Percentile - 0.9 s 
Time to First Byte (TTFB)
0.7 s
Page LoadsGood (≤ 0.8 s)78%Needs Improvement (0.8 s - 1.8 s)16%Poor (> 1.8 s)5%75th Percentile - 0.7 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)
1.3 s
Page LoadsGood (≤ 2.5 s)91%Needs Improvement (2.5 s - 4 s)5%Poor (> 4 s)3%75th Percentile - 1.3 sCore Web Vital
Interaction to Next Paint (INP)
72 ms
Page LoadsGood (≤ 200 ms)93%Needs Improvement (200 ms - 500 ms)4%Poor (> 500 ms)3%75th Percentile - 72 msCore Web Vital
Cumulative Layout Shift (CLS)
0.04
Page LoadsGood (≤ 0.1)85%Needs Improvement (0.1 - 0.25)9%Poor (> 0.25)6%75th Percentile - 0.04Core Web Vital
Other Notable Metrics
First Contentful Paint (FCP)
1 s
Page LoadsGood (≤ 1.8 s)90%Needs Improvement (1.8 s - 3 s)7%Poor (> 3 s)4%75th Percentile - 1 s 
Time to First Byte (TTFB)
0.8 s
Page LoadsGood (≤ 0.8 s)77%Needs Improvement (0.8 s - 1.8 s)16%Poor (> 1.8 s)7%75th Percentile - 0.8 sExperimental
Latest 28-day collection period
Various desktop devicesMany samples (Chrome UX Report)Full visit durationsVarious network connectionsAll Chrome versions
Diagnose performance issues
50 FCP+10LCP+10TBT+3CLS+24SI+4 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
0.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.7 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
830 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.078
Cumulative Layout Shift measures the movement of visible elements within the viewport. Learn more about the Cumulative Layout Shift metric.
Speed Index
2.7 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more about the Speed Index metric.
  • Captured at Mar 4, 2025, 8:00 AM UTC
  • Emulated Desktop with Lighthouse 12.4.0
    Unthrottled CPU/Memory Power: 579 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.126 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
Minimize main-thread work 3.9 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
2,518 ms
Style & Layout
494 ms
Other
481 ms
Garbage Collection
151 ms
Script Parsing & Compilation
106 ms
Rendering
81 ms
Parse HTML & CSS
77 ms
Reduce JavaScript execution time 2.2 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
jacadi.fr
1st party
1,984 ms
1,233 ms
14 ms
1,243 ms
1,007 ms
3 ms
367 ms
95 ms
1 ms
160 ms
3 ms
0 ms
84 ms
51 ms
2 ms
77 ms
32 ms
0 ms
53 ms
44 ms
8 ms
Unattributable
606 ms
256 ms
0 ms
(program):2
340 ms
209 ms
0 ms
Unattributable
267 ms
47 ms
0 ms
Dailymotion
content
377 ms
269 ms
14 ms
158 ms
148 ms
4 ms
82 ms
71 ms
6 ms
72 ms
1 ms
2 ms
66 ms
48 ms
2 ms
Google Tag Manager
tag-manager
206 ms
155 ms
9 ms
/gtm.js?id=GTM-THZXBP
(www.googletagmanager.com)
206 ms
155 ms
9 ms
JSDelivr CDN
cdn
137 ms
122 ms
14 ms
…umd/identity-ui.min.js
(cdn.jsdelivr.net)
137 ms
122 ms
14 ms
Amazon Web Services
other
99 ms
79 ms
6 ms
…prod/velou.min.js
(velou-cloudfront.s3.amazonaws.com)
99 ms
79 ms
6 ms
AB Tasty
analytics
68 ms
62 ms
4 ms
68 ms
62 ms
4 ms
Largest Contentful Paint element 2,680 ms
This is the largest contentful element painted within the viewport. Learn more about the Largest Contentful Paint elementLCP
Element
Style Urbain
<img width="260" height="260" loading="lazy" src="/medias/cross-sell-fl-e25-look-essentiels-MIXTE-parka-alliance.jpg?context…" alt="Style Urbain">
Phase
% of LCP
Timing
TTFB
6%
160 ms
Load Delay
9%
240 ms
Load Time
2%
50 ms
Render Delay
83%
2,230 ms
Largest Contentful Paint image was 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
Style Urbain
<img width="260" height="260" loading="lazy" src="/medias/cross-sell-fl-e25-look-essentiels-MIXTE-parka-alliance.jpg?context…" alt="Style Urbain">
Enable text compression Potential savings of 272 KiB
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. Learn more about text compression.LCPFCP
URL
Transfer Size
Potential Savings
Amazon Web Services
other
382.0 KiB
267.2 KiB
…prod/velou.min.js
(velou-cloudfront.s3.amazonaws.com)
382.0 KiB
267.2 KiB
get-potions.com
6.2 KiB
5.0 KiB
…80/recos
(client.experiences.get-potions.com)
6.2 KiB
5.0 KiB
Reduce unused JavaScript Potential savings of 748 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
Dailymotion
content
327.5 KiB
233.2 KiB
70.6 KiB
47.1 KiB
70.6 KiB
47.1 KiB
61.5 KiB
45.5 KiB
61.5 KiB
45.5 KiB
31.6 KiB
24.0 KiB
31.6 KiB
24.0 KiB
JSDelivr CDN
cdn
281.0 KiB
135.3 KiB
…umd/identity-ui.min.js
(cdn.jsdelivr.net)
281.0 KiB
135.3 KiB
…node_modules/@reachfive/identity-core/es/main.js
76.1 KiB
49.1 KiB
…node_modules/react-dom/cjs/react-dom.production.min.js
35.3 KiB
15.3 KiB
…node_modules/marked/lib/marked.esm.js
10.6 KiB
7.1 KiB
…node_modules/react-phone-number-input/modules/PhoneInputWithCountry.js
3.0 KiB
2.1 KiB
…src/icons/webauthn/keepassxc.svg
1.9 KiB
1.9 KiB
Amazon Web Services
other
382.0 KiB
131.0 KiB
…prod/velou.min.js
(velou-cloudfront.s3.amazonaws.com)
382.0 KiB
131.0 KiB
jacadi.fr
1st party
186.9 KiB
119.2 KiB
131.2 KiB
69.4 KiB
55.8 KiB
49.8 KiB
Forter
utility
152.3 KiB
43.4 KiB
…afd1ebd5256b/script.js
(afd1ebd5256b.cdn4.forter.com)
152.3 KiB
43.4 KiB
Google Tag Manager
tag-manager
96.5 KiB
33.8 KiB
/gtm.js?id=GTM-THZXBP
(www.googletagmanager.com)
96.5 KiB
33.8 KiB
mPulse
analytics
46.7 KiB
29.2 KiB
46.7 KiB
29.2 KiB
get-potions.com
34.6 KiB
23.3 KiB
/jacadi-fr/potions.js
(client.get-potions.com)
34.6 KiB
23.3 KiB
Avoid an excessive DOM size 1,595 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
1,595
Maximum DOM Depth
ul.jac-nav-panel-list > li.jac-nav-panel-list-item > a.jac-nav-panel-list-item-link > span.jac-nav-panel-list-item-link-label
<span class="jac-nav-panel-list-item-link-label">
18
Maximum Child Elements
body.page-homepage
<body class="page-homepage pageType-ContentPage template-pages-layout-homepageLayout pa…" data-frz-flags="{&quot;lazyload&quot;:false,&quot;unlazyload&quot;:false,&quot;deferjs&quot;:false,&quot;cssontop&quot;:true,&quot;mini…" data-frz-version="2" data-frz-target-key="homepage" data-frz-target-label="Homepage">
100
Image elements do not 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
URL
AB Tasty
analytics
header.jac-title-center > h2.jac-title > div > img
<img src="https://assets-manager.abtasty.com/de369e82f81db8ce0e285db1fdf1118e/visa.s…" width="40">
/de369e8…/visa.svg
(assets-manager.abtasty.com)
header.jac-title-center > h2.jac-title > div > img
<img src="https://assets-manager.abtasty.com/de369e82f81db8ce0e285db1fdf1118e/master…" width="40">
/de369e8…/mastercard.svg
(assets-manager.abtasty.com)
header.jac-title-center > h2.jac-title > div > img
<img src="https://assets-manager.abtasty.com/de369e82f81db8ce0e285db1fdf1118e/maestr…" width="40">
/de369e8…/maestro.svg
(assets-manager.abtasty.com)
header.jac-title-center > h2.jac-title > div > img
<img src="https://assets-manager.abtasty.com/de369e82f81db8ce0e285db1fdf1118e/amex.s…" width="40">
/de369e8…/amex.svg
(assets-manager.abtasty.com)
header.jac-title-center > h2.jac-title > div > img
<img src="https://assets-manager.abtasty.com/de369e82f81db8ce0e285db1fdf1118e/klarna…" width="40">
/de369e8…/klarna.svg
(assets-manager.abtasty.com)
header.jac-title-center > h2.jac-title > div > img
<img src="https://assets-manager.abtasty.com/de369e82f81db8ce0e285db1fdf1118e/paypal…" width="40">
/de369e8…/paypal.svg
(assets-manager.abtasty.com)
header.jac-title-center > h2.jac-title > div > img
<img src="https://assets-manager.abtasty.com/de369e82f81db8ce0e285db1fdf1118e/applep…" width="40">
/de369e8…/applepay.svg
(assets-manager.abtasty.com)
Serve images in next-gen formats Potential savings of 58 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
URL
Resource Size
Potential Savings
jacadi.fr
1st party
176.6 KiB
48.1 KiB
Sélection de boutiques participantes à la vente de seconde main Jacadi du 5 au …
<img width="1147" height="714" loading="lazy" src="/medias/e25-jsv-op-boutique-Mineur-rhesseme-desktop-2294x1430.jpg?context=…" alt="Sélection de boutiques participantes à la vente de seconde main Jacadi du …">
98.5 KiB
28.2 KiB
Les bottes de pluie
<img width="1440" height="714" loading="lazy" src="/medias/mineure-emblematique-e25-bottes-pluie-desktop.jpg?context=bWFzdGVy…" alt="Les bottes de pluie">
78.2 KiB
20.0 KiB
Dailymotion
content
20.1 KiB
10.3 KiB
20.1 KiB
10.3 KiB
Serve static assets with an efficient cache policy 16 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
Amazon Web Services
other
382 KiB
…prod/velou.min.js
(velou-cloudfront.s3.amazonaws.com)
None
382 KiB
JSDelivr CDN
cdn
288 KiB
…umd/identity-ui.min.js
(cdn.jsdelivr.net)
7d
288 KiB
get-potions.com
54 KiB
/jacadi-fr/potions.js
(client.get-potions.com)
1h
35 KiB
/80/recos-tag.js
(client.get-potions.com)
1h
19 KiB
mPulse
analytics
47 KiB
7d
47 KiB
XiTi
analytics
26 KiB
/piano-analytics.js
(tag.aticdn.net)
4h
26 KiB
AB Tasty
analytics
14 KiB
/de369e8…/paypal.svg
(assets-manager.abtasty.com)
None
3 KiB
/de369e8…/applepay.svg
(assets-manager.abtasty.com)
None
2 KiB
/de369e8…/maestro.svg
(assets-manager.abtasty.com)
None
1 KiB
/de369e8…/klarna.svg
(assets-manager.abtasty.com)
None
1 KiB
/de369e8…/visa.svg
(assets-manager.abtasty.com)
None
1 KiB
/de369e8…/amex.svg
(assets-manager.abtasty.com)
None
1 KiB
/de369e8…/mastercard.svg
(assets-manager.abtasty.com)
None
1 KiB
/de369e8….js
(try.abtasty.com)
30s
3 KiB
SpeedCurve RUM
analytics
11 KiB
/js/lux.js?id=445…
(cdn.speedcurve.com)
7d
11 KiB
axept.io
1 KiB
/sdk.js
(static.axept.io)
None
1 KiB
Properly size images Potential savings of 278 KiB
Serve images that are appropriately-sized to save cellular data and improve load time. Learn how to size images.LCPFCP
URL
Resource Size
Potential Savings
jacadi.fr
1st party
377.3 KiB
278.5 KiB
Nouvelle collection Sport Chic
<img width="1147" height="714" loading="lazy" src="/medias/Mineur-atelier-design-be-be-desktop-2294x1430.jpg?context=bWFzdGVy…" alt="Nouvelle collection Sport Chic">
112.2 KiB
87.7 KiB
Sélection de boutiques participantes à la vente de seconde main Jacadi du 5 au …
<img width="1147" height="714" loading="lazy" src="/medias/e25-jsv-op-boutique-Mineur-rhesseme-desktop-2294x1430.jpg?context=…" alt="Sélection de boutiques participantes à la vente de seconde main Jacadi du …">
98.5 KiB
77.0 KiB
Les bottes de pluie
<img width="1440" height="714" loading="lazy" src="/medias/mineure-emblematique-e25-bottes-pluie-desktop.jpg?context=bWFzdGVy…" alt="Les bottes de pluie">
78.2 KiB
61.4 KiB
Preppy chic
<img width="260" height="260" loading="lazy" src="/medias/cross-sell-fl-e25-look-essentiels-MIXTE-pull-conquete.jpg?context=…" alt="Preppy chic ">
19.2 KiB
11.4 KiB
Style Urbain
<img width="260" height="260" loading="lazy" src="/medias/cross-sell-fl-e25-look-essentiels-MIXTE-parka-alliance.jpg?context…" alt="Style Urbain">
19.1 KiB
11.3 KiB
Graphique et coloré
<img width="260" height="260" loading="lazy" src="/medias/cross-sell-fl-e25-look-essentiels-LF-robe-gabrielle2.jpg?context=b…" alt="Graphique et coloré">
12.5 KiB
7.4 KiB
Esprit contemporain
<img width="260" height="260" loading="lazy" src="/medias/cross-sell-fl-e25-look-atelier-design-EG-veste-clairiere.jpg?conte…" alt="Esprit contemporain">
11.0 KiB
6.5 KiB
Petit citadin
<img width="260" height="260" loading="lazy" src="/medias/cross-sell-fl-e25-look-atelier-design-LG-chemise-lanobis.jpg?conte…" alt="Petit citadin">
9.6 KiB
5.7 KiB
Esprit worker
<img width="260" height="260" loading="lazy" src="/medias/cross-sell-fl-e25-look-atelier-design-LG-sweat-cadence.jpg?context…" alt="Esprit worker">
9.0 KiB
5.3 KiB
Tennis chic
<img width="260" height="260" loading="lazy" src="/medias/cross-sell-fl-e25-look-essentiels-EF-robe-emilie.jpg?context=bWFzd…" alt="Tennis chic">
8.1 KiB
4.8 KiB
Defer offscreen images Potential savings of 3 KiB
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
URL
Resource Size
Potential Savings
AB Tasty
analytics
3.4 KiB
3.4 KiB
header.jac-title-center > h2.jac-title > div > img
<img src="https://assets-manager.abtasty.com/de369e82f81db8ce0e285db1fdf1118e/paypal…" width="40">
/de369e8…/paypal.svg
(assets-manager.abtasty.com)
3.4 KiB
3.4 KiB
Avoid serving legacy JavaScript to modern browsers Potential savings of 20 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 serve modern JavaScriptLCPFCP
URL
Potential Savings
JSDelivr CDN
cdn
20.1 KiB
…umd/identity-ui.min.js
(cdn.jsdelivr.net)
20.1 KiB
../node_modules/@reachfive/identity-core/es/main.js:2336:8
Array.prototype.fill
../node_modules/@reachfive/identity-core/es/main.js:2351:8
Array.prototype.filter
../node_modules/@reachfive/identity-core/es/main.js:2369:8
Array.prototype.find
../node_modules/@reachfive/identity-core/es/main.js:2390:8
Array.prototype.findIndex
../node_modules/@reachfive/identity-core/es/main.js:2526:8
Array.prototype.forEach
../node_modules/@reachfive/identity-core/es/main.js:2620:8
Array.from
../node_modules/@reachfive/identity-core/es/main.js:2670:8
Array.isArray
../node_modules/@reachfive/identity-core/es/main.js:2934:8
Array.prototype.map
../node_modules/@reachfive/identity-core/es/main.js:2951:8
Array.of
../node_modules/@reachfive/identity-core/es/main.js:3157:8
Array.prototype.some
../node_modules/@reachfive/identity-core/es/main.js:4223:8
Date.now
../node_modules/@reachfive/identity-core/es/main.js:4342:8
Date.prototype.toISOString
../node_modules/@reachfive/identity-core/es/main.js:4353:8
Date.prototype.toJSON
../node_modules/@reachfive/identity-core/es/main.js:5413:8
Number.isInteger
../node_modules/@reachfive/identity-core/es/main.js:5430:8
Number.isSafeInteger
../node_modules/@reachfive/identity-core/es/main.js:5830:8
Object.defineProperties
../node_modules/@reachfive/identity-core/es/main.js:5839:8
Object.defineProperty
../node_modules/@reachfive/identity-core/es/main.js:5900:8
Object.entries
../node_modules/@reachfive/identity-core/es/main.js:5914:8
Object.freeze
../node_modules/@reachfive/identity-core/es/main.js:5947:8
Object.getOwnPropertyDescriptors
../node_modules/@reachfive/identity-core/es/main.js:5978:8
Object.getPrototypeOf
../node_modules/@reachfive/identity-core/es/main.js:6022:8
Object.isExtensible
../node_modules/@reachfive/identity-core/es/main.js:6040:8
Object.isFrozen
../node_modules/@reachfive/identity-core/es/main.js:6055:8
Object.isSealed
../node_modules/@reachfive/identity-core/es/main.js:6067:8
Object.keys
../node_modules/@reachfive/identity-core/es/main.js:6117:8
Object.preventExtensions
../node_modules/@reachfive/identity-core/es/main.js:6157:8
Object.seal
../node_modules/@reachfive/identity-core/es/main.js:6165:8
Object.setPrototypeOf
../node_modules/@reachfive/identity-core/es/main.js:6185:8
Object.values
../node_modules/@reachfive/identity-core/es/main.js:7031:8
Reflect.apply
../node_modules/@reachfive/identity-core/es/main.js:7056:8
Reflect.construct
../node_modules/@reachfive/identity-core/es/main.js:7092:8
Reflect.defineProperty
../node_modules/@reachfive/identity-core/es/main.js:7110:8
Reflect.deleteProperty
../node_modules/@reachfive/identity-core/es/main.js:7134:8
Reflect.get
../node_modules/@reachfive/identity-core/es/main.js:7140:8
Reflect.getOwnPropertyDescriptor
../node_modules/@reachfive/identity-core/es/main.js:7148:8
Reflect.getPrototypeOf
../node_modules/@reachfive/identity-core/es/main.js:7156:8
Reflect.has
../node_modules/@reachfive/identity-core/es/main.js:7164:8
Reflect.isExtensible
../node_modules/@reachfive/identity-core/es/main.js:7173:8
Reflect.ownKeys
../node_modules/@reachfive/identity-core/es/main.js:7179:8
Reflect.preventExtensions
../node_modules/@reachfive/identity-core/es/main.js:7233:34
Reflect.setPrototypeOf
../node_modules/@reachfive/identity-core/es/main.js:7857:8
String.prototype.codePointAt
../node_modules/@reachfive/identity-core/es/main.js:8279:8
String.raw
../node_modules/@reachfive/identity-core/es/main.js:8297:8
String.prototype.repeat
../node_modules/libphonenumber-js/es6/ParseError.js:7:112
@babel/plugin-transform-classes
Amazon Web Services
other
0.2 KiB
…prod/velou.min.js
(velou-cloudfront.s3.amazonaws.com)
0.2 KiB
…prod/velou.min.js:399:9075
(velou-cloudfront.s3.amazonaws.com)
@babel/plugin-transform-classes
jacadi.fr
1st party
0.1 KiB
0.1 KiB
@babel/plugin-transform-classes
0.0 KiB
@babel/plugin-transform-classes
Reduce unused CSS Potential savings of 89 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
jacadi.fr
1st party
69.5 KiB
66.8 KiB
…css/jacadi-R93.css
(www.jacadi.fr)
69.5 KiB
66.8 KiB
Unattributable
22.0 KiB
22.0 KiB
@charset "utf-8";.vl-root{max-width:100%;position:relative;overflow:hidden} …
22.0 KiB
22.0 KiB
Avoid enormous network payloads Total size was 3,093 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
jacadi.fr
1st party
497.6 KiB
133.0 KiB
113.9 KiB
99.8 KiB
79.5 KiB
…css/jacadi-R93.css
(www.jacadi.fr)
71.4 KiB
Amazon Web Services
other
382.4 KiB
…prod/velou.min.js
(velou-cloudfront.s3.amazonaws.com)
382.4 KiB
JSDelivr CDN
cdn
288.3 KiB
…umd/identity-ui.min.js
(cdn.jsdelivr.net)
288.3 KiB
Forter
utility
153.1 KiB
…afd1ebd5256b/script.js
(afd1ebd5256b.cdn4.forter.com)
153.1 KiB
Google Tag Manager
tag-manager
97.6 KiB
/gtm.js?id=GTM-THZXBP
(www.googletagmanager.com)
97.6 KiB
Dailymotion
content
71.2 KiB
71.2 KiB
Avoid long main-thread tasks 4 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
Amazon Web Services
other
768 ms
…prod/velou.min.js
(velou-cloudfront.s3.amazonaws.com)
2,255 ms
768 ms
Unattributable
123 ms
(program):2
489 ms
123 ms
Google Tag Manager
tag-manager
105 ms
/gtm.js?id=GTM-THZXBP
(www.googletagmanager.com)
4,041 ms
105 ms
jacadi.fr
1st party
77 ms
3,937 ms
77 ms
Avoid large layout shifts 3 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
Style Urbain Style Urbain - Ajouter à mes favoris Graphique et coloré Graphique…
<div id="jac-home-main">
0.078
Nouvelle collection Sport Chic
<img width="1147" height="714" loading="lazy" src="/medias/Mineur-atelier-design-be-be-desktop-2294x1430.jpg?context=bWFzdGVy…" alt="Nouvelle collection Sport Chic">
Media element lacking an explicit size
Web font loaded
Web font loaded
Web font loaded
Web font loaded
Web font loaded
Web font loaded
Web font loaded
LA MARQUE LES SERVICES Page d'accueil Jacadi Rechercher Mon compte (non connect…
<section class="jac-header j-container jac-logged-out">
0.001
Nouvelle collection Sport Chic
<img width="1147" height="714" loading="lazy" src="/medias/Mineur-atelier-design-be-be-desktop-2294x1430.jpg?context=bWFzdGVy…" alt="Nouvelle collection Sport Chic">
Media element lacking an explicit size
Browser not compatible
<h1 class="error_title">
0.000
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
98 KiB
55 ms
/gtm.js?id=GTM-THZXBP
(www.googletagmanager.com)
98 KiB
55 ms
JSDelivr CDN
cdn
288 KiB
38 ms
…umd/identity-ui.min.js
(cdn.jsdelivr.net)
288 KiB
38 ms
Amazon Web Services
other
382 KiB
36 ms
…prod/velou.min.js
(velou-cloudfront.s3.amazonaws.com)
382 KiB
36 ms
mPulse
analytics
48 KiB
2 ms
47 KiB
2 ms
/api/config.json?key=…
(c.go-mpulse.net)
1 KiB
0 ms
0 KiB
0 ms
SpeedCurve RUM
analytics
11 KiB
0 ms
/js/lux.js?id=445…
(cdn.speedcurve.com)
11 KiB
0 ms
Dailymotion
content
670 KiB
0 ms
142 KiB
0 ms
124 KiB
0 ms
/ABCFavorit-Regular.woff2
(static1.dmcdn.net)
99 KiB
0 ms
75 KiB
0 ms
64 KiB
0 ms
/DailySans-Bulky.woff2
(static1.dmcdn.net)
39 KiB
0 ms
35 KiB
0 ms
29 KiB
0 ms
21 KiB
0 ms
8 KiB
0 ms
8 KiB
0 ms
8 KiB
0 ms
…video/x9e5ewm?embedder=…
(www.dailymotion.com)
6 KiB
0 ms
6 KiB
0 ms
…video/x9e5ewo?embedder=…
(www.dailymotion.com)
6 KiB
0 ms
1 KiB
0 ms
Forter
utility
155 KiB
0 ms
…afd1ebd5256b/script.js
(afd1ebd5256b.cdn4.forter.com)
153 KiB
0 ms
…0f40b00…/wpt.json
(cdn0.euw.forter.com)
1 KiB
0 ms
0 KiB
0 ms
0 KiB
0 ms
0 KiB
0 ms
/prop.json
(0f40b0030e06417c8df583fbdee92a7a-afd1ebd5256b.cdn.euw.forter.com)
0 KiB
0 ms
/events
(cdn3.euw.forter.com)
0 KiB
0 ms
AB Tasty
analytics
97 KiB
0 ms
65 KiB
0 ms
7 KiB
0 ms
/shared/me.0c0baf9….js
(try.abtasty.com)
4 KiB
0 ms
4 KiB
0 ms
/de369e8…/paypal.svg
(assets-manager.abtasty.com)
3 KiB
0 ms
/de369e8….js
(try.abtasty.com)
3 KiB
0 ms
/de369e8…/applepay.svg
(assets-manager.abtasty.com)
2 KiB
0 ms
2 KiB
0 ms
/de369e8…/maestro.svg
(assets-manager.abtasty.com)
1 KiB
0 ms
/de369e8…/klarna.svg
(assets-manager.abtasty.com)
1 KiB
0 ms
/de369e8…/visa.svg
(assets-manager.abtasty.com)
1 KiB
0 ms
/de369e8…/amex.svg
(assets-manager.abtasty.com)
1 KiB
0 ms
/de369e8…/mastercard.svg
(assets-manager.abtasty.com)
1 KiB
0 ms
/v1/geoip?weather=false
(dcinfos-cache.abtasty.com)
1 KiB
0 ms
/v1/ua-parser
(dcinfos-cache.abtasty.com)
1 KiB
0 ms
get-potions.com
64 KiB
0 ms
/jacadi-fr/potions.js
(client.get-potions.com)
35 KiB
0 ms
/80/recos-tag.js
(client.get-potions.com)
19 KiB
0 ms
…80/recos
(client.experiences.get-potions.com)
7 KiB
0 ms
…multiply/rules.json
(client.get-potions.com)
1 KiB
0 ms
…page_enricher/rules.json
(client.get-potions.com)
1 KiB
0 ms
…cart_recorder/rules.json
(client.get-potions.com)
1 KiB
0 ms
XiTi
analytics
26 KiB
0 ms
/piano-analytics.js
(tag.aticdn.net)
26 KiB
0 ms
TagCommander
tag-manager
17 KiB
0 ms
/6846/tc_jacadi_1.js
(cdn.tagcommander.com)
17 KiB
0 ms
dm-event.net
4 KiB
0 ms
4 KiB
0 ms
reach5.co
4 KiB
0 ms
…sdk/fr.json
(assets.reach5.co)
4 KiB
0 ms
botmind.ai
2 KiB
0 ms
/public/widget.js
(widget.botmind.ai)
2 KiB
0 ms
velou.com
1 KiB
0 ms
/tracking
(api-analytics.velou.com)
1 KiB
0 ms
/popular-searches
(api-search-jacadi.velou.com)
1 KiB
0 ms
axept.io
1 KiB
0 ms
/sdk.js
(static.axept.io)
1 KiB
0 ms
cloudfront.net
1 KiB
0 ms
/events
(dz8rit8v72mig.cloudfront.net)
1 KiB
0 ms
pa-cd.com
0 KiB
0 ms
0 KiB
0 ms
User Timing marks and measures 14 user timings
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.
Name
Type
Start Time
Duration
vital_player_enter
Measure
312.35 ms
222.21 ms
vital_player_enter
Measure
312.35 ms
242.88 ms
vital_first_ui_displayed
Measure
534.56 ms
3.61 ms
vital_first_ui_displayed
Measure
555.24 ms
3.26 ms
vital_first_meaningful_content
Measure
558.49 ms
1,712.76 ms
vital_first_meaningful_content
Measure
558.49 ms
1,723.42 ms
vital_origin
Mark
310.13 ms
vital_origin
Mark
312.35 ms
vital_player_enter
Mark
534.56 ms
vital_first_ui_displayed
Mark
538.17 ms
vital_player_enter
Mark
555.24 ms
vital_first_ui_displayed
Mark
558.49 ms
vital_first_meaningful_content
Mark
2,271.25 ms
vital_first_meaningful_content
Mark
2,281.91 ms
Avoid non-composited animations 1 animated element found
Animations which are not composited can be janky and increase CLS. Learn how to avoid non-composited animationsCLS
Element
Name
div.spinner > div.spinner_image > svg.spinner_circle > circle.path
<circle class="path" cx="25" cy="25" r="20" fill="none" stroke="#fff" stroke-width="4" transform="rotate(-90 25 25)">
Unsupported CSS Property: stroke-dashoffset
dash
Avoid chaining critical requests 2 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: 2,607.629 ms
Initial Navigation
/ABCFavorit-Regular.woff2
(static1.dmcdn.net)
- 0.279 ms, 49.33 KiB
- 162.817 ms, 28.86 KiB
More information about the performance of your application. These numbers don't directly affect the Performance score.
Passed audits (15)
Show Hide
Eliminate render-blocking resources
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
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
Efficiently encode images
Optimized images load faster and consume less cellular data. Learn how to efficiently encode images.LCPFCP
Preconnect to required origins
Warnings:
  • A `<link rel=preconnect>` was found for "https://vod3.cf.dmcdn.net" but was not used by the browser. Only use `preconnect` for important origins that the page will certainly request.
  • More than 2 `<link rel=preconnect>` connections were found. These should be used sparingly and only to the most important 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
Initial server response time was short Root document took 40 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
jacadi.fr
1st party
40 ms
40 ms
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
Remove duplicate modules in JavaScript bundles
Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity. LCPFCP
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
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
Uses 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.
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().
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.
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 have valid values
Assistive technologies, like screen readers, can't interpret ARIA attributes with invalid values. Learn more about valid values for ARIA attributes.
Failing Elements
🧡
<span aria-hidden="”true”">
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
Image elements do not have [alt] attributes
Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the alt attribute.
Failing Elements
header.jac-title-center > h2.jac-title > div > img
<img src="https://assets-manager.abtasty.com/de369e82f81db8ce0e285db1fdf1118e/visa.s…" width="40">
header.jac-title-center > h2.jac-title > div > img
<img src="https://assets-manager.abtasty.com/de369e82f81db8ce0e285db1fdf1118e/master…" width="40">
header.jac-title-center > h2.jac-title > div > img
<img src="https://assets-manager.abtasty.com/de369e82f81db8ce0e285db1fdf1118e/maestr…" width="40">
header.jac-title-center > h2.jac-title > div > img
<img src="https://assets-manager.abtasty.com/de369e82f81db8ce0e285db1fdf1118e/amex.s…" width="40">
header.jac-title-center > h2.jac-title > div > img
<img src="https://assets-manager.abtasty.com/de369e82f81db8ce0e285db1fdf1118e/klarna…" width="40">
header.jac-title-center > h2.jac-title > div > img
<img src="https://assets-manager.abtasty.com/de369e82f81db8ce0e285db1fdf1118e/paypal…" width="40">
header.jac-title-center > h2.jac-title > div > img
<img src="https://assets-manager.abtasty.com/de369e82f81db8ce0e285db1fdf1118e/applep…" width="40">
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
Style Urbain
<img width="260" height="260" loading="lazy" src="/medias/cross-sell-fl-e25-look-essentiels-MIXTE-parka-alliance.jpg?context…" alt="Style Urbain">
Graphique et coloré
<img width="260" height="260" loading="lazy" src="/medias/cross-sell-fl-e25-look-essentiels-LF-robe-gabrielle2.jpg?context=b…" alt="Graphique et coloré">
Preppy chic
<img width="260" height="260" loading="lazy" src="/medias/cross-sell-fl-e25-look-essentiels-MIXTE-pull-conquete.jpg?context=…" alt="Preppy chic ">
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.
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 (26)
Show Hide
[aria-*] attributes 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.
[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 are valid and not misspelled
Assistive technologies, like screen readers, can't interpret ARIA attributes with invalid names. Learn more about valid ARIA attributes.
Buttons have an accessible name
When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.
[user-scalable="no"] is not used in the <meta name="viewport"> element and the [maximum-scale] attribute is not 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.
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.
Elements use only permitted 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.
[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.
<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 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.
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.
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.
Touch targets have sufficient size and 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.
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.
Elements with role="dialog" or role="alertdialog" 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.
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.
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.
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.
<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.
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.
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.
General
Uses deprecated APIs 2 warnings found
Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs.
Deprecation / Warning
Source
jacadi.fr
1st party
Synchronous `XMLHttpRequest` on the main thread is deprecated because of its detrimental effects to the end user's experience. For more help, check https://xhr.spec.whatwg.org/.
Unattributable
Unload event listeners are deprecated and will be removed.
Uses third-party cookies 3 cookies found
Chrome is moving towards a new experience that allows users to choose to browse without third-party cookies. Learn more about third-party cookies.
Name
URL
Dailymotion
content
_TEST_
ts
v1st
Browser errors were 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
Source
Description
jacadi.fr
1st party
…browser/infos:1:0
(www.jacadi.fr)
Failed to load resource: the server responded with a status of 403 (Forbidden)
botmind.ai
/public/widget.js:1:0
(widget.botmind.ai)
Failed to load resource: the server responded with a status of 403 (Forbidden)
Issues were logged 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.
Issue type
Cookie
Detected JavaScript libraries
All front-end JavaScript libraries detected on the page. Learn more about this JavaScript library detection diagnostic audit.
Name
Version
jQuery
3.5.1
jQuery UI
1.12.1
Modernizr
2.8.3
Underscore
1.7.0
boomerang.js
1.571.0
core-js
core-js-global@3.35.0
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
Use a strong HSTS policy
Deployment of the HSTS header significantly reduces the risk of downgrading HTTP connections and eavesdropping attacks. A rollout in stages, starting with a low max-age is recommended. Learn more about using a strong HSTS policy.
Description
Directive
Severity
`max-age` is too low
max-age
High
Ensure proper origin isolation with COOP
The Cross-Origin-Opener-Policy (COOP) can be used to isolate the top-level window from other documents such as pop-ups. Learn more about deploying the COOP header.
Description
Directive
Severity
No COOP header found
High
Passed audits (10)
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.
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.
Page has valid source maps
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
jacadi.fr
1st party
SyntaxError: Unexpected token '<', "<!DOCTYPE "... is not valid JSON
Forter
utility
…afd1ebd5256b/script.js
(afd1ebd5256b.cdn4.forter.com)
Could not resolve map url: https://cdn4.forter.com/map/suid/afd1ebd5256b/13030253103
SpeedCurve RUM
analytics
/js/lux.js?id=445…
(cdn.speedcurve.com)
/js/lux.min.js.map
(cdn.speedcurve.com)
JSDelivr CDN
cdn
…umd/identity-ui.min.js
(cdn.jsdelivr.net)
Not applicable (3)
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.
Mitigate clickjacking with XFO or CSP
The X-Frame-Options (XFO) header or the frame-ancestors directive in the Content-Security-Policy (CSP) header control where a page can be embedded. These can mitigate clickjacking attacks by blocking some or all sites from embedding the page. Learn more about mitigating clickjacking.
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.
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.
Crawling and Indexing
robots.txt is not valid 1 error found
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.
Line #
Content
Error
34
Sitemap: /sitemap.xml
Invalid sitemap URL
To appear in search results, crawlers need access to your app.
Content Best Practices
Image elements do not have [alt] attributes
Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the alt attribute.
Failing Elements
header.jac-title-center > h2.jac-title > div > img
<img src="https://assets-manager.abtasty.com/de369e82f81db8ce0e285db1fdf1118e/visa.s…" width="40">
header.jac-title-center > h2.jac-title > div > img
<img src="https://assets-manager.abtasty.com/de369e82f81db8ce0e285db1fdf1118e/master…" width="40">
header.jac-title-center > h2.jac-title > div > img
<img src="https://assets-manager.abtasty.com/de369e82f81db8ce0e285db1fdf1118e/maestr…" width="40">
header.jac-title-center > h2.jac-title > div > img
<img src="https://assets-manager.abtasty.com/de369e82f81db8ce0e285db1fdf1118e/amex.s…" width="40">
header.jac-title-center > h2.jac-title > div > img
<img src="https://assets-manager.abtasty.com/de369e82f81db8ce0e285db1fdf1118e/klarna…" width="40">
header.jac-title-center > h2.jac-title > div > img
<img src="https://assets-manager.abtasty.com/de369e82f81db8ce0e285db1fdf1118e/paypal…" width="40">
header.jac-title-center > h2.jac-title > div > img
<img src="https://assets-manager.abtasty.com/de369e82f81db8ce0e285db1fdf1118e/applep…" width="40">
Format your HTML in a way that enables crawlers to better understand your app’s content.
Additional items to manually check (1)
Show Hide
Structured data is valid
Run these additional validators on your site to check additional SEO best practices.
Passed audits (8)
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 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
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.