PageSpeed Insights logo
PageSpeed Insights
PageSpeed Insights
This site uses cookies from Google to deliver its services and to analyze traffic.
Report from Feb 22, 2025, 8:00:47 AM
Discover what your real users are experiencing
Core Web Vitals Assessment: Failed
Largest Contentful Paint (LCP)
3.8 s
Page LoadsGood (≤ 2.5 s)59%Needs Improvement (2.5 s - 4 s)19%Poor (> 4 s)22%75th Percentile - 3.8 sCore Web Vital
Interaction to Next Paint (INP)
682 ms
Page LoadsGood (≤ 200 ms)30%Needs Improvement (200 ms - 500 ms)36%Poor (> 500 ms)34%75th Percentile - 682 msCore Web Vital
Cumulative Layout Shift (CLS)
0.01
Page LoadsGood (≤ 0.1)86%Needs Improvement (0.1 - 0.25)7%Poor (> 0.25)7%75th Percentile - 0.01Core Web Vital
Other Notable Metrics
First Contentful Paint (FCP)
1.6 s
Page LoadsGood (≤ 1.8 s)79%Needs Improvement (1.8 s - 3 s)12%Poor (> 3 s)9%75th Percentile - 1.6 s 
Time to First Byte (TTFB)
0.5 s
Page LoadsGood (≤ 0.8 s)84%Needs Improvement (0.8 s - 1.8 s)12%Poor (> 1.8 s)4%75th Percentile - 0.5 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)
3.3 s
Page LoadsGood (≤ 2.5 s)62%Needs Improvement (2.5 s - 4 s)22%Poor (> 4 s)17%75th Percentile - 3.3 sCore Web Vital
Interaction to Next Paint (INP)
385 ms
Page LoadsGood (≤ 200 ms)51%Needs Improvement (200 ms - 500 ms)30%Poor (> 500 ms)19%75th Percentile - 385 msCore Web Vital
Cumulative Layout Shift (CLS)
0.08
Page LoadsGood (≤ 0.1)79%Needs Improvement (0.1 - 0.25)10%Poor (> 0.25)11%75th Percentile - 0.08Core Web Vital
Other Notable Metrics
First Contentful Paint (FCP)
2.6 s
Page LoadsGood (≤ 1.8 s)54%Needs Improvement (1.8 s - 3 s)26%Poor (> 3 s)19%75th Percentile - 2.6 s 
Time to First Byte (TTFB)
0.7 s
Page LoadsGood (≤ 0.8 s)79%Needs Improvement (0.8 s - 1.8 s)16%Poor (> 1.8 s)5%75th Percentile - 0.7 sExperimental
Latest 28-day collection period
Various mobile devicesMany samples (Chrome UX Report)Full visit durationsVarious network connectionsAll Chrome versions
Diagnose performance issues
31
Performance
92
Accessibility
96
Best Practices
100
SEO
31
Performance
92
Accessibility
96
Best Practices
100
SEO
31 FCP+5LCP+0TBT+0CLS+25SI+0 Performance
Values are estimated and may vary. The performance score is calculated directly from these metrics.See calculator.
0–49 50–89 90–100
Final Screenshot
Metrics
First Contentful Paint
2.9 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
17.8 s
Largest Contentful Paint marks the time at which the largest text or image is painted. Learn more about the Largest Contentful Paint metric
Total Blocking Time
3,730 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds. Learn more about the Total Blocking Time metric.
Cumulative Layout Shift
0
Cumulative Layout Shift measures the movement of visible elements within the viewport. Learn more about the Cumulative Layout Shift metric.
Speed Index
13.6 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more about the Speed Index metric.
  • Captured at Feb 22, 2025, 8:00 AM UTC
  • Emulated Moto G Power with Lighthouse 12.2.3
    Unthrottled CPU/Memory Power: 345 CPU throttling: 1.2x slowdown (Simulated) Screen emulation: 412x823, DPR 1.75 Axe version: 4.10.2
  • Single page session
    This data is taken from a single page session, as opposed to field data summarizing many sessions.
  • Initial page load
  • Slow 4G throttling
    Network throttling: 150 ms TCP RTT, 1,638.4 kb/s throughput (Simulated) Browser location: North America
  • Using HeadlessChromium 133.0.6943.53 with lr
    User agent (network): "Mozilla/5.0 (Linux; Android 11; moto g power (2022)) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/119.0.0.0 Mobile Safari/537.36"
