PageSpeed Insights logo
PageSpeed Insights
PageSpeed Insights
This site uses cookies from Google to deliver its services and to analyze traffic.
Report from Mar 11, 2025, 6:00:26 PM
Discover what your real users are experiencing
Core Web Vitals Assessment: Passed
Largest Contentful Paint (LCP)
1.6 s
Page LoadsGood (≤ 2.5 s)89%Needs Improvement (2.5 s - 4 s)7%Poor (> 4 s)4%75th Percentile - 1.6 sCore Web Vital
Interaction to Next Paint (INP)
177 ms
Page LoadsGood (≤ 200 ms)80%Needs Improvement (200 ms - 500 ms)17%Poor (> 500 ms)3%75th Percentile - 177 msCore Web Vital
Cumulative Layout Shift (CLS)
0
Page LoadsGood (≤ 0.1)99%Needs Improvement (0.1 - 0.25)0%Poor (> 0.25)0%75th Percentile - 0Core Web Vital
Other Notable Metrics
First Contentful Paint (FCP)
1.4 s
Page LoadsGood (≤ 1.8 s)83%Needs Improvement (1.8 s - 3 s)11%Poor (> 3 s)6%75th Percentile - 1.4 s 
Time to First Byte (TTFB)
0.8 s
Page LoadsGood (≤ 0.8 s)76%Needs Improvement (0.8 s - 1.8 s)19%Poor (> 1.8 s)5%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: Failed
Largest Contentful Paint (LCP)
4 s
Page LoadsGood (≤ 2.5 s)41%Needs Improvement (2.5 s - 4 s)34%Poor (> 4 s)25%75th Percentile - 4 sCore Web Vital
Interaction to Next Paint (INP)
342 ms
Page LoadsGood (≤ 200 ms)52%Needs Improvement (200 ms - 500 ms)33%Poor (> 500 ms)15%75th Percentile - 342 msCore Web Vital
Cumulative Layout Shift (CLS)
0.13
Page LoadsGood (≤ 0.1)53%Needs Improvement (0.1 - 0.25)40%Poor (> 0.25)7%75th Percentile - 0.13Core Web Vital
Other Notable Metrics
First Contentful Paint (FCP)
3.7 s
Page LoadsGood (≤ 1.8 s)29%Needs Improvement (1.8 s - 3 s)32%Poor (> 3 s)39%75th Percentile - 3.7 s 
Time to First Byte (TTFB)
3 s
Page LoadsGood (≤ 0.8 s)19%Needs Improvement (0.8 s - 1.8 s)27%Poor (> 1.8 s)54%75th Percentile - 3 sExperimental
Latest 28-day collection period
Various mobile devicesMany samples (Chrome UX Report)Full visit durationsVarious network connectionsAll Chrome versions
Diagnose performance issues
55 FCP+1LCP+2TBT+21CLS+25SI+6 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
5.0 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
6.9 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
380 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds. Learn more about the Total Blocking Time metric.
Cumulative Layout Shift
0
Cumulative Layout Shift measures the movement of visible elements within the viewport. Learn more about the Cumulative Layout Shift metric.
Speed Index
5.0 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more about the Speed Index metric.
  • Captured at Mar 11, 2025, 6:00 PM UTC
  • Emulated Moto G Power with Lighthouse 12.4.0
    Unthrottled CPU/Memory Power: 289 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.141 with lr
    User agent (network): "Mozilla/5.0 (Linux; Android 11; moto g power (2022)) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/119.0.0.0 Mobile Safari/537.36"
