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:56 AM
Discover what your real users are experiencing
Core Web Vitals Assessment: Failed
Largest Contentful Paint (LCP)
1.7 s
Page LoadsGood (≤ 2.5 s)87%Needs Improvement (2.5 s - 4 s)8%Poor (> 4 s)5%75th Percentile - 1.7 sCore Web Vital
Interaction to Next Paint (INP)
225 ms
Page LoadsGood (≤ 200 ms)70%Needs Improvement (200 ms - 500 ms)23%Poor (> 500 ms)7%75th Percentile - 225 msCore Web Vital
Cumulative Layout Shift (CLS)
0
Page LoadsGood (≤ 0.1)100%Needs Improvement (0.1 - 0.25)0%Poor (> 0.25)0%75th Percentile - 0Core Web Vital
Other Notable Metrics
First Contentful Paint (FCP)
1.5 s
Page LoadsGood (≤ 1.8 s)83%Needs Improvement (1.8 s - 3 s)11%Poor (> 3 s)6%75th Percentile - 1.5 s 
Time to First Byte (TTFB)
1 s
Page LoadsGood (≤ 0.8 s)66%Needs Improvement (0.8 s - 1.8 s)27%Poor (> 1.8 s)8%75th Percentile - 1 sExperimental
Latest 28-day collection period
Various mobile devicesMany samples (Chrome UX Report)Full visit durationsVarious network connectionsAll Chrome versions
Core Web Vitals Assessment: Failed
Largest Contentful Paint (LCP)
2.5 s
Page LoadsGood (≤ 2.5 s)75%Needs Improvement (2.5 s - 4 s)16%Poor (> 4 s)9%75th Percentile - 2.5 sCore Web Vital
Interaction to Next Paint (INP)
466 ms
Page LoadsGood (≤ 200 ms)53%Needs Improvement (200 ms - 500 ms)23%Poor (> 500 ms)24%75th Percentile - 466 msCore Web Vital
Cumulative Layout Shift (CLS)
0.02
Page LoadsGood (≤ 0.1)81%Needs Improvement (0.1 - 0.25)3%Poor (> 0.25)16%75th Percentile - 0.02Core Web Vital
Other Notable Metrics
First Contentful Paint (FCP)
2 s
Page LoadsGood (≤ 1.8 s)69%Needs Improvement (1.8 s - 3 s)20%Poor (> 3 s)11%75th Percentile - 2 s 
Time to First Byte (TTFB)
1.4 s
Page LoadsGood (≤ 0.8 s)50%Needs Improvement (0.8 s - 1.8 s)33%Poor (> 1.8 s)17%75th Percentile - 1.4 sExperimental
Latest 28-day collection period
Various mobile devicesMany samples (Chrome UX Report)Full visit durationsVarious network connectionsAll Chrome versions
Diagnose performance issues
66 FCP+10LCP+18TBT+13CLS+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
1.4 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
3.2 s
Largest Contentful Paint marks the time at which the largest text or image is painted. Learn more about the Largest Contentful Paint metric
Total Blocking Time
710 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
11.7 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more about the Speed Index metric.
  • Captured at Feb 22, 2025, 8:00 AM UTC
  • Emulated Moto G Power with Lighthouse 12.2.3
    Unthrottled CPU/Memory Power: 421 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