Screenshot
Screenshot
Screenshot
Screenshot
Screenshot
Screenshot
Screenshot
Screenshot
Show audits relevant to:
Diagnostics
Minimize main-thread work 9.3 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to minimize main-thread workTBT
Category
Time Spent
Script Evaluation
5,887 ms
Style & Layout
1,923 ms
Garbage Collection
670 ms
Other
461 ms
Script Parsing & Compilation
232 ms
Rendering
98 ms
Parse HTML & CSS
69 ms
Largest Contentful Paint element 17,850 ms
This is the largest contentful element painted within the viewport. Learn more about the Largest Contentful Paint elementLCP
Element
We use cookies, including third party cookies, for operational purposes, statis…
<div id="onetrust-policy-text">
Phase
% of LCP
Timing
TTFB
3%
600 ms
Load Delay
0%
0 ms
Load Time
0%
0 ms
Render Delay
97%
17,250 ms
Reduce JavaScript execution time 5.9 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to reduce Javascript execution time.TBT
URL
Total CPU Time
Script Evaluation
Script Parse
dior.com
1st party
7,148 ms
4,855 ms
93 ms
…chunks/framework-a32fdada02556615.js
(www.dior.com)
4,329 ms
3,571 ms
3 ms
/fr_fr/fashion
(www.dior.com)
1,212 ms
9 ms
1 ms
…pages/_app-c7aaa6e71a26c10d.js
(www.dior.com)
634 ms
468 ms
47 ms
…9876636/api_static.js
(www.dior.com)
495 ms
405 ms
10 ms
…%5Buniverse%5D/%5B%5B...path%5D%5D-8d1d20fdd7f41e90.js
(www.dior.com)
265 ms
221 ms
1 ms
…9876636/api_dynamic.js
(www.dior.com)
156 ms
129 ms
27 ms
…chunks/main-3ee40a2a2f5cb04c.js
(www.dior.com)
57 ms
52 ms
3 ms
Google Tag Manager
tag-manager
781 ms
322 ms
78 ms
/gtm.js?id=GTM-5NT5ZL8
(www.googletagmanager.com)
461 ms
52 ms
56 ms
/gtm.js?id=GTM-M75MVP67
(www.googletagmanager.com)
222 ms
184 ms
10 ms
/gtm.js?id=GTM-KKVBDVG&l=dataLayer&gtm=45He52k0v916…za200
(www.googletagmanager.com)
98 ms
86 ms
12 ms
Unattributable
521 ms
152 ms
0 ms
Unattributable
521 ms
152 ms
0 ms
Optanon
consent-provider
513 ms
259 ms
12 ms
…202408.1.0/otBannerSdk.js
(cdn.cookielaw.org)
333 ms
81 ms
11 ms
/scripttemplates/otSDKStub.js
(cdn.cookielaw.org)
181 ms
178 ms
1 ms
Dynamic Yield
customer-success
101 ms
89 ms
3 ms
…2.48.0/dy-coll-nojq-min.js
(cdn-eu.dynamicyield.com)
101 ms
89 ms
3 ms
Riskified
utility
65 ms
60 ms
2 ms
/?shop=www.dior.com&sid=88dc7126-9158-4322-95c0-b3a21381b7a1
(beacon.riskified.com)
65 ms
60 ms
2 ms
Reduce unused JavaScript Potential savings of 480 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
Next.jsUse Webpack Bundle Analyzer to detect unused JavaScript code. Learn more
URL
Transfer Size
Potential Savings
dior.com
1st party
632.2 KiB
239.7 KiB
…pages/_app-c7aaa6e71a26c10d.js
(www.dior.com)
488.6 KiB
150.8 KiB
…9876636/api_static.js
(www.dior.com)
114.8 KiB
64.0 KiB
…chunks/1420-aa28d7f7ac15740e.js
(www.dior.com)
28.8 KiB
24.9 KiB
Google Tag Manager
tag-manager
454.2 KiB
181.5 KiB
/gtm.js?id=GTM-5NT5ZL8
(www.googletagmanager.com)
105.4 KiB
54.2 KiB
/gtm.js?id=GTM-KKVBDVG&l=dataLayer&gtm=45He52k0v916…za200
(www.googletagmanager.com)
136.6 KiB
53.9 KiB
/gtm.js?id=GTM-5NT5ZL8
(www.googletagmanager.com)
105.4 KiB
39.2 KiB
/gtm.js?id=GTM-M75MVP67
(www.googletagmanager.com)
106.8 KiB
34.2 KiB
Optanon
consent-provider
110.1 KiB
59.2 KiB
…202408.1.0/otBannerSdk.js
(cdn.cookielaw.org)
110.1 KiB
59.2 KiB
Reduce unused CSS Potential savings of 56 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
Next.jsConsider setting up PurgeCSS in Next.js configuration to remove unused rules from stylesheets. Learn more.
URL
Transfer Size
Potential Savings
dior.com
1st party
42.1 KiB
38.6 KiB
…css/f6e84c4aa67274e8.css
(www.dior.com)
42.1 KiB
38.6 KiB
Unattributable
19.6 KiB
17.1 KiB
#onetrust-banner-sdk .onetrust-vendors-list-handler{cursor:pointer;color:#1f96db;font-size:inherit; … } …
19.6 KiB
17.1 KiB
Avoid an excessive DOM size 2,947 elements
A large DOM will increase memory usage, cause longer style calculations, and produce costly layout reflows. Learn how to avoid an excessive DOM size.TBT
Statistic
Element
Value
Total DOM Elements
2,947
Maximum DOM Depth
li > a.NavigationLink_navigationLink__uTNLK > svg.MuiSvgIcon-root > path
<path fill="currentColor" d="M14 12a2 2 0 1 1-4 0 2 2 0 0 1 4 0">
23
Maximum Child Elements
body.js-focus-visible
<body class="js-focus-visible" style="overflow: hidden;">
21
Reduce the impact of third-party code Third-party code blocked the main thread for 710 ms
Third-party code can significantly impact load performance. Limit the number of redundant third-party providers and try to load third-party code after your page has primarily finished loading. Learn how to minimize third-party impact.TBT
Third-Party
Transfer Size
Main-Thread Blocking Time
Google Tag Manager
tag-manager
352 KiB
478 ms
/gtm.js?id=GTM-5NT5ZL8
(www.googletagmanager.com)
107 KiB
375 ms
/gtm.js?id=GTM-M75MVP67
(www.googletagmanager.com)
108 KiB
91 ms
/gtm.js?id=GTM-KKVBDVG&l=dataLayer&gtm=45He52k0v916…za200
(www.googletagmanager.com)
138 KiB
12 ms
Optanon
consent-provider
190 KiB
228 ms
/scripttemplates/otSDKStub.js
(cdn.cookielaw.org)
8 KiB
122 ms
…202408.1.0/otBannerSdk.js
(cdn.cookielaw.org)
111 KiB
106 ms
…0192f77d-fb93-78fd-85db-1dd6c89e3ca1/en.json
(cdn.cookielaw.org)
32 KiB
0 ms
…v2/otPcCenter.json
(cdn.cookielaw.org)
13 KiB
0 ms
…static/ot_company_logo.png
(cdn.cookielaw.org)
9 KiB
0 ms
…assets/otCommonStyles.css
(cdn.cookielaw.org)
5 KiB
0 ms
…assets/otCenterRounded.json
(cdn.cookielaw.org)
3 KiB
0 ms
…7d443084-35a1-4e89-8253-4ed5a4974685/7d443084-35a1-4e89-8….json
(cdn.cookielaw.org)
3 KiB
0 ms
…static/powered_by_logo.svg
(cdn.cookielaw.org)
3 KiB
0 ms
…static/ot_guard_logo.svg
(cdn.cookielaw.org)
1 KiB
0 ms
…geo/location
(geolocation.onetrust.com)
0 KiB
0 ms
dam-broadcast.com
16,134 KiB
0 ms
/pm_11872_932_932905-cxdprf6i0m.webm
(diorama.dam-broadcast.com)
8,962 KiB
0 ms
/pm_11872_986_986914-q8pnbbr08b.webm
(diorama.dam-broadcast.com)
6,976 KiB
0 ms
…width=640,format=auto/pm_11872_865_865555-nlgxsobv31-whr.jpg
(diorama.dam-broadcast.com)
59 KiB
0 ms
…width=640,format=auto/pm_11872_948_948544-3lygpebgn4-whr.jpg
(diorama.dam-broadcast.com)
37 KiB
0 ms
…width=460,format=auto/pm_11872_948_948649-wfalqu39sc-whr.jpg
(diorama.dam-broadcast.com)
31 KiB
0 ms
…width=460,format=auto/pm_11872_948_948646-6hamrr7x9p-whr.jpg
(diorama.dam-broadcast.com)
31 KiB
0 ms
…width=460,format=auto/pm_11872_948_948640-ad1dldptf2-whr.jpg
(diorama.dam-broadcast.com)
24 KiB
0 ms
…width=460,format=auto/pm_11872_948_948655-007279e2p2-whr.jpg
(diorama.dam-broadcast.com)
14 KiB
0 ms
Salesforce.com
ad
45 KiB
0 ms
…5.0/esw.min.js
(christiandior.my.salesforce.com)
9 KiB
0 ms
…client/liveagent.esw.min.js
(christiandior.my.salesforce.com)
6 KiB
0 ms
…frame/chasitor.esw.min.js
(christiandior.my.salesforce.com)
6 KiB
0 ms
…client/invite.esw.min.js
(christiandior.my.salesforce.com)
5 KiB
0 ms
…5.0/esw.min.css
(christiandior.my.salesforce.com)
5 KiB
0 ms
…utils/inert.min.js
(christiandior.my.salesforce.com)
3 KiB
0 ms
…5.0/eswFrame.min.js
(christiandior.my.salesforce.com)
3 KiB
0 ms
…utils/common.min.js
(christiandior.my.salesforce.com)
3 KiB
0 ms
…5.0/esw.html?parent=https://www.dior.com/fr_fr/fashion
(christiandior.my.salesforce.com)
2 KiB
0 ms
…frame/session.esw.min.js
(christiandior.my.salesforce.com)
2 KiB
0 ms
…frame/broadcast.esw.min.js
(christiandior.my.salesforce.com)
1 KiB
0 ms
…frame/filetransfer.esw.min.js
(christiandior.my.salesforce.com)
1 KiB
0 ms
Dynamic Yield
customer-success
44 KiB
0 ms
…2.48.0/dy-coll-nojq-min.js
(cdn-eu.dynamicyield.com)
33 KiB
0 ms
/st?sec=…
(st-eu.dynamicyield.com)
11 KiB
0 ms
Riskified
utility
17 KiB
0 ms
/?shop=www.dior.com&sid=88dc7126-9158-4322-95c0-b3a21381b7a1
(beacon.riskified.com)
15 KiB
0 ms
/v2/client_infos
(c.riskified.com)
1 KiB
0 ms
/img/image-l.gif?t=…
(img.riskified.com)
0 KiB
0 ms
/img/image-l.gif?t=…
(img.riskified.com)
0 KiB
0 ms
/img/image-l.gif?t=…
(img.riskified.com)
0 KiB
0 ms
/img/image-l.gif?t=…
(img.riskified.com)
0 KiB
0 ms
/img/image-l.gif?t=…
(img.riskified.com)
0 KiB
0 ms
Launch Darkly
utility
7 KiB
0 ms
…contexts/eyJraW5kI…
(app.launchdarkly.com)
3 KiB
0 ms
…goals/63750fc…
(app.launchdarkly.com)
2 KiB
0 ms
…diagnostic/63750fc…
(events.launchdarkly.com)
1 KiB
0 ms
…bulk/63750fc…
(events.launchdarkly.com)
1 KiB
0 ms
…63750fc…/eyJraW5kI…
(clientstream.launchdarkly.com)
0 KiB
0 ms
booxi.eu
3 KiB
0 ms
/booknow/booknow.js
(www.booxi.eu)
3 KiB
0 ms
Salesforce Live Agent
customer-success
1 KiB
0 ms
…Visitor/Settings.jsonp?Settings.prefix=…
(d.la1-c1-ar3.salesforceliveagent.com)
1 KiB
0 ms
…Visitor/Settings.jsonp?Settings.prefix=…
(d.la2-c2-cdg.salesforceliveagent.com)
1 KiB
0 ms
…EmbeddedService/EmbeddedS….jsonp?Settings.prefix=…
(d.la2-c2-cdg.salesforceliveagent.com)
0 KiB
0 ms
Properly size images Potential savings of 29 KiB
Serve images that are appropriately-sized to save cellular data and improve load time. Learn how to size images.LCPFCP
Next.jsUse the next/image component to set the appropriate sizes. Learn more.
URL
Resource Size
Potential Savings
dam-broadcast.com
60.2 KiB
28.7 KiB
div.MuiBox-root > a.MuiBox-root > div.DS-Image > img.MuiBox-root
<img class="MuiBox-root mui-xk80f6" alt="" src="https://diorama.dam-broadcast.com/cdn-cgi/image/width=460,format=auto/pm_1…" fetchpriority="high" decoding="async" sizes="50vw" srcset="https://diorama.dam-broadcast.com/cdn-cgi/image/width=355,format=auto/pm_1…" loading="eager" style="color:transparent">
…width=460,format=auto/pm_11872_948_948649-wfalqu39sc-whr.jpg
(diorama.dam-broadcast.com)
30.1 KiB
14.4 KiB
div.MuiBox-root > a.MuiBox-root > div.DS-Image > img.MuiBox-root
<img class="MuiBox-root mui-xk80f6" alt="" src="https://diorama.dam-broadcast.com/cdn-cgi/image/width=460,format=auto/pm_1…" decoding="async" sizes="50vw" srcset="https://diorama.dam-broadcast.com/cdn-cgi/image/width=355,format=auto/pm_1…" loading="lazy" style="color:transparent">
…width=460,format=auto/pm_11872_948_948646-6hamrr7x9p-whr.jpg
(diorama.dam-broadcast.com)
30.0 KiB
14.3 KiB
Serve static assets with an efficient cache policy 45 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more about efficient cache policies.
Next.jsConfigure caching for immutable assets and Server-side Rendered (SSR) pages. Learn more.
URL
Cache TTL
Transfer Size
dam-broadcast.com
16,134 KiB
/pm_11872_932_932905-cxdprf6i0m.webm
(diorama.dam-broadcast.com)
2d
8,962 KiB
/pm_11872_986_986914-q8pnbbr08b.webm
(diorama.dam-broadcast.com)
2d
3,989 KiB
/pm_11872_986_986914-q8pnbbr08b.webm
(diorama.dam-broadcast.com)
2d
2,965 KiB
…width=640,format=auto/pm_11872_865_865555-nlgxsobv31-whr.jpg
(diorama.dam-broadcast.com)
2d
59 KiB
…width=640,format=auto/pm_11872_948_948544-3lygpebgn4-whr.jpg
(diorama.dam-broadcast.com)
2d
37 KiB
…width=460,format=auto/pm_11872_948_948649-wfalqu39sc-whr.jpg
(diorama.dam-broadcast.com)
2d
31 KiB
…width=460,format=auto/pm_11872_948_948646-6hamrr7x9p-whr.jpg
(diorama.dam-broadcast.com)
2d
31 KiB
…width=460,format=auto/pm_11872_948_948640-ad1dldptf2-whr.jpg
(diorama.dam-broadcast.com)
2d
24 KiB
/pm_11872_986_986914-q8pnbbr08b.webm
(diorama.dam-broadcast.com)
2d
21 KiB
…width=460,format=auto/pm_11872_948_948655-007279e2p2-whr.jpg
(diorama.dam-broadcast.com)
2d
14 KiB
dior.com
1st party
708 KiB
…9876636/api_dynamic.js
(www.dior.com)
30s
113 KiB
…9876636/api_static.js
(www.dior.com)
8h
116 KiB
…AtacamaVAR/AtacamaVAR-VF.woff2
(www.dior.com)
90d
251 KiB
…Semi-bold/Hellix-SemiBold.woff2
(www.dior.com)
90d
43 KiB
…Bold/Hellix-Bold.woff2
(www.dior.com)
90d
43 KiB
…Medium/Hellix-Medium.woff2
(www.dior.com)
90d
43 KiB
…Regular/Hellix-Regular.woff2
(www.dior.com)
90d
43 KiB
…Light/Hellix-Light.woff2
(www.dior.com)
90d
41 KiB
…fonts/DiorSymbols-Regular.otf
(www.dior.com)
90d
10 KiB
…livechat/livechat.js
(www.dior.com)
90d
3 KiB
…Hellix/Hellix.css
(www.dior.com)
90d
1 KiB
…livechat/livechat.css
(www.dior.com)
90d
1 KiB
…AtacamaVAR/AtacamaVAR.css
(www.dior.com)
90d
1 KiB
Optanon
consent-provider
132 KiB
…202408.1.0/otBannerSdk.js
(cdn.cookielaw.org)
1d
111 KiB
…static/ot_company_logo.png
(cdn.cookielaw.org)
1d
9 KiB
/scripttemplates/otSDKStub.js
(cdn.cookielaw.org)
1d
8 KiB
…static/powered_by_logo.svg
(cdn.cookielaw.org)
1d
3 KiB
Salesforce.com
ad
43 KiB
…5.0/esw.min.js
(christiandior.my.salesforce.com)
1d
9 KiB
…client/liveagent.esw.min.js
(christiandior.my.salesforce.com)
1d
6 KiB
…frame/chasitor.esw.min.js
(christiandior.my.salesforce.com)
1d
6 KiB
…client/invite.esw.min.js
(christiandior.my.salesforce.com)
1d
5 KiB
…5.0/esw.min.css
(christiandior.my.salesforce.com)
1d
5 KiB
…utils/inert.min.js
(christiandior.my.salesforce.com)
1d
3 KiB
…5.0/eswFrame.min.js
(christiandior.my.salesforce.com)
1d
3 KiB
…utils/common.min.js
(christiandior.my.salesforce.com)
1d
3 KiB
…frame/session.esw.min.js
(christiandior.my.salesforce.com)
1d
2 KiB
…frame/broadcast.esw.min.js
(christiandior.my.salesforce.com)
1d
1 KiB
…frame/filetransfer.esw.min.js
(christiandior.my.salesforce.com)
1d
1 KiB
Riskified
utility
16 KiB
/img/image-l.gif?t=…
(img.riskified.com)
None
0 KiB
/img/image-l.gif?t=…
(img.riskified.com)
None
0 KiB
/img/image-l.gif?t=…
(img.riskified.com)
None
0 KiB
/img/image-l.gif?t=…
(img.riskified.com)
None
0 KiB
/img/image-l.gif?t=…
(img.riskified.com)
None
0 KiB
/?shop=www.dior.com&sid=88dc7126-9158-4322-95c0-b3a21381b7a1
(beacon.riskified.com)
10m
15 KiB
booxi.eu
3 KiB
/booknow/booknow.js
(www.booxi.eu)
1m
3 KiB
Defer offscreen images Potential savings of 11 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
Next.jsUse the next/image component instead of <img> to automatically lazy-load images. Learn more.
URL
Resource Size
Potential Savings
Optanon
consent-provider
11.3 KiB
11.3 KiB
Company Logo
<img alt="Company Logo" src="https://cdn.cookielaw.org/logos/static/ot_company_logo.png">
…static/ot_company_logo.png
(cdn.cookielaw.org)
8.5 KiB
8.5 KiB
Powered by Onetrust
<img alt="Powered by Onetrust" src="https://cdn.cookielaw.org/logos/static/powered_by_logo.svg">
…static/powered_by_logo.svg
(cdn.cookielaw.org)
2.8 KiB
2.8 KiB
Avoid serving legacy JavaScript to modern browsers Potential savings of 7 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. However, many aren't necessary for modern browsers. For your bundled JavaScript, adopt a modern script deployment strategy using module/nomodule feature detection to reduce the amount of code shipped to modern browsers, while retaining support for legacy browsers. Learn how to use modern JavaScriptLCPFCP
URL
Potential Savings
Optanon
consent-provider
6.9 KiB
…202408.1.0/otBannerSdk.js
(cdn.cookielaw.org)
6.9 KiB
…202408.1.0/otBannerSdk.js:7:7371
(cdn.cookielaw.org)
Array.prototype.fill
dior.com
1st party
0.3 KiB
…chunks/dior-seller-header.d193a04485c5ffc6.js
(www.dior.com)
0.1 KiB
…chunks/dior-seller-header.d193a04485c5ffc6.js:1:8866
(www.dior.com)
@babel/plugin-transform-classes
…chunks/4920-eb849692b958b00a.js
(www.dior.com)
0.1 KiB
…chunks/4920-eb849692b958b00a.js:1:13865
(www.dior.com)
@babel/plugin-transform-classes
…chunks/4930-f0edee5b1564423e.js
(www.dior.com)
0.1 KiB
…chunks/4930-f0edee5b1564423e.js:1:22128
(www.dior.com)
@babel/plugin-transform-classes
…chunks/main-3ee40a2a2f5cb04c.js
(www.dior.com)
0.0 KiB
…chunks/main-3ee40a2a2f5cb04c.js:1:140174
(www.dior.com)
@babel/plugin-transform-classes
…pages/_app-c7aaa6e71a26c10d.js
(www.dior.com)
0.0 KiB
…pages/_app-c7aaa6e71a26c10d.js:14:405177
(www.dior.com)
@babel/plugin-transform-classes
Salesforce.com
ad
0.0 KiB
…utils/inert.min.js
(christiandior.my.salesforce.com)
0.0 KiB
…utils/inert.min.js:3:279
(christiandior.my.salesforce.com)
@babel/plugin-transform-classes
Avoid enormous network payloads Total size was 18,791 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
dam-broadcast.com
15,916.5 KiB
/pm_11872_932_932905-cxdprf6i0m.webm
(diorama.dam-broadcast.com)
8,961.9 KiB
/pm_11872_986_986914-q8pnbbr08b.webm
(diorama.dam-broadcast.com)
3,989.3 KiB
/pm_11872_986_986914-q8pnbbr08b.webm
(diorama.dam-broadcast.com)
2,965.3 KiB
dior.com
1st party
987.6 KiB
…pages/_app-c7aaa6e71a26c10d.js
(www.dior.com)
507.8 KiB
…AtacamaVAR/AtacamaVAR-VF.woff2
(www.dior.com)
250.5 KiB
…9876636/api_static.js
(www.dior.com)
115.9 KiB
…9876636/api_dynamic.js
(www.dior.com)
113.4 KiB
Google Tag Manager
tag-manager
245.6 KiB
/gtm.js?id=GTM-KKVBDVG&l=dataLayer&gtm=45He52k0v916…za200
(www.googletagmanager.com)
137.7 KiB
/gtm.js?id=GTM-M75MVP67
(www.googletagmanager.com)
107.9 KiB
Optanon
consent-provider
111.0 KiB
…202408.1.0/otBannerSdk.js
(cdn.cookielaw.org)
111.0 KiB
Avoid long main-thread tasks 20 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay. Learn how to avoid long main-thread tasksTBT
URL
Start Time
Duration
dior.com
1st party
3,996 ms
…chunks/framework-a32fdada02556615.js
(www.dior.com)
16,451 ms
833 ms
…chunks/main-3ee40a2a2f5cb04c.js
(www.dior.com)
15,179 ms
546 ms
…chunks/framework-a32fdada02556615.js
(www.dior.com)
18,132 ms
537 ms
…chunks/framework-a32fdada02556615.js
(www.dior.com)
15,992 ms
408 ms
…chunks/framework-a32fdada02556615.js
(www.dior.com)
14,702 ms
406 ms
…%5Buniverse%5D/%5B%5B...path%5D%5D-8d1d20fdd7f41e90.js
(www.dior.com)
15,725 ms
267 ms
…chunks/framework-a32fdada02556615.js
(www.dior.com)
17,482 ms
202 ms
…9876636/api_dynamic.js
(www.dior.com)
4,652 ms
156 ms
…9876636/api_static.js
(www.dior.com)
6,549 ms
143 ms
…chunks/framework-a32fdada02556615.js
(www.dior.com)
17,746 ms
138 ms
…chunks/framework-a32fdada02556615.js
(www.dior.com)
17,324 ms
115 ms
/fr_fr/fashion
(www.dior.com)
1,665 ms
112 ms
…chunks/framework-a32fdada02556615.js
(www.dior.com)
15,108 ms
71 ms
…chunks/framework-a32fdada02556615.js
(www.dior.com)
17,684 ms
62 ms
Google Tag Manager
tag-manager
628 ms
/gtm.js?id=GTM-5NT5ZL8
(www.googletagmanager.com)
4,136 ms
425 ms
/gtm.js?id=GTM-M75MVP67
(www.googletagmanager.com)
6,236 ms
141 ms
/gtm.js?id=GTM-KKVBDVG&l=dataLayer&gtm=45He52k0v916…za200
(www.googletagmanager.com)
8,362 ms
62 ms
Optanon
consent-provider
328 ms
/scripttemplates/otSDKStub.js
(cdn.cookielaw.org)
6,377 ms
172 ms
…202408.1.0/otBannerSdk.js
(cdn.cookielaw.org)
17,905 ms
156 ms
Unattributable
176 ms
Unattributable
8,443 ms
176 ms
User Timing marks and measures 11 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.
Next.jsConsider using Next.js Analytics to measure your app's real-world performance. Learn more.
Name
Type
Start Time
Duration
Next.js-before-hydration
Measure
0.00 ms
2,227.30 ms
Next.js-hydration
Measure
2,227.30 ms
702.23 ms
beforeRender
Mark
2,227.30 ms
routeChange
Mark
2,928.89 ms
afterHydrate
Mark
2,929.53 ms
clearMarks
Mark
2,929.87 ms
clearMarks
Mark
2,929.88 ms
clearMarks
Mark
2,929.89 ms
clearMarks
Mark
2,929.89 ms
beforeRender
Mark
4,285.16 ms
afterRender
Mark
7,313.58 ms
Avoid non-composited animations 7 animated elements found
Animations which are not composited can be janky and increase CLS. Learn how to avoid non-composited animationsCLS
Element
Name
div.MuiBox-root > div.MuiFormControl-root > div.MuiInputBase-root > input#emailNewsletter
<input aria-invalid="false" aria-describedby="emailNewsletter-helper-text" autocomplete="email" id="emailNewsletter" required="" type="email" class="MuiInputBase-input MuiOutlinedInput-input mui-42uqqw" value="">
Unsupported CSS Property: display
mui-auto-fill-cancel
Ouvrir le menu
<button id="menuburger" class="Menu_burgerButton__KyYuf" aria-expanded="false" aria-haspopup="true" aria-label="Ouvrir le menu" style="opacity:1">
Effect has unsupported timing parameters
main.main > div > header#mainheader > button
<button aria-expanded="false" aria-haspopup="true" style="display:flex;align-items:center;opacity:1">
Effect has unsupported timing parameters
Ouvrir la recherche
<button class="MuiButtonBase-root MuiTab-root MuiTab-textColorPrimary MuiTab-fullWidth pi…" tabindex="0" role="tab" aria-selected="false" name="Search" aria-label="Ouvrir la recherche" style="opacity: 1;">
Effect has unsupported timing parameters
Wishlists
<a class="MuiButtonBase-root MuiTab-root MuiTab-textColorPrimary MuiTab-fullWidth pi…" tabindex="0" role="button" aria-selected="false" name="Wishlist" aria-label="Wishlists" style="opacity: 1;">
Effect has unsupported timing parameters
Compte
<button class="MuiButtonBase-root MuiTab-root MuiTab-textColorPrimary MuiTab-fullWidth pi…" tabindex="0" role="tab" aria-selected="false" name="Account" aria-label="Compte" style="opacity: 1;">
Effect has unsupported timing parameters
"Nombre d'items dans le panier NaN"
<button class="MuiButtonBase-root MuiTab-root MuiTab-textColorPrimary MuiTab-fullWidth pi…" tabindex="0" role="tab" aria-selected="false" name="Cart" aria-label="&quot;Nombre d'items dans le panier NaN&quot;" style="opacity: 1;">
Effect has unsupported timing parameters
Initial server response time was short Root document took 90 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
dior.com
1st party
90 ms
/fr_fr/fashion
(www.dior.com)
90 ms
More information about the performance of your application. These numbers don't directly affect the Performance score.
Passed audits (20)
Show Hide
Eliminate render-blocking resources
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles. Learn how to eliminate render-blocking resources.LCPFCP
Next.jsUse the next/script component to defer loading of non-critical third-party scripts. Learn more.
Minify CSS
Minifying CSS files can reduce network payload sizes. Learn how to minify CSS.LCPFCP
Minify JavaScript
Minifying JavaScript files can reduce payload sizes and script parse time. Learn how to minify JavaScript.LCPFCP
Efficiently encode images
Optimized images load faster and consume less cellular data. Learn how to efficiently encode images.LCPFCP
Next.jsUse the next/image component instead of <img> to adjust image quality. Learn more.
Serve images in next-gen formats
Image formats like WebP and AVIF often provide better compression than PNG or JPEG, which means faster downloads and less data consumption. Learn more about modern image formats.LCPFCP
Next.jsUse the next/image component instead of <img> to automatically optimize image format. Learn more.
Enable text compression
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. Learn more about text compression.LCPFCP
Next.jsEnable compression on your Next.js server. Learn more.
Preconnect to required origins
Warnings:
  • A `<link rel=preconnect>` was found for "https://rcom-eu.dynamicyield.com" but was not used by the browser. Only use `preconnect` for important origins that the page will certainly request.
  • More than 2 `<link rel=preconnect>` connections were found. These should be used sparingly and only to the most important origins.