Screenshot
Screenshot
Screenshot
Screenshot
Screenshot
Screenshot
Screenshot
Screenshot
Show audits relevant to:
Diagnostics
Largest Contentful Paint element 6,900 ms
This is the largest contentful element painted within the viewport. Learn more about the Largest Contentful Paint elementLCP
Element
main#main > div#quick-content > div.ab-prehome-row > div.ab-prehome-banner-background
<div class="ab-prehome-banner-background mobile-banner" style="background-image: url(&quot;https://www.coursesu.com/dw/image/v2/BBQX_PRD/on/de…&quot;);">
Phase
% of LCP
Timing
TTFB
9%
600 ms
Load Delay
71%
4,900 ms
Load Time
3%
200 ms
Render Delay
17%
1,190 ms
Eliminate render-blocking resources Potential savings of 3,890 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles. Learn how to eliminate render-blocking resources.LCPFCP
URL
Transfer Size
Potential Savings
coursesu.com
1st party
557.4 KiB
4,050 ms
462.2 KiB
3,150 ms
72.2 KiB
450 ms
…css/prehome.css
(www.coursesu.com)
13.5 KiB
300 ms
…css/mainab.css
(www.coursesu.com)
9.5 KiB
150 ms
Cloudflare CDN
cdn
48.5 KiB
1,350 ms
…3.4.29/vue.global.prod.min.js
(cdnjs.cloudflare.com)
48.5 KiB
1,350 ms
TagCommander
tag-manager
48.0 KiB
1,350 ms
/3692/tc_CoursesU_20.js
(cdn.tagcommander.com)
48.0 KiB
1,350 ms
Reduce unused JavaScript Potential savings of 914 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
coursesu.com
1st party
866.5 KiB
670.9 KiB
460.6 KiB
363.6 KiB
102.4 KiB
71.8 KiB
…js/prehome.js
(www.coursesu.com)
84.4 KiB
70.8 KiB
…js/partners.js
(www.coursesu.com)
74.7 KiB
63.2 KiB
…js/vendors.js
(www.coursesu.com)
72.8 KiB
52.7 KiB
71.6 KiB
48.8 KiB
JSDelivr CDN
cdn
220.8 KiB
111.7 KiB
220.8 KiB
111.7 KiB
luckycart.com
82.3 KiB
53.0 KiB
/systeme-u/luckyclient.min.js
(integration.luckycart.com)
82.3 KiB
53.0 KiB
Cloudflare CDN
cdn
47.5 KiB
41.6 KiB
…3.4.29/vue.global.prod.min.js
(cdnjs.cloudflare.com)
47.5 KiB
41.6 KiB
TagCommander
tag-manager
72.2 KiB
37.0 KiB
/3692/tc_CoursesU_21.js
(cdn.tagcommander.com)
72.2 KiB
37.0 KiB
Minimize main-thread work 2.4 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to minimize main-thread workTBT
Category
Time Spent
Script Evaluation
1,290 ms
Style & Layout
451 ms
Other
387 ms
Script Parsing & Compilation
132 ms
Rendering
48 ms
Garbage Collection
48 ms
Parse HTML & CSS
40 ms
Reduce the impact of third-party code Third-party code blocked the main thread for 270 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
JSDelivr CDN
cdn
260 KiB
173 ms
222 KiB
173 ms
32 KiB
0 ms
6 KiB
0 ms
Bazaarvoice
analytics
95 KiB
63 ms
/analytics/bv-analytics.js
(apps.bazaarvoice.com)
13 KiB
40 ms
…fr_FR/bv.js
(apps.bazaarvoice.com)
29 KiB
17 ms
…1/seller.min.js
(srd.bazaarvoice.com)
15 KiB
7 ms
7 KiB
0 ms
…3/bv-analytics.js
(analytics-static.ugc.bazaarvoice.com)
13 KiB
0 ms
…api/api-0.8.2.js
(apps.bazaarvoice.com)
11 KiB
0 ms
…fr_FR/api-config.js
(apps.bazaarvoice.com)
2 KiB
0 ms
…fr_FR/seller_ratings-config.js
(apps.bazaarvoice.com)
1 KiB
0 ms
1 KiB
0 ms
/sid.gif?_=rdymfb
(network.bazaarvoice.com)
1 KiB
0 ms
/st.gif?cl=…
(network.bazaarvoice.com)
0 KiB
0 ms
/id.json?_=z1ijij&callback=_bvajsonp1
(network.bazaarvoice.com)
0 KiB
0 ms
/a.gif?loadId=…
(network-eu-a.bazaarvoice.com)
0 KiB
0 ms
TagCommander
tag-manager
121 KiB
29 ms
/3692/tc_CoursesU_20.js
(cdn.tagcommander.com)
48 KiB
29 ms
/3692/tc_CoursesU_21.js
(cdn.tagcommander.com)
73 KiB
0 ms
Trustcommander
consent-provider
26 KiB
1 ms
…3692/privacy_v2_26.js
(cdn.trustcommander.net)
26 KiB
1 ms
/privacy-consent?site=3692
(privacy.trustcommander.net)
0 KiB
0 ms
Other Google APIs/SDKs
utility
177 KiB
0 ms
…8.7/noSupplie….png
(storage.googleapis.com)
118 KiB
0 ms
…prod/config.json
(storage.googleapis.com)
49 KiB
0 ms
…icons/ArrowLeft_dark.svg
(storage.googleapis.com)
2 KiB
0 ms
…icons/arrow-right.svg
(storage.googleapis.com)
2 KiB
0 ms
…icons/Cross_primary.svg
(storage.googleapis.com)
1 KiB
0 ms
…icons/plus-neutral-black.svg
(storage.googleapis.com)
1 KiB
0 ms
…icons/chevron-down-primary.svg
(storage.googleapis.com)
1 KiB
0 ms
…icons/plus-primary.svg
(storage.googleapis.com)
1 KiB
0 ms
…icons/minus-primary.svg
(storage.googleapis.com)
1 KiB
0 ms
…8.7/BulletPoint.svg
(storage.googleapis.com)
1 KiB
0 ms
luckycart.com
84 KiB
0 ms
/systeme-u/luckyclient.min.js
(integration.luckycart.com)
83 KiB
0 ms
0 KiB
0 ms
Cloudflare CDN
cdn
49 KiB
0 ms
…3.4.29/vue.global.prod.min.js
(cdnjs.cloudflare.com)
49 KiB
0 ms
Salesforce Commerce Cloud
hosting
42 KiB
0 ms
…v2/gretel.min.js
(cdn.cquotient.com)
42 KiB
0 ms
Google Fonts
cdn
34 KiB
0 ms
…v34/BngMUXZYT….woff2
(fonts.gstatic.com)
34 KiB
0 ms
magasins-u.com
12 KiB
0 ms
…logos/logo-u-desktop.svg
(www.magasins-u.com)
6 KiB
0 ms
….well-known/openid-configuration
(moncompte.magasins-u.com)
5 KiB
0 ms
…oauth2/authorize?client_id=…
(moncompte.magasins-u.com)
1 KiB
0 ms
miam.tech
11 KiB
0 ms
3 KiB
0 ms
3 KiB
0 ms
3 KiB
0 ms
…users/authless
(api.miam.tech)
2 KiB
0 ms
Serve images in next-gen formats Potential savings of 115 KiB
Image formats like WebP and AVIF often provide better compression than PNG or JPEG, which means faster downloads and less data consumption. Learn more about modern image formats.LCPFCP
URL
Resource Size
Potential Savings
Other Google APIs/SDKs
utility
117.1 KiB
102.6 KiB
…8.7/noSupplie….png
(storage.googleapis.com)
117.1 KiB
102.6 KiB
coursesu.com
1st party
38.6 KiB
12.2 KiB
main#main > div#quick-content > div.ab-prehome-row > div.ab-prehome-banner-background
<div class="ab-prehome-banner-background mobile-banner" style="background-image: url(&quot;https://www.coursesu.com/dw/image/v2/BBQX_PRD/on/de…&quot;);">
38.6 KiB
12.2 KiB
Enable text compression Potential savings of 100 KiB
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. Learn more about text compression.LCPFCP
URL
Transfer Size
Potential Savings
luckycart.com
82.3 KiB
56.4 KiB
/systeme-u/luckyclient.min.js
(integration.luckycart.com)
82.3 KiB
56.4 KiB
Other Google APIs/SDKs
utility
47.9 KiB
38.8 KiB
…prod/config.json
(storage.googleapis.com)
47.9 KiB
38.8 KiB
magasins-u.com
4.2 KiB
3.2 KiB
….well-known/openid-configuration
(moncompte.magasins-u.com)
4.2 KiB
3.2 KiB
miam.tech
1.8 KiB
1.4 KiB
1.8 KiB
1.4 KiB
Serve static assets with an efficient cache policy 83 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
coursesu.com
1st party
1,597 KiB
…prehome/search-icon.svg
(www.coursesu.com)
1m 8s
1 KiB
2m 53s
46 KiB
…arrows/arrow-simple.svg
(www.coursesu.com)
4m 23s
1 KiB
4m 33s
47 KiB
4m 39s
46 KiB
4m 44s
15 KiB
4m 54s
14 KiB
5m
46 KiB
5m 1s
47 KiB
5m 1s
15 KiB
5m 1s
9 KiB
5m 1s
6 KiB
5m 1s
1 KiB
…prehome/arrow-yellow.svg
(www.coursesu.com)
5m 1s
1 KiB
5m 1s
1 KiB
/tags.js
(dd.coursesu.com)
1h
43 KiB
29d 8h 49m 34s
5 KiB
29d 16h 33m 31s
12 KiB
29d 17h 56m 21s
16 KiB
29d 20h 53m 31s
9 KiB
29d 21h 45m 47s
10 KiB
29d 22h 23m 14s
7 KiB
29d 23h 31m 2s
39 KiB
29d 23h 34m 45s
3 KiB
29d 23h 59m 14s
9 KiB
…css/fonts.css
(www.coursesu.com)
29d 23h 59m 46s
1 KiB
…js/partners.js
(www.coursesu.com)
29d 23h 59m 56s
75 KiB
…js/vendors.js
(www.coursesu.com)
29d 23h 59m 58s
73 KiB
29d 23h 59m 58s
72 KiB
…espaceclient/auth.js
(www.coursesu.com)
29d 23h 59m 58s
2 KiB
…css/fakearkonly.css
(www.coursesu.com)
29d 23h 59m 59s
3 KiB
29d 23h 59m 59s
1 KiB
30d
462 KiB
30d
103 KiB
…js/prehome.js
(www.coursesu.com)
30d
85 KiB
30d
52 KiB
30d
37 KiB
30d
32 KiB
30d
28 KiB
30d
14 KiB
…css/prehome.css
(www.coursesu.com)
30d
14 KiB
30d
12 KiB
30d
12 KiB
…css/mainab.css
(www.coursesu.com)
30d
10 KiB
30d
9 KiB
30d
8 KiB
30d
8 KiB
30d
7 KiB
…css/footer.css
(www.coursesu.com)
30d
5 KiB
30d
3 KiB
30d
3 KiB
…jscript/dwac-21.7.js
(www.coursesu.com)
30d
2 KiB
…jscript/dwac-21.7.js
(www.coursesu.com)
30d
2 KiB
30d
2 KiB
…prehome/drive-icon.svg
(www.coursesu.com)
30d
2 KiB
30d
2 KiB
30d
2 KiB
30d
2 KiB
…folder/more-circle.svg
(www.coursesu.com)
30d
1 KiB
30d
1 KiB
…prehome/yellow-line.svg
(www.coursesu.com)
30d
1 KiB
30d
1 KiB
JSDelivr CDN
cdn
260 KiB
7d
222 KiB
7d
32 KiB
7d
6 KiB
Other Google APIs/SDKs
utility
128 KiB
…8.7/noSupplie….png
(storage.googleapis.com)
1h
118 KiB
…icons/ArrowLeft_dark.svg
(storage.googleapis.com)
1h
2 KiB
…icons/arrow-right.svg
(storage.googleapis.com)
1h
2 KiB
…icons/Cross_primary.svg
(storage.googleapis.com)
1h
1 KiB
…icons/plus-neutral-black.svg
(storage.googleapis.com)
1h
1 KiB
…icons/chevron-down-primary.svg
(storage.googleapis.com)
1h
1 KiB
…icons/plus-primary.svg
(storage.googleapis.com)
1h
1 KiB
…icons/minus-primary.svg
(storage.googleapis.com)
1h
1 KiB
…8.7/BulletPoint.svg
(storage.googleapis.com)
1h
1 KiB
Bazaarvoice
analytics
73 KiB
…fr_FR/bv.js
(apps.bazaarvoice.com)
5m
29 KiB
…fr_FR/api-config.js
(apps.bazaarvoice.com)
5m
2 KiB
…fr_FR/seller_ratings-config.js
(apps.bazaarvoice.com)
5m
1 KiB
…1/seller.min.js
(srd.bazaarvoice.com)
10m
15 KiB
/analytics/bv-analytics.js
(apps.bazaarvoice.com)
7d
13 KiB
…3/bv-analytics.js
(analytics-static.ugc.bazaarvoice.com)
7d
13 KiB
Salesforce Commerce Cloud
hosting
42 KiB
…v2/gretel.min.js
(cdn.cquotient.com)
1h
21 KiB
…v2/gretel.min.js
(cdn.cquotient.com)
1h
21 KiB
magasins-u.com
6 KiB
…logos/logo-u-desktop.svg
(www.magasins-u.com)
1d
6 KiB
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
coursesu.com
1st party
63.3 KiB
24.0 KiB
Viandes, poissons
<img class="category-image" width="80" height="80" loading="lazy" src="/on/demandware.static/-/Sites-DigitalU-Library/default/dwb964d651/pictos-n…" alt="Viandes, poissons" aria-hidden="true">
15.5 KiB
5.9 KiB
Pains, Viennoiseries et Pâtisseries
<img class="category-image" width="80" height="80" loading="lazy" src="/on/demandware.static/-/Sites-DigitalU-Library/default/dw1e909855/pictos-n…" alt="Pains, Viennoiseries et Pâtisseries" aria-hidden="true">
13.6 KiB
5.2 KiB
Nutrition et régimes alimentaires
<img class="category-image" width="80" height="80" loading="lazy" src="/on/demandware.static/-/Sites-DigitalU-Library/default/dw250d3832/pictos-n…" alt="Nutrition et régimes alimentaires" aria-hidden="true">
11.8 KiB
4.5 KiB
Charcuterie, traiteur
<img class="category-image" width="80" height="80" loading="lazy" src="/on/demandware.static/-/Sites-DigitalU-Library/default/dw9ed81dce/pictos-n…" alt="Charcuterie, traiteur" aria-hidden="true">
11.3 KiB
4.3 KiB
Epicerie sucrée
<img class="category-image" width="80" height="80" loading="lazy" src="/on/demandware.static/-/Sites-DigitalU-Library/default/dwbda35221/pictos-n…" alt="Epicerie sucrée" aria-hidden="true">
11.0 KiB
4.2 KiB
Defer offscreen images Potential savings of 18 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
coursesu.com
1st party
14.2 KiB
14.2 KiB
div.footer-app-block > div.footer-details-content > a.footer-app-link > span.store-app-mobile
<span class="store-app-mobile">
8.6 KiB
8.6 KiB
div.footer-app-block > div.footer-details-content > a.footer-app-link > span.store-play-mobile
<span class="store-play-mobile">
5.5 KiB
5.5 KiB
Unattributable
4.1 KiB
4.1 KiB
Bazaarvoice
<img class="bv_bvBranding__logo" alt="Bazaarvoice" src="data:image/svg+xml;base64,PD94bWwgdmVyc2lvbj0iMS4wIiBlbmNvZGluZz0iVVRGLTgi…">
4.1 KiB
4.1 KiB
Avoid serving legacy JavaScript to modern browsers Potential savings of 11 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. However, many aren't necessary for modern browsers. For your bundled JavaScript, adopt a modern script deployment strategy using module/nomodule feature detection to reduce the amount of code shipped to modern browsers, while retaining support for legacy browsers. Learn how to serve modern JavaScriptLCPFCP
URL
Potential Savings
Salesforce Commerce Cloud
hosting
10.5 KiB
…v2/gretel.min.js
(cdn.cquotient.com)
10.5 KiB
…v2/gretel.min.js:1:8822
(cdn.cquotient.com)
Date.prototype.toJSON
…v2/gretel.min.js:1:50385
(cdn.cquotient.com)
Array.prototype.filter
…v2/gretel.min.js:1:50758
(cdn.cquotient.com)
Array.from
…v2/gretel.min.js:1:55268
(cdn.cquotient.com)
@babel/plugin-transform-regenerator
coursesu.com
1st party
0.8 KiB
0.2 KiB
@babel/plugin-transform-classes
0.2 KiB
@babel/plugin-transform-classes
0.2 KiB
@babel/plugin-transform-classes
…js/prehome.js
(www.coursesu.com)
0.0 KiB
…js/prehome.js:2:285528
(www.coursesu.com)
@babel/plugin-transform-classes
…js/partners.js
(www.coursesu.com)
0.0 KiB
…js/partners.js:2:38127
(www.coursesu.com)
@babel/plugin-transform-classes
JSDelivr CDN
cdn
0.2 KiB
0.2 KiB
@babel/plugin-transform-classes
@babel/plugin-transform-regenerator
Bazaarvoice
analytics
0.1 KiB
…api/api-0.8.2.js
(apps.bazaarvoice.com)
0.1 KiB
…api/api-0.8.2.js:2:20659
(apps.bazaarvoice.com)
@babel/plugin-transform-classes
TagCommander
tag-manager
0.0 KiB
/3692/tc_CoursesU_21.js
(cdn.tagcommander.com)
0.0 KiB
/3692/tc_CoursesU_21.js:296:2302
(cdn.tagcommander.com)
@babel/plugin-transform-classes
Reduce unused CSS Potential savings of 43 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
Unattributable
32.2 KiB
31.9 KiB
:root .cors-overlay-container{background-color:transparent !important;align-items:start !important} …
32.2 KiB
31.9 KiB
coursesu.com
1st party
13.0 KiB
10.7 KiB
…css/prehome.css
(www.coursesu.com)
13.0 KiB
10.7 KiB
Avoid long main-thread tasks 8 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
coursesu.com
1st party
320 ms
6,901 ms
120 ms
18,621 ms
74 ms
/drive/home
(www.coursesu.com)
952 ms
64 ms
/tags.js
(dd.coursesu.com)
3,045 ms
62 ms
Bazaarvoice
analytics
275 ms
…fr_FR/bv.js
(apps.bazaarvoice.com)
9,751 ms
128 ms
/analytics/bv-analytics.js
(apps.bazaarvoice.com)
10,929 ms
90 ms
…1/seller.min.js
(srd.bazaarvoice.com)
11,680 ms
57 ms
JSDelivr CDN
cdn
224 ms
14,111 ms
224 ms
User Timing marks and measures 54 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
BV_PERF_MARK_bv_loader_register_api
Measure
0.00 ms
1,466.50 ms
BV_PERF_MARK_bv_loader_register_inline_ratings
Measure
0.00 ms
1,466.80 ms
BV_PERF_MARK_bv_loader_register_inpage_submission
Measure
0.00 ms
1,467.00 ms
BV_PERF_MARK_bv_loader_register_rating_summary
Measure
0.00 ms
1,467.30 ms
BV_PERF_MARK_bv_loader_register_ratings
Measure
0.00 ms
1,467.40 ms
BV_PERF_MARK_bv_loader_register_review-highlights
Measure
0.00 ms
1,467.50 ms
BV_PERF_MARK_bv_loader_register_review_highlights
Measure
0.00 ms
1,467.70 ms
BV_PERF_MARK_bv_loader_register_reviews
Measure
0.00 ms
1,467.80 ms
BV_PERF_MARK_bv_loader_register_seller_ratings
Measure
0.00 ms
1,468.00 ms
BV_PERF_MARK_bv_loader_register_swat-submission
Measure
0.00 ms
1,468.40 ms
BV_PERF_MARK_bv_loader_register_swat_container
Measure
0.00 ms
1,468.50 ms
BV_PERF_MARK_bv_loader
Measure
0.00 ms
1,471.30 ms
BV_PERF_MARK_bv_loader_preconnectMark
Measure
0.00 ms
1,472.10 ms
BV_PERF_MARK_bv_loader_app_seller_ratings_load_config
Measure
0.00 ms
1,999.90 ms
BV_PERF_MARK_bv_loader_app_api_load_config
Measure
0.00 ms
2,001.10 ms
BV_PERF_MARK_bv_loader_app_api_load
Measure
0.00 ms
2,011.00 ms
BV_PERF_MARK_bv_loader_app_seller_ratings_load
Measure
0.00 ms
2,099.10 ms
BV_PERF_MARK_bv_loader_start
Mark
1,463.64 ms
BV_PERF_MARK_bv_loader_register_api_start
Mark
1,464.68 ms
BV_PERF_MARK_bv_loader_app_api_load_start
Mark
1,465.42 ms
BV_PERF_MARK_bv_loader_app_api_load_config_start
Mark
1,465.94 ms
BV_PERF_MARK_bv_loader_register_api_end
Mark
1,466.29 ms
BV_PERF_MARK_bv_loader_register_inline_ratings_start
Mark
1,466.59 ms
BV_PERF_MARK_bv_loader_register_inline_ratings_end
Mark
1,466.73 ms
BV_PERF_MARK_bv_loader_register_inpage_submission_start
Mark
1,466.83 ms
BV_PERF_MARK_bv_loader_register_inpage_submission_end
Mark
1,466.93 ms
BV_PERF_MARK_bv_loader_register_rating_summary_start
Mark
1,467.03 ms
BV_PERF_MARK_bv_loader_register_rating_summary_end
Mark
1,467.12 ms
BV_PERF_MARK_bv_loader_register_ratings_start
Mark
1,467.19 ms
BV_PERF_MARK_bv_loader_register_ratings_end
Mark
1,467.26 ms
BV_PERF_MARK_bv_loader_register_review-highlights_start
Mark
1,467.34 ms
BV_PERF_MARK_bv_loader_register_review-highlights_end
Mark
1,467.42 ms
BV_PERF_MARK_bv_loader_register_review_highlights_start
Mark
1,467.49 ms
BV_PERF_MARK_bv_loader_register_review_highlights_end
Mark
1,467.56 ms
BV_PERF_MARK_bv_loader_register_reviews_start
Mark
1,467.65 ms
BV_PERF_MARK_bv_loader_register_reviews_end
Mark
1,467.75 ms
BV_PERF_MARK_bv_loader_register_seller_ratings_start
Mark
1,467.84 ms
BV_PERF_MARK_bv_loader_register_seller_ratings_end
Mark
1,467.93 ms
BV_PERF_MARK_bv_loader_register_swat-submission_start
Mark
1,468.19 ms
BV_PERF_MARK_bv_loader_register_swat-submission_end
Mark
1,468.28 ms
BV_PERF_MARK_bv_loader_register_swat_container_start
Mark
1,468.37 ms
BV_PERF_MARK_bv_loader_register_swat_container_end
Mark
1,468.44 ms
BV_PERF_MARK_bv_loader_app_seller_ratings_load_start
Mark
1,469.74 ms
BV_PERF_MARK_bv_loader_app_seller_ratings_load_config_start
Mark
1,470.05 ms
BV_PERF_MARK_bv_loader_end
Mark
1,471.18 ms
BV_PERF_MARK_bv_loader_preconnectMark_start
Mark
1,471.62 ms
BV_PERF_MARK_bv_loader_preconnectMark_end
Mark
1,472.00 ms
bv_loader_configure_seller_ratings_start
Mark
1,999.16 ms
BV_PERF_MARK_bv_loader_app_seller_ratings_load_config_end
Mark
1,999.76 ms
bv_loader_configure_api_start
Mark
2,000.59 ms
BV_PERF_MARK_bv_loader_app_api_load_config_end
Mark
2,000.92 ms
BV_PERF_MARK_bv_loader_app_api_load_end
Mark
2,010.80 ms
BV_PERF_MARK_bv_loader_app_seller_ratings_bvShow_start
Mark
2,093.91 ms
BV_PERF_MARK_bv_loader_app_seller_ratings_load_end
Mark
2,098.60 ms
Avoid chaining critical requests 12 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: 1,597.411 ms
Initial Navigation
/drive/home
(www.coursesu.com)
…3.4.29/vue.global.prod.min.js
(cdnjs.cloudflare.com)
- 36.063 ms, 48.54 KiB
- 261.325 ms, 462.21 KiB
- 200.053 ms, 72.16 KiB
…espaceclient/auth.js
(www.coursesu.com)
- 158.269 ms, 2.11 KiB
…v34/BngMUXZYT….woff2
(fonts.gstatic.com)
- 11.332 ms, 34.32 KiB
…css/mainab.css
(www.coursesu.com)
- 144.021 ms, 9.50 KiB
- 146.974 ms, 1.15 KiB
…css/fakearkonly.css
(www.coursesu.com)
- 218.102 ms, 3.39 KiB
…css/footer.css
(www.coursesu.com)
- 151.083 ms, 4.58 KiB
…css/prehome.css
(www.coursesu.com)
- 213.814 ms, 13.54 KiB
- 129.158 ms, 0.70 KiB
/3692/tc_CoursesU_20.js
(cdn.tagcommander.com)
- 25.544 ms, 6.28 KiB
More information about the performance of your application. These numbers don't directly affect the Performance score.
Passed audits (21)
Show Hide
Minify CSS
Minifying CSS files can reduce network payload sizes. Learn how to minify CSS.LCPFCP
Minify JavaScript
Minifying JavaScript files can reduce payload sizes and script parse time. Learn how to minify JavaScript.LCPFCP
Efficiently encode images
Optimized images load faster and consume less cellular data. Learn how to efficiently encode images.LCPFCP
Preconnect to required origins
Warnings: A `<link rel=preconnect>` was found for "https://api.bazaarvoice.com" but was not used by the browser. Only use `preconnect` for important origins that the page will certainly request.
Consider adding preconnect or dns-prefetch resource hints to establish early connections to important third-party origins. Learn how to preconnect to required origins.LCPFCP
Initial server response time was short Root document took 410 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
coursesu.com
1st party
410 ms
/drive/home
(www.coursesu.com)
410 ms
Avoid multiple page redirects
Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.LCPFCP
Use video formats for animated content
Large GIFs are inefficient for delivering animated content. Consider using MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF to save network bytes. Learn more about efficient video formatsLCPFCP
Remove duplicate modules in JavaScript bundles
Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity. LCPFCP
Preload Largest Contentful Paint image
If the LCP element is dynamically added to the page, you should preload the image in order to improve LCP. Learn more about preloading LCP elements.LCP
Avoids enormous network payloads Total size was 2,550 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
coursesu.com
1st party
870.8 KiB
462.2 KiB
102.9 KiB
…js/prehome.js
(www.coursesu.com)
85.0 KiB
…js/partners.js
(www.coursesu.com)
75.3 KiB
…js/vendors.js
(www.coursesu.com)
73.3 KiB
72.2 KiB
JSDelivr CDN
cdn
221.7 KiB
221.7 KiB
Other Google APIs/SDKs
utility
117.9 KiB
…8.7/noSupplie….png
(storage.googleapis.com)
117.9 KiB
luckycart.com
83.1 KiB
/systeme-u/luckyclient.min.js
(integration.luckycart.com)
83.1 KiB
TagCommander
tag-manager
73.1 KiB
/3692/tc_CoursesU_21.js
(cdn.tagcommander.com)
73.1 KiB
Avoids an excessive DOM size 703 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
703
Maximum DOM Depth
3,9 sur 5 étoiles.
<span>
16
Maximum Child Elements
body.tc-modal-open
<body class="tc-modal-open android-device" style="">
21
JavaScript execution time 1.2 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to reduce Javascript execution time.TBT
URL
Total CPU Time
Script Evaluation
Script Parse
coursesu.com
1st party
934 ms
480 ms
53 ms
/drive/home
(www.coursesu.com)
376 ms
13 ms
8 ms
/tags.js
(dd.coursesu.com)
231 ms
209 ms
3 ms
…js/vendors.js
(www.coursesu.com)
127 ms
98 ms
5 ms
126 ms
97 ms
27 ms
74 ms
62 ms
10 ms
Unattributable
368 ms
28 ms
0 ms
Unattributable
368 ms
28 ms
0 ms
JSDelivr CDN
cdn
331 ms
289 ms
27 ms
226 ms
200 ms
23 ms
105 ms
89 ms
4 ms
Bazaarvoice
analytics
266 ms
169 ms
4 ms
…1/seller.min.js
(srd.bazaarvoice.com)
113 ms
27 ms
1 ms
/analytics/bv-analytics.js
(apps.bazaarvoice.com)
94 ms
88 ms
1 ms
…fr_FR/bv.js
(apps.bazaarvoice.com)
59 ms
53 ms
2 ms
TagCommander
tag-manager
132 ms
46 ms
4 ms
/3692/tc_CoursesU_20.js
(cdn.tagcommander.com)
132 ms
46 ms
4 ms
Salesforce Commerce Cloud
hosting
60 ms
49 ms
2 ms
…v2/gretel.min.js
(cdn.cquotient.com)
60 ms
49 ms
2 ms
All text remains visible during webfont loads
Leverage the font-display CSS feature to ensure text is user-visible while webfonts are loading. Learn more about font-display.
Lazy load third-party resources with facades
Some third-party embeds can be lazy loaded. Consider replacing them with a facade until they are required. Learn how to defer third-parties with a facade.TBT
Largest Contentful Paint image was not lazily loaded
Above-the-fold images that are lazily loaded render later in the page lifecycle, which can delay the largest contentful paint. Learn more about optimal lazy loading.LCP
Element
main#main > div#quick-content > div.ab-prehome-row > div.ab-prehome-banner-background
<div class="ab-prehome-banner-background mobile-banner" style="background-image: url(&quot;https://www.coursesu.com/dw/image/v2/BBQX_PRD/on/de…&quot;);">
Avoid large layout shifts
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
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
Image elements have explicit width and height
Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensionsCLS
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
Elements with role="dialog" or role="alertdialog" do not have accessible names.
ARIA dialog elements without accessible names may prevent screen readers users from discerning the purpose of these elements. Learn how to make ARIA dialog elements more accessible.
Failing Elements
La Coopérative U et ses partenaires utilisent des cookies afin de vous offrir l…
<div id="popin_tc_privacy" class="tc-reset-css tc-privacy-banner tc-privacy-popin tc-privacy-mid" aria-describedby="description" role="dialog" aria-modal="true" style="top: 128px; left: 46px;">
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
These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.
Additional items to manually check (10)
Show Hide
Interactive controls are keyboard focusable
Custom interactive controls are keyboard focusable and display a focus indicator. Learn how to make custom controls focusable.
Interactive elements indicate their purpose and state
Interactive elements, such as links and buttons, should indicate their state and be distinguishable from non-interactive elements. Learn how to decorate interactive elements with affordance hints.
The page has a logical tab order
Tabbing through the page follows the visual layout. Users cannot focus elements that are offscreen. Learn more about logical tab ordering.
Visual order on the page follows DOM order
DOM order matches the visual order, improving navigation for assistive technology. Learn more about DOM and visual ordering.
User focus is not accidentally trapped in a region
A user can tab into and out of any control or region without accidentally trapping their focus. Learn how to avoid focus traps.
The user's focus is directed to new content added to the page
If new content, such as a dialog, is added to the page, the user's focus is directed to it. Learn how to direct focus to new content.
HTML5 landmark elements are used to improve navigation
Landmark elements (<main>, <nav>, etc.) are used to improve the keyboard navigation of the page for assistive technology. Learn more about landmark elements.
Offscreen content is hidden from assistive technology
Offscreen content is hidden with display: none or aria-hidden=true. Learn how to properly hide offscreen content.
Custom controls have associated labels
Custom interactive controls have associated labels, provided by aria-label or aria-labelledby. Learn more about custom controls and labels.
Custom controls have ARIA roles
Custom interactive controls have appropriate ARIA roles. Learn how to add roles to custom controls.
These items address areas which an automated testing tool cannot cover. Learn more in our guide on conducting an accessibility review.
Passed audits (30)
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.
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.
[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.
Image elements have [alt] attributes
Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the alt attribute.
[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.
[aria-hidden="true"] elements do not contain focusable descendents
Focusable descendents within an [aria-hidden="true"] element prevent those interactive elements from being available to users of assistive technologies like screen readers. Learn how aria-hidden affects focusable elements.
Elements use only permitted ARIA attributes
Using ARIA attributes in roles where they are prohibited can mean that important information is not communicated to users of assistive technologies. Learn more about prohibited ARIA roles.
[role] values are valid
ARIA roles must have valid values in order to perform their intended accessibility functions. Learn more about valid ARIA roles.
Background and foreground colors have a sufficient contrast ratio
Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.
Document has a <title> element
The title gives screen reader users an overview of the page, and search engine users rely on it heavily to determine if a page is relevant to their search. Learn more about document titles.
<html> element has a [lang] attribute
If a page doesn't specify a lang attribute, a screen reader assumes that the page is in the default language that the user chose when setting up the screen reader. If the page isn't actually in the default language, then the screen reader might not announce the page's text correctly. Learn more about the lang attribute.
<html> element has a valid value for its [lang] attribute
Specifying a valid BCP 47 language helps screen readers announce text properly. Learn how to use the lang attribute.
Form elements have associated labels
Labels ensure that form controls are announced properly by assistive technologies, like screen readers. Learn more about form element labels.
Lists contain only <li> elements and script supporting elements (<script> and <template>).
Screen readers have a specific way of announcing lists. Ensuring proper list structure aids screen reader output. Learn more about proper list structure.
List items (<li>) are contained within <ul>, <ol> or <menu> parent elements
Screen readers require list items (<li>) to be contained within a parent <ul>, <ol> or <menu> to be announced properly. Learn more about proper list structure.
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.
Touch targets have sufficient size and spacing.
Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.
[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.
Uses ARIA roles only on compatible elements
Many HTML elements can only be assigned certain ARIA roles. Using ARIA roles where they are not allowed can interfere with the accessibility of the web page. Learn more about ARIA roles.
Deprecated ARIA roles were not used
Deprecated ARIA roles may not be processed correctly by assistive technology. Learn more about deprecated ARIA roles.
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 (25)
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 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 1 warning found
Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs.
Deprecation / Warning
Source
coursesu.com
1st party
`<source src>` with a `<picture>` parent is invalid and therefore ignored. Please use `<source srcset>` instead.
/drive/home:2987:-1
(www.coursesu.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
JSDelivr CDN
cdn
[Mealz] could not find coursesu basket element to listen for change, sync is broken
Detected JavaScript libraries
All front-end JavaScript libraries detected on the page. Learn more about this JavaScript library detection diagnostic audit.
Name
Version
jQuery
3.7.1
jQuery UI
1.13.3
Angular
11.2.14
Vue
3.4.29
core-js
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
coursesu.com
1st party
Large JavaScript file is missing a source map
User Experience
Document doesn't use legible font sizes 42.78% 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
#tc_text_body
56.69%
10px
Legible text
42.78%
≥ 12px
coursesu.com
1st party
…css/mainab.css:1:4622
(www.coursesu.com)
a
0.54%
10px
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
`script-src` directive is missing. This can allow the execution of unsafe scripts.
script-src
High
Missing `object-src` allows the injection of plugins that execute unsafe scripts. Consider setting `object-src` to `'none'` if you can.
object-src
High
Use a strong HSTS policy
Deployment of the HSTS header significantly reduces the risk of downgrading HTTP connections and eavesdropping attacks. A rollout in stages, starting with a low max-age is recommended. Learn more about using a strong HSTS policy.
Description
Directive
Severity
No `preload` directive found
preload
Medium
Ensure proper origin isolation with COOP
The Cross-Origin-Opener-Policy (COOP) can be used to isolate the top-level window from other documents such as pop-ups. Learn more about deploying the COOP header.
Description
Directive
Severity
No COOP header found
High
Passed audits (11)
Show Hide
Uses HTTPS
All sites should be protected with HTTPS, even ones that don't handle sensitive data. This includes avoiding mixed content, where some resources are loaded over HTTP despite the initial request being served over HTTPS. HTTPS prevents intruders from tampering with or passively listening in on the communications between your app and your users, and is a prerequisite for HTTP/2 and many new web platform APIs. Learn more about HTTPS.
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.
Mitigate clickjacking with XFO or CSP
The X-Frame-Options (XFO) header or the frame-ancestors directive in the Content-Security-Policy (CSP) header control where a page can be embedded. These can mitigate clickjacking attacks by blocking some or all sites from embedding the page. Learn more about mitigating clickjacking.
These checks ensure that your page is following basic search engine optimization advice. There are many additional factors Lighthouse does not score here that may affect your search ranking, including performance on Core Web Vitals. Learn more about Google Search Essentials.
Crawling and Indexing
robots.txt is not valid 1 error found
If your robots.txt file is malformed, crawlers may not be able to understand how you want your website to be crawled or indexed. Learn more about robots.txt.
Line #
Content
Error
52
Disallow: /*$REORDER_PAGE_URL$*
"$" should only be used at the end of the pattern
To appear in search results, crawlers need access to your app.
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 (9)
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
Image elements have [alt] attributes
Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the alt attribute.
Document has a valid hreflang
hreflang links tell search engines what version of a page they should list in search results for a given language or region. Learn more about hreflang.
Document has a valid rel=canonical
Canonical links suggest which URL to show in search results. Learn more about canonical links.
Discover what your real users are experiencing
Core Web Vitals Assessment: 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)
87 ms
Page LoadsGood (≤ 200 ms)91%Needs Improvement (200 ms - 500 ms)6%Poor (> 500 ms)3%75th Percentile - 87 msCore Web Vital
Cumulative Layout Shift (CLS)
0.03
Page LoadsGood (≤ 0.1)99%Needs Improvement (0.1 - 0.25)1%Poor (> 0.25)0%75th Percentile - 0.03Core Web Vital
Other Notable Metrics
First Contentful Paint (FCP)
1.5 s
Page LoadsGood (≤ 1.8 s)82%Needs Improvement (1.8 s - 3 s)11%Poor (> 3 s)7%75th Percentile - 1.5 s 
Time to First Byte (TTFB)
0.9 s
Page LoadsGood (≤ 0.8 s)72%Needs Improvement (0.8 s - 1.8 s)22%Poor (> 1.8 s)6%75th Percentile - 0.9 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)
4.8 s
Page LoadsGood (≤ 2.5 s)26%Needs Improvement (2.5 s - 4 s)35%Poor (> 4 s)39%75th Percentile - 4.8 sCore Web Vital
Interaction to Next Paint (INP)
261 ms
Page LoadsGood (≤ 200 ms)66%Needs Improvement (200 ms - 500 ms)21%Poor (> 500 ms)13%75th Percentile - 261 msCore Web Vital
Cumulative Layout Shift (CLS)
0.14
Page LoadsGood (≤ 0.1)70%Needs Improvement (0.1 - 0.25)17%Poor (> 0.25)14%75th Percentile - 0.14Core Web Vital
Other Notable Metrics
First Contentful Paint (FCP)
4 s
Page LoadsGood (≤ 1.8 s)18%Needs Improvement (1.8 s - 3 s)32%Poor (> 3 s)50%75th Percentile - 4 s 
Time to First Byte (TTFB)
3.5 s
Page LoadsGood (≤ 0.8 s)12%Needs Improvement (0.8 s - 1.8 s)17%Poor (> 1.8 s)71%75th Percentile - 3.5 sExperimental
Latest 28-day collection period
Various desktop devicesMany samples (Chrome UX Report)Full visit durationsVarious network connectionsAll Chrome versions
Diagnose performance issues
84 FCP+8LCP+14TBT+29CLS+25SI+8 Performance
Values are estimated and may vary. The performance score is calculated directly from these metrics.See calculator.
0–49 50–89 90–100
Final Screenshot
Metrics
First Contentful Paint
1.1 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more about the First Contentful Paint metric.
Largest Contentful Paint
2.2 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
100 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.008
Cumulative Layout Shift measures the movement of visible elements within the viewport. Learn more about the Cumulative Layout Shift metric.
Speed Index
1.7 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more about the Speed Index metric.
  • Captured at Mar 11, 2025, 6:00 PM UTC
  • Emulated Desktop with Lighthouse 12.4.0
    Unthrottled CPU/Memory Power: 475 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.141 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
Largest Contentful Paint element 2,220 ms
This is the largest contentful element painted within the viewport. Learn more about the Largest Contentful Paint elementLCP
Element
main#main > div#quick-content > div.ab-prehome-row > div.ab-prehome-banner-background
<div class="ab-prehome-banner-background desktop-banner" style="background-image: url(&quot;https://www.coursesu.com/dw/image/v2/BBQX_PRD/on/de…&quot;);">
Phase
% of LCP
Timing
TTFB
7%
160 ms
Load Delay
69%
1,530 ms
Load Time
9%
190 ms
Render Delay
16%
350 ms
Reduce unused JavaScript Potential savings of 906 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
coursesu.com
1st party
866.5 KiB
662.7 KiB
460.6 KiB
363.6 KiB
102.4 KiB
71.8 KiB
…js/prehome.js
(www.coursesu.com)
84.4 KiB
70.8 KiB
…js/partners.js
(www.coursesu.com)
74.7 KiB
63.2 KiB
71.6 KiB
48.8 KiB
…js/vendors.js
(www.coursesu.com)
72.8 KiB
44.6 KiB
JSDelivr CDN
cdn
220.9 KiB
111.7 KiB
220.9 KiB
111.7 KiB
luckycart.com
82.3 KiB
53.2 KiB
/systeme-u/luckyclient.min.js
(integration.luckycart.com)
82.3 KiB
53.2 KiB
Cloudflare CDN
cdn
47.5 KiB
41.6 KiB
…3.4.29/vue.global.prod.min.js
(cdnjs.cloudflare.com)
47.5 KiB
41.6 KiB
TagCommander
tag-manager
72.2 KiB
37.0 KiB
/3692/tc_CoursesU_21.js
(cdn.tagcommander.com)
72.2 KiB
37.0 KiB
Eliminate render-blocking resources Potential savings of 780 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles. Learn how to eliminate render-blocking resources.LCPFCP
URL
Transfer Size
Potential Savings
coursesu.com
1st party
462.2 KiB
640 ms
462.2 KiB
640 ms
Cloudflare CDN
cdn
48.5 KiB
320 ms
…3.4.29/vue.global.prod.min.js
(cdnjs.cloudflare.com)
48.5 KiB
320 ms
TagCommander
tag-manager
48.0 KiB
320 ms
/3692/tc_CoursesU_20.js
(cdn.tagcommander.com)
48.0 KiB
320 ms
Serve images in next-gen formats Potential savings of 103 KiB
Image formats like WebP and AVIF often provide better compression than PNG or JPEG, which means faster downloads and less data consumption. Learn more about modern image formats.LCPFCP
URL
Resource Size
Potential Savings
Other Google APIs/SDKs
utility
117.1 KiB
102.6 KiB
…8.7/noSupplie….png
(storage.googleapis.com)
117.1 KiB
102.6 KiB
Enable text compression Potential savings of 100 KiB
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. Learn more about text compression.LCPFCP
URL
Transfer Size
Potential Savings
luckycart.com
82.3 KiB
56.4 KiB
/systeme-u/luckyclient.min.js
(integration.luckycart.com)
82.3 KiB
56.4 KiB
Other Google APIs/SDKs
utility
47.9 KiB
38.8 KiB
…prod/config.json
(storage.googleapis.com)
47.9 KiB
38.8 KiB
magasins-u.com
4.2 KiB
3.2 KiB
….well-known/openid-configuration
(moncompte.magasins-u.com)
4.2 KiB
3.2 KiB
miam.tech
1.8 KiB
1.4 KiB
1.8 KiB
1.4 KiB
Serve static assets with an efficient cache policy 91 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
coursesu.com
1st party
1,681 KiB
…prehome/search-icon.svg
(www.coursesu.com)
1m 1s
1 KiB
3m 55s
47 KiB
4m 7s
14 KiB
4m 43s
47 KiB
4m 45s
1 KiB
4m 57s
46 KiB
4m 57s
15 KiB
5m 1s
46 KiB
5m 1s
46 KiB
5m 1s
15 KiB
5m 1s
9 KiB
5m 1s
6 KiB
5m 1s
1 KiB
…prehome/arrow-yellow.svg
(www.coursesu.com)
5m 1s
1 KiB
…arrows/arrow-simple.svg
(www.coursesu.com)
5m 1s
1 KiB
/tags.js
(dd.coursesu.com)
1h
43 KiB
29d 9h 32m 23s
2 KiB
…prehome/drive-icon.svg
(www.coursesu.com)
29d 13h 49m 25s
2 KiB
29d 14h 57m 42s
2 KiB
…footer/footer-hi….svg
(www.coursesu.com)
29d 15h 59m 25s
3 KiB
29d 18h 13m 31s
9 KiB
…footer/alcool.png
(www.coursesu.com)
29d 21h 17m 49s
8 KiB
29d 22h 14m 48s
4 KiB
29d 22h 37m 37s
8 KiB
29d 22h 49m 44s
14 KiB
29d 22h 55m 40s
10 KiB
…pictos/LogoPRC_N….png
(www.coursesu.com)
29d 22h 59m 4s
7 KiB
29d 23h 19m 17s
8 KiB
29d 23h 34m 11s
3 KiB
…css/mainab.css
(www.coursesu.com)
29d 23h 41m 46s
10 KiB
29d 23h 46m 38s
12 KiB
…css/prehome.css
(www.coursesu.com)
29d 23h 47m 45s
14 KiB
29d 23h 49m 29s
3 KiB
…prehome/yellow-line.svg
(www.coursesu.com)
29d 23h 55m 19s
1 KiB
…css/fonts.css
(www.coursesu.com)
29d 23h 59m 55s
1 KiB
29d 23h 59m 57s
3 KiB
29d 23h 59m 57s
3 KiB
…folder/more-circle.svg
(www.coursesu.com)
29d 23h 59m 57s
1 KiB
…folder/less-circle.svg
(www.coursesu.com)
29d 23h 59m 57s
1 KiB
…jscript/dwac-21.7.js
(www.coursesu.com)
29d 23h 59m 59s
2 KiB
…jscript/dwac-21.7.js
(www.coursesu.com)
29d 23h 59m 59s
2 KiB
30d
462 KiB
30d
103 KiB
30d
89 KiB
…js/prehome.js
(www.coursesu.com)
30d
85 KiB
…js/partners.js
(www.coursesu.com)
30d
75 KiB
…js/vendors.js
(www.coursesu.com)
30d
73 KiB
30d
72 KiB
30d
52 KiB
30d
37 KiB
30d
32 KiB
30d
28 KiB
30d
16 KiB
30d
12 KiB
30d
12 KiB
30d
9 KiB
30d
9 KiB
30d
7 KiB
30d
7 KiB
30d
6 KiB
30d
5 KiB
…css/footer.css
(www.coursesu.com)
30d
5 KiB
30d
4 KiB
…css/fakearkonly.css
(www.coursesu.com)
30d
3 KiB
30d
2 KiB
…espaceclient/auth.js
(www.coursesu.com)
30d
2 KiB
30d
2 KiB
30d
1 KiB
30d
1 KiB
30d
1 KiB
JSDelivr CDN
cdn
260 KiB
7d
222 KiB
7d
32 KiB
7d
6 KiB
Other Google APIs/SDKs
utility
128 KiB
…8.7/noSupplie….png
(storage.googleapis.com)
1h
118 KiB
…icons/ArrowLeft_dark.svg
(storage.googleapis.com)
1h
2 KiB
…icons/arrow-right.svg
(storage.googleapis.com)
1h
2 KiB
…icons/Cross_primary.svg
(storage.googleapis.com)
1h
1 KiB
…icons/plus-neutral-black.svg
(storage.googleapis.com)
1h
1 KiB
…icons/chevron-down-primary.svg
(storage.googleapis.com)
1h
1 KiB
…icons/plus-primary.svg
(storage.googleapis.com)
1h
1 KiB
…icons/minus-primary.svg
(storage.googleapis.com)
1h
1 KiB
…8.7/BulletPoint.svg
(storage.googleapis.com)
1h
1 KiB
Bazaarvoice
analytics
73 KiB
…fr_FR/bv.js
(apps.bazaarvoice.com)
5m
29 KiB
…fr_FR/api-config.js
(apps.bazaarvoice.com)
5m
2 KiB
…fr_FR/seller_ratings-config.js
(apps.bazaarvoice.com)
5m
1 KiB
…1/seller.min.js
(srd.bazaarvoice.com)
10m
15 KiB
/analytics/bv-analytics.js
(apps.bazaarvoice.com)
7d
13 KiB
…3/bv-analytics.js
(analytics-static.ugc.bazaarvoice.com)
7d
13 KiB
Salesforce Commerce Cloud
hosting
42 KiB
…v2/gretel.min.js
(cdn.cquotient.com)
1h
21 KiB
…v2/gretel.min.js
(cdn.cquotient.com)
1h
21 KiB
magasins-u.com
6 KiB
…logos/logo-u-desktop.svg
(www.magasins-u.com)
1d
6 KiB
Does not use passive listeners to improve scrolling performance
Consider marking your touch and wheel event listeners as passive to improve your page's scroll performance. Learn more about adopting passive event listeners.
Source
coursesu.com
1st party
…js/vendors.js:2:211746
(www.coursesu.com)
Properly size images Potential savings of 49 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
coursesu.com
1st party
88.5 KiB
49.2 KiB
Viandes, poissons
<img class="category-image" width="80" height="80" loading="lazy" src="/on/demandware.static/-/Sites-DigitalU-Library/default/dwb964d651/pictos-n…" alt="Viandes, poissons" aria-hidden="true">
15.6 KiB
8.6 KiB
Pains, Viennoiseries et Pâtisseries
<img class="category-image" width="80" height="80" loading="lazy" src="/on/demandware.static/-/Sites-DigitalU-Library/default/dw1e909855/pictos-n…" alt="Pains, Viennoiseries et Pâtisseries" aria-hidden="true">
13.6 KiB
7.6 KiB
Nutrition et régimes alimentaires
<img class="category-image" width="80" height="80" loading="lazy" src="/on/demandware.static/-/Sites-DigitalU-Library/default/dw250d3832/pictos-n…" alt="Nutrition et régimes alimentaires" aria-hidden="true">
11.8 KiB
6.5 KiB
Charcuterie, traiteur
<img class="category-image" width="80" height="80" loading="lazy" src="/on/demandware.static/-/Sites-DigitalU-Library/default/dw9ed81dce/pictos-n…" alt="Charcuterie, traiteur" aria-hidden="true">
11.3 KiB
6.3 KiB
Epicerie sucrée
<img class="category-image" width="80" height="80" loading="lazy" src="/on/demandware.static/-/Sites-DigitalU-Library/default/dwbda35221/pictos-n…" alt="Epicerie sucrée" aria-hidden="true">
11.0 KiB
6.1 KiB
Epicerie salée
<img class="category-image" width="80" height="80" loading="lazy" src="/on/demandware.static/-/Sites-DigitalU-Library/default/dwaade1fc6/pictos-n…" alt="Epicerie salée" aria-hidden="true">
9.3 KiB
5.1 KiB
Produits frais
<img class="category-image" width="80" height="80" loading="lazy" src="/on/demandware.static/-/Sites-DigitalU-Library/default/dw69a938fe/pictos-n…" alt="Produits frais" aria-hidden="true">
8.4 KiB
4.7 KiB
Boissons sans alcool
<img class="category-image" width="80" height="80" loading="lazy" src="/on/demandware.static/-/Sites-DigitalU-Library/default/dw04788cfd/pictos-n…" alt="Boissons sans alcool" aria-hidden="true">
7.5 KiB
4.2 KiB
Avoid serving legacy JavaScript to modern browsers Potential savings of 11 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. However, many aren't necessary for modern browsers. For your bundled JavaScript, adopt a modern script deployment strategy using module/nomodule feature detection to reduce the amount of code shipped to modern browsers, while retaining support for legacy browsers. Learn how to serve modern JavaScriptLCPFCP
URL
Potential Savings
Salesforce Commerce Cloud
hosting
10.5 KiB
…v2/gretel.min.js
(cdn.cquotient.com)
10.5 KiB
…v2/gretel.min.js:1:8822
(cdn.cquotient.com)
Date.prototype.toJSON
…v2/gretel.min.js:1:50385
(cdn.cquotient.com)
Array.prototype.filter
…v2/gretel.min.js:1:50758
(cdn.cquotient.com)
Array.from
…v2/gretel.min.js:1:55268
(cdn.cquotient.com)
@babel/plugin-transform-regenerator
coursesu.com
1st party
0.8 KiB
0.2 KiB
@babel/plugin-transform-classes
0.2 KiB
@babel/plugin-transform-classes
0.2 KiB
@babel/plugin-transform-classes
…js/prehome.js
(www.coursesu.com)
0.0 KiB
…js/prehome.js:2:285528
(www.coursesu.com)
@babel/plugin-transform-classes
…js/partners.js
(www.coursesu.com)
0.0 KiB
…js/partners.js:2:38127
(www.coursesu.com)
@babel/plugin-transform-classes
JSDelivr CDN
cdn
0.2 KiB
0.2 KiB
@babel/plugin-transform-classes
@babel/plugin-transform-regenerator
Bazaarvoice
analytics
0.1 KiB
…api/api-0.8.2.js
(apps.bazaarvoice.com)
0.1 KiB
…api/api-0.8.2.js:2:20659
(apps.bazaarvoice.com)
@babel/plugin-transform-classes
TagCommander
tag-manager
0.0 KiB
/3692/tc_CoursesU_21.js
(cdn.tagcommander.com)
0.0 KiB
/3692/tc_CoursesU_21.js:296:2302
(cdn.tagcommander.com)
@babel/plugin-transform-classes
Reduce unused CSS Potential savings of 32 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
:root .cors-overlay-container{background-color:transparent !important;align-items:start !important} …
32.2 KiB
32.0 KiB
Minimize third-party usage Third-party code blocked the main thread for 70 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
JSDelivr CDN
cdn
260 KiB
59 ms
222 KiB
59 ms
32 KiB
0 ms
6 KiB
0 ms
TagCommander
tag-manager
121 KiB
8 ms
/3692/tc_CoursesU_20.js
(cdn.tagcommander.com)
48 KiB
8 ms
/3692/tc_CoursesU_21.js
(cdn.tagcommander.com)
73 KiB
0 ms
Cloudflare CDN
cdn
49 KiB
4 ms
…3.4.29/vue.global.prod.min.js
(cdnjs.cloudflare.com)
49 KiB
4 ms
Trustcommander
consent-provider
26 KiB
0 ms
…3692/privacy_v2_26.js
(cdn.trustcommander.net)
26 KiB
0 ms
/privacy-consent?site=3692
(privacy.trustcommander.net)
0 KiB
0 ms
Bazaarvoice
analytics
95 KiB
0 ms
…fr_FR/bv.js
(apps.bazaarvoice.com)
29 KiB
0 ms
…1/seller.min.js
(srd.bazaarvoice.com)
15 KiB
0 ms
/analytics/bv-analytics.js
(apps.bazaarvoice.com)
13 KiB
0 ms
…3/bv-analytics.js
(analytics-static.ugc.bazaarvoice.com)
13 KiB
0 ms
…api/api-0.8.2.js
(apps.bazaarvoice.com)
11 KiB
0 ms
7 KiB
0 ms
…fr_FR/api-config.js
(apps.bazaarvoice.com)
2 KiB
0 ms
…fr_FR/seller_ratings-config.js
(apps.bazaarvoice.com)
1 KiB
0 ms
1 KiB
0 ms
/sid.gif?_=av7ld2
(network.bazaarvoice.com)
1 KiB
0 ms
/st.gif?cl=…
(network.bazaarvoice.com)
0 KiB
0 ms
/id.json?_=qcsk6c&callback=_bvajsonp1
(network.bazaarvoice.com)
0 KiB
0 ms
/a.gif?loadId=…
(network-eu-a.bazaarvoice.com)
0 KiB
0 ms
Other Google APIs/SDKs
utility
177 KiB
0 ms
…8.7/noSupplie….png
(storage.googleapis.com)
118 KiB
0 ms
…prod/config.json
(storage.googleapis.com)
49 KiB
0 ms
…icons/ArrowLeft_dark.svg
(storage.googleapis.com)
2 KiB
0 ms
…icons/arrow-right.svg
(storage.googleapis.com)
2 KiB
0 ms
…icons/Cross_primary.svg
(storage.googleapis.com)
1 KiB
0 ms
…icons/plus-neutral-black.svg
(storage.googleapis.com)
1 KiB
0 ms
…icons/chevron-down-primary.svg
(storage.googleapis.com)
1 KiB
0 ms
…icons/plus-primary.svg
(storage.googleapis.com)
1 KiB
0 ms
…icons/minus-primary.svg
(storage.googleapis.com)
1 KiB
0 ms
…8.7/BulletPoint.svg
(storage.googleapis.com)
1 KiB
0 ms
luckycart.com
84 KiB
0 ms
/systeme-u/luckyclient.min.js
(integration.luckycart.com)
83 KiB
0 ms
0 KiB
0 ms
Salesforce Commerce Cloud
hosting
42 KiB
0 ms
…v2/gretel.min.js
(cdn.cquotient.com)
42 KiB
0 ms
Google Fonts
cdn
34 KiB
0 ms
…v34/BngMUXZYT….woff2
(fonts.gstatic.com)
34 KiB
0 ms
magasins-u.com
12 KiB
0 ms
…logos/logo-u-desktop.svg
(www.magasins-u.com)
6 KiB
0 ms
….well-known/openid-configuration
(moncompte.magasins-u.com)
5 KiB
0 ms
…oauth2/authorize?client_id=…
(moncompte.magasins-u.com)
1 KiB
0 ms
miam.tech
11 KiB
0 ms
3 KiB
0 ms
3 KiB
0 ms
3 KiB
0 ms
…users/authless
(api.miam.tech)
2 KiB
0 ms
Avoid long main-thread tasks 3 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
coursesu.com
1st party
118 ms
1,281 ms
118 ms
JSDelivr CDN
cdn
109 ms
2,887 ms
109 ms
Bazaarvoice
analytics
50 ms
…fr_FR/bv.js
(apps.bazaarvoice.com)
1,961 ms
50 ms
Avoid large layout shifts 2 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
Je découvre Nouvelle fenêtre Je découvre
<div class="ab-prehome-row ab-prehome-slots homepage-pushes--layout">
0.007
div.ab-prehome-delivery-methods-left > div.ab-prehome-delivery-subtitle > span.ab-prehome-yellow-line > img
<img width="74" height="9" alt="" src="https://www.coursesu.com/on/demandware.static/-/Sites-DigitalU-Library/def…">
Media element lacking an explicit size
Se connecter Ma Carte U Découvrir
<div class="fake-ark-profile-container su-text-color-white" data-fake-ark-profile-container="">
0.002
User Timing marks and measures 54 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
BV_PERF_MARK_bv_loader_register_api
Measure
0.00 ms
1,354.60 ms
BV_PERF_MARK_bv_loader_register_inline_ratings
Measure
0.00 ms
1,354.80 ms
BV_PERF_MARK_bv_loader_register_inpage_submission
Measure
0.00 ms
1,355.00 ms
BV_PERF_MARK_bv_loader_register_rating_summary
Measure
0.00 ms
1,355.20 ms
BV_PERF_MARK_bv_loader_register_ratings
Measure
0.00 ms
1,355.30 ms
BV_PERF_MARK_bv_loader_register_review-highlights
Measure
0.00 ms
1,355.50 ms
BV_PERF_MARK_bv_loader_register_review_highlights
Measure
0.00 ms
1,355.60 ms
BV_PERF_MARK_bv_loader_register_reviews
Measure
0.00 ms
1,355.70 ms
BV_PERF_MARK_bv_loader_register_seller_ratings
Measure
0.00 ms
1,355.80 ms
BV_PERF_MARK_bv_loader_register_swat-submission
Measure
0.00 ms
1,356.00 ms
BV_PERF_MARK_bv_loader_register_swat_container
Measure
0.00 ms
1,356.20 ms
BV_PERF_MARK_bv_loader
Measure
0.00 ms
1,357.70 ms
BV_PERF_MARK_bv_loader_preconnectMark
Measure
0.00 ms
1,358.20 ms
BV_PERF_MARK_bv_loader_app_api_load_config
Measure
0.00 ms
1,597.80 ms
BV_PERF_MARK_bv_loader_app_seller_ratings_load_config
Measure
0.00 ms
1,598.50 ms
BV_PERF_MARK_bv_loader_app_api_load
Measure
0.00 ms
1,603.80 ms
BV_PERF_MARK_bv_loader_app_seller_ratings_load
Measure
0.00 ms
1,608.50 ms
BV_PERF_MARK_bv_loader_start
Mark
1,352.79 ms
BV_PERF_MARK_bv_loader_register_api_start
Mark
1,353.43 ms
BV_PERF_MARK_bv_loader_app_api_load_start
Mark
1,353.93 ms
BV_PERF_MARK_bv_loader_app_api_load_config_start
Mark
1,354.28 ms
BV_PERF_MARK_bv_loader_register_api_end
Mark
1,354.53 ms
BV_PERF_MARK_bv_loader_register_inline_ratings_start
Mark
1,354.71 ms
BV_PERF_MARK_bv_loader_register_inline_ratings_end
Mark
1,354.80 ms
BV_PERF_MARK_bv_loader_register_inpage_submission_start
Mark
1,354.89 ms
BV_PERF_MARK_bv_loader_register_inpage_submission_end
Mark
1,354.97 ms
BV_PERF_MARK_bv_loader_register_rating_summary_start
Mark
1,355.09 ms
BV_PERF_MARK_bv_loader_register_rating_summary_end
Mark
1,355.15 ms
BV_PERF_MARK_bv_loader_register_ratings_start
Mark
1,355.22 ms
BV_PERF_MARK_bv_loader_register_ratings_end
Mark
1,355.27 ms
BV_PERF_MARK_bv_loader_register_review-highlights_start
Mark
1,355.34 ms
BV_PERF_MARK_bv_loader_register_review-highlights_end
Mark
1,355.40 ms
BV_PERF_MARK_bv_loader_register_review_highlights_start
Mark
1,355.47 ms
BV_PERF_MARK_bv_loader_register_review_highlights_end
Mark
1,355.52 ms
BV_PERF_MARK_bv_loader_register_reviews_start
Mark
1,355.58 ms
BV_PERF_MARK_bv_loader_register_reviews_end
Mark
1,355.63 ms
BV_PERF_MARK_bv_loader_register_seller_ratings_start
Mark
1,355.70 ms
BV_PERF_MARK_bv_loader_register_seller_ratings_end
Mark
1,355.79 ms
BV_PERF_MARK_bv_loader_register_swat-submission_start
Mark
1,355.90 ms
BV_PERF_MARK_bv_loader_register_swat-submission_end
Mark
1,355.97 ms
BV_PERF_MARK_bv_loader_register_swat_container_start
Mark
1,356.03 ms
BV_PERF_MARK_bv_loader_register_swat_container_end
Mark
1,356.08 ms
BV_PERF_MARK_bv_loader_app_seller_ratings_load_start
Mark
1,356.70 ms
BV_PERF_MARK_bv_loader_app_seller_ratings_load_config_start
Mark
1,356.93 ms
BV_PERF_MARK_bv_loader_end
Mark
1,357.70 ms
BV_PERF_MARK_bv_loader_preconnectMark_start
Mark
1,357.98 ms
BV_PERF_MARK_bv_loader_preconnectMark_end
Mark
1,358.19 ms
bv_loader_configure_api_start
Mark
1,597.33 ms
BV_PERF_MARK_bv_loader_app_api_load_config_end
Mark
1,597.77 ms
bv_loader_configure_seller_ratings_start
Mark
1,598.28 ms
BV_PERF_MARK_bv_loader_app_seller_ratings_load_config_end
Mark
1,598.41 ms
BV_PERF_MARK_bv_loader_app_api_load_end
Mark
1,603.76 ms
BV_PERF_MARK_bv_loader_app_seller_ratings_bvShow_start
Mark
1,607.22 ms
BV_PERF_MARK_bv_loader_app_seller_ratings_load_end
Mark
1,608.42 ms
Avoid chaining critical requests 12 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: 1,775.303 ms
Initial Navigation
/drive/home
(www.coursesu.com)
…3.4.29/vue.global.prod.min.js
(cdnjs.cloudflare.com)
- 24.254 ms, 48.54 KiB
- 87.58 ms, 462.21 KiB
- 183.023 ms, 72.16 KiB
…espaceclient/auth.js
(www.coursesu.com)
- 164.308 ms, 2.11 KiB
…v34/BngMUXZYT….woff2
(fonts.gstatic.com)
- 6.633 ms, 34.32 KiB
…css/mainab.css
(www.coursesu.com)
- 60.901 ms, 9.50 KiB
- 51.573 ms, 1.15 KiB
…css/fakearkonly.css
(www.coursesu.com)
- 55.122 ms, 3.39 KiB
…css/footer.css
(www.coursesu.com)
- 246.004 ms, 4.58 KiB
…css/prehome.css
(www.coursesu.com)
- 61.446 ms, 13.54 KiB
- 157.726 ms, 0.70 KiB
/3692/tc_CoursesU_20.js
(cdn.tagcommander.com)
- 359.282 ms, 6.28 KiB
More information about the performance of your application. These numbers don't directly affect the Performance score.
Passed audits (21)
Show Hide
Defer offscreen images
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive. Learn how to defer offscreen images.LCPFCP
Minify CSS
Minifying CSS files can reduce network payload sizes. Learn how to minify CSS.LCPFCP
Minify JavaScript
Minifying JavaScript files can reduce payload sizes and script parse time. Learn how to minify JavaScript.LCPFCP
Efficiently encode images
Optimized images load faster and consume less cellular data. Learn how to efficiently encode images.LCPFCP
Preconnect to required origins
Warnings: A `<link rel=preconnect>` was found for "https://api.bazaarvoice.com" but was not used by the browser. Only use `preconnect` for important origins that the page will certainly request.
Consider adding preconnect or dns-prefetch resource hints to establish early connections to important third-party origins. Learn how to preconnect to required origins.LCPFCP
Initial server response time was short Root document took 520 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
coursesu.com
1st party
520 ms
/drive/home
(www.coursesu.com)
520 ms
Avoid multiple page redirects
Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.LCPFCP
Use video formats for animated content
Large GIFs are inefficient for delivering animated content. Consider using MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF to save network bytes. Learn more about efficient video formatsLCPFCP
Remove duplicate modules in JavaScript bundles
Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity. LCPFCP
Preload Largest Contentful Paint image
If the LCP element is dynamically added to the page, you should preload the image in order to improve LCP. Learn more about preloading LCP elements.LCP
Avoids enormous network payloads Total size was 2,634 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
coursesu.com
1st party
887.9 KiB
462.2 KiB
102.9 KiB
89.2 KiB
…js/prehome.js
(www.coursesu.com)
85.0 KiB
…js/partners.js
(www.coursesu.com)
75.3 KiB
…js/vendors.js
(www.coursesu.com)
73.3 KiB
JSDelivr CDN
cdn
222.0 KiB
222.0 KiB
Other Google APIs/SDKs
utility
117.9 KiB
…8.7/noSupplie….png
(storage.googleapis.com)
117.9 KiB
luckycart.com
83.1 KiB
/systeme-u/luckyclient.min.js
(integration.luckycart.com)
83.1 KiB
TagCommander
tag-manager
73.1 KiB
/3692/tc_CoursesU_21.js
(cdn.tagcommander.com)
73.1 KiB
Avoids an excessive DOM size 705 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
705
Maximum DOM Depth
3,9 sur 5 étoiles.
<span>
16
Maximum Child Elements
body.tc-modal-open
<body class="tc-modal-open" style="">
21
JavaScript execution time 0.4 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to reduce Javascript execution time.TBT
URL
Total CPU Time
Script Evaluation
Script Parse
coursesu.com
1st party
421 ms
209 ms
26 ms
/drive/home
(www.coursesu.com)
157 ms
7 ms
5 ms
…js/vendors.js
(www.coursesu.com)
116 ms
80 ms
3 ms
76 ms
58 ms
17 ms
/tags.js
(dd.coursesu.com)
71 ms
63 ms
2 ms
JSDelivr CDN
cdn
173 ms
145 ms
18 ms
113 ms
94 ms
14 ms
60 ms
51 ms
4 ms
Unattributable
146 ms
4 ms
0 ms
Unattributable
146 ms
4 ms
0 ms
TagCommander
tag-manager
72 ms
24 ms
3 ms
/3692/tc_CoursesU_20.js
(cdn.tagcommander.com)
72 ms
24 ms
3 ms
Minimizes main-thread work 1.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
605 ms
Style & Layout
191 ms
Other
178 ms
Script Parsing & Compilation
79 ms
Rendering
28 ms
Parse HTML & CSS
23 ms
Garbage Collection
4 ms
All text remains visible during webfont loads
Leverage the font-display CSS feature to ensure text is user-visible while webfonts are loading. Learn more about font-display.
Lazy load third-party resources with facades
Some third-party embeds can be lazy loaded. Consider replacing them with a facade until they are required. Learn how to defer third-parties with a facade.TBT
Largest Contentful Paint image was not lazily loaded
Above-the-fold images that are lazily loaded render later in the page lifecycle, which can delay the largest contentful paint. Learn more about optimal lazy loading.LCP
Element
main#main > div#quick-content > div.ab-prehome-row > div.ab-prehome-banner-background
<div class="ab-prehome-banner-background desktop-banner" style="background-image: url(&quot;https://www.coursesu.com/dw/image/v2/BBQX_PRD/on/de…&quot;);">
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
Image elements have explicit width and height
Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensionsCLS
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
Elements with role="dialog" or role="alertdialog" do not have accessible names.
ARIA dialog elements without accessible names may prevent screen readers users from discerning the purpose of these elements. Learn how to make ARIA dialog elements more accessible.
Failing Elements
La Coopérative U et ses partenaires utilisent des cookies afin de vous offrir l…
<div id="popin_tc_privacy" class="tc-reset-css tc-privacy-banner tc-privacy-popin tc-privacy-mid" aria-describedby="description" role="dialog" aria-modal="true" style="top: 196px; left: 346px;">
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
These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.
Additional items to manually check (10)
Show Hide
Interactive controls are keyboard focusable
Custom interactive controls are keyboard focusable and display a focus indicator. Learn how to make custom controls focusable.
Interactive elements indicate their purpose and state
Interactive elements, such as links and buttons, should indicate their state and be distinguishable from non-interactive elements. Learn how to decorate interactive elements with affordance hints.
The page has a logical tab order
Tabbing through the page follows the visual layout. Users cannot focus elements that are offscreen. Learn more about logical tab ordering.
Visual order on the page follows DOM order
DOM order matches the visual order, improving navigation for assistive technology. Learn more about DOM and visual ordering.
User focus is not accidentally trapped in a region
A user can tab into and out of any control or region without accidentally trapping their focus. Learn how to avoid focus traps.
The user's focus is directed to new content added to the page
If new content, such as a dialog, is added to the page, the user's focus is directed to it. Learn how to direct focus to new content.
HTML5 landmark elements are used to improve navigation
Landmark elements (<main>, <nav>, etc.) are used to improve the keyboard navigation of the page for assistive technology. Learn more about landmark elements.
Offscreen content is hidden from assistive technology
Offscreen content is hidden with display: none or aria-hidden=true. Learn how to properly hide offscreen content.
Custom controls have associated labels
Custom interactive controls have associated labels, provided by aria-label or aria-labelledby. Learn more about custom controls and labels.
Custom controls have ARIA roles
Custom interactive controls have appropriate ARIA roles. Learn how to add roles to custom controls.
These items address areas which an automated testing tool cannot cover. Learn more in our guide on conducting an accessibility review.
Passed audits (30)
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.
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.
[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.
Image elements have [alt] attributes
Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the alt attribute.
[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.
[aria-hidden="true"] elements do not contain focusable descendents
Focusable descendents within an [aria-hidden="true"] element prevent those interactive elements from being available to users of assistive technologies like screen readers. Learn how aria-hidden affects focusable elements.
Elements use only permitted ARIA attributes
Using ARIA attributes in roles where they are prohibited can mean that important information is not communicated to users of assistive technologies. Learn more about prohibited ARIA roles.
[role] values are valid
ARIA roles must have valid values in order to perform their intended accessibility functions. Learn more about valid ARIA roles.
Background and foreground colors have a sufficient contrast ratio
Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.
Document has a <title> element
The title gives screen reader users an overview of the page, and search engine users rely on it heavily to determine if a page is relevant to their search. Learn more about document titles.
<html> element has a [lang] attribute
If a page doesn't specify a lang attribute, a screen reader assumes that the page is in the default language that the user chose when setting up the screen reader. If the page isn't actually in the default language, then the screen reader might not announce the page's text correctly. Learn more about the lang attribute.
<html> element has a valid value for its [lang] attribute
Specifying a valid BCP 47 language helps screen readers announce text properly. Learn how to use the lang attribute.
Form elements have associated labels
Labels ensure that form controls are announced properly by assistive technologies, like screen readers. Learn more about form element labels.
Lists contain only <li> elements and script supporting elements (<script> and <template>).
Screen readers have a specific way of announcing lists. Ensuring proper list structure aids screen reader output. Learn more about proper list structure.
List items (<li>) are contained within <ul>, <ol> or <menu> parent elements
Screen readers require list items (<li>) to be contained within a parent <ul>, <ol> or <menu> to be announced properly. Learn more about proper list structure.
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.
Touch targets have sufficient size and spacing.
Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.
[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.
Uses ARIA roles only on compatible elements
Many HTML elements can only be assigned certain ARIA roles. Using ARIA roles where they are not allowed can interfere with the accessibility of the web page. Learn more about ARIA roles.
Deprecated ARIA roles were not used
Deprecated ARIA roles may not be processed correctly by assistive technology. Learn more about deprecated ARIA roles.
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 (25)
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 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 1 warning found
Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs.
Deprecation / Warning
Source
coursesu.com
1st party
`<source src>` with a `<picture>` parent is invalid and therefore ignored. Please use `<source srcset>` instead.
/drive/home:2987:-1
(www.coursesu.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
JSDelivr CDN
cdn
[Mealz] could not find coursesu basket element to listen for change, sync is broken
Detected JavaScript libraries
All front-end JavaScript libraries detected on the page. Learn more about this JavaScript library detection diagnostic audit.
Name
Version
jQuery
3.7.1
jQuery UI
1.13.3
Angular
11.2.14
Vue
3.4.29
core-js
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
coursesu.com
1st party
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
`script-src` directive is missing. This can allow the execution of unsafe scripts.
script-src
High
Missing `object-src` allows the injection of plugins that execute unsafe scripts. Consider setting `object-src` to `'none'` if you can.
object-src
High
Use a strong HSTS policy
Deployment of the HSTS header significantly reduces the risk of downgrading HTTP connections and eavesdropping attacks. A rollout in stages, starting with a low max-age is recommended. Learn more about using a strong HSTS policy.
Description
Directive
Severity
No `preload` directive found
preload
Medium
Ensure proper origin isolation with COOP
The Cross-Origin-Opener-Policy (COOP) can be used to isolate the top-level window from other documents such as pop-ups. Learn more about deploying the COOP header.
Description
Directive
Severity
No COOP header found
High
Passed audits (11)
Show Hide
Uses HTTPS
All sites should be protected with HTTPS, even ones that don't handle sensitive data. This includes avoiding mixed content, where some resources are loaded over HTTP despite the initial request being served over HTTPS. HTTPS prevents intruders from tampering with or passively listening in on the communications between your app and your users, and is a prerequisite for HTTP/2 and many new web platform APIs. Learn more about HTTPS.
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 (3)
Show Hide
Redirects HTTP traffic to HTTPS
Make sure that you redirect all HTTP traffic to HTTPS in order to enable secure web features for all your users. Learn more.
Mitigate clickjacking with XFO or CSP
The X-Frame-Options (XFO) header or the frame-ancestors directive in the Content-Security-Policy (CSP) header control where a page can be embedded. These can mitigate clickjacking attacks by blocking some or all sites from embedding the page. Learn more about mitigating clickjacking.
Document uses legible font sizes
Font sizes less than 12px are too small to be legible and require mobile visitors to “pinch to zoom” in order to read. Strive to have >60% of page text ≥12px. Learn more about legible font sizes.
These checks ensure that your page is following basic search engine optimization advice. There are many additional factors Lighthouse does not score here that may affect your search ranking, including performance on Core Web Vitals. Learn more about Google Search Essentials.
Crawling and Indexing
robots.txt is not valid 1 error found
If your robots.txt file is malformed, crawlers may not be able to understand how you want your website to be crawled or indexed. Learn more about robots.txt.
Line #
Content
Error
52
Disallow: /*$REORDER_PAGE_URL$*
"$" should only be used at the end of the pattern
To appear in search results, crawlers need access to your app.
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 (9)
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
Image elements have [alt] attributes
Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the alt attribute.
Document has a valid hreflang
hreflang links tell search engines what version of a page they should list in search results for a given language or region. Learn more about hreflang.
Document has a valid rel=canonical
Canonical links suggest which URL to show in search results. Learn more about canonical links.