Reduce JavaScript execution time 3.0 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
burberry.com
1st party
3,047 ms
2,239 ms
41 ms
1,736 ms
1,502 ms
5 ms
482 ms
182 ms
7 ms
460 ms
237 ms
24 ms
/assets/9dac7dd…
(fr.burberry.com)
210 ms
172 ms
3 ms
105 ms
103 ms
2 ms
54 ms
43 ms
0 ms
Unattributable
377 ms
108 ms
0 ms
Unattributable
377 ms
108 ms
0 ms
Brightcove
video
257 ms
189 ms
18 ms
…Tc5iqtzRUb_default/index.min.js
(players.brightcove.net)
257 ms
189 ms
18 ms
Google Tag Manager
tag-manager
159 ms
110 ms
13 ms
/gtm.js?id=…
(www.googletagmanager.com)
159 ms
110 ms
13 ms
Optimizely
analytics
152 ms
143 ms
6 ms
/js/174….js
(cdn.optimizely.com)
152 ms
143 ms
6 ms
Optanon
consent-provider
128 ms
80 ms
11 ms
…202403.2.0/otBannerSdk.js
(cdn.cookielaw.org)
128 ms
80 ms
11 ms
New Relic
utility
82 ms
76 ms
2 ms
/nr-spa-1.283.2.min.js
(js-agent.newrelic.com)
82 ms
76 ms
2 ms
Minimize main-thread work 4.5 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to minimize main-thread workTBT
Category
Time Spent
Script Evaluation
3,098 ms
Other
505 ms
Style & Layout
348 ms
Garbage Collection
222 ms
Script Parsing & Compilation
128 ms
Parse HTML & CSS
82 ms
Rendering
70 ms
Reduce initial server response time Root document took 1,830 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
burberry.com
1st party
1,830 ms
1,830 ms
Largest Contentful Paint element 3,230 ms
This is the largest contentful element painted within the viewport. Learn more about the Largest Contentful Paint elementLCP
Element
La campagne "It's Always Burberry Weather" avec Aimee Lou Wood et Michael Ward …
<img alt="La campagne &quot;It's Always Burberry Weather&quot; avec Aimee Lou Wood et Michael …" src="https://assets.burberry.com/is/image/Burberryltd/AA55BFA4-E3C7-4006-9730-5…" sizes="100vw" loading="eager" fetchpriority="high" style="opacity:1">
Phase
% of LCP
Timing
TTFB
19%
600 ms
Load Delay
78%
2,500 ms
Load Time
1%
20 ms
Render Delay
3%
100 ms
Properly size images Potential savings of 270 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
burberry.com
1st party
963.7 KiB
270.4 KiB
Dessin du Chevalier Burberry EKD sur un cheval
<img alt="Dessin du Chevalier Burberry EKD sur un cheval" sizes="(max-width: 1023px) 100vw, 50vw" loading="lazy" fetchpriority="auto" style="transition: opacity 200ms; opacity: 1;" src="https://assets.burberry.com/is/image/Burberryltd/51C8CF36-1B11-4C3A-BF5E-C…">
317.1 KiB
59.1 KiB
La campagne "It's Always Burberry Weather" avec un mannequin portant un trench …
<img alt="La campagne &quot;It's Always Burberry Weather&quot; avec un mannequin portant un tr…" sizes="(max-width: 1023px) 100vw, 50vw" loading="lazy" fetchpriority="auto" style="transition: opacity 200ms; opacity: 1;" src="https://assets.burberry.com/is/image/Burberryltd/AC285F74-08C8-4367-B05E-E…">
228.3 KiB
43.0 KiB
Écharpe en laine Check EKD coloris sable
<img alt="Écharpe en laine Check EKD coloris sable" sizes="(max-width: 1023px) 100vw, 50vw" loading="lazy" fetchpriority="auto" style="transition: opacity 200ms; opacity: 1;" src="https://assets.burberry.com/is/image/Burberryltd/6D2CED73-0B22-4F13-BEDE-E…" srcset="https://assets.burberry.com/is/image/Burberryltd/6D2CED73-0B22-4F13-BEDE-E…">
54.8 KiB
40.8 KiB
La campagne "It's Always Burberry Weather" avec deux mannequins portant des tre…
<img alt="La campagne &quot;It's Always Burberry Weather&quot; avec deux mannequins portant de…" sizes="(max-width: 1023px) 100vw, 50vw" loading="lazy" fetchpriority="auto" style="transition: opacity 200ms; opacity: 1;" src="https://assets.burberry.com/is/image/Burberryltd/218AC153-7B13-41EC-881C-E…">
160.8 KiB
30.3 KiB
Ceinture en toile Check coloris sable
<img alt="Ceinture en toile Check coloris sable" sizes="(max-width: 1023px) 100vw, 50vw" loading="lazy" fetchpriority="auto" style="transition: opacity 200ms; opacity: 1;" src="https://assets.burberry.com/is/image/Burberryltd/FA50A4EA-C670-4166-8A43-4…" srcset="https://assets.burberry.com/is/image/Burberryltd/FA50A4EA-C670-4166-8A43-4…">
28.9 KiB
21.5 KiB
La campagne "It's Always Burberry Weather" avec Aimee Lou Wood et Michael Ward …
<img alt="La campagne &quot;It's Always Burberry Weather&quot; avec Aimee Lou Wood et Michael …" src="https://assets.burberry.com/is/image/Burberryltd/AA55BFA4-E3C7-4006-9730-5…" sizes="100vw" loading="eager" fetchpriority="high" style="opacity:1">
96.6 KiB
18.1 KiB
Veste trench en coton mélangé coloris beige
<img alt="Veste trench en coton mélangé coloris beige" src="https://assets.burberry.com/is/image/Burberryltd/95E5A846-F470-44B7-BEDF-0…" srcset="https://assets.burberry.com/is/image/Burberryltd/95E5A846-F470-44B7-BEDF-0…" sizes="(max-width: 1023px) 100vw, 50vw" loading="lazy" fetchpriority="auto" style="transition: opacity 200ms; opacity: 1;">
23.2 KiB
17.3 KiB
Trench long Castleford coloris beige
<img alt="Trench long Castleford coloris beige" sizes="(max-width: 1023px) 100vw, 50vw" loading="lazy" fetchpriority="auto" style="transition: opacity 200ms; opacity: 1;" src="https://assets.burberry.com/is/image/Burberryltd/266684BD-EB0B-4E63-8304-0…" srcset="https://assets.burberry.com/is/image/Burberryltd/266684BD-EB0B-4E63-8304-0…">
19.4 KiB
14.5 KiB
Paletot long en gabardine coloris Fossil
<img alt="Paletot long en gabardine coloris Fossil" sizes="(max-width: 1023px) 100vw, 50vw" loading="lazy" fetchpriority="auto" style="transition: opacity 200ms; opacity: 1;" src="https://assets.burberry.com/is/image/Burberryltd/2102306A-6768-45CD-87E4-A…" srcset="https://assets.burberry.com/is/image/Burberryltd/2102306A-6768-45CD-87E4-A…">
17.4 KiB
13.0 KiB
Trench long Castleford coloris Juniper
<img alt="Trench long Castleford coloris Juniper" sizes="(max-width: 1023px) 100vw, 50vw" loading="lazy" fetchpriority="auto" style="transition: opacity 200ms; opacity: 1;" src="https://assets.burberry.com/is/image/Burberryltd/D0846537-D111-4A70-B3BD-4…" srcset="https://assets.burberry.com/is/image/Burberryltd/D0846537-D111-4A70-B3BD-4…">
17.2 KiB
12.8 KiB
Avoid an excessive DOM size 1,987 elements
A large DOM will increase memory usage, cause longer style calculations, and produce costly layout reflows. Learn how to avoid an excessive DOM size.TBT
Statistic
Element
Value
Total DOM Elements
1,987
Maximum DOM Depth
a.css-11cfnoo > div.e14owicd1 > picture > source
<source sizes="(max-width: 1023px) 100vw, 50vw" srcset="https://assets.burberry.com/is/image/Burberryltd/2102306A-6768-45CD-87E4-A…" media="(max-width: 1023px)">
17
Maximum Child Elements
PlayUnmuteCurrent Time 0:00/Duration 0:00Loaded: 0%Stream Type LIVESeek to live…
<div class="vjs-control-bar" dir="ltr">
17
Enable text compression Potential savings of 2 KiB
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.
URL
Transfer Size
Potential Savings
Brightcove
video
3.4 KiB
2.4 KiB
…videos/636…
(edge.api.brightcove.com)
3.4 KiB
2.4 KiB
Serve static assets with an efficient cache policy 64 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
burberry.com
1st party
5,406 KiB
45s
1 KiB
1m 5s
30 KiB
1m 11s
83 KiB
1m 40s
6 KiB
2m 22s
2 KiB
3m 9s
352 KiB
3m 27s
9 KiB
4m 50s
21 KiB
5m 52s
12 KiB
6m 10s
1 KiB
7m 3s
4 KiB
7m 47s
5 KiB
9m 53s
6 KiB
/assets/9dac7dd…
(fr.burberry.com)
10m
56 KiB
10m 16s
6 KiB
11m 14s
5 KiB
13m 4s
1 KiB
13m 32s
1 KiB
…assets/index-B9nRAYWM.js
(creativetech.static.burberry.com)
20m
4 KiB
…assets/index-BR9hTRLz.css
(creativetech.static.burberry.com)
20m
1 KiB
7d
2,786 KiB
7d
549 KiB
7d
318 KiB
7d
229 KiB
7d
161 KiB
7d
97 KiB
7d
55 KiB
7d
30 KiB
7d
24 KiB
7d
20 KiB
7d
19 KiB
7d
18 KiB
7d
18 KiB
7d
15 KiB
7d
14 KiB
7d
12 KiB
7d
10 KiB
7d
2 KiB
9d 1h 3m 27s
19 KiB
9d 23h 7m 12s
4 KiB
11d 6h 19m 57s
7 KiB
11d 14h 47m 36s
192 KiB
12d 6h 56m 32s
64 KiB
…oracle-book/oracle-book.woff2
(common.static.burberry.com)
12d 6h 56m 32s
60 KiB
12d 6h 56m 32s
17 KiB
12d 9h 56m 32s
11 KiB
12d 13h 10m 34s
7 KiB
12d 14h 14m 34s
4 KiB
12d 16h 1m 37s
6 KiB
12d 17h 2m 35s
1 KiB
12d 19h 25m 33s
1 KiB
13d 15h 38m 39s
1 KiB
13d 21h 18m 49s
12 KiB
13d 22h 20m 40s
3 KiB
13d 22h 40m 17s
7 KiB
20d 5h 55m 12s
5 KiB
29d 16m 22s
4 KiB
Brightcove
video
223 KiB
…Tc5iqtzRUb_default/index.min.js
(players.brightcove.net)
5m
223 KiB
Optanon
consent-provider
123 KiB
…202403.2.0/otBannerSdk.js
(cdn.cookielaw.org)
1d
109 KiB
1d
8 KiB
1d
3 KiB
1d
3 KiB
Optimizely
analytics
101 KiB
/js/174….js
(cdn.optimizely.com)
2m
101 KiB
cloudfront.net
23 KiB
/v3.1.4/3c8ksv.js
(dabs7b6g7t59l.cloudfront.net)
None
23 KiB
Defer offscreen images Potential savings of 3 KiB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive. Learn how to defer offscreen images.LCPFCP
Next.jsUse the next/image component instead of <img> to automatically lazy-load images. Learn more.
URL
Resource Size
Potential Savings
Optanon
consent-provider
2.8 KiB
2.8 KiB
Powered by Onetrust
<img alt="Powered by Onetrust" src="https://cdn.cookielaw.org/logos/static/powered_by_logo.svg">
2.8 KiB
2.8 KiB
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
…202403.2.0/otBannerSdk.js
(cdn.cookielaw.org)
6.9 KiB
Array.prototype.fill
burberry.com
1st party
0.3 KiB
0.1 KiB
@babel/plugin-transform-classes
0.1 KiB
@babel/plugin-transform-classes
0.1 KiB
@babel/plugin-transform-classes
0.0 KiB
@babel/plugin-transform-classes
0.0 KiB
@babel/plugin-transform-classes
Brightcove
video
0.0 KiB
…Tc5iqtzRUb_default/index.min.js
(players.brightcove.net)
0.0 KiB
@babel/plugin-transform-classes
Reduce unused CSS Potential savings of 18 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
#onetrust-banner-sdk{-ms-text-size-adjust:100%;-webkit-text-size-adjust:100%} …
21.2 KiB
18.1 KiB
Reduce unused JavaScript Potential savings of 699 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
burberry.com
1st party
679.9 KiB
415.1 KiB
191.3 KiB
189.7 KiB
351.1 KiB
174.1 KiB
82.3 KiB
29.8 KiB
/assets/9dac7dd…
(fr.burberry.com)
55.2 KiB
21.6 KiB
Brightcove
video
221.8 KiB
134.3 KiB
…Tc5iqtzRUb_default/index.min.js
(players.brightcove.net)
221.8 KiB
134.3 KiB
Optanon
consent-provider
108.2 KiB
57.5 KiB
…202403.2.0/otBannerSdk.js
(cdn.cookielaw.org)
108.2 KiB
57.5 KiB
Google Tag Manager
tag-manager
139.4 KiB
53.5 KiB
/gtm.js?id=…
(www.googletagmanager.com)
139.4 KiB
53.5 KiB
Optimizely
analytics
100.4 KiB
38.9 KiB
/js/174….js
(cdn.optimizely.com)
100.4 KiB
38.9 KiB
Avoid enormous network payloads Total size was 6,322 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
burberry.com
1st party
4,709.5 KiB
2,785.7 KiB
548.9 KiB
351.9 KiB
317.7 KiB
229.0 KiB
192.2 KiB
161.4 KiB
122.7 KiB
Brightcove
video
222.7 KiB
…Tc5iqtzRUb_default/index.min.js
(players.brightcove.net)
222.7 KiB
Google Tag Manager
tag-manager
140.5 KiB
/gtm.js?id=…
(www.googletagmanager.com)
140.5 KiB
Avoid long main-thread tasks 13 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay. Learn how to avoid long main-thread tasksTBT
URL
Start Time
Duration
burberry.com
1st party
1,401 ms
15,647 ms
399 ms
16,046 ms
312 ms
15,337 ms
310 ms
/assets/9dac7dd…
(fr.burberry.com)
3,337 ms
141 ms
9,787 ms
72 ms
16,376 ms
61 ms
9,883 ms
54 ms
16,522 ms
52 ms
Optimizely
analytics
146 ms
/js/174….js
(cdn.optimizely.com)
5,141 ms
146 ms
Brightcove
video
109 ms
…Tc5iqtzRUb_default/index.min.js
(players.brightcove.net)
13,845 ms
109 ms
Google Tag Manager
tag-manager
81 ms
/gtm.js?id=…
(www.googletagmanager.com)
18,409 ms
81 ms
Unattributable
63 ms
Unattributable
18,490 ms
63 ms
Optanon
consent-provider
54 ms
…202403.2.0/otBannerSdk.js
(cdn.cookielaw.org)
6,526 ms
54 ms
Minimize third-party usage Third-party code blocked the main thread for 190 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
Optimizely
analytics
103 KiB
93 ms
/js/174….js
(cdn.optimizely.com)
101 KiB
93 ms
/client_storage/a174….html
(a17489381590.cdn-pci.optimizely.com)
1 KiB
0 ms
/v1/events
(logx.optimizely.com)
1 KiB
0 ms
Brightcove
video
238 KiB
58 ms
…Tc5iqtzRUb_default/index.min.js
(players.brightcove.net)
223 KiB
58 ms
8 KiB
0 ms
…videos/636…
(edge.api.brightcove.com)
6 KiB
0 ms
/v2/tracker?domain=…
(metrics.brightcove.com)
0 KiB
0 ms
/v2/tracker?domain=…
(metrics.brightcove.com)
0 KiB
0 ms
/v2/tracker?domain=…
(metrics.brightcove.com)
0 KiB
0 ms
/v2/tracker?domain=…
(metrics.brightcove.com)
0 KiB
0 ms
Google Tag Manager
tag-manager
140 KiB
31 ms
/gtm.js?id=…
(www.googletagmanager.com)
140 KiB
31 ms
Optanon
consent-provider
175 KiB
4 ms
…202403.2.0/otBannerSdk.js
(cdn.cookielaw.org)
109 KiB
4 ms
25 KiB
0 ms
…v2/otPcTab.json
(cdn.cookielaw.org)
14 KiB
0 ms
8 KiB
0 ms
…assets/otCommonStyles.css
(cdn.cookielaw.org)
5 KiB
0 ms
3 KiB
0 ms
3 KiB
0 ms
3 KiB
0 ms
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
New Relic
utility
34 KiB
0 ms
/nr-spa-1.283.2.min.js
(js-agent.newrelic.com)
33 KiB
0 ms
/1/883cbb608e?a=…
(bam.nr-data.net)
1 KiB
0 ms
…1/883cbb608e?a=…
(bam.nr-data.net)
0 KiB
0 ms
cloudfront.net
23 KiB
0 ms
/v3.1.4/3c8ksv.js
(dabs7b6g7t59l.cloudfront.net)
23 KiB
0 ms
User Timing marks and measures 15 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
4,693.02 ms
Next.js-hydration
Measure
4,693.02 ms
554.04 ms
bcAdBlockDetect
Measure
6,135.30 ms
276.90 ms
bcInit
Measure
6,155.77 ms
188.33 ms
optimizely:blockBegin
Mark
4,264.25 ms
beforeRender
Mark
4,693.02 ms
afterHydrate
Mark
5,247.07 ms
clearMarks
Mark
5,247.54 ms
clearMarks
Mark
5,247.55 ms
clearMarks
Mark
5,247.55 ms
clearMarks
Mark
5,247.55 ms
bcAdBlockDetectStart
Mark
6,135.30 ms
bcInitStart
Mark
6,155.77 ms
bcInitEnd
Mark
6,344.10 ms
bcAdBlockDetectEnd
Mark
6,412.19 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
body > div#loading-animation
<div id="loading-animation" class="hidden">
0.000
…assets/index-BR9hTRLz.css
(creativetech.static.burberry.com)
A late network request adjusted the page layout
Avoid non-composited animations 2 animated elements found
Animations which are not composited can be janky and increase CLS. Learn how to avoid non-composited animationsCLS
Element
Name
section.css-1ea9d78 > div.css-1elx8sn > div.css-1965q92 > div.css-m91ho0
<div color="black" data-testid="dashEl" class="css-m91ho0 emvjbqg5">
Unsupported CSS Property: background-color
background-color
section.css-1ea9d78 > div.css-1elx8sn > div.css-1965q92 > div.css-m91ho0
<div color="black" data-testid="dashEl" class="css-m91ho0 emvjbqg5">
Unsupported CSS Property: background-color
background-color
More information about the performance of your application. These numbers don't directly affect the Performance score.
Passed audits (18)
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.
Preconnect to required origins
Warnings:
  • A `<link rel=preconnect>` was found for "https://api.burberry.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: 4,037.133 ms