Consider adding preconnect or dns-prefetch resource hints to establish early connections to important third-party origins. Learn how to preconnect to required origins.LCPFCP
Avoid multiple page redirects
Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.LCPFCP
Use video formats for animated content
Large GIFs are inefficient for delivering animated content. Consider using MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF to save network bytes. Learn more about efficient video formatsLCPFCP
Remove duplicate modules in JavaScript bundles
Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity. LCPFCP
Preload Largest Contentful Paint image
If the LCP element is dynamically added to the page, you should preload the image in order to improve LCP. Learn more about preloading LCP elements.LCP
Next.jsUse the next/image component and set "priority" to true to preload LCP image. Learn more.
Avoid chaining critical requests
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: 251.982 ms
Initial Navigation
/fr_fr/fashion
(www.dior.com)
- 251.982 ms, 73.71 KiB
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
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().
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
Next.jsUse the next/image component to make sure images are always sized appropriately. Learn more.
Has a <meta name="viewport"> tag with width or initial-scale
A <meta name="viewport"> not only optimizes your app for mobile screen sizes, but also prevents a 300 millisecond delay to user input. Learn more about using the viewport meta tag.
92
Accessibility
These checks highlight opportunities to improve the accessibility of your web app. Automatic detection can only detect a subset of issues and does not guarantee the accessibility of your web app, so manual testing is also encouraged.
ARIA
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
Bienvenue sur dior.com Vous accédez depuis États-Unis d'Amérique, souhaitez-vo…
<div class="MuiPaper-root MuiPaper-elevation MuiPaper-rounded MuiPaper-elevation0 MuiD…" role="dialog" aria-labelledby=":r0:" aria-modal="true" data-testid="geolocation-popin" style="--Paper-shadow: none;">
ARIA IDs are unique
The value of an ARIA ID must be unique to prevent other instances from being overlooked by assistive technologies. Learn how to fix duplicate ARIA IDs.
Failing Elements
div.MuiCollapse-root > div.MuiCollapse-wrapper > div.MuiCollapse-wrapperInner > div#contact-content
<div aria-labelledby="contact-header" id="contact-content" role="region" class="MuiAccordion-region">
div.MuiCollapse-wrapper > div.MuiCollapse-wrapperInner > div#contact-content > div#contact-content
<div class="MuiAccordionDetails-root mui-1rrv0vl" id="contact-content" aria-labelledby="contact-header">
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Contrast
Background and foreground colors do not have a sufficient contrast ratio.
Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.
Failing Elements
Nouveauté
<span class="MuiTypography-root MuiTypography-label-m-regular DS-Typography copy-cell__…" style="color:#7B8487FF">
Fashion & Accessories Printemps-Été 2025 Raffinement intemporel et impulsions s…
<div class="MuiScopedCssBaseline-root mui-1urmbdg" style="background-color: rgb(248, 248, 248);">
Nouveau sac
<span class="MuiTypography-root MuiTypography-label-m-regular DS-Typography copy-cell__…" style="color:#7B8487FF">
Fashion & Accessories Printemps-Été 2025 Raffinement intemporel et impulsions s…
<div class="MuiScopedCssBaseline-root mui-1urmbdg" style="background-color: rgb(248, 248, 248);">
Contact
<p class="MuiTypography-root MuiTypography-label-m-regular DS-Typography mui-1pr1fuf">
Contact
<div class="MuiPaper-root MuiPaper-elevation MuiPaper-elevation0 MuiAccordion-root mui…" style="--Paper-shadow:none">
FAQ
<p class="MuiTypography-root MuiTypography-label-m-regular DS-Typography mui-1pr1fuf">
FAQ
<div class="MuiPaper-root MuiPaper-elevation MuiPaper-elevation0 MuiAccordion-root mui…" style="--Paper-shadow:none">
Index d'égalité femmes-hommes
<p class="MuiTypography-root MuiTypography-label-m-regular DS-Typography mui-1pr1fuf">
Index d'égalité femmes-hommes
<div class="MuiPaper-root MuiPaper-elevation MuiPaper-elevation0 MuiAccordion-root mui…" style="--Paper-shadow:none">
Mentions légales
<p class="MuiTypography-root MuiTypography-label-m-regular DS-Typography mui-1pr1fuf">
Mentions légales
<div class="MuiPaper-root MuiPaper-elevation MuiPaper-elevation0 MuiAccordion-root mui…" style="--Paper-shadow:none">
Notice de vie privée
<p class="MuiTypography-root MuiTypography-label-m-regular DS-Typography mui-1pr1fuf">
Notice de vie privée
<div class="MuiPaper-root MuiPaper-elevation MuiPaper-elevation0 MuiAccordion-root mui…" style="--Paper-shadow:none">
Gestion des cookies
<p class="MuiTypography-root MuiTypography-label-m-regular DS-Typography mui-1pr1fuf">
Retrait en boutique Commander en ligne et retirer vos articles dans la boutiqu…
<div class="MuiPaper-root MuiPaper-elevation MuiPaper-rounded MuiPaper-elevation0 DS-P…" style="--Paper-shadow:none">
Conditions générales de vente
<p class="MuiTypography-root MuiTypography-label-m-regular DS-Typography mui-1pr1fuf">
Conditions générales de vente
<div class="MuiPaper-root MuiPaper-elevation MuiPaper-elevation0 MuiAccordion-root mui…" style="--Paper-shadow:none">
Plan du site
<p class="MuiTypography-root MuiTypography-label-m-regular DS-Typography mui-1pr1fuf">
Retrait en boutique Commander en ligne et retirer vos articles dans la boutiqu…
<div class="MuiPaper-root MuiPaper-elevation MuiPaper-rounded MuiPaper-elevation0 DS-P…" style="--Paper-shadow:none">
Pays/Région
<p class="MuiTypography-root MuiTypography-label-m-regular DS-Typography mui-erpn9y">
Retrait en boutique Commander en ligne et retirer vos articles dans la boutiqu…
<div class="MuiPaper-root MuiPaper-elevation MuiPaper-rounded MuiPaper-elevation0 DS-P…" style="--Paper-shadow:none">
Vous accédez depuis États-Unis d'Amérique, souhaitez-vous consulter notre site …
<p class="MuiTypography-root MuiTypography-body-s MuiTypography-alignCenter DS-Typog…" style="--Typography-textAlign: center;">
Bienvenue sur dior.com Vous accédez depuis États-Unis d'Amérique, souhaitez-vo…
<div class="MuiPaper-root MuiPaper-elevation MuiPaper-rounded MuiPaper-elevation0 MuiD…" role="dialog" aria-labelledby=":r0:" aria-modal="true" data-testid="geolocation-popin" style="--Paper-shadow: none;">
These are opportunities to improve the legibility of your content.
Additional items to manually check (10)
Show Hide
Interactive controls are keyboard focusable
Custom interactive controls are keyboard focusable and display a focus indicator. Learn how to make custom controls focusable.
Interactive elements indicate their purpose and state
Interactive elements, such as links and buttons, should indicate their state and be distinguishable from non-interactive elements. Learn how to decorate interactive elements with affordance hints.
The page has a logical tab order
Tabbing through the page follows the visual layout. Users cannot focus elements that are offscreen. Learn more about logical tab ordering.
Visual order on the page follows DOM order
DOM order matches the visual order, improving navigation for assistive technology. Learn more about DOM and visual ordering.
User focus is not accidentally trapped in a region
A user can tab into and out of any control or region without accidentally trapping their focus. Learn how to avoid focus traps.
The user's focus is directed to new content added to the page
If new content, such as a dialog, is added to the page, the user's focus is directed to it. Learn how to direct focus to new content.
HTML5 landmark elements are used to improve navigation
Landmark elements (<main>, <nav>, etc.) are used to improve the keyboard navigation of the page for assistive technology. Learn more about landmark elements.
Offscreen content is hidden from assistive technology
Offscreen content is hidden with display: none or aria-hidden=true. Learn how to properly hide offscreen content.
Custom controls have associated labels
Custom interactive controls have associated labels, provided by aria-label or aria-labelledby. Learn more about custom controls and labels.
Custom controls have ARIA roles
Custom interactive controls have appropriate ARIA roles. Learn how to add roles to custom controls.
These items address areas which an automated testing tool cannot cover. Learn more in our guide on conducting an accessibility review.
Passed audits (21)
Show Hide
[aria-*] attributes match their roles
Each ARIA role supports a specific subset of aria-* attributes. Mismatching these invalidates the aria-* attributes. Learn how to match ARIA attributes to their roles.
[aria-hidden="true"] is not present on the document <body>
Assistive technologies, like screen readers, work inconsistently when aria-hidden="true" is set on the document <body>. Learn how aria-hidden affects the document body.
[role]s have all required [aria-*] attributes
Some ARIA roles have required attributes that describe the state of the element to screen readers. Learn more about roles and required attributes.
[aria-*] attributes have valid values
Assistive technologies, like screen readers, can't interpret ARIA attributes with invalid values. Learn more about valid values for ARIA attributes.
[aria-*] attributes are valid and not misspelled
Assistive technologies, like screen readers, can't interpret ARIA attributes with invalid names. Learn more about valid ARIA attributes.
Buttons have an accessible name
When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.
[user-scalable="no"] is not used in the <meta name="viewport"> element and the [maximum-scale] attribute is not less than 5.
Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a web page. Learn more about the viewport meta tag.
ARIA attributes are used as specified for the element's role
Some ARIA attributes are only allowed on an element under certain conditions. Learn more about conditional ARIA attributes.
[aria-hidden="true"] elements do not contain focusable descendents
Focusable descendents within an [aria-hidden="true"] element prevent those interactive elements from being available to users of assistive technologies like screen readers. Learn how aria-hidden affects focusable elements.
Elements use only permitted ARIA attributes
Using ARIA attributes in roles where they are prohibited can mean that important information is not communicated to users of assistive technologies. Learn more about prohibited ARIA roles.
[role] values are valid
ARIA roles must have valid values in order to perform their intended accessibility functions. Learn more about valid ARIA roles.
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.
Links are distinguishable without relying on color.
Low-contrast text is difficult or impossible for many users to read. Link text that is discernible improves the experience for users with low vision. Learn how to make links distinguishable.
Links have a discernible name
Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.
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.
Heading elements appear in a sequentially-descending order
Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.
Uses ARIA roles only on compatible elements
Many HTML elements can only be assigned certain ARIA roles. Using ARIA roles where they are not allowed can interfere with the accessibility of the web page. Learn more about ARIA roles.
Deprecated ARIA roles were not used
Deprecated ARIA roles may not be processed correctly by assistive technology. Learn more about deprecated ARIA roles.
Not applicable (33)
Show Hide
[accesskey] values are unique
Access keys let users quickly focus a part of the page. For proper navigation, each access key must be unique. Learn more about access keys.
button, link, and menuitem elements have accessible names
When an element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn how to make command elements more accessible.
ARIA input fields have accessible names
When an input field doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn more about input field labels.
ARIA meter elements have accessible names
When a meter element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn how to name meter elements.
ARIA progressbar elements have accessible names
When a progressbar element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn how to label progressbar elements.
Elements with an ARIA [role] that require children to contain a specific [role] have all required children.
Some ARIA parent roles must contain specific child roles to perform their intended accessibility functions. Learn more about roles and required children elements.
[role]s are contained by their required parent element
Some ARIA child roles must be contained by specific parent roles to properly perform their intended accessibility functions. Learn more about ARIA roles and required parent element.
Elements with the role=text attribute do not have focusable descendents.
Adding role=text around a text node split by markup enables VoiceOver to treat it as one phrase, but the element's focusable descendents will not be announced. Learn more about the role=text attribute.
ARIA toggle fields have accessible names
When a toggle field doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn more about toggle fields.
ARIA tooltip elements have accessible names
When a tooltip element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn how to name tooltip elements.
ARIA treeitem elements have accessible names
When a treeitem element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn more about labeling treeitem elements.
The page contains a heading, skip link, or landmark region
Adding ways to bypass repetitive content lets keyboard users navigate the page more efficiently. Learn more about bypass blocks.
<dl>'s contain only properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements.
When definition lists are not properly marked up, screen readers may produce confusing or inaccurate output. Learn how to structure definition lists correctly.
Definition list items are wrapped in <dl> elements
Definition list items (<dt> and <dd>) must be wrapped in a parent <dl> element to ensure that screen readers can properly announce them. Learn how to structure definition lists correctly.
No form fields have multiple labels
Form fields with multiple labels can be confusingly announced by assistive technologies like screen readers which use either the first, the last, or all of the labels. Learn how to use form labels.
<frame> or <iframe> elements have a title
Screen reader users rely on frame titles to describe the contents of frames. Learn more about frame titles.
<html> element has an [xml:lang] attribute with the same base language as the [lang] attribute.
If the webpage does not specify a consistent language, then the screen reader might not announce the page's text correctly. Learn more about the lang attribute.
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.
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.
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.
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.
The document does not use <meta http-equiv="refresh">
Users do not expect a page to refresh automatically, and doing so will move focus back to the top of the page. This may create a frustrating or confusing experience. Learn more about the refresh meta tag.
<object> elements have alternate text
Screen readers cannot translate non-text content. Adding alternate text to <object> elements helps screen readers convey meaning to users. Learn more about alt text for object elements.
Select elements have associated label elements.
Form elements without effective labels can create frustrating experiences for screen reader users. Learn more about the select element.
Tables have different content in the summary attribute and <caption>.
The summary attribute should describe the table structure, while <caption> should have the onscreen title. Accurate table mark-up helps users of screen readers. Learn more about summary and caption.
Cells in a <table> element that use the [headers] attribute refer to table cells within the same table.
Screen readers have features to make navigating tables easier. Ensuring <td> cells using the [headers] attribute only refer to other cells in the same table may improve the experience for screen reader users. Learn more about the headers attribute.
<th> elements and elements with [role="columnheader"/"rowheader"] have data cells they describe.
Screen readers have features to make navigating tables easier. Ensuring table headers always refer to some set of cells may improve the experience for screen reader users. Learn more about table headers.
[lang] attributes have a valid value
Specifying a valid BCP 47 language on elements helps ensure that text is pronounced correctly by a screen reader. Learn how to use the lang attribute.
<video> elements contain a <track> element with [kind="captions"]
When a video provides a caption it is easier for deaf and hearing impaired users to access its information. Learn more about video captions.
96
Best Practices
General
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
Salesforce Live Agent
customer-success
…EmbeddedService/EmbeddedS….jsonp?Settings.prefix=…:1:0
(d.la2-c2-cdg.salesforceliveagent.com)
Failed to load resource: net::ERR_TIMED_OUT
Launch Darkly
utility
…63750fc…/eyJraW5kI…:1:0
(clientstream.launchdarkly.com)
Failed to load resource: net::ERR_TIMED_OUT
Detected JavaScript libraries
All front-end JavaScript libraries detected on the page. Learn more about this JavaScript library detection diagnostic audit.
Name
Version
Next.js
14.2.18
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
dior.com
1st party
…9876636/api_dynamic.js
(www.dior.com)
Large JavaScript file is missing a source map
…pages/_app-c7aaa6e71a26c10d.js
(www.dior.com)
Large JavaScript file is missing a source map
Riskified
utility
/?shop=www.dior.com&sid=88dc7126-9158-4322-95c0-b3a21381b7a1
(beacon.riskified.com)
…d3d3LmRpb3IuY29t/ODhkYzcxM…
(beacon.riskified.com)
Warning: missing 1 item in `.sourcesContent`
Trust and Safety
Ensure CSP is effective against XSS attacks
A strong Content Security Policy (CSP) significantly reduces the risk of cross-site scripting (XSS) attacks. Learn how to use a CSP to prevent XSS
Description
Directive
Severity
No CSP found in enforcement mode
High
Passed audits (13)
Show Hide
Uses HTTPS
All sites should be protected with HTTPS, even ones that don't handle sensitive data. This includes avoiding mixed content, where some resources are loaded over HTTP despite the initial request being served over HTTPS. HTTPS prevents intruders from tampering with or passively listening in on the communications between your app and your users, and is a prerequisite for HTTP/2 and many new web platform APIs. Learn more about HTTPS.
Avoids deprecated APIs
Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs.
Avoids third-party cookies
Chrome is moving towards a new experience that allows users to choose to browse without third-party cookies. Learn more about third-party cookies.
Allows users to paste into input fields
Preventing input pasting is a bad practice for the UX, and weakens security by blocking password managers.Learn more about user-friendly input fields.
Avoids requesting the geolocation permission on page load
Users are mistrustful of or confused by sites that request their location without context. Consider tying the request to a user action instead. Learn more about the geolocation permission.
Avoids requesting the notification permission on page load
Users are mistrustful of or confused by sites that request to send notifications without context. Consider tying the request to user gestures instead. Learn more about responsibly getting permission for notifications.
Displays images with correct aspect ratio
Image display dimensions should match natural aspect ratio. Learn more about image aspect ratio.
Serves images with appropriate resolution
Image natural dimensions should be proportional to the display size and the pixel ratio to maximize image clarity. Learn how to provide responsive images.
Has a <meta name="viewport"> tag with width or initial-scale
A <meta name="viewport"> not only optimizes your app for mobile screen sizes, but also prevents a 300 millisecond delay to user input. Learn more about using the viewport meta tag.
Document uses legible font sizes 79.33% legible text
Font sizes less than 12px are too small to be legible and require mobile visitors to “pinch to zoom” in order to read. Strive to have >60% of page text ≥12px. Learn more about legible font sizes.
Source
Selector
% of Page Text
Font Size
Unattributable
dynamic
#onetrust-banner-sdk #onetrust-policy-text, #onetrust-banner-sdk .ot-b-addl-desc, #onetrust-banner-sdk .ot-gv-list-handler
20.40%
11.382px
dynamic
#onetrust-banner-sdk #onetrust-policy-text *, #onetrust-banner-sdk .ot-b-addl-desc *, #onetrust-banner-sdk .ot-gv-list-handler *
0.20%
11.382px
Legible text
79.33%
≥ 12px
dior.com
1st party
/fr_fr/fashion:43:47746
(www.dior.com)
.mui-81qg8w
0.07%
10.5px
Page has the HTML doctype
Specifying a doctype prevents the browser from switching to quirks-mode. Learn more about the doctype declaration.
Properly defines charset
A character encoding declaration is required. It can be done with a <meta> tag in the first 1024 bytes of the HTML or in the Content-Type HTTP response header. Learn more about declaring the character encoding.
No issues in the Issues panel in Chrome Devtools
Issues logged to the Issues panel in Chrome Devtools indicate unresolved problems. They can come from network request failures, insufficient security controls, and other browser concerns. Open up the Issues panel in Chrome DevTools for more details on each issue.
Not applicable (1)
Show Hide
Redirects HTTP traffic to HTTPS
Make sure that you redirect all HTTP traffic to HTTPS in order to enable secure web features for all your users. Learn more.
100
SEO
These checks ensure that your page is following basic search engine optimization advice. There are many additional factors Lighthouse does not score here that may affect your search ranking, including performance on Core Web Vitals. Learn more about Google Search Essentials.
Additional items to manually check (1)
Show Hide
Structured data is valid
Run the Structured Data Testing Tool and the Structured Data Linter to validate structured data. Learn more about Structured Data.
Run these additional validators on your site to check additional SEO best practices.
Passed audits (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 have descriptive text
Descriptive link text helps search engines understand your content. Learn how to make links more accessible.
Links are crawlable
Search engines may use href attributes on links to crawl websites. Ensure that the href attribute of anchor elements links to an appropriate destination, so more pages of the site can be discovered. Learn how to make links crawlable
robots.txt is valid
If your robots.txt file is malformed, crawlers may not be able to understand how you want your website to be crawled or indexed. Learn more about robots.txt.
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.
Not applicable (1)
Show Hide
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.
Discover what your real users are experiencing
Core Web Vitals Assessment: Failed
Largest Contentful Paint (LCP)
2.4 s
Page LoadsGood (≤ 2.5 s)76%Needs Improvement (2.5 s - 4 s)13%Poor (> 4 s)11%75th Percentile - 2.4 sCore Web Vital
Interaction to Next Paint (INP)
293 ms
Page LoadsGood (≤ 200 ms)64%Needs Improvement (200 ms - 500 ms)22%Poor (> 500 ms)15%75th Percentile - 293 msCore Web Vital
Cumulative Layout Shift (CLS)
0.01
Page LoadsGood (≤ 0.1)88%Needs Improvement (0.1 - 0.25)5%Poor (> 0.25)6%75th Percentile - 0.01Core Web Vital
Other Notable Metrics
First Contentful Paint (FCP)
1.1 s
Page LoadsGood (≤ 1.8 s)89%Needs Improvement (1.8 s - 3 s)8%Poor (> 3 s)3%75th Percentile - 1.1 s 
Time to First Byte (TTFB)
0.5 s
Page LoadsGood (≤ 0.8 s)86%Needs Improvement (0.8 s - 1.8 s)10%Poor (> 1.8 s)3%75th Percentile - 0.5 sExperimental
Latest 28-day collection period
Various desktop devicesMany samples (Chrome UX Report)Full visit durationsVarious network connectionsAll Chrome versions
Core Web Vitals Assessment: Passed
Largest Contentful Paint (LCP)
2.4 s
Page LoadsGood (≤ 2.5 s)76%Needs Improvement (2.5 s - 4 s)15%Poor (> 4 s)9%75th Percentile - 2.4 sCore Web Vital
Interaction to Next Paint (INP)
176 ms
Page LoadsGood (≤ 200 ms)78%Needs Improvement (200 ms - 500 ms)14%Poor (> 500 ms)8%75th Percentile - 176 msCore Web Vital
Cumulative Layout Shift (CLS)
0.05
Page LoadsGood (≤ 0.1)87%Needs Improvement (0.1 - 0.25)7%Poor (> 0.25)6%75th Percentile - 0.05Core Web Vital
Other Notable Metrics
First Contentful Paint (FCP)
2 s
Page LoadsGood (≤ 1.8 s)70%Needs Improvement (1.8 s - 3 s)19%Poor (> 3 s)11%75th Percentile - 2 s 
Time to First Byte (TTFB)
0.7 s
Page LoadsGood (≤ 0.8 s)80%Needs Improvement (0.8 s - 1.8 s)16%Poor (> 1.8 s)4%75th Percentile - 0.7 sExperimental
Latest 28-day collection period
Various desktop devicesMany samples (Chrome UX Report)Full visit durationsVarious network connectionsAll Chrome versions
Diagnose performance issues
37
Performance
92
Accessibility
96
Best Practices
100
SEO
37
Performance
92
Accessibility
96
Best Practices
100
SEO
37 FCP+10LCP+2TBT+0CLS+25SI+0 Performance
Values are estimated and may vary. The performance score is calculated directly from these metrics.See calculator.
0–49 50–89 90–100
Final Screenshot
Metrics
First Contentful Paint
0.7 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
5.3 s
Largest Contentful Paint marks the time at which the largest text or image is painted. Learn more about the Largest Contentful Paint metric
Total Blocking Time
3,460 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
6.3 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more about the Speed Index metric.
  • Captured at Feb 22, 2025, 8:00 AM UTC
  • Emulated Desktop with Lighthouse 12.2.3
    Unthrottled CPU/Memory Power: 304 CPU throttling: 1x slowdown (Simulated) Screen emulation: 1350x940, DPR 1 Axe version: 4.10.2
  • Single page session
    This data is taken from a single page session, as opposed to field data summarizing many sessions.
  • Initial page load
  • Custom throttling
    Network throttling: 40 ms TCP RTT, 10,240 kb/s throughput (Simulated) Browser location: North America
  • Using HeadlessChromium 133.0.6943.53 with lr
    User agent (network): "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/119.0.0.0 Safari/537.36"
Screenshot
Screenshot
Screenshot
Screenshot
Screenshot
Screenshot
Screenshot
Screenshot
Show audits relevant to:
Diagnostics
Minimize main-thread work 7.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 minimize main-thread workTBT
Category
Time Spent
Script Evaluation
4,769 ms
Style & Layout
1,235 ms
Garbage Collection
497 ms
Other
309 ms
Script Parsing & Compilation
235 ms
Parse HTML & CSS
71 ms
Rendering
61 ms
Largest Contentful Paint element 5,300 ms
This is the largest contentful element painted within the viewport. Learn more about the Largest Contentful Paint elementLCP
Element
We use cookies, including third party cookies, for operational purposes, statis…
<div id="onetrust-policy-text">
Phase
% of LCP
Timing
TTFB
3%
160 ms
Load Delay
0%
0 ms
Load Time
0%
0 ms
Render Delay
97%
5,140 ms
Reduce JavaScript execution time 4.8 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to reduce Javascript execution time.TBT
URL
Total CPU Time
Script Evaluation
Script Parse
dior.com
1st party
5,811 ms
4,008 ms
109 ms
…chunks/framework-a32fdada02556615.js
(www.dior.com)
3,877 ms
3,041 ms
3 ms
/fr_fr/fashion
(www.dior.com)
616 ms
5 ms
1 ms
…pages/_app-c7aaa6e71a26c10d.js
(www.dior.com)
531 ms
413 ms
46 ms
…%5Buniverse%5D/%5B%5B...path%5D%5D-8d1d20fdd7f41e90.js
(www.dior.com)
280 ms
201 ms
1 ms
…9876636/api_static.js
(www.dior.com)
242 ms
166 ms
11 ms
…9876636/api_dynamic.js
(www.dior.com)
128 ms
101 ms
27 ms
…chunks/main-3ee40a2a2f5cb04c.js
(www.dior.com)
84 ms
67 ms
16 ms
…chunks/4951.435fd113d844f634.js
(www.dior.com)
53 ms
13 ms
4 ms
Optanon
consent-provider
458 ms
239 ms
10 ms
…202408.1.0/otBannerSdk.js
(cdn.cookielaw.org)
276 ms
75 ms
9 ms
/scripttemplates/otSDKStub.js
(cdn.cookielaw.org)
183 ms
164 ms
1 ms
Unattributable
353 ms
100 ms
0 ms
Unattributable
353 ms
100 ms
0 ms
Google Tag Manager
tag-manager
329 ms
277 ms
51 ms
/gtm.js?id=GTM-M75MVP67
(www.googletagmanager.com)
190 ms
182 ms
8 ms
/gtm.js?id=GTM-KKVBDVG&l=dataLayer&gtm=45He52k0v916…za200
(www.googletagmanager.com)
75 ms
62 ms
12 ms
/gtm.js?id=GTM-5NT5ZL8
(www.googletagmanager.com)
64 ms
32 ms
32 ms
Riskified
utility
53 ms
50 ms
1 ms
/?shop=www.dior.com&sid=39b21053-5a00-4b29-81f6-01328f685209
(beacon.riskified.com)
53 ms
50 ms
1 ms
Reduce unused JavaScript Potential savings of 478 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
Next.jsUse Webpack Bundle Analyzer to detect unused JavaScript code. Learn more
URL
Transfer Size
Potential Savings
dior.com
1st party
632.2 KiB
239.4 KiB
…pages/_app-c7aaa6e71a26c10d.js
(www.dior.com)
488.6 KiB
150.6 KiB
…9876636/api_static.js
(www.dior.com)
114.8 KiB
63.9 KiB
…chunks/1420-aa28d7f7ac15740e.js
(www.dior.com)
28.8 KiB
24.9 KiB
Google Tag Manager
tag-manager
443.7 KiB
179.3 KiB
/gtm.js?id=GTM-KKVBDVG&l=dataLayer&gtm=45He52k0v916…za200
(www.googletagmanager.com)
136.6 KiB
53.9 KiB
/gtm.js?id=GTM-5NT5ZL8
(www.googletagmanager.com)
99.7 KiB
51.4 KiB
/gtm.js?id=GTM-5NT5ZL8
(www.googletagmanager.com)
99.7 KiB
37.1 KiB
/gtm.js?id=GTM-M75MVP67
(www.googletagmanager.com)
107.7 KiB
36.9 KiB
Optanon
consent-provider
110.1 KiB
59.2 KiB
…202408.1.0/otBannerSdk.js
(cdn.cookielaw.org)
110.1 KiB
59.2 KiB
Avoid an excessive DOM size 2,940 elements
A large DOM will increase memory usage, cause longer style calculations, and produce costly layout reflows. Learn how to avoid an excessive DOM size.TBT
Statistic
Element
Value
Total DOM Elements
2,940
Maximum DOM Depth
li > a.NavigationLink_navigationLink__uTNLK > svg.MuiSvgIcon-root > path
<path fill="currentColor" d="M14 12a2 2 0 1 1-4 0 2 2 0 0 1 4 0">
23
Maximum Child Elements
body.js-focus-visible
<body class="js-focus-visible" style="padding-right: 15px; overflow: hidden;">
22
Reduce the impact of third-party code Third-party code blocked the main thread for 260 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
Optanon
consent-provider
190 KiB
204 ms
/scripttemplates/otSDKStub.js
(cdn.cookielaw.org)
8 KiB
125 ms
…202408.1.0/otBannerSdk.js
(cdn.cookielaw.org)
111 KiB
79 ms
…0192f77d-fb93-78fd-85db-1dd6c89e3ca1/en.json
(cdn.cookielaw.org)
32 KiB
0 ms
…v2/otPcCenter.json
(cdn.cookielaw.org)
13 KiB
0 ms
…static/ot_company_logo.png
(cdn.cookielaw.org)
9 KiB
0 ms
…assets/otCommonStyles.css
(cdn.cookielaw.org)
5 KiB
0 ms
…assets/otCenterRounded.json
(cdn.cookielaw.org)
3 KiB
0 ms
…7d443084-35a1-4e89-8253-4ed5a4974685/7d443084-35a1-4e89-8….json
(cdn.cookielaw.org)
3 KiB
0 ms
…static/powered_by_logo.svg
(cdn.cookielaw.org)
3 KiB
0 ms
…static/ot_guard_logo.svg
(cdn.cookielaw.org)
1 KiB
0 ms
…geo/location
(geolocation.onetrust.com)
0 KiB
0 ms
Google Tag Manager
tag-manager
347 KiB
60 ms
/gtm.js?id=GTM-M75MVP67
(www.googletagmanager.com)
109 KiB
60 ms
/gtm.js?id=GTM-KKVBDVG&l=dataLayer&gtm=45He52k0v916…za200
(www.googletagmanager.com)
138 KiB
0 ms
/gtm.js?id=GTM-5NT5ZL8
(www.googletagmanager.com)
101 KiB
0 ms
dam-broadcast.com
17,059 KiB
0 ms
/pm_11872_932_932863-4xg9owjbwp.webm
(diorama.dam-broadcast.com)
9,306 KiB
0 ms
/pm_11872_949_949366-6vjso0wq3i.webm
(diorama.dam-broadcast.com)
7,407 KiB
0 ms
…width=1440,format=auto/pm_11872_946_946906-mrcoldsj3v-whr.jpg
(diorama.dam-broadcast.com)
115 KiB
0 ms
…width=1440,format=auto/pm_11872_865_865561-i216y17bj9-whr.jpg
(diorama.dam-broadcast.com)
107 KiB
0 ms
…width=1280,format=auto/pm_11872_948_948958-uq3cp17r5k-whr.jpg
(diorama.dam-broadcast.com)
56 KiB
0 ms
…width=460,format=auto/pm_11872_948_948649-wfalqu39sc-whr.jpg
(diorama.dam-broadcast.com)
31 KiB
0 ms
…width=460,format=auto/pm_11872_948_948640-ad1dldptf2-whr.jpg
(diorama.dam-broadcast.com)
24 KiB
0 ms
…width=460,format=auto/pm_11872_948_948655-007279e2p2-whr.jpg
(diorama.dam-broadcast.com)
14 KiB
0 ms
Dynamic Yield
customer-success
44 KiB
0 ms
…2.48.0/dy-coll-nojq-min.js
(cdn-eu.dynamicyield.com)
33 KiB
0 ms
/st?sec=…
(st-eu.dynamicyield.com)
11 KiB
0 ms
Riskified
utility
17 KiB
0 ms
/?shop=www.dior.com&sid=39b21053-5a00-4b29-81f6-01328f685209
(beacon.riskified.com)
15 KiB
0 ms
/v2/client_infos
(c.riskified.com)
1 KiB
0 ms
/img/image-l.gif?t=…
(img.riskified.com)
0 KiB
0 ms
/img/image-l.gif?t=…
(img.riskified.com)
0 KiB
0 ms
/img/image-l.gif?t=…
(img.riskified.com)
0 KiB
0 ms
/img/image-l.gif?t=…
(img.riskified.com)
0 KiB
0 ms
/img/image-l.gif?t=…
(img.riskified.com)
0 KiB
0 ms
Salesforce.com
ad
9 KiB
0 ms
…5.0/esw.min.js
(christiandior.my.salesforce.com)
9 KiB
0 ms
…utils/common.min.js
(christiandior.my.salesforce.com)
0 KiB
0 ms
Launch Darkly
utility
7 KiB
0 ms
…contexts/eyJraW5kI…
(app.launchdarkly.com)
3 KiB
0 ms
…goals/63750fc…
(app.launchdarkly.com)
2 KiB
0 ms
…diagnostic/63750fc…
(events.launchdarkly.com)
1 KiB
0 ms
…bulk/63750fc…
(events.launchdarkly.com)
1 KiB
0 ms
…63750fc…/eyJraW5kI…
(clientstream.launchdarkly.com)
0 KiB
0 ms
booxi.eu
3 KiB
0 ms
/booknow/booknow.js
(www.booxi.eu)
3 KiB
0 ms
Serve static assets with an efficient cache policy 35 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more about efficient cache policies.
Next.jsConfigure caching for immutable assets and Server-side Rendered (SSR) pages. Learn more.
URL
Cache TTL
Transfer Size
dam-broadcast.com
17,059 KiB
/pm_11872_932_932863-4xg9owjbwp.webm
(diorama.dam-broadcast.com)
2d
9,306 KiB
/pm_11872_949_949366-6vjso0wq3i.webm
(diorama.dam-broadcast.com)
2d
4,208 KiB
/pm_11872_949_949366-6vjso0wq3i.webm
(diorama.dam-broadcast.com)
2d
3,184 KiB
…width=1440,format=auto/pm_11872_946_946906-mrcoldsj3v-whr.jpg
(diorama.dam-broadcast.com)
2d
115 KiB
…width=1440,format=auto/pm_11872_865_865561-i216y17bj9-whr.jpg
(diorama.dam-broadcast.com)
2d
107 KiB
…width=1280,format=auto/pm_11872_948_948958-uq3cp17r5k-whr.jpg
(diorama.dam-broadcast.com)
2d
56 KiB
…width=460,format=auto/pm_11872_948_948649-wfalqu39sc-whr.jpg
(diorama.dam-broadcast.com)
2d
31 KiB
…width=460,format=auto/pm_11872_948_948640-ad1dldptf2-whr.jpg
(diorama.dam-broadcast.com)
2d
24 KiB
/pm_11872_949_949366-6vjso0wq3i.webm
(diorama.dam-broadcast.com)
2d
16 KiB
…width=460,format=auto/pm_11872_948_948655-007279e2p2-whr.jpg
(diorama.dam-broadcast.com)
2d
14 KiB
dior.com
1st party
708 KiB
…9876636/api_dynamic.js
(www.dior.com)
30s
113 KiB
…9876636/api_static.js
(www.dior.com)
8h
116 KiB
…AtacamaVAR/AtacamaVAR-VF.woff2
(www.dior.com)
90d
251 KiB
…Semi-bold/Hellix-SemiBold.woff2
(www.dior.com)
90d
43 KiB
…Bold/Hellix-Bold.woff2
(www.dior.com)
90d
43 KiB
…Medium/Hellix-Medium.woff2
(www.dior.com)
90d
43 KiB
…Regular/Hellix-Regular.woff2
(www.dior.com)
90d
43 KiB
…Light/Hellix-Light.woff2
(www.dior.com)
90d
41 KiB
…fonts/DiorSymbols-Regular.otf
(www.dior.com)
90d
10 KiB
…livechat/livechat.js
(www.dior.com)
90d
3 KiB
…Hellix/Hellix.css
(www.dior.com)
90d
1 KiB
…livechat/livechat.css
(www.dior.com)
90d
1 KiB
…AtacamaVAR/AtacamaVAR.css
(www.dior.com)
90d
1 KiB
Optanon
consent-provider
132 KiB
…202408.1.0/otBannerSdk.js
(cdn.cookielaw.org)
1d
111 KiB
…static/ot_company_logo.png
(cdn.cookielaw.org)
1d
9 KiB
/scripttemplates/otSDKStub.js
(cdn.cookielaw.org)
1d
8 KiB
…static/powered_by_logo.svg
(cdn.cookielaw.org)
1d
3 KiB
Riskified
utility
16 KiB
/img/image-l.gif?t=…
(img.riskified.com)
None
0 KiB
/img/image-l.gif?t=…
(img.riskified.com)
None
0 KiB
/img/image-l.gif?t=…
(img.riskified.com)
None
0 KiB
/img/image-l.gif?t=…
(img.riskified.com)
None
0 KiB
/img/image-l.gif?t=…
(img.riskified.com)
None
0 KiB
/?shop=www.dior.com&sid=39b21053-5a00-4b29-81f6-01328f685209
(beacon.riskified.com)
10m
15 KiB
Salesforce.com
ad
9 KiB
…5.0/esw.min.js
(christiandior.my.salesforce.com)
1d
9 KiB
booxi.eu
3 KiB
/booknow/booknow.js
(www.booxi.eu)
1m
3 KiB
Properly size images Potential savings of 35 KiB
Serve images that are appropriately-sized to save cellular data and improve load time. Learn how to size images.LCPFCP
Next.jsUse the next/image component to set the appropriate sizes. Learn more.
URL
Resource Size
Potential Savings
dam-broadcast.com
161.4 KiB
34.9 KiB
div.MuiBox-root > a.MuiBox-root > div.DS-Image > img.MuiBox-root
<img class="MuiBox-root mui-soqdc0" alt="" src="https://diorama.dam-broadcast.com/cdn-cgi/image/width=1440,format=auto/pm_…" decoding="async" sizes="100vw" srcset="https://diorama.dam-broadcast.com/cdn-cgi/image/width=640,format=auto/pm_1…" loading="lazy" style="color:transparent">
…width=1440,format=auto/pm_11872_865_865561-i216y17bj9-whr.jpg
(diorama.dam-broadcast.com)
106.3 KiB
19.3 KiB
div.MuiBox-root > a.MuiBox-root > div.DS-Image > img.MuiBox-root
<img class="MuiBox-root mui-soqdc0" alt="" src="https://diorama.dam-broadcast.com/cdn-cgi/image/width=1280,format=auto/pm_…" decoding="async" sizes="83.33333333333334vw" srcset="https://diorama.dam-broadcast.com/cdn-cgi/image/width=55,format=auto/pm_11…" loading="lazy" style="color:transparent">
…width=1280,format=auto/pm_11872_948_948958-uq3cp17r5k-whr.jpg
(diorama.dam-broadcast.com)
55.0 KiB
15.7 KiB
Defer offscreen images Potential savings of 11 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
Next.jsUse the next/image component instead of <img> to automatically lazy-load images. Learn more.
URL
Resource Size
Potential Savings
Optanon
consent-provider
11.3 KiB
11.3 KiB
Company Logo
<img alt="Company Logo" src="https://cdn.cookielaw.org/logos/static/ot_company_logo.png">
…static/ot_company_logo.png
(cdn.cookielaw.org)
8.5 KiB
8.5 KiB
Powered by Onetrust
<img alt="Powered by Onetrust" src="https://cdn.cookielaw.org/logos/static/powered_by_logo.svg">
…static/powered_by_logo.svg
(cdn.cookielaw.org)
2.8 KiB
2.8 KiB
Avoid serving legacy JavaScript to modern browsers Potential savings of 7 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. However, many aren't necessary for modern browsers. For your bundled JavaScript, adopt a modern script deployment strategy using module/nomodule feature detection to reduce the amount of code shipped to modern browsers, while retaining support for legacy browsers. Learn how to use modern JavaScriptLCPFCP
URL
Potential Savings
Optanon
consent-provider
6.9 KiB
…202408.1.0/otBannerSdk.js
(cdn.cookielaw.org)
6.9 KiB
…202408.1.0/otBannerSdk.js:7:7371
(cdn.cookielaw.org)
Array.prototype.fill
dior.com
1st party
0.3 KiB
…chunks/dior-seller-header.d193a04485c5ffc6.js
(www.dior.com)
0.1 KiB
…chunks/dior-seller-header.d193a04485c5ffc6.js:1:8866
(www.dior.com)
@babel/plugin-transform-classes
…chunks/4920-eb849692b958b00a.js
(www.dior.com)
0.1 KiB
…chunks/4920-eb849692b958b00a.js:1:13865
(www.dior.com)
@babel/plugin-transform-classes
…chunks/4930-f0edee5b1564423e.js
(www.dior.com)
0.1 KiB
…chunks/4930-f0edee5b1564423e.js:1:22128
(www.dior.com)
@babel/plugin-transform-classes
…chunks/main-3ee40a2a2f5cb04c.js
(www.dior.com)
0.0 KiB
…chunks/main-3ee40a2a2f5cb04c.js:1:140174
(www.dior.com)
@babel/plugin-transform-classes
…pages/_app-c7aaa6e71a26c10d.js
(www.dior.com)
0.0 KiB
…pages/_app-c7aaa6e71a26c10d.js:14:405177
(www.dior.com)
@babel/plugin-transform-classes
Salesforce.com
ad
0.1 KiB
…utils/inert.min.js
(christiandior.my.salesforce.com)
0.1 KiB
…utils/inert.min.js:3:279
(christiandior.my.salesforce.com)
@babel/plugin-transform-classes
Reduce unused CSS Potential savings of 56 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
Next.jsConsider setting up PurgeCSS in Next.js configuration to remove unused rules from stylesheets. Learn more.
URL
Transfer Size
Potential Savings
dior.com
1st party
42.1 KiB
38.5 KiB
…css/f6e84c4aa67274e8.css
(www.dior.com)
42.1 KiB
38.5 KiB
Unattributable
19.6 KiB
17.3 KiB
#onetrust-banner-sdk .onetrust-vendors-list-handler{cursor:pointer;color:#1f96db;font-size:inherit; … } …
19.6 KiB
17.3 KiB
Avoid enormous network payloads Total size was 19,674 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
dam-broadcast.com
16,811.9 KiB
/pm_11872_932_932863-4xg9owjbwp.webm
(diorama.dam-broadcast.com)
9,306.1 KiB
/pm_11872_949_949366-6vjso0wq3i.webm
(diorama.dam-broadcast.com)
4,207.6 KiB
/pm_11872_949_949366-6vjso0wq3i.webm
(diorama.dam-broadcast.com)
3,183.6 KiB
…width=1440,format=auto/pm_11872_946_946906-mrcoldsj3v-whr.jpg
(diorama.dam-broadcast.com)
114.6 KiB
dior.com
1st party
987.6 KiB
…pages/_app-c7aaa6e71a26c10d.js
(www.dior.com)
507.8 KiB
…AtacamaVAR/AtacamaVAR-VF.woff2
(www.dior.com)
250.5 KiB
…9876636/api_static.js
(www.dior.com)
115.9 KiB
…9876636/api_dynamic.js
(www.dior.com)
113.4 KiB
Google Tag Manager
tag-manager
137.7 KiB
/gtm.js?id=GTM-KKVBDVG&l=dataLayer&gtm=45He52k0v916…za200
(www.googletagmanager.com)
137.7 KiB
Optanon
consent-provider
111.0 KiB
…202408.1.0/otBannerSdk.js
(cdn.cookielaw.org)
111.0 KiB
Avoid long main-thread tasks 18 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
dior.com
1st party
3,939 ms
…chunks/payment-m….c0feaf606c8e736f.js
(www.dior.com)
3,655 ms
940 ms
…chunks/framework-a32fdada02556615.js
(www.dior.com)
5,236 ms
771 ms
…chunks/framework-a32fdada02556615.js
(www.dior.com)
3,001 ms
654 ms
…chunks/framework-a32fdada02556615.js
(www.dior.com)
4,722 ms
459 ms
…chunks/framework-a32fdada02556615.js
(www.dior.com)
6,593 ms
296 ms
…chunks/framework-a32fdada02556615.js
(www.dior.com)
6,207 ms
158 ms
…9876636/api_dynamic.js
(www.dior.com)
961 ms
128 ms
…pages/_app-c7aaa6e71a26c10d.js
(www.dior.com)
4,595 ms
127 ms
…9876636/api_static.js
(www.dior.com)
1,449 ms
123 ms
…chunks/framework-a32fdada02556615.js
(www.dior.com)
6,889 ms
91 ms
…chunks/framework-a32fdada02556615.js
(www.dior.com)
6,123 ms
71 ms
…chunks/framework-a32fdada02556615.js
(www.dior.com)
6,365 ms
67 ms
…chunks/4951.435fd113d844f634.js
(www.dior.com)
6,028 ms
54 ms
Optanon
consent-provider
304 ms
/scripttemplates/otSDKStub.js
(cdn.cookielaw.org)
1,572 ms
175 ms
…202408.1.0/otBannerSdk.js
(cdn.cookielaw.org)
6,464 ms
129 ms
Unattributable
135 ms
Unattributable
2,049 ms
81 ms
Unattributable
365 ms
54 ms
Google Tag Manager
tag-manager
110 ms
/gtm.js?id=GTM-M75MVP67
(www.googletagmanager.com)
1,339 ms
110 ms
User Timing marks and measures 11 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.
Next.jsConsider using Next.js Analytics to measure your app's real-world performance. Learn more.
Name
Type
Start Time
Duration
Next.js-before-hydration
Measure
0.00 ms
2,268.92 ms
Next.js-hydration
Measure
2,268.92 ms
786.59 ms
beforeRender
Mark
2,268.92 ms
routeChange
Mark
3,054.66 ms
afterHydrate
Mark
3,055.52 ms
clearMarks
Mark
3,055.88 ms
clearMarks
Mark
3,055.89 ms
clearMarks
Mark
3,055.89 ms
clearMarks
Mark
3,055.89 ms
beforeRender
Mark
4,343.88 ms
afterRender
Mark
7,192.31 ms
Avoid large layout shifts 1 layout shift found
These are the largest layout shifts observed on the page. Each table item represents a single layout shift, and shows the element that shifted the most. Below each item are possible root causes that led to the layout shift. Some of these layout shifts may not be included in the CLS metric value due to windowing. Learn how to improve CLSCLS
Element
Layout shift score
Aller à la page d'accueil Dior
<div>
0.000
Avoid non-composited animations 6 animated elements found
Animations which are not composited can be janky and increase CLS. Learn how to avoid non-composited animationsCLS
Element
Name
div.MuiBox-root > div.MuiFormControl-root > div.MuiInputBase-root > input#emailNewsletter
<input aria-invalid="false" aria-describedby="emailNewsletter-helper-text" autocomplete="email" id="emailNewsletter" required="" type="email" class="MuiInputBase-input MuiOutlinedInput-input mui-42uqqw" value="">
Unsupported CSS Property: display
mui-auto-fill-cancel
Ouvrir le menu
<button id="menuburger" class="Menu_burgerButton__KyYuf" aria-expanded="false" aria-haspopup="true" aria-label="Ouvrir le menu" style="opacity:1">
Effect has unsupported timing parameters
Ouvrir la recherche
<button class="MuiButtonBase-root MuiTab-root MuiTab-textColorPrimary MuiTab-fullWidth pi…" tabindex="0" role="tab" aria-selected="false" name="Search" aria-label="Ouvrir la recherche" style="opacity: 1;">
Effect has unsupported timing parameters
Wishlists
<a class="MuiButtonBase-root MuiTab-root MuiTab-textColorPrimary MuiTab-fullWidth pi…" tabindex="0" role="button" aria-selected="false" name="Wishlist" aria-label="Wishlists" style="opacity: 1;">
Effect has unsupported timing parameters
Compte
<button class="MuiButtonBase-root MuiTab-root MuiTab-textColorPrimary MuiTab-fullWidth pi…" tabindex="0" role="tab" aria-selected="false" name="Account" aria-label="Compte" style="opacity: 1;">
Effect has unsupported timing parameters
"Nombre d'items dans le panier NaN"
<button class="MuiButtonBase-root MuiTab-root MuiTab-textColorPrimary MuiTab-fullWidth pi…" tabindex="0" role="tab" aria-selected="false" name="Cart" aria-label="&quot;Nombre d'items dans le panier NaN&quot;" style="opacity: 1;">
Effect has unsupported timing parameters
Initial server response time was short Root document took 120 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
dior.com
1st party
120 ms
/fr_fr/fashion
(www.dior.com)
120 ms
More information about the performance of your application. These numbers don't directly affect the Performance score.
Passed audits (19)
Show Hide
Eliminate render-blocking resources
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles. Learn how to eliminate render-blocking resources.LCPFCP
Next.jsUse the next/script component to defer loading of non-critical third-party scripts. Learn more.
Minify CSS
Minifying CSS files can reduce network payload sizes. Learn how to minify CSS.LCPFCP
Minify JavaScript
Minifying JavaScript files can reduce payload sizes and script parse time. Learn how to minify JavaScript.LCPFCP
Efficiently encode images
Optimized images load faster and consume less cellular data. Learn how to efficiently encode images.LCPFCP
Next.jsUse the next/image component instead of <img> to adjust image quality. Learn more.
Serve images in next-gen formats
Image formats like WebP and AVIF often provide better compression than PNG or JPEG, which means faster downloads and less data consumption. Learn more about modern image formats.LCPFCP
Next.jsUse the next/image component instead of <img> to automatically optimize image format. Learn more.
Enable text compression
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. Learn more about text compression.LCPFCP
Next.jsEnable compression on your Next.js server. Learn more.
Preconnect to required origins
Warnings:
  • A `<link rel=preconnect>` was found for "https://rcom-eu.dynamicyield.com" but was not used by the browser. Only use `preconnect` for important origins that the page will certainly request.
  • More than 2 `<link rel=preconnect>` connections were found. These should be used sparingly and only to the most important origins.
Consider adding preconnect or dns-prefetch resource hints to establish early connections to important third-party origins. Learn how to preconnect to required origins.LCPFCP
Avoid multiple page redirects
Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.LCPFCP
Use video formats for animated content
Large GIFs are inefficient for delivering animated content. Consider using MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF to save network bytes. Learn more about efficient video formatsLCPFCP
Remove duplicate modules in JavaScript bundles
Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity. LCPFCP
Preload Largest Contentful Paint image
If the LCP element is dynamically added to the page, you should preload the image in order to improve LCP. Learn more about preloading LCP elements.LCP
Next.jsUse the next/image component and set "priority" to true to preload LCP image. Learn more.
Avoid chaining critical requests
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: 181.798 ms
Initial Navigation
/fr_fr/fashion
(www.dior.com)
- 181.798 ms, 73.83 KiB
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
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().
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
Next.jsUse the next/image component to make sure images are always sized appropriately. Learn more.
Has a <meta name="viewport"> tag with width or initial-scale
A <meta name="viewport"> not only optimizes your app for mobile screen sizes, but also prevents a 300 millisecond delay to user input. Learn more about using the viewport meta tag.
92
Accessibility
These checks highlight opportunities to improve the accessibility of your web app. Automatic detection can only detect a subset of issues and does not guarantee the accessibility of your web app, so manual testing is also encouraged.
ARIA
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
Bienvenue sur dior.com Vous accédez depuis États-Unis d'Amérique, souhaitez-vo…
<div class="MuiPaper-root MuiPaper-elevation MuiPaper-rounded MuiPaper-elevation0 MuiD…" role="dialog" aria-labelledby=":r0:" aria-modal="true" data-testid="geolocation-popin" style="--Paper-shadow: none;">
ARIA IDs are unique
The value of an ARIA ID must be unique to prevent other instances from being overlooked by assistive technologies. Learn how to fix duplicate ARIA IDs.
Failing Elements
div.MuiCollapse-root > div.MuiCollapse-wrapper > div.MuiCollapse-wrapperInner > div#contact-content
<div aria-labelledby="contact-header" id="contact-content" role="region" class="MuiAccordion-region">
div.MuiCollapse-wrapper > div.MuiCollapse-wrapperInner > div#contact-content > div#contact-content
<div class="MuiAccordionDetails-root mui-1rrv0vl" id="contact-content" aria-labelledby="contact-header">
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Contrast
Background and foreground colors do not have a sufficient contrast ratio.
Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.
Failing Elements
Nouveauté
<span class="MuiTypography-root MuiTypography-label-m-regular DS-Typography copy-cell__…" style="color:#7B8487FF">
Fashion & Accessories Printemps-Été 2025 Raffinement intemporel et impulsions s…
<div class="MuiScopedCssBaseline-root mui-1urmbdg" style="background-color: rgb(248, 248, 248);">
Nouveau sac
<span class="MuiTypography-root MuiTypography-label-m-regular DS-Typography copy-cell__…" style="color:#7B8487FF">
Fashion & Accessories Printemps-Été 2025 Raffinement intemporel et impulsions s…
<div class="MuiScopedCssBaseline-root mui-1urmbdg" style="background-color: rgb(248, 248, 248);">
Contact
<p class="MuiTypography-root MuiTypography-label-m-regular DS-Typography mui-1pr1fuf">
Contact
<div class="MuiPaper-root MuiPaper-elevation MuiPaper-elevation0 MuiAccordion-root mui…" style="--Paper-shadow:none">
FAQ
<p class="MuiTypography-root MuiTypography-label-m-regular DS-Typography mui-1pr1fuf">
FAQ
<div class="MuiPaper-root MuiPaper-elevation MuiPaper-elevation0 MuiAccordion-root mui…" style="--Paper-shadow:none">
Index d'égalité femmes-hommes
<p class="MuiTypography-root MuiTypography-label-m-regular DS-Typography mui-1pr1fuf">
Index d'égalité femmes-hommes
<div class="MuiPaper-root MuiPaper-elevation MuiPaper-elevation0 MuiAccordion-root mui…" style="--Paper-shadow:none">
Mentions légales
<p class="MuiTypography-root MuiTypography-label-m-regular DS-Typography mui-1pr1fuf">
Mentions légales
<div class="MuiPaper-root MuiPaper-elevation MuiPaper-elevation0 MuiAccordion-root mui…" style="--Paper-shadow:none">
Notice de vie privée
<p class="MuiTypography-root MuiTypography-label-m-regular DS-Typography mui-1pr1fuf">
Notice de vie privée
<div class="MuiPaper-root MuiPaper-elevation MuiPaper-elevation0 MuiAccordion-root mui…" style="--Paper-shadow:none">
Gestion des cookies
<p class="MuiTypography-root MuiTypography-label-m-regular DS-Typography mui-1pr1fuf">
Retrait en boutique Commander en ligne et retirer vos articles dans la boutiqu…
<div class="MuiPaper-root MuiPaper-elevation MuiPaper-rounded MuiPaper-elevation0 DS-P…" style="--Paper-shadow:none">
Conditions générales de vente
<p class="MuiTypography-root MuiTypography-label-m-regular DS-Typography mui-1pr1fuf">
Conditions générales de vente
<div class="MuiPaper-root MuiPaper-elevation MuiPaper-elevation0 MuiAccordion-root mui…" style="--Paper-shadow:none">
Plan du site
<p class="MuiTypography-root MuiTypography-label-m-regular DS-Typography mui-1pr1fuf">
Retrait en boutique Commander en ligne et retirer vos articles dans la boutiqu…
<div class="MuiPaper-root MuiPaper-elevation MuiPaper-rounded MuiPaper-elevation0 DS-P…" style="--Paper-shadow:none">
Pays/Région
<p class="MuiTypography-root MuiTypography-label-m-regular DS-Typography mui-erpn9y">
Retrait en boutique Commander en ligne et retirer vos articles dans la boutiqu…
<div class="MuiPaper-root MuiPaper-elevation MuiPaper-rounded MuiPaper-elevation0 DS-P…" style="--Paper-shadow:none">
Suivez nous
<p class="MuiTypography-root MuiTypography-label-m-regular DS-Typography mui-nu6thf">
Retrait en boutique Commander en ligne et retirer vos articles dans la boutiqu…
<div class="MuiPaper-root MuiPaper-elevation MuiPaper-rounded MuiPaper-elevation0 DS-P…" style="--Paper-shadow:none">
These are opportunities to improve the legibility of your content.
Additional items to manually check (10)
Show Hide
Interactive controls are keyboard focusable
Custom interactive controls are keyboard focusable and display a focus indicator. Learn how to make custom controls focusable.
Interactive elements indicate their purpose and state
Interactive elements, such as links and buttons, should indicate their state and be distinguishable from non-interactive elements. Learn how to decorate interactive elements with affordance hints.
The page has a logical tab order
Tabbing through the page follows the visual layout. Users cannot focus elements that are offscreen. Learn more about logical tab ordering.
Visual order on the page follows DOM order
DOM order matches the visual order, improving navigation for assistive technology. Learn more about DOM and visual ordering.
User focus is not accidentally trapped in a region
A user can tab into and out of any control or region without accidentally trapping their focus. Learn how to avoid focus traps.
The user's focus is directed to new content added to the page
If new content, such as a dialog, is added to the page, the user's focus is directed to it. Learn how to direct focus to new content.
HTML5 landmark elements are used to improve navigation
Landmark elements (<main>, <nav>, etc.) are used to improve the keyboard navigation of the page for assistive technology. Learn more about landmark elements.
Offscreen content is hidden from assistive technology
Offscreen content is hidden with display: none or aria-hidden=true. Learn how to properly hide offscreen content.
Custom controls have associated labels
Custom interactive controls have associated labels, provided by aria-label or aria-labelledby. Learn more about custom controls and labels.
Custom controls have ARIA roles
Custom interactive controls have appropriate ARIA roles. Learn how to add roles to custom controls.
These items address areas which an automated testing tool cannot cover. Learn more in our guide on conducting an accessibility review.
Passed audits (21)
Show Hide
[aria-*] attributes match their roles
Each ARIA role supports a specific subset of aria-* attributes. Mismatching these invalidates the aria-* attributes. Learn how to match ARIA attributes to their roles.
[aria-hidden="true"] is not present on the document <body>
Assistive technologies, like screen readers, work inconsistently when aria-hidden="true" is set on the document <body>. Learn how aria-hidden affects the document body.
[role]s have all required [aria-*] attributes
Some ARIA roles have required attributes that describe the state of the element to screen readers. Learn more about roles and required attributes.
[aria-*] attributes have valid values
Assistive technologies, like screen readers, can't interpret ARIA attributes with invalid values. Learn more about valid values for ARIA attributes.
[aria-*] attributes are valid and not misspelled
Assistive technologies, like screen readers, can't interpret ARIA attributes with invalid names. Learn more about valid ARIA attributes.
Buttons have an accessible name
When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.
[user-scalable="no"] is not used in the <meta name="viewport"> element and the [maximum-scale] attribute is not less than 5.
Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a web page. Learn more about the viewport meta tag.
ARIA attributes are used as specified for the element's role
Some ARIA attributes are only allowed on an element under certain conditions. Learn more about conditional ARIA attributes.
[aria-hidden="true"] elements do not contain focusable descendents
Focusable descendents within an [aria-hidden="true"] element prevent those interactive elements from being available to users of assistive technologies like screen readers. Learn how aria-hidden affects focusable elements.
Elements use only permitted ARIA attributes
Using ARIA attributes in roles where they are prohibited can mean that important information is not communicated to users of assistive technologies. Learn more about prohibited ARIA roles.
[role] values are valid
ARIA roles must have valid values in order to perform their intended accessibility functions. Learn more about valid ARIA roles.
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.
Links are distinguishable without relying on color.
Low-contrast text is difficult or impossible for many users to read. Link text that is discernible improves the experience for users with low vision. Learn how to make links distinguishable.
Links have a discernible name
Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.
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.
Heading elements appear in a sequentially-descending order
Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.
Uses ARIA roles only on compatible elements
Many HTML elements can only be assigned certain ARIA roles. Using ARIA roles where they are not allowed can interfere with the accessibility of the web page. Learn more about ARIA roles.
Deprecated ARIA roles were not used
Deprecated ARIA roles may not be processed correctly by assistive technology. Learn more about deprecated ARIA roles.
Not applicable (33)
Show Hide
[accesskey] values are unique
Access keys let users quickly focus a part of the page. For proper navigation, each access key must be unique. Learn more about access keys.
button, link, and menuitem elements have accessible names
When an element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn how to make command elements more accessible.
ARIA input fields have accessible names
When an input field doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn more about input field labels.
ARIA meter elements have accessible names
When a meter element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn how to name meter elements.
ARIA progressbar elements have accessible names
When a progressbar element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn how to label progressbar elements.
Elements with an ARIA [role] that require children to contain a specific [role] have all required children.
Some ARIA parent roles must contain specific child roles to perform their intended accessibility functions. Learn more about roles and required children elements.
[role]s are contained by their required parent element
Some ARIA child roles must be contained by specific parent roles to properly perform their intended accessibility functions. Learn more about ARIA roles and required parent element.
Elements with the role=text attribute do not have focusable descendents.
Adding role=text around a text node split by markup enables VoiceOver to treat it as one phrase, but the element's focusable descendents will not be announced. Learn more about the role=text attribute.
ARIA toggle fields have accessible names
When a toggle field doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn more about toggle fields.
ARIA tooltip elements have accessible names
When a tooltip element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn how to name tooltip elements.
ARIA treeitem elements have accessible names
When a treeitem element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn more about labeling treeitem elements.
The page contains a heading, skip link, or landmark region
Adding ways to bypass repetitive content lets keyboard users navigate the page more efficiently. Learn more about bypass blocks.
<dl>'s contain only properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements.
When definition lists are not properly marked up, screen readers may produce confusing or inaccurate output. Learn how to structure definition lists correctly.
Definition list items are wrapped in <dl> elements
Definition list items (<dt> and <dd>) must be wrapped in a parent <dl> element to ensure that screen readers can properly announce them. Learn how to structure definition lists correctly.
No form fields have multiple labels
Form fields with multiple labels can be confusingly announced by assistive technologies like screen readers which use either the first, the last, or all of the labels. Learn how to use form labels.
<frame> or <iframe> elements have a title
Screen reader users rely on frame titles to describe the contents of frames. Learn more about frame titles.
<html> element has an [xml:lang] attribute with the same base language as the [lang] attribute.
If the webpage does not specify a consistent language, then the screen reader might not announce the page's text correctly. Learn more about the lang attribute.
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.
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.
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.
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.
The document does not use <meta http-equiv="refresh">
Users do not expect a page to refresh automatically, and doing so will move focus back to the top of the page. This may create a frustrating or confusing experience. Learn more about the refresh meta tag.
<object> elements have alternate text
Screen readers cannot translate non-text content. Adding alternate text to <object> elements helps screen readers convey meaning to users. Learn more about alt text for object elements.
Select elements have associated label elements.
Form elements without effective labels can create frustrating experiences for screen reader users. Learn more about the select element.
Tables have different content in the summary attribute and <caption>.
The summary attribute should describe the table structure, while <caption> should have the onscreen title. Accurate table mark-up helps users of screen readers. Learn more about summary and caption.
Cells in a <table> element that use the [headers] attribute refer to table cells within the same table.
Screen readers have features to make navigating tables easier. Ensuring <td> cells using the [headers] attribute only refer to other cells in the same table may improve the experience for screen reader users. Learn more about the headers attribute.
<th> elements and elements with [role="columnheader"/"rowheader"] have data cells they describe.
Screen readers have features to make navigating tables easier. Ensuring table headers always refer to some set of cells may improve the experience for screen reader users. Learn more about table headers.
[lang] attributes have a valid value
Specifying a valid BCP 47 language on elements helps ensure that text is pronounced correctly by a screen reader. Learn how to use the lang attribute.
<video> elements contain a <track> element with [kind="captions"]
When a video provides a caption it is easier for deaf and hearing impaired users to access its information. Learn more about video captions.
96
Best Practices
General
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
Launch Darkly
utility
…63750fc…/eyJraW5kI…:1:0
(clientstream.launchdarkly.com)
Failed to load resource: net::ERR_TIMED_OUT
Detected JavaScript libraries
All front-end JavaScript libraries detected on the page. Learn more about this JavaScript library detection diagnostic audit.
Name
Version
Next.js
14.2.18
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
dior.com
1st party
…9876636/api_dynamic.js
(www.dior.com)
Large JavaScript file is missing a source map
…pages/_app-c7aaa6e71a26c10d.js
(www.dior.com)
Large JavaScript file is missing a source map
Riskified
utility
/?shop=www.dior.com&sid=39b21053-5a00-4b29-81f6-01328f685209
(beacon.riskified.com)
…d3d3LmRpb3IuY29t/MzliMjEwN…
(beacon.riskified.com)
Warning: missing 1 item in `.sourcesContent`
Trust and Safety
Ensure CSP is effective against XSS attacks
A strong Content Security Policy (CSP) significantly reduces the risk of cross-site scripting (XSS) attacks. Learn how to use a CSP to prevent XSS
Description
Directive
Severity
No CSP found in enforcement mode
High
Passed audits (12)
Show Hide
Uses HTTPS
All sites should be protected with HTTPS, even ones that don't handle sensitive data. This includes avoiding mixed content, where some resources are loaded over HTTP despite the initial request being served over HTTPS. HTTPS prevents intruders from tampering with or passively listening in on the communications between your app and your users, and is a prerequisite for HTTP/2 and many new web platform APIs. Learn more about HTTPS.
Avoids deprecated APIs
Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs.
Avoids third-party cookies
Chrome is moving towards a new experience that allows users to choose to browse without third-party cookies. Learn more about third-party cookies.
Allows users to paste into input fields
Preventing input pasting is a bad practice for the UX, and weakens security by blocking password managers.Learn more about user-friendly input fields.
Avoids requesting the geolocation permission on page load
Users are mistrustful of or confused by sites that request their location without context. Consider tying the request to a user action instead. Learn more about the geolocation permission.
Avoids requesting the notification permission on page load
Users are mistrustful of or confused by sites that request to send notifications without context. Consider tying the request to user gestures instead. Learn more about responsibly getting permission for notifications.
Displays images with correct aspect ratio
Image display dimensions should match natural aspect ratio. Learn more about image aspect ratio.
Serves images with appropriate resolution
Image natural dimensions should be proportional to the display size and the pixel ratio to maximize image clarity. Learn how to provide responsive images.
Has a <meta name="viewport"> tag with width or initial-scale
A <meta name="viewport"> not only optimizes your app for mobile screen sizes, but also prevents a 300 millisecond delay to user input. Learn more about using the viewport meta tag.
Page has the HTML doctype
Specifying a doctype prevents the browser from switching to quirks-mode. Learn more about the doctype declaration.
Properly defines charset
A character encoding declaration is required. It can be done with a <meta> tag in the first 1024 bytes of the HTML or in the Content-Type HTTP response header. Learn more about declaring the character encoding.
No issues in the Issues panel in Chrome Devtools
Issues logged to the Issues panel in Chrome Devtools indicate unresolved problems. They can come from network request failures, insufficient security controls, and other browser concerns. Open up the Issues panel in Chrome DevTools for more details on each issue.
Not applicable (2)
Show Hide
Redirects HTTP traffic to HTTPS
Make sure that you redirect all HTTP traffic to HTTPS in order to enable secure web features for all your users. Learn more.
Document uses legible font sizes
Font sizes less than 12px are too small to be legible and require mobile visitors to “pinch to zoom” in order to read. Strive to have >60% of page text ≥12px. Learn more about legible font sizes.
100
SEO
These checks ensure that your page is following basic search engine optimization advice. There are many additional factors Lighthouse does not score here that may affect your search ranking, including performance on Core Web Vitals. Learn more about Google Search Essentials.
Additional items to manually check (1)
Show Hide
Structured data is valid
Run the Structured Data Testing Tool and the Structured Data Linter to validate structured data. Learn more about Structured Data.
Run these additional validators on your site to check additional SEO best practices.
Passed audits (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 have descriptive text
Descriptive link text helps search engines understand your content. Learn how to make links more accessible.
Links are crawlable
Search engines may use href attributes on links to crawl websites. Ensure that the href attribute of anchor elements links to an appropriate destination, so more pages of the site can be discovered. Learn how to make links crawlable
robots.txt is valid
If your robots.txt file is malformed, crawlers may not be able to understand how you want your website to be crawled or indexed. Learn more about robots.txt.
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.
Not applicable (1)
Show Hide
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.