PageSpeed Insights logo
PageSpeed Insights
PageSpeed Insights
This site uses cookies from Google to deliver its services and to analyze traffic.
Report from Feb 24, 2025, 6:00:36 PM
Discover what your real users are experiencing
Core Web Vitals Assessment: Passed
Largest Contentful Paint (LCP)
1.8 s
Page LoadsGood (≤ 2.5 s)86%Needs Improvement (2.5 s - 4 s)8%Poor (> 4 s)6%75th Percentile - 1.8 sCore Web Vital
Interaction to Next Paint (INP)
192 ms
Page LoadsGood (≤ 200 ms)77%Needs Improvement (200 ms - 500 ms)19%Poor (> 500 ms)4%75th Percentile - 192 msCore Web Vital
Cumulative Layout Shift (CLS)
0.03
Page LoadsGood (≤ 0.1)97%Needs Improvement (0.1 - 0.25)2%Poor (> 0.25)0%75th Percentile - 0.03Core Web Vital
Other Notable Metrics
First Contentful Paint (FCP)
1.3 s
Page LoadsGood (≤ 1.8 s)85%Needs Improvement (1.8 s - 3 s)9%Poor (> 3 s)7%75th Percentile - 1.3 s 
Time to First Byte (TTFB)
0.8 s
Page LoadsGood (≤ 0.8 s)73%Needs Improvement (0.8 s - 1.8 s)19%Poor (> 1.8 s)7%75th Percentile - 0.8 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.4 s
Page LoadsGood (≤ 2.5 s)88%Needs Improvement (2.5 s - 4 s)6%Poor (> 4 s)5%75th Percentile - 1.4 sCore Web Vital
Interaction to Next Paint (INP)
180 ms
Page LoadsGood (≤ 200 ms)79%Needs Improvement (200 ms - 500 ms)17%Poor (> 500 ms)4%75th Percentile - 180 msCore Web Vital
Cumulative Layout Shift (CLS)
0.04
Page LoadsGood (≤ 0.1)83%Needs Improvement (0.1 - 0.25)6%Poor (> 0.25)11%75th Percentile - 0.04Core Web Vital
Other Notable Metrics
First Contentful Paint (FCP)
1 s
Page LoadsGood (≤ 1.8 s)87%Needs Improvement (1.8 s - 3 s)6%Poor (> 3 s)7%75th Percentile - 1 s 
Time to First Byte (TTFB)
0.6 s
Page LoadsGood (≤ 0.8 s)79%Needs Improvement (0.8 s - 1.8 s)11%Poor (> 1.8 s)10%75th Percentile - 0.6 sExperimental
Latest 28-day collection period
Various mobile devicesMany samples (Chrome UX Report)Full visit durationsVarious network connectionsAll Chrome versions
Diagnose performance issues
57 FCP+7LCP+11TBT+12CLS+25SI+2 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
2.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
4.3 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
730 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.016
Cumulative Layout Shift measures the movement of visible elements within the viewport. Learn more about the Cumulative Layout Shift metric.
Speed Index
8.3 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more about the Speed Index metric.
  • Captured at Feb 24, 2025, 6:00 PM UTC
  • Emulated Moto G Power with Lighthouse 12.2.3
    Unthrottled CPU/Memory Power: 426 CPU throttling: 1.2x slowdown (Simulated) Screen emulation: 412x823, DPR 1.75 Axe version: 4.10.2
  • Single page session
    This data is taken from a single page session, as opposed to field data summarizing many sessions.
  • Initial page load
  • Slow 4G throttling
    Network throttling: 150 ms TCP RTT, 1,638.4 kb/s throughput (Simulated) Browser location: North America
  • Using HeadlessChromium 133.0.6943.53 with lr
    User agent (network): "Mozilla/5.0 (Linux; Android 11; moto g power (2022)) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/119.0.0.0 Mobile Safari/537.36"