Initial Navigation
- 4,037.133 ms, 122.69 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
Element
La campagne "It's Always Burberry Weather" avec Aimee Lou Wood et Michael Ward …
<img alt="La campagne &quot;It's Always Burberry Weather&quot; avec Aimee Lou Wood et Michael …" src="https://assets.burberry.com/is/image/Burberryltd/AA55BFA4-E3C7-4006-9730-5…" sizes="100vw" loading="eager" fetchpriority="high" style="opacity:1">
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.
These checks highlight opportunities to improve the accessibility of your web app. Automatic detection can only detect a subset of issues and does not guarantee the accessibility of your web app, so manual testing is also encouraged.
ARIA
[aria-*] attributes do not have valid values
Assistive technologies, like screen readers, can't interpret ARIA attributes with invalid values. Learn more about valid values for ARIA attributes.
Failing Elements
Langue Français
<button data-testid="language-picker-button" aria-controls="language-picker-modal" aria-label="Cliquez pour ouvrir la fenêtre des langues et modifier la langue" class="css-8sgliu e1yvoxgm0">
Lieu de livraison France (€)
<button data-testid="country-picker-button" aria-controls="country-picker-modal" aria-label="Cliquez pour ouvrir la fenêtre des destinations et modifier le lieu de liv…" class="css-8sgliu e1yvoxgm0">
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Names and labels
Buttons do not have an accessible name
When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.
Failing Elements
div#blte5df5423f7e8e1f9 > div.e1w7ayjm0 > article#blte5df542f7e8e1f9-position-0 > button
<button data-state="playing" style="border: 0px solid transparent; background: none; position: absolute;">
<frame> or <iframe> elements do not have a title
Screen reader users rely on frame titles to describe the contents of frames. Learn more about frame titles.
Failing Elements
div.css-1et4pk2 > div#blta677215f3311460e > div.css-v7gwe8 > iframe.css-1dzg4bz
<iframe data-testid="iframe" src="https://creativetech.static.burberry.com/yt-reveal/injection/live/index.ht…" loading="lazy" allow="fullscreen; gyroscope; accelerometer; camera *; autoplay *; web-share" class="css-1dzg4bz emxi7ie2">
div#blte5df5423f7e8e1f9 > div.e1w7ayjm0 > article#blte5df542f7e8e1f9-position-0 > iframe
<iframe src="https://creativetech.static.burberry.com/signup-video-overlay/live/index.h…" style="position: absolute; z-index: 10; border: none; height: 100%; width: 100%;">
<object> elements do not 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.
Failing Elements
div#video-player > div.css-jsngzv > video-js#vjs_video_3 > object#vjs_video_3_flash_api
<object type="application/x-shockwave-flash" data="//players.brightcove.net/videojs-flashls-source-handler/1.4.8/video-js.swf" width="100%" height="100%" id="vjs_video_3_flash_api" name="vjs_video_3_flash_api" class="vjs-tech">
These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.
Best practices
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a web page. Learn more about the viewport meta tag.
Failing Elements
head > meta
<meta name="viewport" content="width=device-width, initial-scale=1, maximum-scale=1, viewport-fit=cover" data-next-head="">
These items highlight common accessibility best practices.
Additional items to manually check (10)
Show Hide
Interactive controls are keyboard focusable
Custom interactive controls are keyboard focusable and display a focus indicator. Learn how to make custom controls focusable.
Interactive elements indicate their purpose and state
Interactive elements, such as links and buttons, should indicate their state and be distinguishable from non-interactive elements. Learn how to decorate interactive elements with affordance hints.
The page has a logical tab order
Tabbing through the page follows the visual layout. Users cannot focus elements that are offscreen. Learn more about logical tab ordering.
Visual order on the page follows DOM order
DOM order matches the visual order, improving navigation for assistive technology. Learn more about DOM and visual ordering.
User focus is not accidentally trapped in a region
A user can tab into and out of any control or region without accidentally trapping their focus. Learn how to avoid focus traps.
The user's focus is directed to new content added to the page
If new content, such as a dialog, is added to the page, the user's focus is directed to it. Learn how to direct focus to new content.
HTML5 landmark elements are used to improve navigation
Landmark elements (<main>, <nav>, etc.) are used to improve the keyboard navigation of the page for assistive technology. Learn more about landmark elements.
Offscreen content is hidden from assistive technology
Offscreen content is hidden with display: none or aria-hidden=true. Learn how to properly hide offscreen content.
Custom controls have associated labels
Custom interactive controls have associated labels, provided by aria-label or aria-labelledby. Learn more about custom controls and labels.
Custom controls have ARIA roles
Custom interactive controls have appropriate ARIA roles. Learn how to add roles to custom controls.
These items address areas which an automated testing tool cannot cover. Learn more in our guide on conducting an accessibility review.
Passed audits (26)
Show Hide
[aria-*] attributes match their roles
Each ARIA role supports a specific subset of aria-* attributes. Mismatching these invalidates the aria-* attributes. Learn how to match ARIA attributes to their roles.
[aria-hidden="true"] is not present on the document <body>
Assistive technologies, like screen readers, work inconsistently when aria-hidden="true" is set on the document <body>. Learn how aria-hidden affects the document body.
[role]s have all required [aria-*] attributes
Some ARIA roles have required attributes that describe the state of the element to screen readers. Learn more about roles and required attributes.
[aria-*] attributes are valid and not misspelled
Assistive technologies, like screen readers, can't interpret ARIA attributes with invalid names. Learn more about valid ARIA attributes.
Image elements have [alt] attributes
Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the alt attribute.
ARIA attributes are used as specified for the element's role
Some ARIA attributes are only allowed on an element under certain conditions. Learn more about conditional ARIA attributes.
Elements with role="dialog" or role="alertdialog" have accessible names.
ARIA dialog elements without accessible names may prevent screen readers users from discerning the purpose of these elements. Learn how to make ARIA dialog elements more accessible.
[aria-hidden="true"] elements do not contain focusable descendents
Focusable descendents within an [aria-hidden="true"] element prevent those interactive elements from being available to users of assistive technologies like screen readers. Learn how aria-hidden affects focusable elements.
Elements use only permitted ARIA attributes
Using ARIA attributes in roles where they are prohibited can mean that important information is not communicated to users of assistive technologies. Learn more about prohibited ARIA roles.
[role] values are valid
ARIA roles must have valid values in order to perform their intended accessibility functions. Learn more about valid ARIA roles.
Background and foreground colors have a sufficient contrast ratio
Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.
Document has a <title> element
The title gives screen reader users an overview of the page, and search engine users rely on it heavily to determine if a page is relevant to their search. Learn more about document titles.
<html> element has a [lang] attribute
If a page doesn't specify a lang attribute, a screen reader assumes that the page is in the default language that the user chose when setting up the screen reader. If the page isn't actually in the default language, then the screen reader might not announce the page's text correctly. Learn more about the lang attribute.
<html> element has a valid value for its [lang] attribute
Specifying a valid BCP 47 language helps screen readers announce text properly. Learn how to use the lang attribute.
Form elements have associated labels
Labels ensure that form controls are announced properly by assistive technologies, like screen readers. Learn more about form element labels.
Lists contain only <li> elements and script supporting elements (<script> and <template>).
Screen readers have a specific way of announcing lists. Ensuring proper list structure aids screen reader output. Learn more about proper list structure.
List items (<li>) are contained within <ul>, <ol> or <menu> parent elements
Screen readers require list items (<li>) to be contained within a parent <ul>, <ol> or <menu> to be announced properly. Learn more about proper list structure.
No element has a [tabindex] value greater than 0
A value greater than 0 implies an explicit navigation ordering. Although technically valid, this often creates frustrating experiences for users who rely on assistive technologies. Learn more about the tabindex attribute.
Touch targets have sufficient size and spacing.
Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.
[lang] attributes have a valid value
Specifying a valid BCP 47 language on elements helps ensure that text is pronounced correctly by a screen reader. Learn how to use the lang attribute.
Heading elements appear in a sequentially-descending order
Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.
Uses ARIA roles only on compatible elements
Many HTML elements can only be assigned certain ARIA roles. Using ARIA roles where they are not allowed can interfere with the accessibility of the web page. Learn more about ARIA roles.
Deprecated ARIA roles were not used
Deprecated ARIA roles may not be processed correctly by assistive technology. Learn more about deprecated ARIA roles.
Image elements do not have [alt] attributes that are redundant text.
Informative elements should aim for short, descriptive alternative text. Alternative text that is exactly the same as the text adjacent to the link or image is potentially confusing for screen reader users, because the text will be read twice. Learn more about the alt attribute.
Not applicable (26)
Show Hide
[accesskey] values are unique
Access keys let users quickly focus a part of the page. For proper navigation, each access key must be unique. Learn more about access keys.
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.
ARIA IDs are unique
The value of an ARIA ID must be unique to prevent other instances from being overlooked by assistive technologies. Learn how to fix duplicate ARIA IDs.
No form fields have multiple labels
Form fields with multiple labels can be confusingly announced by assistive technologies like screen readers which use either the first, the last, or all of the labels. Learn how to use form labels.
<html> element has an [xml:lang] attribute with the same base language as the [lang] attribute.
If the webpage does not specify a consistent language, then the screen reader might not announce the page's text correctly. Learn more about the lang attribute.
Input buttons have discernible text.
Adding discernable and accessible text to input buttons may help screen reader users understand the purpose of the input button. Learn more about input buttons.
<input type="image"> elements have [alt] text
When an image is being used as an <input> button, providing alternative text can help screen reader users understand the purpose of the button. Learn about input image alt text.
The document does not use <meta http-equiv="refresh">
Users do not expect a page to refresh automatically, and doing so will move focus back to the top of the page. This may create a frustrating or confusing experience. Learn more about the refresh meta tag.
Select elements have associated label elements.
Form elements without effective labels can create frustrating experiences for screen reader users. Learn more about the select element.
Tables have different content in the summary attribute and <caption>.
The summary attribute should describe the table structure, while <caption> should have the onscreen title. Accurate table mark-up helps users of screen readers. Learn more about summary and caption.
Cells in a <table> element that use the [headers] attribute refer to table cells within the same table.
Screen readers have features to make navigating tables easier. Ensuring <td> cells using the [headers] attribute only refer to other cells in the same table may improve the experience for screen reader users. Learn more about the headers attribute.
<th> elements and elements with [role="columnheader"/"rowheader"] have data cells they describe.
Screen readers have features to make navigating tables easier. Ensuring table headers always refer to some set of cells may improve the experience for screen reader users. Learn more about table headers.
<video> elements contain a <track> element with [kind="captions"]
When a video provides a caption it is easier for deaf and hearing impaired users to access its information. Learn more about video captions.
General
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
burberry.com
1st party
Refused to load plugin data from 'https://players.brightcove.net/videojs-flashls-source-handler/1.4.8/video-js.swf' because it violates the following Content Security Policy directive: "object-src 'self'".
Issues were logged in the Issues panel in Chrome Devtools
Issues logged to the Issues panel in Chrome Devtools indicate unresolved problems. They can come from network request failures, insufficient security controls, and other browser concerns. Open up the Issues panel in Chrome DevTools for more details on each issue.
Issue type
Content security policy
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
15.1.4
core-js
core-js-global@3.33.0
Missing source maps for large first-party JavaScript
Source maps translate minified code to the original source code. This helps developers debug in production. In addition, Lighthouse is able to provide further insights. Consider deploying source maps to take advantage of these benefits. Learn more about source maps.
URL
Map URL
burberry.com
1st party
Large JavaScript file is missing a source map
Large JavaScript file is missing a source map
cloudfront.net
/v3.1.4/3c8ksv.js
(dabs7b6g7t59l.cloudfront.net)
/v3.1.4/sp.js.map
(dabs7b6g7t59l.cloudfront.net)
SyntaxError: Unexpected token '<', "<?xml vers"... is not valid JSON
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
Host allowlists can frequently be bypassed. Consider using CSP nonces or hashes instead, along with `'strict-dynamic'` if necessary.
default-src
High
`'unsafe-inline'` allows the execution of unsafe in-page scripts and event handlers. Consider using CSP nonces or hashes to allow scripts individually.
default-src
High
Avoid using plain URL schemes (data:) in this directive. Plain URL schemes allow scripts to be sourced from an unsafe domain.
default-src
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.
Document uses legible font sizes 100% legible text
Font sizes less than 12px are too small to be legible and require mobile visitors to “pinch to zoom” in order to read. Strive to have >60% of page text ≥12px. Learn more about legible font sizes.
Source
Selector
% of Page Text
Font Size
Legible text
100.00%
≥ 12px
Page has the HTML doctype
Specifying a doctype prevents the browser from switching to quirks-mode. Learn more about the doctype declaration.
Properly defines charset
A character encoding declaration is required. It can be done with a <meta> tag in the first 1024 bytes of the HTML or in the Content-Type HTTP response header. Learn more about declaring the character encoding.
Not applicable (1)
Show Hide
Redirects HTTP traffic to HTTPS
Make sure that you redirect all HTTP traffic to HTTPS in order to enable secure web features for all your users. Learn more.
These checks ensure that your page is following basic search engine optimization advice. There are many additional factors Lighthouse does not score here that may affect your search ranking, including performance on Core Web Vitals. Learn more about Google Search Essentials.
Crawling and Indexing
robots.txt is not valid 1 error found
If your robots.txt file is malformed, crawlers may not be able to understand how you want your website to be crawled or indexed. Learn more about robots.txt.
Line #
Content
Error
32
https://fr.burberry.com/sitemap-fr.xml
Unknown directive
To appear in search results, crawlers need access to your app.
Additional items to manually check (1)
Show Hide
Structured data is valid
Run these additional validators on your site to check additional SEO best practices.
Passed audits (9)
Show Hide
Page isn’t blocked from indexing
Search engines are unable to include your pages in search results if they don't have permission to crawl them. Learn more about crawler directives.
Document has a <title> element
The title gives screen reader users an overview of the page, and search engine users rely on it heavily to determine if a page is relevant to their search. Learn more about document titles.
Document has a meta description
Meta descriptions may be included in search results to concisely summarize page content. Learn more about the meta description.
Page has successful HTTP status code
Pages with unsuccessful HTTP status codes may not be indexed properly. Learn more about HTTP status codes.
Links are crawlable
Search engines may use href attributes on links to crawl websites. Ensure that the href attribute of anchor elements links to an appropriate destination, so more pages of the site can be discovered. Learn how to make links crawlable
Image elements have [alt] attributes
Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the alt attribute.
Document has a valid hreflang
hreflang links tell search engines what version of a page they should list in search results for a given language or region. Learn more about hreflang.
Document has a valid rel=canonical
Canonical links suggest which URL to show in search results. Learn more about canonical links.
Discover what your real users are experiencing
Core Web Vitals Assessment: Passed
Largest Contentful Paint (LCP)
1.4 s
Page LoadsGood (≤ 2.5 s)91%Needs Improvement (2.5 s - 4 s)6%Poor (> 4 s)3%75th Percentile - 1.4 sCore Web Vital
Interaction to Next Paint (INP)
61 ms
Page LoadsGood (≤ 200 ms)96%Needs Improvement (200 ms - 500 ms)3%Poor (> 500 ms)1%75th Percentile - 61 msCore Web Vital
Cumulative Layout Shift (CLS)
0
Page LoadsGood (≤ 0.1)100%Needs Improvement (0.1 - 0.25)0%Poor (> 0.25)0%75th Percentile - 0Core Web Vital
Other Notable Metrics
First Contentful Paint (FCP)
1.2 s
Page LoadsGood (≤ 1.8 s)90%Needs Improvement (1.8 s - 3 s)6%Poor (> 3 s)3%75th Percentile - 1.2 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 desktop devicesMany samples (Chrome UX Report)Full visit durationsVarious network connectionsAll Chrome versions
Core Web Vitals Assessment: Passed
Largest Contentful Paint (LCP)
2 s
Page LoadsGood (≤ 2.5 s)84%Needs Improvement (2.5 s - 4 s)11%Poor (> 4 s)5%75th Percentile - 2 sCore Web Vital
Interaction to Next Paint (INP)
162 ms
Page LoadsGood (≤ 200 ms)80%Needs Improvement (200 ms - 500 ms)14%Poor (> 500 ms)7%75th Percentile - 162 msCore Web Vital
Cumulative Layout Shift (CLS)
0.04
Page LoadsGood (≤ 0.1)79%Needs Improvement (0.1 - 0.25)5%Poor (> 0.25)16%75th Percentile - 0.04Core Web Vital
Other Notable Metrics
First Contentful Paint (FCP)
1.6 s
Page LoadsGood (≤ 1.8 s)80%Needs Improvement (1.8 s - 3 s)13%Poor (> 3 s)7%75th Percentile - 1.6 s 
Time to First Byte (TTFB)
1.2 s
Page LoadsGood (≤ 0.8 s)60%Needs Improvement (0.8 s - 1.8 s)27%Poor (> 1.8 s)12%75th Percentile - 1.2 sExperimental
Latest 28-day collection period
Various desktop devicesMany samples (Chrome UX Report)Full visit durationsVarious network connectionsAll Chrome versions
Diagnose performance issues
63 FCP+10LCP+24TBT+3CLS+25SI+1 Performance
Values are estimated and may vary. The performance score is calculated directly from these metrics.See calculator.
0–49 50–89 90–100
Final Screenshot
Metrics
First Contentful Paint
0.4 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more about the First Contentful Paint metric.
Largest Contentful Paint
1.0 s
Largest Contentful Paint marks the time at which the largest text or image is painted. Learn more about the Largest Contentful Paint metric
Total Blocking Time
770 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.001
Cumulative Layout Shift measures the movement of visible elements within the viewport. Learn more about the Cumulative Layout Shift metric.
Speed Index
3.9 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: 486 CPU throttling: 1x slowdown (Simulated) Screen emulation: 1350x940, DPR 1 Axe version: 4.10.2
  • Single page session
    This data is taken from a single page session, as opposed to field data summarizing many sessions.
  • Initial page load
  • Custom throttling
    Network throttling: 40 ms TCP RTT, 10,240 kb/s throughput (Simulated) Browser location: North America
  • Using HeadlessChromium 133.0.6943.53 with lr
    User agent (network): "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/119.0.0.0 Safari/537.36"
Screenshot
Screenshot
Screenshot
Screenshot
Screenshot
Screenshot
Screenshot
Screenshot
Show audits relevant to:
Diagnostics
Reduce JavaScript execution time 2.6 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to reduce Javascript execution time.TBT
URL
Total CPU Time
Script Evaluation
Script Parse
burberry.com
1st party
2,683 ms
1,826 ms
28 ms
/assets/9dac7dd…
(fr.burberry.com)
1,604 ms
1,408 ms
3 ms
639 ms
164 ms
9 ms
369 ms
184 ms
16 ms
71 ms
70 ms
1 ms
Unattributable
338 ms
70 ms
0 ms
Unattributable
338 ms
70 ms
0 ms
Brightcove
video
332 ms
265 ms
14 ms
…Tc5iqtzRUb_default/index.min.js
(players.brightcove.net)
332 ms
265 ms
14 ms
Google Tag Manager
tag-manager
144 ms
110 ms
8 ms
/gtm.js?id=…
(www.googletagmanager.com)
144 ms
110 ms
8 ms
Optimizely
analytics
120 ms
111 ms
5 ms
/js/174….js
(cdn.optimizely.com)
120 ms
111 ms
5 ms
Optanon
consent-provider
110 ms
69 ms
6 ms
…202403.2.0/otBannerSdk.js
(cdn.cookielaw.org)
110 ms
69 ms
6 ms
New Relic
utility
59 ms
55 ms
2 ms
/nr-spa-1.283.2.min.js
(js-agent.newrelic.com)
59 ms
55 ms
2 ms
Minimize main-thread work 4.1 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to minimize main-thread workTBT
Category
Time Spent
Script Evaluation
2,708 ms
Other
539 ms
Style & Layout
320 ms
Garbage Collection
236 ms
Script Parsing & Compilation
92 ms
Parse HTML & CSS
89 ms
Rendering
86 ms
Reduce initial server response time Root document took 3,100 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
burberry.com
1st party
3,100 ms
3,100 ms
Avoid an excessive DOM size 2,465 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,465
Maximum DOM Depth
a.css-11cfnoo > div.e14owicd1 > picture > source
<source sizes="(max-width: 1023px) 100vw, 50vw" srcset="https://assets.burberry.com/is/image/Burberryltd/2102306A-6768-45CD-87E4-A…" media="(max-width: 1023px)">
17
Maximum Child Elements
PlayUnmuteCurrent Time 0:00/Duration 0:00Loaded: 0%Stream Type LIVESeek to live…
<div class="vjs-control-bar" dir="ltr">
17
Reduce unused JavaScript Potential savings of 699 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
burberry.com
1st party
679.9 KiB
415.4 KiB
191.3 KiB
189.6 KiB
351.1 KiB
174.3 KiB
82.3 KiB
29.9 KiB
/assets/9dac7dd…
(fr.burberry.com)
55.2 KiB
21.5 KiB
Brightcove
video
221.9 KiB
134.1 KiB
…Tc5iqtzRUb_default/index.min.js
(players.brightcove.net)
221.9 KiB
134.1 KiB
Optanon
consent-provider
108.2 KiB
57.5 KiB
…202403.2.0/otBannerSdk.js
(cdn.cookielaw.org)
108.2 KiB
57.5 KiB
Google Tag Manager
tag-manager
139.4 KiB
53.5 KiB
/gtm.js?id=…
(www.googletagmanager.com)
139.4 KiB
53.5 KiB
Optimizely
analytics
100.4 KiB
38.9 KiB
/js/174….js
(cdn.optimizely.com)
100.4 KiB
38.9 KiB
Enable text compression Potential savings of 5 KiB
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.
URL
Transfer Size
Potential Savings
Brightcove
video
6.6 KiB
4.6 KiB
…videos/636…
(edge.api.brightcove.com)
3.3 KiB
2.3 KiB
…videos/636…
(edge.api.brightcove.com)
3.3 KiB
2.3 KiB
Serve static assets with an efficient cache policy 84 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
burberry.com
1st party
5,907 KiB
1m 22s
4 KiB
1m 39s
5 KiB
1m 58s
1 KiB
2m 19s
4 KiB
…assets/index-BR9hTRLz.css
(creativetech.static.burberry.com)
2m 30s
1 KiB
2m 46s
30 KiB
2m 58s
9 KiB
3m
2 KiB
3m 17s
352 KiB
3m 23s
21 KiB
4m 35s
6 KiB
7m 8s
12 KiB
7m 35s
4 KiB
7m 56s
2 KiB
9m 7s
5 KiB
9m 34s
6 KiB
9m 57s
6 KiB
/assets/9dac7dd…
(fr.burberry.com)
10m
56 KiB
11m 5s
5 KiB
11m 23s
1 KiB
12m 27s
83 KiB
12m 52s
6 KiB
13m 34s
1 KiB
…assets/index-B9nRAYWM.js
(creativetech.static.burberry.com)
18m 55s
4 KiB
7d
2,786 KiB
7d
549 KiB
7d
275 KiB
7d
259 KiB
7d
175 KiB
7d
125 KiB
7d
90 KiB
7d
55 KiB
7d
37 KiB
7d
33 KiB
7d
30 KiB
7d
29 KiB
7d
27 KiB
7d
27 KiB
7d
26 KiB
7d
24 KiB
7d
23 KiB
7d
22 KiB
7d
22 KiB
7d
20 KiB
7d
19 KiB
7d
19 KiB
7d
19 KiB
7d
18 KiB
7d
18 KiB
7d
18 KiB
7d
18 KiB
7d
16 KiB
7d
16 KiB
7d
15 KiB
7d
15 KiB
7d
15 KiB
7d
12 KiB
7d
10 KiB
7d
10 KiB
7d
2 KiB
7d
1 KiB
…oracle-book/oracle-book.woff2
(common.static.burberry.com)
11d 6h 45m 8s
60 KiB
11d 14h 45m 34s
192 KiB
11d 18h 52m 1s
3 KiB
12d 3h 26m 33s
64 KiB
12d 3h 26m 33s
17 KiB
12d 12h 40m 20s
5 KiB
12d 12h 46m 46s
7 KiB
12d 13h 13m 2s
7 KiB
12d 17h 25s
7 KiB
12d 17h 3m 38s
1 KiB
12d 17h 3m 41s
1 KiB
12d 17h 35m 5s
11 KiB
12d 18h 27m 52s
1 KiB
12d 21h 41m 14s
12 KiB
12d 22h 48m 41s
2 KiB
13d 10h 29m 40s
19 KiB
Brightcove
video
223 KiB
…Tc5iqtzRUb_default/index.min.js
(players.brightcove.net)
1s
223 KiB
Optanon
consent-provider
123 KiB
…202403.2.0/otBannerSdk.js
(cdn.cookielaw.org)
1d
109 KiB
1d
8 KiB
1d
3 KiB
1d
3 KiB
Optimizely
analytics
101 KiB
/js/174….js
(cdn.optimizely.com)
2m
101 KiB
cloudfront.net
22 KiB
/v3.1.4/3c8ksv.js
(dabs7b6g7t59l.cloudfront.net)
None
22 KiB
Properly size images Potential savings of 787 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
burberry.com
1st party
1,318.2 KiB
786.9 KiB
Dessin du Chevalier Burberry EKD sur un cheval
<img alt="Dessin du Chevalier Burberry EKD sur un cheval" sizes="(max-width: 1023px) 100vw, 50vw" loading="lazy" fetchpriority="auto" style="transition: opacity 200ms; opacity: 1;" src="https://assets.burberry.com/is/image/Burberryltd/0DBF5FF6-83B8-4976-982D-D…">
274.4 KiB
139.0 KiB
La campagne "It's Always Burberry Weather" avec un mannequin portant un trench …
<img alt="La campagne &quot;It's Always Burberry Weather&quot; avec un mannequin portant un tr…" sizes="(max-width: 1023px) 100vw, 50vw" loading="lazy" fetchpriority="auto" style="transition: opacity 200ms; opacity: 1;" src="https://assets.burberry.com/is/image/Burberryltd/5BFA5685-90EB-4FB7-9037-3…">
258.7 KiB
131.1 KiB
La campagne "It's Always Burberry Weather" avec deux mannequins portant des tre…
<img alt="La campagne &quot;It's Always Burberry Weather&quot; avec deux mannequins portant de…" sizes="(max-width: 1023px) 100vw, 50vw" loading="lazy" fetchpriority="auto" style="transition: opacity 200ms; opacity: 1;" src="https://assets.burberry.com/is/image/Burberryltd/3743A52B-9F26-44CC-A53F-2…">
174.3 KiB
88.3 KiB
Écharpe en laine Check EKD coloris sable
<img alt="Écharpe en laine Check EKD coloris sable" sizes="(max-width: 1023px) 100vw, 50vw" loading="lazy" fetchpriority="auto" style="transition: opacity 200ms; opacity: 1;" src="https://assets.burberry.com/is/image/Burberryltd/6D2CED73-0B22-4F13-BEDE-E…" srcset="https://assets.burberry.com/is/image/Burberryltd/6D2CED73-0B22-4F13-BEDE-E…">
54.8 KiB
42.9 KiB
Petit sac Messenger B Clip
<img alt="Petit sac Messenger B Clip" src="https://assets.burberry.com/is/image/Burberryltd/7C364AEA-0A11-44C1-9D41-5…" sizes="(max-width: 1023px) 50vw, 30vw" loading="lazy" fetchpriority="auto" style="transition: opacity 200ms; opacity: 1;">
35.9 KiB
28.6 KiB
Trench long avec foulard soie
<img alt="Trench long avec foulard soie" src="https://assets.burberry.com/is/image/Burberryltd/D28197A8-B145-4045-95B3-7…" sizes="(max-width: 1023px) 50vw, 30vw" loading="lazy" fetchpriority="auto" style="transition: opacity 200ms; opacity: 1;">
31.8 KiB
25.4 KiB
Ceinture en toile Check coloris sable
<img alt="Ceinture en toile Check coloris sable" src="https://assets.burberry.com/is/image/Burberryltd/FA50A4EA-C670-4166-8A43-4…" srcset="https://assets.burberry.com/is/image/Burberryltd/FA50A4EA-C670-4166-8A43-4…" sizes="(max-width: 1023px) 100vw, 50vw" loading="lazy" fetchpriority="auto" style="transition: opacity 200ms; opacity: 1;">
28.9 KiB
22.6 KiB
Veste trench en gabardine
<img alt="Veste trench en gabardine" src="https://assets.burberry.com/is/image/Burberryltd/BFC71332-5EF9-40BD-AAA6-F…" sizes="(max-width: 1023px) 50vw, 30vw" loading="lazy" fetchpriority="auto" style="transition: opacity 200ms; opacity: 1;">
28.1 KiB
22.4 KiB
Sac ceinture Check
<img alt="Sac ceinture Check" src="https://assets.burberry.com/is/image/Burberryltd/9F4B6758-BED4-4A55-883D-8…" sizes="(max-width: 1023px) 50vw, 30vw" loading="lazy" fetchpriority="auto" style="transition: opacity 200ms; opacity: 1;">
26.7 KiB
21.3 KiB
Petit sac Messenger B Clip
<img alt="Petit sac Messenger B Clip" src="https://assets.burberry.com/is/image/Burberryltd/3B61FBE3-C53E-463C-91E9-F…" sizes="(max-width: 1023px) 50vw, 30vw" loading="lazy" fetchpriority="auto" style="transition: opacity 200ms; opacity: 1;">
26.1 KiB
20.8 KiB
Trench mi-long en gabardine
<img alt="Trench mi-long en gabardine" src="https://assets.burberry.com/is/image/Burberryltd/5ABDCF4D-0009-492B-9EAD-8…" sizes="(max-width: 1023px) 50vw, 30vw" loading="lazy" fetchpriority="auto" style="transition: opacity 200ms; opacity: 1;">
25.6 KiB
20.4 KiB
Veste trench en coton mélangé coloris beige
<img alt="Veste trench en coton mélangé coloris beige" src="https://assets.burberry.com/is/image/Burberryltd/95E5A846-F470-44B7-BEDF-0…" srcset="https://assets.burberry.com/is/image/Burberryltd/95E5A846-F470-44B7-BEDF-0…" sizes="(max-width: 1023px) 100vw, 50vw" loading="lazy" fetchpriority="auto" style="transition: opacity 200ms; opacity: 1;">
23.2 KiB
18.1 KiB
Trench long avec foulard soie
<img alt="Trench long avec foulard soie" src="https://assets.burberry.com/is/image/Burberryltd/FE5185CD-1EBF-4579-8738-7…" sizes="(max-width: 1023px) 50vw, 30vw" loading="lazy" fetchpriority="auto" style="transition: opacity 200ms; opacity: 1;">
22.4 KiB
17.8 KiB
Trench mi-long en gabardine
<img alt="Trench mi-long en gabardine" src="https://assets.burberry.com/is/image/Burberryltd/2121FAA5-147E-4E6B-8987-5…" sizes="(max-width: 1023px) 50vw, 30vw" loading="lazy" fetchpriority="auto" style="transition: opacity 200ms; opacity: 1;">
21.4 KiB
17.1 KiB
Débardeur Festival en coton mélangé
<img alt="Débardeur Festival en coton mélangé" src="https://assets.burberry.com/is/image/Burberryltd/EE9D6F02-7AE4-4192-9CE2-1…" sizes="(max-width: 1023px) 50vw, 30vw" loading="lazy" fetchpriority="auto" style="transition: opacity 200ms; opacity: 1;">
21.2 KiB
16.9 KiB
div#video-player > div.css-h0bjib > picture > img
<img sizes="100vw" loading="lazy" fetchpriority="auto" style="transition: opacity 200ms; opacity: 1;" src="https://assets.burberry.com/is/image/Burberryltd/3469BA15-BDCD-48A8-A3FC-9…">
89.8 KiB
16.0 KiB
Trench long Castleford coloris beige
<img alt="Trench long Castleford coloris beige" sizes="(max-width: 1023px) 100vw, 50vw" loading="lazy" fetchpriority="auto" style="transition: opacity 200ms; opacity: 1;" src="https://assets.burberry.com/is/image/Burberryltd/266684BD-EB0B-4E63-8304-0…" srcset="https://assets.burberry.com/is/image/Burberryltd/266684BD-EB0B-4E63-8304-0…">
19.4 KiB
15.2 KiB
Veste trench en gabardine
<img alt="Veste trench en gabardine" src="https://assets.burberry.com/is/image/Burberryltd/27733B82-3A28-4FC2-8A61-2…" sizes="(max-width: 1023px) 50vw, 30vw" loading="lazy" fetchpriority="auto" style="transition: opacity 200ms; opacity: 1;">
18.8 KiB
14.9 KiB
Trench long en coton mélangé coloris Heron
<img alt="Trench long en coton mélangé coloris Heron" src="https://assets.burberry.com/is/image/Burberryltd/7951DA2F-72ED-4300-8AE3-D…" srcset="https://assets.burberry.com/is/image/Burberryltd/7951DA2F-72ED-4300-8AE3-D…" sizes="(max-width: 1023px) 100vw, 50vw" loading="lazy" fetchpriority="auto" style="transition: opacity 200ms; opacity: 1;">
18.5 KiB
14.5 KiB
Paletot long en coton mélangé
<img alt="Paletot long en coton mélangé" src="https://assets.burberry.com/is/image/Burberryltd/3990F3CA-A5EE-400D-9D62-3…" sizes="(max-width: 1023px) 50vw, 30vw" loading="lazy" fetchpriority="auto" style="transition: opacity 200ms; opacity: 1;">
18.1 KiB
14.4 KiB
Paletot long en coton mélangé
<img alt="Paletot long en coton mélangé" src="https://assets.burberry.com/is/image/Burberryltd/AD66ACB3-3DB7-4113-8808-6…" sizes="(max-width: 1023px) 50vw, 30vw" loading="lazy" fetchpriority="auto" style="transition: opacity 200ms; opacity: 1;">
17.5 KiB
13.9 KiB
Paletot long en gabardine coloris Fossil
<img alt="Paletot long en gabardine coloris Fossil" sizes="(max-width: 1023px) 100vw, 50vw" loading="lazy" fetchpriority="auto" style="transition: opacity 200ms; opacity: 1;" src="https://assets.burberry.com/is/image/Burberryltd/2102306A-6768-45CD-87E4-A…" srcset="https://assets.burberry.com/is/image/Burberryltd/2102306A-6768-45CD-87E4-A…">
17.4 KiB
13.6 KiB
Sac ceinture Check
<img alt="Sac ceinture Check" src="https://assets.burberry.com/is/image/Burberryltd/2396429B-AA3F-472A-BDF7-1…" sizes="(max-width: 1023px) 50vw, 30vw" loading="lazy" fetchpriority="auto" style="transition: opacity 200ms; opacity: 1;">
17.1 KiB
13.6 KiB
Trench long Castleford coloris Juniper
<img alt="Trench long Castleford coloris Juniper" sizes="(max-width: 1023px) 100vw, 50vw" loading="lazy" fetchpriority="auto" style="transition: opacity 200ms; opacity: 1;" src="https://assets.burberry.com/is/image/Burberryltd/D0846537-D111-4A70-B3BD-4…" srcset="https://assets.burberry.com/is/image/Burberryltd/D0846537-D111-4A70-B3BD-4…">
17.2 KiB
13.4 KiB
Débardeur Festival en coton mélangé
<img alt="Débardeur Festival en coton mélangé" src="https://assets.burberry.com/is/image/Burberryltd/B8E4BF57-15E3-47FA-A07A-F…" sizes="(max-width: 1023px) 50vw, 30vw" loading="lazy" fetchpriority="auto" style="transition: opacity 200ms; opacity: 1;">
15.5 KiB
12.3 KiB
Polo en coton
<img alt="Polo en coton" src="https://assets.burberry.com/is/image/Burberryltd/68388EA4-A103-4397-A0B6-1…" sizes="(max-width: 1023px) 50vw, 30vw" loading="lazy" fetchpriority="auto" style="transition: opacity 200ms; opacity: 1;">
15.4 KiB
12.3 KiB
Defer offscreen images Potential savings of 3 KiB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive. Learn how to defer offscreen images.LCPFCP
Next.jsUse the next/image component instead of <img> to automatically lazy-load images. Learn more.
URL
Resource Size
Potential Savings
Optanon
consent-provider
2.8 KiB
2.8 KiB
Powered by Onetrust
<img alt="Powered by Onetrust" src="https://cdn.cookielaw.org/logos/static/powered_by_logo.svg">
2.8 KiB
2.8 KiB
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
…202403.2.0/otBannerSdk.js
(cdn.cookielaw.org)
6.9 KiB
Array.prototype.fill
burberry.com
1st party
0.3 KiB
0.1 KiB
@babel/plugin-transform-classes
0.1 KiB
@babel/plugin-transform-classes
0.1 KiB
@babel/plugin-transform-classes
0.0 KiB
@babel/plugin-transform-classes
0.0 KiB
@babel/plugin-transform-classes
Brightcove
video
0.0 KiB
…Tc5iqtzRUb_default/index.min.js
(players.brightcove.net)
0.0 KiB
@babel/plugin-transform-classes
Reduce unused CSS Potential savings of 18 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
#onetrust-banner-sdk{-ms-text-size-adjust:100%;-webkit-text-size-adjust:100%} …
21.2 KiB
18.3 KiB
Avoid enormous network payloads Total size was 6,837 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
burberry.com
1st party
4,712.7 KiB
2,785.8 KiB
548.9 KiB
351.9 KiB
275.0 KiB
259.3 KiB
192.2 KiB
174.9 KiB
124.8 KiB
Brightcove
video
222.7 KiB
…Tc5iqtzRUb_default/index.min.js
(players.brightcove.net)
222.7 KiB
Google Tag Manager
tag-manager
140.5 KiB
/gtm.js?id=…
(www.googletagmanager.com)
140.5 KiB
Avoid long main-thread tasks 8 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay. Learn how to avoid long main-thread tasksTBT
URL
Start Time
Duration
burberry.com
1st party
1,004 ms
3,164 ms
294 ms
/assets/9dac7dd…
(fr.burberry.com)
3,465 ms
239 ms
/assets/9dac7dd…
(fr.burberry.com)
2,955 ms
209 ms
3,983 ms
140 ms
/assets/9dac7dd…
(fr.burberry.com)
715 ms
122 ms
Brightcove
video
141 ms
…Tc5iqtzRUb_default/index.min.js
(players.brightcove.net)
2,769 ms
141 ms
Optimizely
analytics
107 ms
/js/174….js
(cdn.optimizely.com)
1,081 ms
107 ms
Google Tag Manager
tag-manager
62 ms
/gtm.js?id=…
(www.googletagmanager.com)
3,753 ms
62 ms
Minimize third-party usage Third-party code blocked the main thread for 150 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
Brightcove
video
252 KiB
87 ms
…Tc5iqtzRUb_default/index.min.js
(players.brightcove.net)
223 KiB
87 ms
…videos/636…
(edge.api.brightcove.com)
11 KiB
0 ms
8 KiB
0 ms
…videos/636…
(edge.api.brightcove.com)
5 KiB
0 ms
/v2/tracker?domain=…
(metrics.brightcove.com)
0 KiB
0 ms
/v2/tracker?domain=…
(metrics.brightcove.com)
0 KiB
0 ms
/v2/tracker?domain=…
(metrics.brightcove.com)
0 KiB
0 ms
/v2/tracker?domain=…
(metrics.brightcove.com)
0 KiB
0 ms
/v2/tracker?domain=…
(metrics.brightcove.com)
0 KiB
0 ms
/v2/tracker?domain=…
(metrics.brightcove.com)
0 KiB
0 ms
/v2/tracker?domain=…
(metrics.brightcove.com)
0 KiB
0 ms
/v2/tracker?domain=…
(metrics.brightcove.com)
0 KiB
0 ms
/v2/tracker?domain=…
(metrics.brightcove.com)
0 KiB
0 ms
/v2/tracker?domain=…
(metrics.brightcove.com)
0 KiB
0 ms
/v2/tracker?domain=…
(metrics.brightcove.com)
0 KiB
0 ms
/v2/tracker?domain=…
(metrics.brightcove.com)
0 KiB
0 ms
Optimizely
analytics
103 KiB
56 ms
/js/174….js
(cdn.optimizely.com)
101 KiB
56 ms
/client_storage/a174….html
(a17489381590.cdn-pci.optimizely.com)
1 KiB
0 ms
/v1/events
(logx.optimizely.com)
1 KiB
0 ms
Google Tag Manager
tag-manager
140 KiB
12 ms
/gtm.js?id=…
(www.googletagmanager.com)
140 KiB
12 ms
Optanon
consent-provider
175 KiB
0 ms
…202403.2.0/otBannerSdk.js
(cdn.cookielaw.org)
109 KiB
0 ms
25 KiB
0 ms
…v2/otPcTab.json
(cdn.cookielaw.org)
14 KiB
0 ms
8 KiB
0 ms
…assets/otCommonStyles.css
(cdn.cookielaw.org)
5 KiB
0 ms
3 KiB
0 ms
3 KiB
0 ms
3 KiB
0 ms
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
New Relic
utility
34 KiB
0 ms
/nr-spa-1.283.2.min.js
(js-agent.newrelic.com)
33 KiB
0 ms
/1/883cbb608e?a=…
(bam.nr-data.net)
1 KiB
0 ms
…1/883cbb608e?a=…
(bam.nr-data.net)
0 KiB
0 ms
cloudfront.net
22 KiB
0 ms
/v3.1.4/3c8ksv.js
(dabs7b6g7t59l.cloudfront.net)
22 KiB
0 ms
Avoid large layout shifts 3 layout shifts found
These are the largest layout shifts observed on the page. Each table item represents a single layout shift, and shows the element that shifted the most. Below each item are possible root causes that led to the layout shift. Some of these layout shifts may not be included in the CLS metric value due to windowing. Learn how to improve CLSCLS
Element
Layout shift score
Nos news
<li>
0.001
Web font loaded
Découvrir
<span class="css-1x38lbv ehdpulm0">
0.000
Web font loaded
…oracle-book/oracle-book.woff2
(common.static.burberry.com)
Web font loaded
Web font loaded
body > div#loading-animation
<div id="loading-animation" class="hidden">
0.000
…assets/index-BR9hTRLz.css
(creativetech.static.burberry.com)
A late network request adjusted the page layout
User Timing marks and measures 21 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
4,772.90 ms
Next.js-hydration
Measure
4,772.90 ms
332.52 ms
bcAdBlockDetect
Measure
5,937.24 ms
377.44 ms
bcInit
Measure
6,133.38 ms
113.02 ms
bcInit
Measure
6,133.38 ms
128.83 ms
bcInit
Measure
6,133.38 ms
145.84 ms
optimizely:blockBegin
Mark
4,022.36 ms
beforeRender
Mark
4,772.90 ms
afterHydrate
Mark
5,105.42 ms
clearMarks
Mark
5,105.82 ms
clearMarks
Mark
5,105.83 ms
clearMarks
Mark
5,105.83 ms
clearMarks
Mark
5,105.83 ms
bcAdBlockDetectStart
Mark
5,937.24 ms
bcInitStart
Mark
5,956.66 ms
bcInitStart
Mark
6,081.71 ms
bcInitStart
Mark
6,133.38 ms
bcInitEnd
Mark
6,246.41 ms
bcInitEnd
Mark
6,262.21 ms
bcInitEnd
Mark
6,279.22 ms
bcAdBlockDetectEnd
Mark
6,314.67 ms
Avoid non-composited animations 4 animated elements found
Animations which are not composited can be janky and increase CLS. Learn how to avoid non-composited animationsCLS
Element
Name
section.css-1ea9d78 > div.css-1elx8sn > div.css-1965q92 > div.css-m91ho0
<div color="black" data-testid="dashEl" class="css-m91ho0 emvjbqg5">
Unsupported CSS Property: background-color
background-color
section.css-1ea9d78 > div.css-1elx8sn > div.css-1965q92 > div.css-m91ho0
<div color="black" data-testid="dashEl" class="css-m91ho0 emvjbqg5">
Unsupported CSS Property: background-color
background-color
section.css-1ea9d78 > div.css-1elx8sn > div.css-1965q92 > div.css-m91ho0
<div color="black" data-testid="dashEl" class="css-m91ho0 emvjbqg5">
Unsupported CSS Property: background-color
background-color
section.css-1ea9d78 > div.css-1elx8sn > div.css-1965q92 > div.css-m91ho0
<div color="black" data-testid="dashEl" class="css-m91ho0 emvjbqg5">
Unsupported CSS Property: background-color
background-color
Largest Contentful Paint element 1,030 ms
This is the largest contentful element painted within the viewport. Learn more about the Largest Contentful Paint elementLCP
Element
La campagne "It's Always Burberry Weather" avec Aimee Lou Wood et Michael Ward …
<img alt="La campagne &quot;It's Always Burberry Weather&quot; avec Aimee Lou Wood et Michael …" src="https://assets.burberry.com/is/image/Burberryltd/2830A59F-F04B-4401-99E2-5…" sizes="100vw" loading="eager" fetchpriority="high" style="opacity:1">
Phase
% of LCP
Timing
TTFB
16%
160 ms
Load Delay
75%
770 ms
Load Time
3%
40 ms
Render Delay
6%
60 ms
More information about the performance of your application. These numbers don't directly affect the Performance score.
Passed audits (18)
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.
Preconnect to required origins
Warnings:
  • A `<link rel=preconnect>` was found for "https://api.burberry.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: 3,613.376 ms