Screenshot
Screenshot
Screenshot
Screenshot
Screenshot
Screenshot
Screenshot
Screenshot
Show audits relevant to:
Diagnostics
Minimize main-thread work 4.1 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,428 ms
Style & Layout
606 ms
Other
458 ms
Parse HTML & CSS
175 ms
Garbage Collection
173 ms
Script Parsing & Compilation
164 ms
Rendering
90 ms
Reduce JavaScript execution time 2.3 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to reduce Javascript execution time.TBT
URL
Total CPU Time
Script Evaluation
Script Parse
courir.com
1st party
2,069 ms
1,047 ms
67 ms
632 ms
77 ms
3 ms
544 ms
429 ms
8 ms
532 ms
372 ms
26 ms
…swiper/swiper.js
(www.courir.com)
215 ms
50 ms
5 ms
…js/bundle_checkout.js
(www.courir.com)
94 ms
82 ms
11 ms
…ui/jquery-ui.min.js
(www.courir.com)
53 ms
37 ms
13 ms
Google Tag Manager
tag-manager
896 ms
725 ms
30 ms
/gtm.js?id=GTM-NQTQQRC
(www.googletagmanager.com)
542 ms
507 ms
16 ms
/gtag/js?id=…
(www.googletagmanager.com)
282 ms
154 ms
7 ms
/gtag/destination?id=…
(www.googletagmanager.com)
71 ms
64 ms
7 ms
Unattributable
305 ms
20 ms
0 ms
Unattributable
305 ms
20 ms
0 ms
Optanon
consent-provider
221 ms
152 ms
13 ms
…202408.1.0/otBannerSdk.js
(cdn.cookielaw.org)
159 ms
94 ms
12 ms
62 ms
58 ms
1 ms
PayPal
utility
167 ms
152 ms
12 ms
167 ms
152 ms
12 ms
AB Tasty
analytics
71 ms
62 ms
8 ms
71 ms
62 ms
8 ms
Reduce the impact of third-party code Third-party code blocked the main thread for 640 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
377 KiB
577 ms
/gtm.js?id=GTM-NQTQQRC
(www.googletagmanager.com)
138 KiB
329 ms
/gtag/js?id=…
(www.googletagmanager.com)
133 KiB
229 ms
/gtag/destination?id=…
(www.googletagmanager.com)
104 KiB
19 ms
2 KiB
0 ms
PayPal
utility
179 KiB
27 ms
169 KiB
27 ms
4 KiB
0 ms
4 KiB
0 ms
2 KiB
0 ms
Optanon
consent-provider
187 KiB
23 ms
…202408.1.0/otBannerSdk.js
(cdn.cookielaw.org)
111 KiB
19 ms
8 KiB
4 ms
26 KiB
0 ms
…v2/otPcTab.json
(cdn.cookielaw.org)
14 KiB
0 ms
12 KiB
0 ms
…assets/otCommonStyles.css
(cdn.cookielaw.org)
5 KiB
0 ms
3 KiB
0 ms
3 KiB
0 ms
3 KiB
0 ms
…static/ot_guard_logo.svg
(cdn.cookielaw.org)
1 KiB
0 ms
…geo/location
(geolocation.onetrust.com)
0 KiB
0 ms
AB Tasty
analytics
82 KiB
17 ms
63 KiB
17 ms
/6018fb1….js
(try.abtasty.com)
3 KiB
0 ms
7 KiB
0 ms
/shared/me.160b8ec….js
(try.abtasty.com)
4 KiB
0 ms
4 KiB
0 ms
Facebook
social
83 KiB
0 ms
/en_US/sdk.js?hash=c0b7bf0…
(connect.facebook.net)
76 KiB
0 ms
/en_US/sdk.js
(connect.facebook.net)
4 KiB
0 ms
2 KiB
0 ms
Cloudflare CDN
cdn
76 KiB
0 ms
76 KiB
0 ms
Google Fonts
cdn
60 KiB
0 ms
…v47/KFO5CnqEu….woff2
(fonts.gstatic.com)
38 KiB
0 ms
…v47/KFO7CnqEu….woff2
(fonts.gstatic.com)
22 KiB
0 ms
Bing Ads
ad
36 KiB
0 ms
…s/0.7.69
(bat.bing.com)
17 KiB
0 ms
/bat.js
(bat.bing.com)
15 KiB
0 ms
…action/5713906.js
(bat.bing.com)
2 KiB
0 ms
…t/5713906
(bat.bing.com)
1 KiB
0 ms
…c/s
(bat.bing.com)
1 KiB
0 ms
Cloudflare
utility
14 KiB
0 ms
/beacon.min.js/vcd15cbe…
(static.cloudflareinsights.com)
14 KiB
0 ms
beeroot.io
8 KiB
0 ms
…js/619193a….js
(api.beeroot.io)
6 KiB
0 ms
/api/visitors
(api.beeroot.io)
1 KiB
0 ms
/api/config?hello=…
(api.beeroot.io)
1 KiB
0 ms
Kameleoon
analytics
3 KiB
0 ms
/audiences/segments.js
(fgb0vnr9yv.kameleoon.io)
2 KiB
0 ms
/visit/events?siteCode=…
(data.kameleoon.io)
1 KiB
0 ms
1 KiB
0 ms
Salesforce Commerce Cloud
hosting
1 KiB
0 ms
/pebble?tla=…
(p.cquotient.com)
1 KiB
0 ms
1 KiB
0 ms
Google Analytics
analytics
1 KiB
0 ms
/g/collect?v=…
(www.google-analytics.com)
1 KiB
0 ms
bing.net
0 KiB
0 ms
/action/0?ti=…
(bat.bing.net)
0 KiB
0 ms
/actionp/0?ti=…
(bat.bing.net)
0 KiB
0 ms
Google/Doubleclick Ads
ad
0 KiB
0 ms
/ccm/collect?en=…
(pagead2.googlesyndication.com)
0 KiB
0 ms
Largest Contentful Paint element 4,280 ms
This is the largest contentful element painted within the viewport. Learn more about the Largest Contentful Paint elementLCP
Element
NIKE FIELD GENERAL
<img class="home__main-banner__image" src="https://www.courir.com/on/demandware.static/-/Library-Sites-Courir/default…" alt="NIKE FIELD GENERAL">
Phase
% of LCP
Timing
TTFB
14%
600 ms
Load Delay
27%
1,180 ms
Load Time
26%
1,110 ms
Render Delay
32%
1,390 ms
Reduce unused CSS Potential savings of 142 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
courir.com
1st party
129.2 KiB
124.5 KiB
129.2 KiB
124.5 KiB
Unattributable
20.3 KiB
17.4 KiB
#onetrust-banner-sdk .onetrust-vendors-list-handler{cursor:pointer;color:#1f96db;font-size:inherit; … } …
20.3 KiB
17.4 KiB
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
courir.com
1st party
660 ms
660 ms
Properly size images Potential savings of 24 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
courir.com
1st party
30.6 KiB
23.5 KiB
center > a.slide > picture > img.marque__banner__img
<img src="https://www.courir.com/on/demandware.static/-/Library-Sites-Courir/default…" class="marque__banner__img">
30.6 KiB
23.5 KiB
Reduce unused JavaScript Potential savings of 593 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
courir.com
1st party
283.9 KiB
225.0 KiB
…js/bundle_checkout.js
(www.courir.com)
110.7 KiB
83.4 KiB
…ui/jquery-ui.min.js
(www.courir.com)
52.6 KiB
46.8 KiB
40.9 KiB
40.9 KiB
…js/bundle_neo.js
(www.courir.com)
38.8 KiB
29.2 KiB
…swiper/swiper.js
(www.courir.com)
41.0 KiB
24.8 KiB
Google Tag Manager
tag-manager
372.0 KiB
154.5 KiB
/gtag/destination?id=…
(www.googletagmanager.com)
103.4 KiB
59.4 KiB
/gtag/js?id=…
(www.googletagmanager.com)
131.8 KiB
52.3 KiB
/gtm.js?id=GTM-NQTQQRC
(www.googletagmanager.com)
136.8 KiB
42.9 KiB
PayPal
utility
164.2 KiB
86.7 KiB
82.1 KiB
47.3 KiB
82.1 KiB
39.5 KiB
Optanon
consent-provider
110.1 KiB
59.3 KiB
…202408.1.0/otBannerSdk.js
(cdn.cookielaw.org)
110.1 KiB
59.3 KiB
Facebook
social
73.3 KiB
45.7 KiB
/en_US/sdk.js?hash=c0b7bf0…
(connect.facebook.net)
73.3 KiB
45.7 KiB
AB Tasty
analytics
62.7 KiB
21.7 KiB
62.7 KiB
21.7 KiB
Avoid an excessive DOM size 2,266 elements
A large DOM will increase memory usage, cause longer style calculations, and produce costly layout reflows. Learn how to avoid an excessive DOM size.TBT
Statistic
Element
Value
Total DOM Elements
2,266
Maximum DOM Depth
li.js_subsub_menu_item > a.subsubmenu-link > div.menu_picto > img.lazyfrz
<img src="data:image/gif;base64,R0lGODlhAQABAAAAACH5BAEKAAEALAAAAAABAAEAAAICTAEAOw==" alt="" data-frz-src="/on/demandware.static/-/Sites-storefront-catalog-fr/default/dw1f577f86/ico…" class="lazyfrz">
24
Maximum Child Elements
body
<body data-frz-flags="{&quot;lazyload&quot;:true,&quot;unlazyload&quot;:false,&quot;deferjs&quot;:true,&quot;cssontop&quot;:true,&quot;minify…" data-frz-version="2" data-frz-target-key="page_caching_policies_1" data-frz-target-label="HP">
57
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
courir.com
1st party
center > a.slide > picture > img.marque__banner__img
<img src="https://www.courir.com/on/demandware.static/-/Library-Sites-Courir/default…" class="marque__banner__img">
Minify JavaScript Potential savings of 12 KiB
Minifying JavaScript files can reduce payload sizes and script parse time. Learn how to minify JavaScript.LCPFCP
URL
Transfer Size
Potential Savings
courir.com
1st party
19.0 KiB
11.6 KiB
…capphone/capphone.js
(www.courir.com)
12.9 KiB
7.9 KiB
6.1 KiB
3.7 KiB
Serve static assets with an efficient cache policy 58 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
courir.com
1st party
840 KiB
…v2/gretel.min.js
(www.courir.com)
1h
21 KiB
4h
42 KiB
30d
130 KiB
…js/bundle_checkout.js
(www.courir.com)
30d
111 KiB
…ui/jquery-ui.min.js
(www.courir.com)
30d
53 KiB
…swiper/swiper.js
(www.courir.com)
30d
42 KiB
…js/bundle_neo.js
(www.courir.com)
30d
40 KiB
…fonts/neo.ttf.woff2
(www.courir.com)
30d
37 KiB
30d
32 KiB
30d
31 KiB
30d
27 KiB
30d
27 KiB
30d
19 KiB
30d
15 KiB
30d
15 KiB
30d
15 KiB
30d
15 KiB
30d
14 KiB
…capphone/capphone.js
(www.courir.com)
30d
14 KiB
30d
13 KiB
30d
13 KiB
30d
11 KiB
30d
9 KiB
30d
9 KiB
30d
9 KiB
30d
8 KiB
…lib/jquery.cycle2.js
(www.courir.com)
30d
7 KiB
30d
7 KiB
30d
7 KiB
30d
7 KiB
30d
5 KiB
…ui/jquery-ui.min.css
(www.courir.com)
30d
5 KiB
…js/bundle_gtm.js
(www.courir.com)
30d
4 KiB
30d
3 KiB
…swiper/swiper.css
(www.courir.com)
30d
3 KiB
30d
3 KiB
…lib/svg-inject.min.js
(www.courir.com)
30d
3 KiB
…jscript/applepay.js
(www.courir.com)
30d
3 KiB
30d
2 KiB
…jscript/dwac-21.7.js
(www.courir.com)
30d
2 KiB
30d
2 KiB
30d
2 KiB
30d
2 KiB
…lib/hoverintent.js
(www.courir.com)
30d
1 KiB
30d
1 KiB
30d
1 KiB
PayPal
utility
169 KiB
1h
85 KiB
1h
85 KiB
Optanon
consent-provider
135 KiB
…202408.1.0/otBannerSdk.js
(cdn.cookielaw.org)
1d
111 KiB
1d
12 KiB
1d
8 KiB
1d
3 KiB
Bing Ads
ad
17 KiB
…s/0.7.69
(bat.bing.com)
1d
17 KiB
Cloudflare
utility
14 KiB
/beacon.min.js/vcd15cbe…
(static.cloudflareinsights.com)
1d
7 KiB
/beacon.min.js/vcd15cbe…
(static.cloudflareinsights.com)
1d
7 KiB
beeroot.io
6 KiB
…js/619193a….js
(api.beeroot.io)
8h
6 KiB
AB Tasty
analytics
3 KiB
/6018fb1….js
(try.abtasty.com)
30s
3 KiB
Salesforce Commerce Cloud
hosting
1 KiB
/pebble?tla=…
(p.cquotient.com)
None
1 KiB
Ensure text remains visible during webfont load
Leverage the font-display CSS feature to ensure text is user-visible while webfonts are loading. Learn more about font-display.
URL
Potential Savings
courir.com
1st party
360 ms
360 ms
Cloudflare CDN
cdn
30 ms
30 ms
Defer offscreen images Potential savings of 103 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
courir.com
1st party
86.8 KiB
86.8 KiB
Push item #1
<img class="frz-img mobile-menu__push__image lazyloaded" src="https://www.courir.com/on/demandware.static/-/Library-Sites-Courir/default…" alt="Push item #1" data-frz-src="https://www.courir.com/on/demandware.static/-/Library-Sites-Courir/default…" width="450" height="300" onload="frzRemoveDimensionsTag(this)">
31.3 KiB
31.3 KiB
e-carte cadeau courir
<img class="gift-card__packshot lazyloaded" src="/on/demandware.static/-/Sites/default/dw5af98056/DIVERS/CARTEKDO/CARTECADE…" alt="e-carte cadeau courir" data-frz-src="/on/demandware.static/-/Sites/default/dw5af98056/DIVERS/CARTEKDO/CARTECADE…" onload="frzRemoveDimensionsTag(this)">
12.9 KiB
12.9 KiB
Push item #2
<img class="mobile-menu__push__image lazyloaded" src="https://www.courir.com/on/demandware.static/-/Library-Sites-Courir/default…" alt="Push item #2" data-frz-src="https://www.courir.com/on/demandware.static/-/Library-Sites-Courir/default…">
9.9 KiB
9.9 KiB
ul.menu_topcat-wrapper > li.js_main_menu_item > a.submenu-link > div.topcat-image
<div class="topcat-image" style="background-image: url(&quot;/on/demandware.static/-/Sites-storefront-catalog-fr…&quot;);" alt="">
8.6 KiB
8.6 KiB
ul.menu_topcat-wrapper > li.js_main_menu_item > a.submenu-link > div.topcat-image
<div class="topcat-image" style="background-image: url(&quot;/on/demandware.static/-/Sites-storefront-catalog-fr…&quot;);" alt="">
7.9 KiB
7.9 KiB
ul.menu_topcat-wrapper > li.js_main_menu_item > a.submenu-link > div.topcat-image
<div class="topcat-image" style="background-image: url(&quot;/on/demandware.static/-/Sites-storefront-catalog-fr…&quot;);" alt="">
7.4 KiB
7.4 KiB
Sneakers Spirit
<img class="frz-img logoSN lazyloaded" src="https://www.courir.com/on/demandware.static/-/Library-Sites-Courir/default…" alt="Sneakers Spirit" data-frz-src="https://www.courir.com/on/demandware.static/-/Library-Sites-Courir/default…" width="1200" height="440" onload="frzRemoveDimensionsTag(this)">
6.1 KiB
6.1 KiB
Uniquement chez courir
<img class="frz-img product-tags-item macaron-tag" aria-hidden="true" src="/on/demandware.static/-/Sites-master-catalog-courir/fr/dw5401b9df/images/m…" alt="Uniquement chez courir" data-code="uniquement_esc_chez_esc_courir" width="100" height="100" onload="frzRemoveDimensionsTag(this)">
2.6 KiB
2.6 KiB
Optanon
consent-provider
14.4 KiB
14.4 KiB
Logo de la société
<img alt="Logo de la société" src="https://cdn.cookielaw.org/logos/48157018-b4a4-440f-9f15-983b39d958b9/82672…">
11.6 KiB
11.6 KiB
Powered by Onetrust
<img alt="Powered by Onetrust" src="https://cdn.cookielaw.org/logos/static/powered_by_logo.svg">
2.9 KiB
2.9 KiB
Unattributable
2.2 KiB
2.2 KiB
Chaussures en ligne, vente en ligne de basket - Courir
<img class="frz-img search__logo__img" itemprop="logo" src="data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAQAAAAEACAMAAABrrFhUAAACN1BM…" alt="Chaussures en ligne, vente en ligne de basket - Courir" width="256" height="256" onload="frzRemoveDimensionsTag(this)">
2.2 KiB
2.2 KiB
Avoid serving legacy JavaScript to modern browsers Potential savings of 48 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. However, many aren't necessary for modern browsers. For your bundled JavaScript, adopt a modern script deployment strategy using module/nomodule feature detection to reduce the amount of code shipped to modern browsers, while retaining support for legacy browsers. Learn how to use modern JavaScriptLCPFCP
URL
Potential Savings
PayPal
utility
23.6 KiB
11.8 KiB
Array.from
Array.prototype.find
Object.entries
Object.keys
11.8 KiB
Array.from
Array.prototype.find
Object.entries
Object.keys
courir.com
1st party
10.3 KiB
…v2/gretel.min.js
(www.courir.com)
10.1 KiB
Date.prototype.toJSON
Array.prototype.filter
Array.from
@babel/plugin-transform-regenerator
…js/bundle_checkout.js
(www.courir.com)
0.2 KiB
@babel/plugin-transform-classes
@babel/plugin-transform-regenerator
beeroot.io
7.3 KiB
…js/619193a….js
(api.beeroot.io)
7.3 KiB
Array.isArray
Optanon
consent-provider
6.9 KiB
…202408.1.0/otBannerSdk.js
(cdn.cookielaw.org)
6.9 KiB
Array.prototype.fill
AB Tasty
analytics
0.0 KiB
0.0 KiB
@babel/plugin-transform-classes
Avoid long main-thread tasks 13 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
Google Tag Manager
tag-manager
828 ms
/gtm.js?id=GTM-NQTQQRC
(www.googletagmanager.com)
11,174 ms
319 ms
/gtag/js?id=…
(www.googletagmanager.com)
14,193 ms
279 ms
/gtm.js?id=GTM-NQTQQRC
(www.googletagmanager.com)
16,573 ms
111 ms
/gtag/destination?id=…
(www.googletagmanager.com)
15,672 ms
69 ms
/gtm.js?id=GTM-NQTQQRC
(www.googletagmanager.com)
11,124 ms
50 ms
courir.com
1st party
290 ms
7,958 ms
146 ms
…js/bundle_checkout.js
(www.courir.com)
7,501 ms
93 ms
4,151 ms
51 ms
PayPal
utility
127 ms
6,301 ms
67 ms
5,251 ms
60 ms
Optanon
consent-provider
124 ms
…202408.1.0/otBannerSdk.js
(cdn.cookielaw.org)
16,684 ms
70 ms
15,741 ms
54 ms
AB Tasty
analytics
67 ms
9,613 ms
67 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
Sneaker deals : Jusqu'à -30% sur une sélection de produits* - J'y vais !
<div class="swiper-slide swiper-slide-active" role="group" aria-label="1 / 3" data-swiper-slide-index="0" style="height: 32px;">
0.016
Web font loaded
A late network request adjusted the page layout
null
<li role="button" tabindex="0" class="top-banner__stores js--top-banner__stores focus-visible" aria-label="null">
0.000
…fonts/neo.ttf.woff2
(www.courir.com)
Web font loaded
Web font loaded
Web font loaded
Web font loaded
Web font loaded
A late network request adjusted the page layout
div.global__information__container > div.swiper > div.swiper-button-prev > ::after
<::after>
0.000
User Timing marks and measures 9 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
__paypal_messaging_performance__scriptLoadDelay
Measure
0.00 ms
2,591.00 ms
__paypal_messaging_performance__firstRenderDelay
Measure
0.00 ms
3,156.50 ms
__paypal_messaging_performance__scriptLoadDelay
Measure
3,154.90 ms
759.60 ms
frz_deferjs_registerScriptTags
Mark
2,499.50 ms
frz_deferjs_executing
Mark
2,500.81 ms
__paypal_messaging_performance__scriptLoadDelay
Mark
2,591.18 ms
frz_deferjs_sync_done
Mark
3,063.48 ms
__paypal_messaging_performance__firstRenderDelay
Mark
3,156.60 ms
__paypal_messaging_performance__scriptLoadDelay
Mark
3,914.56 ms
Avoids enormous network payloads Total size was 2,078 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
Google Tag Manager
tag-manager
375.1 KiB
/gtm.js?id=GTM-NQTQQRC
(www.googletagmanager.com)
137.9 KiB
/gtag/js?id=…
(www.googletagmanager.com)
132.8 KiB
/gtag/destination?id=…
(www.googletagmanager.com)
104.4 KiB
courir.com
1st party
241.5 KiB
130.0 KiB
…js/bundle_checkout.js
(www.courir.com)
111.5 KiB
PayPal
utility
169.3 KiB
84.6 KiB
84.6 KiB
Optanon
consent-provider
111.0 KiB
…202408.1.0/otBannerSdk.js
(cdn.cookielaw.org)
111.0 KiB
Cloudflare CDN
cdn
76.3 KiB
76.3 KiB
Facebook
social
76.1 KiB
/en_US/sdk.js?hash=c0b7bf0…
(connect.facebook.net)
76.1 KiB
Avoid chaining critical requests 1 chain 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: 1,684.528 ms
Initial Navigation
- 136.597 ms, 5.63 KiB
More information about the performance of your application. These numbers don't directly affect the Performance score.
Passed audits (16)
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
Efficiently encode images
Optimized images load faster and consume less cellular data. Learn how to efficiently encode images.LCPFCP
Serve images in next-gen formats
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
Enable text compression
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. Learn more about text compression.LCPFCP
Preconnect to required origins
Consider adding preconnect or dns-prefetch resource hints to establish early connections to important third-party origins. Learn how to preconnect to required origins.LCPFCP
Avoid multiple page redirects
Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.LCPFCP
Use video formats for animated content
Large GIFs are inefficient for delivering animated content. Consider using MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF to save network bytes. Learn more about efficient video formatsLCPFCP
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
Lazy load third-party resources with facades
Some third-party embeds can be lazy loaded. Consider replacing them with a facade until they are required. Learn how to defer third-parties with a facade.TBT
Largest Contentful Paint image was not lazily loaded
Above-the-fold images that are lazily loaded render later in the page lifecycle, which can delay the largest contentful paint. Learn more about optimal lazy loading.LCP
Element
NIKE FIELD GENERAL
<img class="home__main-banner__image" src="https://www.courir.com/on/demandware.static/-/Library-Sites-Courir/default…" alt="NIKE FIELD GENERAL">
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().
Avoid non-composited animations
Animations which are not composited can be janky and increase CLS. Learn how to avoid non-composited animationsCLS
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
center > a.slide > picture > img.marque__banner__img
<img src="https://www.courir.com/on/demandware.static/-/Library-Sites-Courir/default…" class="marque__banner__img">
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
Elements use prohibited ARIA attributes
Using ARIA attributes in roles where they are prohibited can mean that important information is not communicated to users of assistive technologies. Learn more about prohibited ARIA roles.
Failing Elements
Rechercher
<div type="submit" class="search__btn js-search__btn" aria-label="Rechercher">
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
null
<li role="button" tabindex="0" class="top-banner__stores js--top-banner__stores focus-visible" aria-label="null">
ARIA IDs are unique
The value of an ARIA ID must be unique to prevent other instances from being overlooked by assistive technologies. Learn how to fix duplicate ARIA IDs.
Failing Elements
Rechercher dans le catalogue
<input class="search__input js-search__input valid" type="text" id="q" name="q" value="" placeholder="Rechercher" aria-label="Rechercher dans le catalogue" autocomplete="off" aria-invalid="false">
div.mobile-menu__search > form.search__form > div.search__fieldset > input#q
<input class="search__input js-search-terms__input" type="text" id="q" name="q" value="" placeholder="Rechercher">
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.
Contrast
Background and foreground colors do not have a sufficient contrast ratio.
Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.
Failing Elements
JE M'ABONNE
<span>
JE M'ABONNE
<button class="footer__newsletter__button btn" type="submit" name="home-email" value="Je m'abonne">
These are opportunities to improve the legibility of your content.
Tables and lists
Lists do not 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.
Failing Elements
null
<ul class="top-banner__wrapper">
null
<li role="button" tabindex="0" class="top-banner__stores js--top-banner__stores focus-visible" aria-label="null">
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Best practices
Touch targets do not have sufficient size or spacing.
Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.
Failing Elements
Foire aux questions
<a href="https://www.courir.com/on/demandware.store/Sites-Courir-FR-Site/fr_FR/FAQ-…">
Nous contacter
<a href="https://www.courir.com/fr/contact">
Nous contacter
<a href="https://www.courir.com/fr/contact">
Foire aux questions
<a href="https://www.courir.com/on/demandware.store/Sites-Courir-FR-Site/fr_FR/FAQ-…">
Suivre mes commandes
<a href="https://www.courir.com/fr/suivre-mes-commandes">
Suivre mes commandes
<a href="https://www.courir.com/fr/suivre-mes-commandes">
Nous contacter
<a href="https://www.courir.com/fr/contact">
Effectuer un retour
<a href="https://www.courir.com/on/demandware.store/Sites-Courir-FR-Site/fr_FR/FAQ-…">
Effectuer un retour
<a href="https://www.courir.com/on/demandware.store/Sites-Courir-FR-Site/fr_FR/FAQ-…">
Suivre mes commandes
<a href="https://www.courir.com/fr/suivre-mes-commandes">
Guide des tailles
<a href="https://www.courir.com/on/demandware.store/Sites-Courir-FR-Site/fr_FR/Size…">
Guide des tailles
<a href="https://www.courir.com/on/demandware.store/Sites-Courir-FR-Site/fr_FR/Size…">
Effectuer un retour
<a href="https://www.courir.com/on/demandware.store/Sites-Courir-FR-Site/fr_FR/FAQ-…">
Consulter le solde de votre e-carte cadeau Courir
<a href="https://www.courir.com/on/demandware.store/Sites-Courir-FR-Site/fr_FR/SVSC…">
Consulter le solde de votre e-carte cadeau Courir
<a href="https://www.courir.com/on/demandware.store/Sites-Courir-FR-Site/fr_FR/SVSC…">
Guide des tailles
<a href="https://www.courir.com/on/demandware.store/Sites-Courir-FR-Site/fr_FR/Size…">
E-réservation
<a href="https://www.courir.com/fr/nos-services-e-reservation.html">
Click and Collect
<a href="https://www.courir.com/fr/nos-services-click-and-collect.html">
Click and Collect
<a href="https://www.courir.com/fr/nos-services-click-and-collect.html">
E-réservation
<a href="https://www.courir.com/fr/nos-services-e-reservation.html">
Commande web en magasin
<a href="https://www.courir.com/fr/nos-services-commande-web-en-magasin.html">
Commande web en magasin
<a href="https://www.courir.com/fr/nos-services-commande-web-en-magasin.html">
Click and Collect
<a href="https://www.courir.com/fr/nos-services-click-and-collect.html">
Programme fidélité myCOURIR
<a href="https://www.courir.com/on/demandware.store/Sites-Courir-FR-Site/fr_FR/Loya…">
Programme fidélité myCOURIR
<a href="https://www.courir.com/on/demandware.store/Sites-Courir-FR-Site/fr_FR/Loya…">
Commande web en magasin
<a href="https://www.courir.com/fr/nos-services-commande-web-en-magasin.html">
Qui sommes-nous ?
<a href="https://www.courir.com/fr/qui-sommes-nous/">
Accessibilité - partiellement conforme
<a href="https://www.courir.com/fr/Accessibilit%C3%A9.html">
Accessibilité - partiellement conforme
<a href="https://www.courir.com/fr/Accessibilit%C3%A9.html">
Qui sommes-nous ?
<a href="https://www.courir.com/fr/qui-sommes-nous/">
Traçabilité produits
<a href=" https://app.traceforgood.com/public-search/courir" target="_blank">
Traçabilité produits
<a href=" https://app.traceforgood.com/public-search/courir" target="_blank">
Accessibilité - partiellement conforme
<a href="https://www.courir.com/fr/Accessibilit%C3%A9.html">
Recycle Your Ex Sneakers
<a href="https://www.courir.com/fr/c/recycle-your-ex-sneakers/">
Recycle Your Ex Sneakers
<a href="https://www.courir.com/fr/c/recycle-your-ex-sneakers/">
Traçabilité produits
<a href=" https://app.traceforgood.com/public-search/courir" target="_blank">
Hot drops
<a href="https://www.courir.com/fr/c/latest-hot-drops/">
Hot drops
<a href="https://www.courir.com/fr/c/latest-hot-drops/">
Recycle Your Ex Sneakers
<a href="https://www.courir.com/fr/c/recycle-your-ex-sneakers/">
Magasins Courir
<a href="https://www.courir.com/fr/stores">
Magasins Courir
<a href="https://www.courir.com/fr/stores">
Hot drops
<a href="https://www.courir.com/fr/c/latest-hot-drops/">
Rejoignez-nous
<a href="https://jobs.courir.com/" target="_blank">
Rejoignez-nous
<a href="https://jobs.courir.com/" target="_blank">
Magasins Courir
<a href="https://www.courir.com/fr/stores">
Conditions Générales programme fidélité myCOURIR
<a href="https://www.courir.com/fr/cgv-cartemycourir.html">
Charte de Protection des Données Personnelles des Clients
<a href="https://www.courir.com/fr/charte-de-protection.html">
Charte de Protection des Données Personnelles des Clients
<a href="https://www.courir.com/fr/charte-de-protection.html">
Conditions Générales programme fidélité myCOURIR
<a href="https://www.courir.com/fr/cgv-cartemycourir.html">
Préférences de cookies
<a href="#" onclick="return Optanon.ToggleInfoDisplay()">
Préférences de cookies
<a href="#" onclick="return Optanon.ToggleInfoDisplay()">
Charte de Protection des Données Personnelles des Clients
<a href="https://www.courir.com/fr/charte-de-protection.html">
*Mentions légales des opérations en cours
<a href="https://www.courir.com/fr/mentions-operations-en-cours">
*Mentions légales des opérations en cours
<a href="https://www.courir.com/fr/mentions-operations-en-cours">
Préférences de cookies
<a href="#" onclick="return Optanon.ToggleInfoDisplay()">
Soldes
<a href="https://www.courir.com/fr/c/soldes/">
Soldes
<a href="https://www.courir.com/fr/c/soldes/">
*Mentions légales des opérations en cours
<a href="https://www.courir.com/fr/mentions-operations-en-cours">
Ventes privées
<a href="https://www.courir.com/fr/c/ventes-privees/">
Ventes privées
<a href="https://www.courir.com/fr/c/ventes-privees/">
Soldes
<a href="https://www.courir.com/fr/c/soldes/">
Black friday
<a href="https://www.courir.com/fr/c/sneakers-friday/">
Black friday
<a href="https://www.courir.com/fr/c/sneakers-friday/">
Ventes privées
<a href="https://www.courir.com/fr/c/ventes-privees/">
Idées cadeaux
<a href="https://www.courir.com/fr/c/idees-cadeaux/">
Idées cadeaux
<a href="https://www.courir.com/fr/c/idees-cadeaux/">
Black friday
<a href="https://www.courir.com/fr/c/sneakers-friday/">
These items highlight common accessibility best practices.
Additional items to manually check (10)
Show Hide
Interactive controls are keyboard focusable
Custom interactive controls are keyboard focusable and display a focus indicator. Learn how to make custom controls focusable.
Interactive elements indicate their purpose and state
Interactive elements, such as links and buttons, should indicate their state and be distinguishable from non-interactive elements. Learn how to decorate interactive elements with affordance hints.
The page has a logical tab order
Tabbing through the page follows the visual layout. Users cannot focus elements that are offscreen. Learn more about logical tab ordering.
Visual order on the page follows DOM order
DOM order matches the visual order, improving navigation for assistive technology. Learn more about DOM and visual ordering.
User focus is not accidentally trapped in a region
A user can tab into and out of any control or region without accidentally trapping their focus. Learn how to avoid focus traps.
The user's focus is directed to new content added to the page
If new content, such as a dialog, is added to the page, the user's focus is directed to it. Learn how to direct focus to new content.
HTML5 landmark elements are used to improve navigation
Landmark elements (<main>, <nav>, etc.) are used to improve the keyboard navigation of the page for assistive technology. Learn more about landmark elements.
Offscreen content is hidden from assistive technology
Offscreen content is hidden with display: none or aria-hidden=true. Learn how to properly hide offscreen content.
Custom controls have associated labels
Custom interactive controls have associated labels, provided by aria-label or aria-labelledby. Learn more about custom controls and labels.
Custom controls have ARIA roles
Custom interactive controls have appropriate ARIA roles. Learn how to add roles to custom controls.
These items address areas which an automated testing tool cannot cover. Learn more in our guide on conducting an accessibility review.
Passed audits (24)
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.
button, link, and menuitem elements have accessible names
When an element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn how to make command elements more accessible.
ARIA 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.
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-hidden="true"] elements do not contain focusable descendents
Focusable descendents within an [aria-hidden="true"] element prevent those interactive elements from being available to users of assistive technologies like screen readers. Learn how aria-hidden affects focusable elements.
[role] values are valid
ARIA roles must have valid values in order to perform their intended accessibility functions. Learn more about valid ARIA roles.
Document has a <title> element
The title gives screen reader users an overview of the page, and search engine users rely on it heavily to determine if a page is relevant to their search. Learn more about document titles.
<html> element has a [lang] attribute
If a page doesn't specify a lang attribute, a screen reader assumes that the page is in the default language that the user chose when setting up the screen reader. If the page isn't actually in the default language, then the screen reader might not announce the page's text correctly. Learn more about the lang attribute.
<html> element has a valid value for its [lang] attribute
Specifying a valid BCP 47 language helps screen readers announce text properly. Learn how to use the lang attribute.
Form elements have associated labels
Labels ensure that form controls are announced properly by assistive technologies, like screen readers. Learn more about form element labels.
List items (<li>) are contained within <ul>, <ol> or <menu> parent elements
Screen readers require list items (<li>) to be contained within a parent <ul>, <ol> or <menu> to be announced properly. Learn more about proper list structure.
No element has a [tabindex] value greater than 0
A value greater than 0 implies an explicit navigation ordering. Although technically valid, this often creates frustrating experiences for users who rely on assistive technologies. Learn more about the tabindex attribute.
[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.
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.
Image elements do not 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.
Not applicable (26)
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.
ARIA input fields have accessible names
When an input field doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn more about input field labels.
ARIA meter elements have accessible names
When a meter element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn how to name meter elements.
ARIA progressbar elements have accessible names
When a progressbar element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn how to label progressbar elements.
Elements with an ARIA [role] that require children to contain a specific [role] have all required children.
Some ARIA parent roles must contain specific child roles to perform their intended accessibility functions. Learn more about roles and required children elements.
[role]s are contained by their required parent element
Some ARIA child roles must be contained by specific parent roles to properly perform their intended accessibility functions. Learn more about ARIA roles and required parent element.
Elements with the role=text attribute do not have focusable descendents.
Adding role=text around a text node split by markup enables VoiceOver to treat it as one phrase, but the element's focusable descendents will not be announced. Learn more about the role=text attribute.
ARIA toggle fields have accessible names
When a toggle field doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn more about toggle fields.
ARIA tooltip elements have accessible names
When a tooltip element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn how to name tooltip elements.
ARIA treeitem elements have accessible names
When a treeitem element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn more about labeling treeitem elements.
The page contains a heading, skip link, or landmark region
Adding ways to bypass repetitive content lets keyboard users navigate the page more efficiently. Learn more about bypass blocks.
<dl>'s contain only properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements.
When definition lists are not properly marked up, screen readers may produce confusing or inaccurate output. Learn how to structure definition lists correctly.
Definition list items are wrapped in <dl> elements
Definition list items (<dt> and <dd>) must be wrapped in a parent <dl> element to ensure that screen readers can properly announce them. Learn how to structure definition lists correctly.
No form fields have multiple labels
Form fields with multiple labels can be confusingly announced by assistive technologies like screen readers which use either the first, the last, or all of the labels. Learn how to use form labels.
<frame> or <iframe> elements have a title
Screen reader users rely on frame titles to describe the contents of frames. Learn more about frame titles.
<html> element has an [xml:lang] attribute with the same base language as the [lang] attribute.
If the webpage does not specify a consistent language, then the screen reader might not announce the page's text correctly. Learn more about the lang attribute.
Input buttons have discernible text.
Adding discernable and accessible text to input buttons may help screen reader users understand the purpose of the input button. Learn more about input buttons.
<input type="image"> elements have [alt] text
When an image is being used as an <input> button, providing alternative text can help screen reader users understand the purpose of the button. Learn about input image alt text.
The document does not use <meta http-equiv="refresh">
Users do not expect a page to refresh automatically, and doing so will move focus back to the top of the page. This may create a frustrating or confusing experience. Learn more about the refresh meta tag.
<object> elements have alternate text
Screen readers cannot translate non-text content. Adding alternate text to <object> elements helps screen readers convey meaning to users. Learn more about alt text for object elements.
Select elements have associated label elements.
Form elements without effective labels can create frustrating experiences for screen reader users. Learn more about the select element.
Tables have different content in the summary attribute and <caption>.
The summary attribute should describe the table structure, while <caption> should have the onscreen title. Accurate table mark-up helps users of screen readers. Learn more about summary and caption.
Cells in a <table> element that use the [headers] attribute refer to table cells within the same table.
Screen readers have features to make navigating tables easier. Ensuring <td> cells using the [headers] attribute only refer to other cells in the same table may improve the experience for screen reader users. Learn more about the headers attribute.
<th> elements and elements with [role="columnheader"/"rowheader"] have data cells they describe.
Screen readers have features to make navigating tables easier. Ensuring table headers always refer to some set of cells may improve the experience for screen reader users. Learn more about table headers.
<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 1 warning found
Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs.
Deprecation / Warning
Source
courir.com
1st party
UnloadHandler
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
Kameleoon
analytics
Failed to load resource: the server responded with a status of 403 (Forbidden)
Failed to load resource: the server responded with a status of 403 (Forbidden)
Detected JavaScript libraries
All front-end JavaScript libraries detected on the page. Learn more about this JavaScript library detection diagnostic audit.
Name
Version
jQuery
2.1.1
jQuery UI
1.11.2
Lo-Dash
4.17.21
core-js
core-js-pure@3.31.1; core-js-global@2.6.12; core-js-global@3.27.0
Missing source maps for large first-party JavaScript
Source maps translate minified code to the original source code. This helps developers debug in production. In addition, Lighthouse is able to provide further insights. Consider deploying source maps to take advantage of these benefits. Learn more about source maps.
URL
Map URL
courir.com
1st party
…js/bundle_checkout.js
(www.courir.com)
Large JavaScript file is missing a source map
User Experience
Document doesn't use legible font sizes 29.59% 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
Unattributable
dynamic
#onetrust-banner-sdk #onetrust-policy-text, #onetrust-banner-sdk .ot-b-addl-desc, #onetrust-banner-sdk .ot-gv-list-handler
66.31%
11.382px
dynamic
#onetrust-banner-sdk #onetrust-accept-btn-handler, #onetrust-banner-sdk #onetrust-reject-all-handler, #onetrust-banner-sdk #onetrust-pc-btn-handler
0.25%
11.382px
dynamic
#onetrust-banner-sdk #onetrust-policy-text *, #onetrust-banner-sdk .ot-b-addl-desc *, #onetrust-banner-sdk .ot-gv-list-handler *
0.08%
11.382px
Add'l illegible text
0.45%
< 12px
Legible text
29.59%
≥ 12px
courir.com
1st party
.footer-container .footer-item li
2.15%
11.9px
.reassurance ul li
0.73%
11.2px
ul.footer-bottom-links
0.36%
11.2px
.footer-container h3, .footer-container h4
0.08%
11.2px
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
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.
Avoids third-party cookies
Chrome is moving towards a new experience that allows users to choose to browse without third-party cookies. Learn more about third-party cookies.
Allows users to paste into input fields
Preventing input pasting is a bad practice for the UX, and weakens security by blocking password managers.Learn more about user-friendly input fields.
Avoids requesting the geolocation permission on page load
Users are mistrustful of or confused by sites that request their location without context. Consider tying the request to a user action instead. Learn more about the geolocation permission.
Avoids requesting the notification permission on page load
Users are mistrustful of or confused by sites that request to send notifications without context. Consider tying the request to user gestures instead. Learn more about responsibly getting permission for notifications.
Displays images with correct aspect ratio
Image display dimensions should match natural aspect ratio. Learn more about image aspect ratio.
Serves images with appropriate resolution
Image natural dimensions should be proportional to the display size and the pixel ratio to maximize image clarity. Learn how to provide responsive images.
Has a <meta name="viewport"> tag with width or initial-scale
A <meta name="viewport"> not only optimizes your app for mobile screen sizes, but also prevents a 300 millisecond delay to user input. Learn more about using the viewport meta tag.
Page has the HTML doctype
Specifying a doctype prevents the browser from switching to quirks-mode. Learn more about the doctype declaration.
Properly defines charset
A character encoding declaration is required. It can be done with a <meta> tag in the first 1024 bytes of the HTML or in the Content-Type HTTP response header. Learn more about declaring the character encoding.
No issues in the Issues panel in Chrome Devtools
Issues logged to the Issues panel in Chrome Devtools indicate unresolved problems. They can come from network request failures, insufficient security controls, and other browser concerns. Open up the Issues panel in Chrome DevTools for more details on each issue.
Not applicable (1)
Show Hide
Redirects HTTP traffic to HTTPS
Make sure that you redirect all HTTP traffic to HTTPS in order to enable secure web features for all your users. Learn more.
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
Links are not 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
Uncrawlable Link
Langue
<a class="country-selectorlink link">
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
center > a.slide > picture > img.marque__banner__img
<img src="https://www.courir.com/on/demandware.static/-/Library-Sites-Courir/default…" class="marque__banner__img">
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 (7)
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.
robots.txt is valid
If your robots.txt file is malformed, crawlers may not be able to understand how you want your website to be crawled or indexed. Learn more about robots.txt.
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.
Not applicable (1)
Show Hide
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.4 s
Page LoadsGood (≤ 2.5 s)90%Needs Improvement (2.5 s - 4 s)6%Poor (> 4 s)4%75th Percentile - 1.4 sCore Web Vital
Interaction to Next Paint (INP)
77 ms
Page LoadsGood (≤ 200 ms)95%Needs Improvement (200 ms - 500 ms)4%Poor (> 500 ms)1%75th Percentile - 77 msCore Web Vital
Cumulative Layout Shift (CLS)
0.07
Page LoadsGood (≤ 0.1)97%Needs Improvement (0.1 - 0.25)2%Poor (> 0.25)1%75th Percentile - 0.07Core Web Vital
Other Notable Metrics
First Contentful Paint (FCP)
1 s
Page LoadsGood (≤ 1.8 s)89%Needs Improvement (1.8 s - 3 s)6%Poor (> 3 s)5%75th Percentile - 1 s 
Time to First Byte (TTFB)
0.6 s
Page LoadsGood (≤ 0.8 s)81%Needs Improvement (0.8 s - 1.8 s)14%Poor (> 1.8 s)5%75th Percentile - 0.6 sExperimental
Latest 28-day collection period
Various desktop devicesMany samples (Chrome UX Report)Full visit durationsVarious network connectionsAll Chrome versions
Core Web Vitals Assessment: Failed
Largest Contentful Paint (LCP)
1.4 s
Page LoadsGood (≤ 2.5 s)86%Needs Improvement (2.5 s - 4 s)6%Poor (> 4 s)8%75th Percentile - 1.4 sCore Web Vital
Interaction to Next Paint (INP)
79 ms
Page LoadsGood (≤ 200 ms)94%Needs Improvement (200 ms - 500 ms)4%Poor (> 500 ms)3%75th Percentile - 79 msCore Web Vital
Cumulative Layout Shift (CLS)
0.15
Page LoadsGood (≤ 0.1)67%Needs Improvement (0.1 - 0.25)19%Poor (> 0.25)15%75th Percentile - 0.15Core Web Vital
Other Notable Metrics
First Contentful Paint (FCP)
0.9 s
Page LoadsGood (≤ 1.8 s)87%Needs Improvement (1.8 s - 3 s)4%Poor (> 3 s)8%75th Percentile - 0.9 s 
Time to First Byte (TTFB)
0.5 s
Page LoadsGood (≤ 0.8 s)82%Needs Improvement (0.8 s - 1.8 s)9%Poor (> 1.8 s)9%75th Percentile - 0.5 sExperimental
Latest 28-day collection period
Various desktop devicesMany samples (Chrome UX Report)Full visit durationsVarious network connectionsAll Chrome versions
Diagnose performance issues
73 FCP+10LCP+24TBT+11CLS+25SI+3 Performance
Values are estimated and may vary. The performance score is calculated directly from these metrics.See calculator.
0–49 50–89 90–100
Final Screenshot
Metrics
First Contentful Paint
0.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
1.0 s
Largest Contentful Paint marks the time at which the largest text or image is painted. Learn more about the Largest Contentful Paint metric
Total Blocking Time
430 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.035
Cumulative Layout Shift measures the movement of visible elements within the viewport. Learn more about the Cumulative Layout Shift metric.
Speed Index
2.8 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more about the Speed Index metric.
  • Captured at Feb 24, 2025, 6:00 PM UTC
  • Emulated Desktop with Lighthouse 12.2.3
    Unthrottled CPU/Memory Power: 465 CPU throttling: 1x slowdown (Simulated) Screen emulation: 1350x940, DPR 1 Axe version: 4.10.2
  • Single page session
    This data is taken from a single page session, as opposed to field data summarizing many sessions.
  • Initial page load
  • Custom throttling
    Network throttling: 40 ms TCP RTT, 10,240 kb/s throughput (Simulated) Browser location: North America
  • Using HeadlessChromium 133.0.6943.53 with lr
    User agent (network): "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/119.0.0.0 Safari/537.36"
Screenshot
Screenshot
Screenshot
Screenshot
Screenshot
Screenshot
Screenshot
Screenshot
Show audits relevant to:
Diagnostics
Minimize main-thread work 2.8 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to minimize main-thread workTBT
Category
Time Spent
Script Evaluation
1,742 ms
Style & Layout
363 ms
Other
297 ms
Garbage Collection
118 ms
Script Parsing & Compilation
113 ms
Parse HTML & CSS
98 ms
Rendering
77 ms
Reduce JavaScript execution time 1.6 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
courir.com
1st party
1,446 ms
800 ms
38 ms
430 ms
36 ms
2 ms
297 ms
205 ms
20 ms
283 ms
254 ms
5 ms
…jsd/main.js
(www.courir.com)
223 ms
210 ms
0 ms
…swiper/swiper.js
(www.courir.com)
145 ms
34 ms
3 ms
…js/bundle_checkout.js
(www.courir.com)
69 ms
61 ms
8 ms
Google Tag Manager
tag-manager
608 ms
480 ms
23 ms
/gtm.js?id=GTM-NQTQQRC
(www.googletagmanager.com)
419 ms
304 ms
10 ms
/gtag/js?id=…
(www.googletagmanager.com)
137 ms
128 ms
8 ms
/gtag/destination?id=…
(www.googletagmanager.com)
53 ms
47 ms
6 ms
Optanon
consent-provider
165 ms
109 ms
8 ms
…202408.1.0/otBannerSdk.js
(cdn.cookielaw.org)
112 ms
70 ms
7 ms
54 ms
39 ms
1 ms
Unattributable
152 ms
7 ms
0 ms
Unattributable
152 ms
7 ms
0 ms
PayPal
utility
125 ms
112 ms
11 ms
125 ms
112 ms
11 ms
Reduce the impact of third-party code Third-party code blocked the main thread for 330 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
377 KiB
327 ms
/gtm.js?id=GTM-NQTQQRC
(www.googletagmanager.com)
138 KiB
240 ms
/gtag/js?id=…
(www.googletagmanager.com)
133 KiB
85 ms
/gtag/destination?id=…
(www.googletagmanager.com)
104 KiB
2 ms
2 KiB
0 ms
PayPal
utility
179 KiB
4 ms
169 KiB
4 ms
4 KiB
0 ms
4 KiB
0 ms
2 KiB
0 ms
Optanon
consent-provider
187 KiB
0 ms
…202408.1.0/otBannerSdk.js
(cdn.cookielaw.org)
111 KiB
0 ms
26 KiB
0 ms
…v2/otPcTab.json
(cdn.cookielaw.org)
14 KiB
0 ms
12 KiB
0 ms
8 KiB
0 ms
…assets/otCommonStyles.css
(cdn.cookielaw.org)
5 KiB
0 ms
3 KiB
0 ms
3 KiB
0 ms
3 KiB
0 ms
…static/ot_guard_logo.svg
(cdn.cookielaw.org)
1 KiB
0 ms
…geo/location
(geolocation.onetrust.com)
0 KiB
0 ms
Facebook
social
83 KiB
0 ms
/en_US/sdk.js?hash=c0b7bf0…
(connect.facebook.net)
76 KiB
0 ms
/en_US/sdk.js
(connect.facebook.net)
4 KiB
0 ms
2 KiB
0 ms
AB Tasty
analytics
82 KiB
0 ms
63 KiB
0 ms
7 KiB
0 ms
/shared/me.160b8ec….js
(try.abtasty.com)
4 KiB
0 ms
4 KiB
0 ms
/6018fb1….js
(try.abtasty.com)
3 KiB
0 ms
Cloudflare CDN
cdn
76 KiB
0 ms
76 KiB
0 ms
Google Fonts
cdn
60 KiB
0 ms
…v47/KFO5CnqEu….woff2
(fonts.gstatic.com)
38 KiB
0 ms
…v47/KFO7CnqEu….woff2
(fonts.gstatic.com)
22 KiB
0 ms
Bing Ads
ad
35 KiB
0 ms
…s/0.7.69
(bat.bing.com)
17 KiB
0 ms
/bat.js
(bat.bing.com)
15 KiB
0 ms
…t/5713906
(bat.bing.com)
1 KiB
0 ms
…action/5713906.js
(bat.bing.com)
1 KiB
0 ms
…c/x
(bat.bing.com)
1 KiB
0 ms
beeroot.io
8 KiB
0 ms
…js/619193a….js
(api.beeroot.io)
6 KiB
0 ms
/api/visitors
(api.beeroot.io)
1 KiB
0 ms
/api/config?hello=…
(api.beeroot.io)
1 KiB
0 ms
Kameleoon
analytics
3 KiB
0 ms
/audiences/segments.js
(fgb0vnr9yv.kameleoon.io)
2 KiB
0 ms
/visit/events?siteCode=…
(data.kameleoon.io)
1 KiB
0 ms
1 KiB
0 ms
Salesforce Commerce Cloud
hosting
1 KiB
0 ms
/pebble?tla=…
(p.cquotient.com)
1 KiB
0 ms
1 KiB
0 ms
Google Analytics
analytics
1 KiB
0 ms
/g/collect?v=…
(www.google-analytics.com)
1 KiB
0 ms
bing.net
0 KiB
0 ms
/action/0?ti=…
(bat.bing.net)
0 KiB
0 ms
/actionp/0?ti=…
(bat.bing.net)
0 KiB
0 ms
Google/Doubleclick Ads
ad
0 KiB
0 ms
/ccm/collect?en=…
(pagead2.googlesyndication.com)
0 KiB
0 ms
Reduce initial server response time Root document took 700 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
courir.com
1st party
700 ms
700 ms
Properly size images Potential savings of 102 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
courir.com
1st party
169.4 KiB
101.8 KiB
NIKE FIELD GENERAL
<img class="home__main-banner__image" src="https://www.courir.com/on/demandware.static/-/Library-Sites-Courir/default…" alt="NIKE FIELD GENERAL">
119.1 KiB
61.5 KiB
center > a.slide > picture > img.marque__banner__img
<img src="https://www.courir.com/on/demandware.static/-/Library-Sites-Courir/default…" class="marque__banner__img">
50.3 KiB
40.3 KiB
Reduce unused CSS Potential savings of 141 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
courir.com
1st party
129.2 KiB
123.3 KiB
129.2 KiB
123.3 KiB
Unattributable
20.3 KiB
17.5 KiB
#onetrust-banner-sdk .onetrust-vendors-list-handler{cursor:pointer;color:#1f96db;font-size:inherit; … } …
20.3 KiB
17.5 KiB
Reduce unused JavaScript Potential savings of 593 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
courir.com
1st party
283.9 KiB
225.0 KiB
…js/bundle_checkout.js
(www.courir.com)
110.7 KiB
83.4 KiB
…ui/jquery-ui.min.js
(www.courir.com)
52.6 KiB
46.8 KiB
40.9 KiB
40.8 KiB
…js/bundle_neo.js
(www.courir.com)
38.8 KiB
29.2 KiB
…swiper/swiper.js
(www.courir.com)
41.0 KiB
24.8 KiB
Google Tag Manager
tag-manager
372.0 KiB
154.5 KiB
/gtag/destination?id=…
(www.googletagmanager.com)
103.4 KiB
59.4 KiB
/gtag/js?id=…
(www.googletagmanager.com)
131.8 KiB
52.3 KiB
/gtm.js?id=GTM-NQTQQRC
(www.googletagmanager.com)
136.8 KiB
42.9 KiB
PayPal
utility
164.2 KiB
86.7 KiB
82.1 KiB
47.3 KiB
82.1 KiB
39.5 KiB
Optanon
consent-provider
110.1 KiB
59.3 KiB
…202408.1.0/otBannerSdk.js
(cdn.cookielaw.org)
110.1 KiB
59.3 KiB
Facebook
social
73.3 KiB
45.7 KiB
/en_US/sdk.js?hash=c0b7bf0…
(connect.facebook.net)
73.3 KiB
45.7 KiB
AB Tasty
analytics
62.7 KiB
21.7 KiB
62.7 KiB
21.7 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
courir.com
1st party
center > a.slide > picture > img.marque__banner__img
<img src="https://www.courir.com/on/demandware.static/-/Library-Sites-Courir/default…" class="marque__banner__img">
Unattributable
SWEAT CREW CLUB
<img src="data:image/gif;base64,R0lGODlhAQABAAAAACH5BAEKAAEALAAAAAABAAEAAAICTAEAOw==" alt="SWEAT CREW CLUB" aria-hidden="true" data-frz-src="https://www.courir.com/dw/image/v2/BCCL_PRD/on/demandware.static/-/Sites-m…" class="lazyfrz">
Minify JavaScript Potential savings of 12 KiB
Minifying JavaScript files can reduce payload sizes and script parse time. Learn how to minify JavaScript.LCPFCP
URL
Transfer Size
Potential Savings
courir.com
1st party
19.0 KiB
11.6 KiB
…capphone/capphone.js
(www.courir.com)
12.9 KiB
7.9 KiB
6.1 KiB
3.7 KiB
Serve static assets with an efficient cache policy 56 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
courir.com
1st party
1,004 KiB
…v2/gretel.min.js
(www.courir.com)
1h
21 KiB
4h
42 KiB
30d
130 KiB
30d
120 KiB
…js/bundle_checkout.js
(www.courir.com)
30d
111 KiB
30d
55 KiB
…ui/jquery-ui.min.js
(www.courir.com)
30d
53 KiB
30d
51 KiB
…swiper/swiper.js
(www.courir.com)
30d
42 KiB
…js/bundle_neo.js
(www.courir.com)
30d
40 KiB
…fonts/neo.ttf.woff2
(www.courir.com)
30d
37 KiB
30d
27 KiB
30d
27 KiB
30d
23 KiB
30d
17 KiB
30d
15 KiB
30d
15 KiB
30d
15 KiB
30d
15 KiB
…capphone/capphone.js
(www.courir.com)
30d
14 KiB
30d
13 KiB
30d
13 KiB
30d
11 KiB
30d
9 KiB
30d
9 KiB
30d
9 KiB
30d
8 KiB
…lib/jquery.cycle2.js
(www.courir.com)
30d
7 KiB
30d
7 KiB
30d
7 KiB
30d
5 KiB
…ui/jquery-ui.min.css
(www.courir.com)
30d
5 KiB
…js/bundle_gtm.js
(www.courir.com)
30d
4 KiB
30d
3 KiB
…swiper/swiper.css
(www.courir.com)
30d
3 KiB
30d
3 KiB
…lib/svg-inject.min.js
(www.courir.com)
30d
3 KiB
…jscript/applepay.js
(www.courir.com)
30d
3 KiB
30d
2 KiB
…jscript/dwac-21.7.js
(www.courir.com)
30d
2 KiB
30d
2 KiB
30d
2 KiB
30d
2 KiB
…lib/hoverintent.js
(www.courir.com)
30d
1 KiB
30d
1 KiB
30d
1 KiB
PayPal
utility
169 KiB
1h
85 KiB
1h
85 KiB
Optanon
consent-provider
135 KiB
…202408.1.0/otBannerSdk.js
(cdn.cookielaw.org)
1d
111 KiB
1d
12 KiB
1d
8 KiB
1d
3 KiB
Bing Ads
ad
17 KiB
…s/0.7.69
(bat.bing.com)
1d
17 KiB
beeroot.io
6 KiB
…js/619193a….js
(api.beeroot.io)
8h
6 KiB
AB Tasty
analytics
3 KiB
/6018fb1….js
(try.abtasty.com)
30s
3 KiB
Salesforce Commerce Cloud
hosting
1 KiB
/pebble?tla=…
(p.cquotient.com)
None
1 KiB
Ensure text remains visible during webfont load
Leverage the font-display CSS feature to ensure text is user-visible while webfonts are loading. Learn more about font-display.
URL
Potential Savings
courir.com
1st party
250 ms
250 ms
Cloudflare CDN
cdn
20 ms
20 ms
Defer offscreen images Potential savings of 41 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
courir.com
1st party
23.9 KiB
23.9 KiB
ul.menu_topcat-wrapper > li.js_main_menu_item > a.submenu-link > div.topcat-image
<div class="topcat-image" style="background-image: url(&quot;/on/demandware.static/-/Sites-storefront-catalog-fr…&quot;);" alt="">
8.6 KiB
8.6 KiB
ul.menu_topcat-wrapper > li.js_main_menu_item > a.submenu-link > div.topcat-image
<div class="topcat-image" style="background-image: url(&quot;/on/demandware.static/-/Sites-storefront-catalog-fr…&quot;);" alt="">
7.9 KiB
7.9 KiB
ul.menu_topcat-wrapper > li.js_main_menu_item > a.submenu-link > div.topcat-image
<div class="topcat-image" style="background-image: url(&quot;/on/demandware.static/-/Sites-storefront-catalog-fr…&quot;);" alt="">
7.4 KiB
7.4 KiB
Optanon
consent-provider
14.4 KiB
14.4 KiB
Logo de la société
<img alt="Logo de la société" src="https://cdn.cookielaw.org/logos/48157018-b4a4-440f-9f15-983b39d958b9/82672…">
11.6 KiB
11.6 KiB
Powered by Onetrust
<img alt="Powered by Onetrust" src="https://cdn.cookielaw.org/logos/static/powered_by_logo.svg">
2.8 KiB
2.8 KiB
Unattributable
2.9 KiB
2.9 KiB
li.country__selector__item > div.country__selector__country > div.country-selector__flag__container > img.country-selector__flag
<img class="country-selector__flag" src="data:image/svg+xml;charset=utf-8,%3Csvg%20xmlns%3D%22http%3A%2F%2Fwww.w3.o…" alt="" aria-hidden="true">
2.9 KiB
2.9 KiB
Avoid serving legacy JavaScript to modern browsers Potential savings of 48 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. However, many aren't necessary for modern browsers. For your bundled JavaScript, adopt a modern script deployment strategy using module/nomodule feature detection to reduce the amount of code shipped to modern browsers, while retaining support for legacy browsers. Learn how to use modern JavaScriptLCPFCP
URL
Potential Savings
PayPal
utility
23.6 KiB
11.8 KiB
Array.from
Array.prototype.find
Object.entries
Object.keys
11.8 KiB
Array.from
Array.prototype.find
Object.entries
Object.keys
courir.com
1st party
10.3 KiB
…v2/gretel.min.js
(www.courir.com)
10.1 KiB
Date.prototype.toJSON
Array.prototype.filter
Array.from
@babel/plugin-transform-regenerator
…js/bundle_checkout.js
(www.courir.com)
0.2 KiB
@babel/plugin-transform-classes
@babel/plugin-transform-regenerator
beeroot.io
7.3 KiB
…js/619193a….js
(api.beeroot.io)
7.3 KiB
Array.isArray
Optanon
consent-provider
6.9 KiB
…202408.1.0/otBannerSdk.js
(cdn.cookielaw.org)
6.9 KiB
Array.prototype.fill
AB Tasty
analytics
0.0 KiB
0.0 KiB
@babel/plugin-transform-classes
Avoid an excessive DOM size 1,456 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,456
Maximum DOM Depth
DÉCOUVRIR
<strong>
16
Maximum Child Elements
body
<body data-frz-flags="{&quot;lazyload&quot;:true,&quot;unlazyload&quot;:false,&quot;deferjs&quot;:true,&quot;cssontop&quot;:true,&quot;minify…" data-frz-version="2" data-frz-target-key="page_caching_policies_1" data-frz-target-label="HP">
55
Avoid long main-thread tasks 10 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
Google Tag Manager
tag-manager
527 ms
/gtm.js?id=GTM-NQTQQRC
(www.googletagmanager.com)
2,548 ms
270 ms
/gtag/js?id=…
(www.googletagmanager.com)
3,218 ms
135 ms
/gtm.js?id=GTM-NQTQQRC
(www.googletagmanager.com)
3,831 ms
70 ms
/gtag/destination?id=…
(www.googletagmanager.com)
3,553 ms
52 ms
courir.com
1st party
314 ms
…jsd/main.js
(www.courir.com)
2,139 ms
111 ms
1,786 ms
69 ms
…js/bundle_checkout.js
(www.courir.com)
1,681 ms
68 ms
841 ms
66 ms
PayPal
utility
54 ms
1,481 ms
54 ms
Optanon
consent-provider
50 ms
…202408.1.0/otBannerSdk.js
(cdn.cookielaw.org)
3,901 ms
50 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
Sneaker deals : Jusqu'à -30% sur une sélection de produits* - J'y vais !
<div class="swiper-slide swiper-slide-active" role="group" aria-label="1 / 3" data-swiper-slide-index="0" style="height: 32px;">
0.035
Nouvelle collection : Découvrez la nouvelle collection - J'y vais !
<div class="swiper-slide swiper-slide-next" role="group" aria-label="2 / 3" data-swiper-slide-index="1" style="height: 32px;">
0.000
Web font loaded
Web font loaded
J'y vais !
<u>
0.000
A late network request adjusted the page layout
User Timing marks and measures 10 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
__paypal_messaging_performance__scriptLoadDelay
Measure
0.00 ms
2,414.20 ms
__paypal_messaging_performance__firstRenderDelay
Measure
0.00 ms
2,784.10 ms
__paypal_messaging_performance__scriptLoadDelay
Measure
2,782.80 ms
844.10 ms
frz_insert_fragments
Mark
2,266.21 ms
frz_deferjs_registerScriptTags
Mark
2,331.08 ms
frz_deferjs_executing
Mark
2,331.86 ms
__paypal_messaging_performance__scriptLoadDelay
Mark
2,415.11 ms
frz_deferjs_sync_done
Mark
2,714.82 ms
__paypal_messaging_performance__firstRenderDelay
Mark
2,784.32 ms
__paypal_messaging_performance__scriptLoadDelay
Mark
3,627.11 ms
Avoids enormous network payloads Total size was 2,225 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
Google Tag Manager
tag-manager
375.1 KiB
/gtm.js?id=GTM-NQTQQRC
(www.googletagmanager.com)
137.9 KiB
/gtag/js?id=…
(www.googletagmanager.com)
132.8 KiB
/gtag/destination?id=…
(www.googletagmanager.com)
104.4 KiB
courir.com
1st party
361.4 KiB
130.0 KiB
119.9 KiB
…js/bundle_checkout.js
(www.courir.com)
111.5 KiB
PayPal
utility
169.3 KiB
84.6 KiB
84.6 KiB
Optanon
consent-provider
111.0 KiB
…202408.1.0/otBannerSdk.js
(cdn.cookielaw.org)
111.0 KiB
Cloudflare CDN
cdn
76.3 KiB
76.3 KiB
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,118.174 ms
Initial Navigation
- 473.947 ms, 5.63 KiB
- 1,228.375 ms, 8.60 KiB
Largest Contentful Paint element 1,000 ms
This is the largest contentful element painted within the viewport. Learn more about the Largest Contentful Paint elementLCP
Element
NIKE FIELD GENERAL
<img class="home__main-banner__image" src="https://www.courir.com/on/demandware.static/-/Library-Sites-Courir/default…" alt="NIKE FIELD GENERAL">
Phase
% of LCP
Timing
TTFB
16%
160 ms
Load Delay
26%
260 ms
Load Time
40%
400 ms
Render Delay
18%
180 ms
More information about the performance of your application. These numbers don't directly affect the Performance score.
Passed audits (16)
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
Efficiently encode images
Optimized images load faster and consume less cellular data. Learn how to efficiently encode images.LCPFCP
Serve images in next-gen formats
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
Enable text compression
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. Learn more about text compression.LCPFCP
Preconnect to required origins
Consider adding preconnect or dns-prefetch resource hints to establish early connections to important third-party origins. Learn how to preconnect to required origins.LCPFCP
Avoid multiple page redirects
Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.LCPFCP
Use video formats for animated content
Large GIFs are inefficient for delivering animated content. Consider using MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF to save network bytes. Learn more about efficient video formatsLCPFCP
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
Lazy load third-party resources with facades
Some third-party embeds can be lazy loaded. Consider replacing them with a facade until they are required. Learn how to defer third-parties with a facade.TBT
Largest Contentful Paint image was not lazily loaded
Above-the-fold images that are lazily loaded render later in the page lifecycle, which can delay the largest contentful paint. Learn more about optimal lazy loading.LCP
Element
NIKE FIELD GENERAL
<img class="home__main-banner__image" src="https://www.courir.com/on/demandware.static/-/Library-Sites-Courir/default…" alt="NIKE FIELD GENERAL">
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().
Avoid non-composited animations
Animations which are not composited can be janky and increase CLS. Learn how to avoid non-composited animationsCLS
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
New
<a class="submenu-link " href="https://www.courir.com/fr/c/nouveautes/" id="menubtn-nouveautes" aria-haspopup="false" aria-controls="menu-nouveautes">
Promos
<a class="submenu-link " href="https://www.courir.com/fr/c/promotions/" id="menubtn-promotions" aria-haspopup="false" aria-controls="menu-promotions">
Outlet
<a class="submenu-link " href="https://www.courir.com/fr/c/outlet/" id="menubtn-outlet" aria-haspopup="false" aria-controls="menu-outlet">
Elements use prohibited ARIA attributes
Using ARIA attributes in roles where they are prohibited can mean that important information is not communicated to users of assistive technologies. Learn more about prohibited ARIA roles.
Failing Elements
Rechercher
<div type="submit" class="search__btn js-search__btn" aria-label="Rechercher">
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
MAGASINS
<li role="button" tabindex="0" class="top-banner__stores js--top-banner__stores focus-visible" aria-label="Magasins Courir à travers le monde">
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
center > a.slide > picture > img.marque__banner__img
<img src="https://www.courir.com/on/demandware.static/-/Library-Sites-Courir/default…" class="marque__banner__img">
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.
Contrast
Background and foreground colors do not have a sufficient contrast ratio.
Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.
Failing Elements
Rechercher dans le catalogue
<input class="search__input js-search__input valid" type="text" id="q" name="q" value="" placeholder="Rechercher" aria-label="Rechercher dans le catalogue" autocomplete="off" aria-invalid="false">
JE M'ABONNE
<span>
JE M'ABONNE
<button class="footer__newsletter__button btn" type="submit" name="home-email" value="Je m'abonne">
These are opportunities to improve the legibility of your content.
Tables and lists
Lists do not 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.
Failing Elements
MAGASINS MON COMPTE PANIER
<ul class="top-banner__wrapper" data-fstrz-fragment-id="fstrz-scss-1" data-fstrz-fragment-selector=".top-banner__wrapper">
MAGASINS
<li role="button" tabindex="0" class="top-banner__stores js--top-banner__stores focus-visible" aria-label="Magasins Courir à travers le monde">
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Best practices
Touch targets do not have sufficient size or spacing.
Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.
Failing Elements
visitez le sous catégorie: CHAUSSURES
<button aria-label="visitez le sous catégorie: CHAUSSURES" type="button" aria-expanded="false" aria-haspopup="dialog" aria-controls="menu-chaussures" class="btn-ada-menu js-btn-ada-menu">
Chaussures
<a class="submenu-link has-sub-menu " href="https://www.courir.com/fr/c/chaussures/" id="menubtn-chaussures" aria-haspopup="true" aria-expanded="false" aria-controls="menu-chaussures">
Vêtements
<a class="submenu-link has-sub-menu " href="https://www.courir.com/fr/c/vetements/" id="menubtn-vetements" aria-haspopup="true" aria-expanded="false" aria-controls="menu-vetements">
visitez le sous catégorie: VÊTEMENTS
<button aria-label="visitez le sous catégorie: VÊTEMENTS" type="button" aria-expanded="false" aria-haspopup="dialog" aria-controls="menu-vetements" class="btn-ada-menu js-btn-ada-menu">
Vêtements
<a class="submenu-link has-sub-menu " href="https://www.courir.com/fr/c/vetements/" id="menubtn-vetements" aria-haspopup="true" aria-expanded="false" aria-controls="menu-vetements">
Accessoires
<a class="submenu-link has-sub-menu " href="https://www.courir.com/fr/c/accessoires/" id="menubtn-accessoires" aria-haspopup="true" aria-expanded="false" aria-controls="menu-accessoires">
visitez le sous catégorie: ACCESSOIRES
<button aria-label="visitez le sous catégorie: ACCESSOIRES" type="button" aria-expanded="false" aria-haspopup="dialog" aria-controls="menu-accessoires" class="btn-ada-menu js-btn-ada-menu">
Accessoires
<a class="submenu-link has-sub-menu " href="https://www.courir.com/fr/c/accessoires/" id="menubtn-accessoires" aria-haspopup="true" aria-expanded="false" aria-controls="menu-accessoires">
Marques
<a class="submenu-link has-sub-menu brand_menu" href="https://www.courir.com/fr/c/marques/" id="menubtn-marques" aria-haspopup="true" aria-expanded="false" aria-controls="menu-marques" style="color: !important">
visitez le sous catégorie: MARQUES
<button aria-label="visitez le sous catégorie: MARQUES" type="button" aria-expanded="false" aria-haspopup="dialog" aria-controls="menu-marques" class="btn-ada-menu js-btn-ada-menu">
Marques
<a class="submenu-link has-sub-menu brand_menu" href="https://www.courir.com/fr/c/marques/" id="menubtn-marques" aria-haspopup="true" aria-expanded="false" aria-controls="menu-marques" style="color: !important">
New
<a class="submenu-link " href="https://www.courir.com/fr/c/nouveautes/" id="menubtn-nouveautes" aria-haspopup="false" aria-controls="menu-nouveautes">
Magasins Courir
<a href="https://www.courir.com/fr/stores">
Rejoignez-nous
<a href="https://jobs.courir.com/" target="_blank">
Rejoignez-nous
<a href="https://jobs.courir.com/" target="_blank">
Magasins Courir
<a href="https://www.courir.com/fr/stores">
These items highlight common accessibility best practices.
Additional items to manually check (10)
Show Hide
Interactive controls are keyboard focusable
Custom interactive controls are keyboard focusable and display a focus indicator. Learn how to make custom controls focusable.
Interactive elements indicate their purpose and state
Interactive elements, such as links and buttons, should indicate their state and be distinguishable from non-interactive elements. Learn how to decorate interactive elements with affordance hints.
The page has a logical tab order
Tabbing through the page follows the visual layout. Users cannot focus elements that are offscreen. Learn more about logical tab ordering.
Visual order on the page follows DOM order
DOM order matches the visual order, improving navigation for assistive technology. Learn more about DOM and visual ordering.
User focus is not accidentally trapped in a region
A user can tab into and out of any control or region without accidentally trapping their focus. Learn how to avoid focus traps.
The user's focus is directed to new content added to the page
If new content, such as a dialog, is added to the page, the user's focus is directed to it. Learn how to direct focus to new content.
HTML5 landmark elements are used to improve navigation
Landmark elements (<main>, <nav>, etc.) are used to improve the keyboard navigation of the page for assistive technology. Learn more about landmark elements.
Offscreen content is hidden from assistive technology
Offscreen content is hidden with display: none or aria-hidden=true. Learn how to properly hide offscreen content.
Custom controls have associated labels
Custom interactive controls have associated labels, provided by aria-label or aria-labelledby. Learn more about custom controls and labels.
Custom controls have ARIA roles
Custom interactive controls have appropriate ARIA roles. Learn how to add roles to custom controls.
These items address areas which an automated testing tool cannot cover. Learn more in our guide on conducting an accessibility review.
Passed audits (24)
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.
button, link, and menuitem elements have accessible names
When an element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn how to make command elements more accessible.
ARIA 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.
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-hidden="true"] elements do not contain focusable descendents
Focusable descendents within an [aria-hidden="true"] element prevent those interactive elements from being available to users of assistive technologies like screen readers. Learn how aria-hidden affects focusable elements.
[role] values are valid
ARIA roles must have valid values in order to perform their intended accessibility functions. Learn more about valid ARIA roles.
Document has a <title> element
The title gives screen reader users an overview of the page, and search engine users rely on it heavily to determine if a page is relevant to their search. Learn more about document titles.
<html> element has a [lang] attribute
If a page doesn't specify a lang attribute, a screen reader assumes that the page is in the default language that the user chose when setting up the screen reader. If the page isn't actually in the default language, then the screen reader might not announce the page's text correctly. Learn more about the lang attribute.
<html> element has a valid value for its [lang] attribute
Specifying a valid BCP 47 language helps screen readers announce text properly. Learn how to use the lang attribute.
Form elements have associated labels
Labels ensure that form controls are announced properly by assistive technologies, like screen readers. Learn more about form element labels.
List items (<li>) are contained within <ul>, <ol> or <menu> parent elements
Screen readers require list items (<li>) to be contained within a parent <ul>, <ol> or <menu> to be announced properly. Learn more about proper list structure.
No element has a [tabindex] value greater than 0
A value greater than 0 implies an explicit navigation ordering. Although technically valid, this often creates frustrating experiences for users who rely on assistive technologies. Learn more about the tabindex attribute.
[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.
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.
Image elements do not 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.
Not applicable (26)
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.
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.
<frame> or <iframe> elements have a title
Screen reader users rely on frame titles to describe the contents of frames. Learn more about frame titles.
<html> element has an [xml:lang] attribute with the same base language as the [lang] attribute.
If the webpage does not specify a consistent language, then the screen reader might not announce the page's text correctly. Learn more about the lang attribute.
Input buttons have discernible text.
Adding discernable and accessible text to input buttons may help screen reader users understand the purpose of the input button. Learn more about input buttons.
<input type="image"> elements have [alt] text
When an image is being used as an <input> button, providing alternative text can help screen reader users understand the purpose of the button. Learn about input image alt text.
The document does not use <meta http-equiv="refresh">
Users do not expect a page to refresh automatically, and doing so will move focus back to the top of the page. This may create a frustrating or confusing experience. Learn more about the refresh meta tag.
<object> elements have alternate text
Screen readers cannot translate non-text content. Adding alternate text to <object> elements helps screen readers convey meaning to users. Learn more about alt text for object elements.
Select elements have associated label elements.
Form elements without effective labels can create frustrating experiences for screen reader users. Learn more about the select element.
Tables have different content in the summary attribute and <caption>.
The summary attribute should describe the table structure, while <caption> should have the onscreen title. Accurate table mark-up helps users of screen readers. Learn more about summary and caption.
Cells in a <table> element that use the [headers] attribute refer to table cells within the same table.
Screen readers have features to make navigating tables easier. Ensuring <td> cells using the [headers] attribute only refer to other cells in the same table may improve the experience for screen reader users. Learn more about the headers attribute.
<th> elements and elements with [role="columnheader"/"rowheader"] have data cells they describe.
Screen readers have features to make navigating tables easier. Ensuring table headers always refer to some set of cells may improve the experience for screen reader users. Learn more about table headers.
<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
courir.com
1st party
UnloadHandler
`StorageType.persistent` is deprecated. Please use standardized `navigator.storage` instead.
…jsd/main.js:1:6504
(www.courir.com)
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
Kameleoon
analytics
Failed to load resource: the server responded with a status of 403 (Forbidden)
Failed to load resource: the server responded with a status of 403 (Forbidden)
Detected JavaScript libraries
All front-end JavaScript libraries detected on the page. Learn more about this JavaScript library detection diagnostic audit.
Name
Version
jQuery
2.1.1
jQuery UI
1.11.2
Lo-Dash
4.17.21
core-js
core-js-pure@3.31.1; core-js-global@2.6.12; core-js-global@3.27.0
Missing source maps for large first-party JavaScript
Source maps translate minified code to the original source code. This helps developers debug in production. In addition, Lighthouse is able to provide further insights. Consider deploying source maps to take advantage of these benefits. Learn more about source maps.
URL
Map URL
courir.com
1st party
…js/bundle_checkout.js
(www.courir.com)
Large JavaScript file is missing a source map
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
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.
Avoids third-party cookies
Chrome is moving towards a new experience that allows users to choose to browse without third-party cookies. Learn more about third-party cookies.
Allows users to paste into input fields
Preventing input pasting is a bad practice for the UX, and weakens security by blocking password managers.Learn more about user-friendly input fields.
Avoids requesting the geolocation permission on page load
Users are mistrustful of or confused by sites that request their location without context. Consider tying the request to a user action instead. Learn more about the geolocation permission.
Avoids requesting the notification permission on page load
Users are mistrustful of or confused by sites that request to send notifications without context. Consider tying the request to user gestures instead. Learn more about responsibly getting permission for notifications.
Displays images with correct aspect ratio
Image display dimensions should match natural aspect ratio. Learn more about image aspect ratio.
Serves images with appropriate resolution
Image natural dimensions should be proportional to the display size and the pixel ratio to maximize image clarity. Learn how to provide responsive images.
Has a <meta name="viewport"> tag with width or initial-scale
A <meta name="viewport"> not only optimizes your app for mobile screen sizes, but also prevents a 300 millisecond delay to user input. Learn more about using the viewport meta tag.
Page has the HTML doctype
Specifying a doctype prevents the browser from switching to quirks-mode. Learn more about the doctype declaration.
Properly defines charset
A character encoding declaration is required. It can be done with a <meta> tag in the first 1024 bytes of the HTML or in the Content-Type HTTP response header. Learn more about declaring the character encoding.
No issues in the Issues panel in Chrome Devtools
Issues logged to the Issues panel in Chrome Devtools indicate unresolved problems. They can come from network request failures, insufficient security controls, and other browser concerns. Open up the Issues panel in Chrome DevTools for more details on each issue.
Not applicable (2)
Show Hide
Redirects HTTP traffic to HTTPS
Make sure that you redirect all HTTP traffic to HTTPS in order to enable secure web features for all your users. Learn more.
Document uses legible font sizes
Font sizes less than 12px are too small to be legible and require mobile visitors to “pinch to zoom” in order to read. Strive to have >60% of page text ≥12px. Learn more about legible font sizes.
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.
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
center > a.slide > picture > img.marque__banner__img
<img src="https://www.courir.com/on/demandware.static/-/Library-Sites-Courir/default…" class="marque__banner__img">
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
robots.txt is valid
If your robots.txt file is malformed, crawlers may not be able to understand how you want your website to be crawled or indexed. Learn more about robots.txt.
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.
Not applicable (1)
Show Hide
Document has a valid rel=canonical
Canonical links suggest which URL to show in search results. Learn more about canonical links.