Initial Navigation
- 3,613.376 ms, 123.81 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
Element
La campagne "It's Always Burberry Weather" avec Aimee Lou Wood et Michael Ward …
<img alt="La campagne &quot;It's Always Burberry Weather&quot; avec Aimee Lou Wood et Michael …" src="https://assets.burberry.com/is/image/Burberryltd/2830A59F-F04B-4401-99E2-5…" sizes="100vw" loading="eager" fetchpriority="high" style="opacity:1">
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.
These checks highlight opportunities to improve the accessibility of your web app. Automatic detection can only detect a subset of issues and does not guarantee the accessibility of your web app, so manual testing is also encouraged.
ARIA
[aria-*] attributes do not have valid values
Assistive technologies, like screen readers, can't interpret ARIA attributes with invalid values. Learn more about valid values for ARIA attributes.
Failing Elements
Langue Français
<button data-testid="language-picker-button" aria-controls="language-picker-modal" aria-label="Cliquez pour ouvrir la fenêtre des langues et modifier la langue" class="css-8sgliu e1yvoxgm0">
Lieu de livraison France (€)
<button data-testid="country-picker-button" aria-controls="country-picker-modal" aria-label="Cliquez pour ouvrir la fenêtre des destinations et modifier le lieu de liv…" class="css-8sgliu e1yvoxgm0">
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Names and labels
Buttons do not have an accessible name
When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.
Failing Elements
div.css-4upfm0 > section.css-1ea9d78 > div#carousel-pagination-controls > button.css-3dcfz3
<button aria-label="" class="css-3dcfz3 e1o4l6710">
div.css-4upfm0 > section.css-1ea9d78 > div#carousel-pagination-controls > button.css-3dcfz3
<button aria-label="" class="css-3dcfz3 e1o4l6710">
div#blte5df5423f7e8e1f9 > div.e1w7ayjm0 > article#blte5df542f7e8e1f9-position-0 > button
<button data-state="playing" style="border: 0px solid transparent; background: none; position: absolute;">
Image elements do not have [alt] attributes
Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the alt attribute.
Failing Elements
div#video-player > div.css-h0bjib > picture > img
<img sizes="100vw" loading="lazy" fetchpriority="auto" style="transition: opacity 200ms; opacity: 1;" src="https://assets.burberry.com/is/image/Burberryltd/3469BA15-BDCD-48A8-A3FC-9…">
div#video-player > div.css-h0bjib > picture > img
<img sizes="100vw" loading="lazy" fetchpriority="auto" style="transition: opacity 200ms; opacity: 1;" src="https://assets.burberry.com/is/image/Burberryltd/3469BA15-BDCD-48A8-A3FC-9…">
<frame> or <iframe> elements do not have a title
Screen reader users rely on frame titles to describe the contents of frames. Learn more about frame titles.
Failing Elements
div.css-1et4pk2 > div#blta677215f3311460e > div.css-v7gwe8 > iframe.css-1dzg4bz
<iframe data-testid="iframe" src="https://creativetech.static.burberry.com/yt-reveal/injection/live/index.ht…" loading="lazy" allow="fullscreen; gyroscope; accelerometer; camera *; autoplay *; web-share" class="css-1dzg4bz emxi7ie2">
div#blte5df5423f7e8e1f9 > div.e1w7ayjm0 > article#blte5df542f7e8e1f9-position-0 > iframe
<iframe src="https://creativetech.static.burberry.com/signup-video-overlay/live/index.h…" style="position: absolute; z-index: 10; border: none; height: 100%; width: 100%;">
<object> elements do not 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.
Failing Elements
div#video-player > div.css-jsngzv > video-js#vjs_video_3 > object#vjs_video_3_flash_api
<object type="application/x-shockwave-flash" data="//players.brightcove.net/videojs-flashls-source-handler/1.4.8/video-js.swf" width="100%" height="100%" id="vjs_video_3_flash_api" name="vjs_video_3_flash_api" class="vjs-tech">
div#video-player > div.css-jsngzv > video-js#vjs_video_655 > object#vjs_video_655_flash_api
<object type="application/x-shockwave-flash" data="//players.brightcove.net/videojs-flashls-source-handler/1.4.8/video-js.swf" width="100%" height="100%" id="vjs_video_655_flash_api" name="vjs_video_655_flash_api" class="vjs-tech">
div#video-player > div.css-jsngzv > video-js#vjs_video_1280 > object#vjs_video_1280_flash_api
<object type="application/x-shockwave-flash" data="//players.brightcove.net/videojs-flashls-source-handler/1.4.8/video-js.swf" width="100%" height="100%" id="vjs_video_1280_flash_api" name="vjs_video_1280_flash_api" class="vjs-tech">
These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.
Best practices
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a web page. Learn more about the viewport meta tag.
Failing Elements
head > meta
<meta name="viewport" content="width=device-width, initial-scale=1, maximum-scale=1, viewport-fit=cover" data-next-head="">
These items highlight common accessibility best practices.
Additional items to manually check (10)
Show Hide
Interactive controls are keyboard focusable
Custom interactive controls are keyboard focusable and display a focus indicator. Learn how to make custom controls focusable.
Interactive elements indicate their purpose and state
Interactive elements, such as links and buttons, should indicate their state and be distinguishable from non-interactive elements. Learn how to decorate interactive elements with affordance hints.
The page has a logical tab order
Tabbing through the page follows the visual layout. Users cannot focus elements that are offscreen. Learn more about logical tab ordering.
Visual order on the page follows DOM order
DOM order matches the visual order, improving navigation for assistive technology. Learn more about DOM and visual ordering.
User focus is not accidentally trapped in a region
A user can tab into and out of any control or region without accidentally trapping their focus. Learn how to avoid focus traps.
The user's focus is directed to new content added to the page
If new content, such as a dialog, is added to the page, the user's focus is directed to it. Learn how to direct focus to new content.
HTML5 landmark elements are used to improve navigation
Landmark elements (<main>, <nav>, etc.) are used to improve the keyboard navigation of the page for assistive technology. Learn more about landmark elements.
Offscreen content is hidden from assistive technology
Offscreen content is hidden with display: none or aria-hidden=true. Learn how to properly hide offscreen content.
Custom controls have associated labels
Custom interactive controls have associated labels, provided by aria-label or aria-labelledby. Learn more about custom controls and labels.
Custom controls have ARIA roles
Custom interactive controls have appropriate ARIA roles. Learn how to add roles to custom controls.
These items address areas which an automated testing tool cannot cover. Learn more in our guide on conducting an accessibility review.
Passed audits (25)
Show Hide
[aria-*] attributes match their roles
Each ARIA role supports a specific subset of aria-* attributes. Mismatching these invalidates the aria-* attributes. Learn how to match ARIA attributes to their roles.
[aria-hidden="true"] is not present on the document <body>
Assistive technologies, like screen readers, work inconsistently when aria-hidden="true" is set on the document <body>. Learn how aria-hidden affects the document body.
[role]s have all required [aria-*] attributes
Some ARIA roles have required attributes that describe the state of the element to screen readers. Learn more about roles and required attributes.
[aria-*] attributes are valid and not misspelled
Assistive technologies, like screen readers, can't interpret ARIA attributes with invalid names. Learn more about valid ARIA attributes.
ARIA attributes are used as specified for the element's role
Some ARIA attributes are only allowed on an element under certain conditions. Learn more about conditional ARIA attributes.
Elements with role="dialog" or role="alertdialog" have accessible names.
ARIA dialog elements without accessible names may prevent screen readers users from discerning the purpose of these elements. Learn how to make ARIA dialog elements more accessible.
[aria-hidden="true"] elements do not contain focusable descendents
Focusable descendents within an [aria-hidden="true"] element prevent those interactive elements from being available to users of assistive technologies like screen readers. Learn how aria-hidden affects focusable elements.
Elements use only permitted ARIA attributes
Using ARIA attributes in roles where they are prohibited can mean that important information is not communicated to users of assistive technologies. Learn more about prohibited ARIA roles.
[role] values are valid
ARIA roles must have valid values in order to perform their intended accessibility functions. Learn more about valid ARIA roles.
Background and foreground colors have a sufficient contrast ratio
Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.
Document has a <title> element
The title gives screen reader users an overview of the page, and search engine users rely on it heavily to determine if a page is relevant to their search. Learn more about document titles.
<html> element has a [lang] attribute
If a page doesn't specify a lang attribute, a screen reader assumes that the page is in the default language that the user chose when setting up the screen reader. If the page isn't actually in the default language, then the screen reader might not announce the page's text correctly. Learn more about the lang attribute.
<html> element has a valid value for its [lang] attribute
Specifying a valid BCP 47 language helps screen readers announce text properly. Learn how to use the lang attribute.
Form elements have associated labels
Labels ensure that form controls are announced properly by assistive technologies, like screen readers. Learn more about form element labels.
Lists contain only <li> elements and script supporting elements (<script> and <template>).
Screen readers have a specific way of announcing lists. Ensuring proper list structure aids screen reader output. Learn more about proper list structure.
List items (<li>) are contained within <ul>, <ol> or <menu> parent elements
Screen readers require list items (<li>) to be contained within a parent <ul>, <ol> or <menu> to be announced properly. Learn more about proper list structure.
No element has a [tabindex] value greater than 0
A value greater than 0 implies an explicit navigation ordering. Although technically valid, this often creates frustrating experiences for users who rely on assistive technologies. Learn more about the tabindex attribute.
Touch targets have sufficient size and spacing.
Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.
[lang] attributes have a valid value
Specifying a valid BCP 47 language on elements helps ensure that text is pronounced correctly by a screen reader. Learn how to use the lang attribute.
Heading elements appear in a sequentially-descending order
Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.
Uses ARIA roles only on compatible elements
Many HTML elements can only be assigned certain ARIA roles. Using ARIA roles where they are not allowed can interfere with the accessibility of the web page. Learn more about ARIA roles.
Deprecated ARIA roles were not used
Deprecated ARIA roles may not be processed correctly by assistive technology. Learn more about deprecated ARIA roles.
Image elements do not have [alt] attributes that are redundant text.
Informative elements should aim for short, descriptive alternative text. Alternative text that is exactly the same as the text adjacent to the link or image is potentially confusing for screen reader users, because the text will be read twice. Learn more about the alt attribute.
Not applicable (26)
Show Hide
[accesskey] values are unique
Access keys let users quickly focus a part of the page. For proper navigation, each access key must be unique. Learn more about access keys.
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.
ARIA IDs are unique
The value of an ARIA ID must be unique to prevent other instances from being overlooked by assistive technologies. Learn how to fix duplicate ARIA IDs.
No form fields have multiple labels
Form fields with multiple labels can be confusingly announced by assistive technologies like screen readers which use either the first, the last, or all of the labels. Learn how to use form labels.
<html> element has an [xml:lang] attribute with the same base language as the [lang] attribute.
If the webpage does not specify a consistent language, then the screen reader might not announce the page's text correctly. Learn more about the lang attribute.
Input buttons have discernible text.
Adding discernable and accessible text to input buttons may help screen reader users understand the purpose of the input button. Learn more about input buttons.
<input type="image"> elements have [alt] text
When an image is being used as an <input> button, providing alternative text can help screen reader users understand the purpose of the button. Learn about input image alt text.
The document does not use <meta http-equiv="refresh">
Users do not expect a page to refresh automatically, and doing so will move focus back to the top of the page. This may create a frustrating or confusing experience. Learn more about the refresh meta tag.
Select elements have associated label elements.
Form elements without effective labels can create frustrating experiences for screen reader users. Learn more about the select element.
Tables have different content in the summary attribute and <caption>.
The summary attribute should describe the table structure, while <caption> should have the onscreen title. Accurate table mark-up helps users of screen readers. Learn more about summary and caption.
Cells in a <table> element that use the [headers] attribute refer to table cells within the same table.
Screen readers have features to make navigating tables easier. Ensuring <td> cells using the [headers] attribute only refer to other cells in the same table may improve the experience for screen reader users. Learn more about the headers attribute.
<th> elements and elements with [role="columnheader"/"rowheader"] have data cells they describe.
Screen readers have features to make navigating tables easier. Ensuring table headers always refer to some set of cells may improve the experience for screen reader users. Learn more about table headers.
<video> elements contain a <track> element with [kind="captions"]
When a video provides a caption it is easier for deaf and hearing impaired users to access its information. Learn more about video captions.
General
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
Brightcove
video
Refused to load plugin data from 'https://players.brightcove.net/videojs-flashls-source-handler/1.4.8/video-js.swf' because it violates the following Content Security Policy directive: "object-src 'self'".
Refused to load plugin data from 'https://players.brightcove.net/videojs-flashls-source-handler/1.4.8/video-js.swf' because it violates the following Content Security Policy directive: "object-src 'self'".
burberry.com
1st party
Refused to load plugin data from 'https://players.brightcove.net/videojs-flashls-source-handler/1.4.8/video-js.swf' because it violates the following Content Security Policy directive: "object-src 'self'".
Issues were logged in the Issues panel in Chrome Devtools
Issues logged to the Issues panel in Chrome Devtools indicate unresolved problems. They can come from network request failures, insufficient security controls, and other browser concerns. Open up the Issues panel in Chrome DevTools for more details on each issue.
Issue type
Content security policy
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
15.1.4
core-js
core-js-global@3.33.0
Missing source maps for large first-party JavaScript
Source maps translate minified code to the original source code. This helps developers debug in production. In addition, Lighthouse is able to provide further insights. Consider deploying source maps to take advantage of these benefits. Learn more about source maps.
URL
Map URL
burberry.com
1st party
Large JavaScript file is missing a source map
Large JavaScript file is missing a source map
cloudfront.net
/v3.1.4/3c8ksv.js
(dabs7b6g7t59l.cloudfront.net)
/v3.1.4/sp.js.map
(dabs7b6g7t59l.cloudfront.net)
SyntaxError: Unexpected token '<', "<?xml vers"... is not valid JSON
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
Host allowlists can frequently be bypassed. Consider using CSP nonces or hashes instead, along with `'strict-dynamic'` if necessary.
default-src
High
`'unsafe-inline'` allows the execution of unsafe in-page scripts and event handlers. Consider using CSP nonces or hashes to allow scripts individually.
default-src
High
Avoid using plain URL schemes (data:) in this directive. Plain URL schemes allow scripts to be sourced from an unsafe domain.
default-src
High
Passed audits (11)
Show Hide
Uses HTTPS
All sites should be protected with HTTPS, even ones that don't handle sensitive data. This includes avoiding mixed content, where some resources are loaded over HTTP despite the initial request being served over HTTPS. HTTPS prevents intruders from tampering with or passively listening in on the communications between your app and your users, and is a prerequisite for HTTP/2 and many new web platform APIs. Learn more about HTTPS.
Avoids 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.
Not applicable (2)
Show Hide
Redirects HTTP traffic to HTTPS
Make sure that you redirect all HTTP traffic to HTTPS in order to enable secure web features for all your users. Learn more.
Document uses legible font sizes
Font sizes less than 12px are too small to be legible and require mobile visitors to “pinch to zoom” in order to read. Strive to have >60% of page text ≥12px. Learn more about legible font sizes.
These checks ensure that your page is following basic search engine optimization advice. There are many additional factors Lighthouse does not score here that may affect your search ranking, including performance on Core Web Vitals. Learn more about Google Search Essentials.
Crawling and Indexing
robots.txt is not valid 1 error found
If your robots.txt file is malformed, crawlers may not be able to understand how you want your website to be crawled or indexed. Learn more about robots.txt.
Line #
Content
Error
32
https://fr.burberry.com/sitemap-fr.xml
Unknown directive
To appear in search results, crawlers need access to your app.
Content Best Practices
Image elements do not have [alt] attributes
Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the alt attribute.
Failing Elements
div#video-player > div.css-h0bjib > picture > img
<img sizes="100vw" loading="lazy" fetchpriority="auto" style="transition: opacity 200ms; opacity: 1;" src="https://assets.burberry.com/is/image/Burberryltd/3469BA15-BDCD-48A8-A3FC-9…">
div#video-player > div.css-h0bjib > picture > img
<img sizes="100vw" loading="lazy" fetchpriority="auto" style="transition: opacity 200ms; opacity: 1;" src="https://assets.burberry.com/is/image/Burberryltd/3469BA15-BDCD-48A8-A3FC-9…">
Format your HTML in a way that enables crawlers to better understand your app’s content.
Additional items to manually check (1)
Show Hide
Structured data is valid
Run these additional validators on your site to check additional SEO best practices.
Passed audits (8)
Show Hide
Page isn’t blocked from indexing
Search engines are unable to include your pages in search results if they don't have permission to crawl them. Learn more about crawler directives.
Document has a <title> element
The title gives screen reader users an overview of the page, and search engine users rely on it heavily to determine if a page is relevant to their search. Learn more about document titles.
Document has a meta description
Meta descriptions may be included in search results to concisely summarize page content. Learn more about the meta description.
Page has successful HTTP status code
Pages with unsuccessful HTTP status codes may not be indexed properly. Learn more about HTTP status codes.
Links are crawlable
Search engines may use href attributes on links to crawl websites. Ensure that the href attribute of anchor elements links to an appropriate destination, so more pages of the site can be discovered. Learn how to make links crawlable
Document has a valid hreflang
hreflang links tell search engines what version of a page they should list in search results for a given language or region. Learn more about hreflang.
Document has a valid rel=canonical
Canonical links suggest which URL to show in search results. Learn more about canonical links.