PageSpeed Insights logo
PageSpeed Insights
PageSpeed Insights
This site uses cookies from Google to deliver its services and to analyze traffic.
Report from Mar 9, 2025, 6:00:22 PM
Discover what your real users are experiencing
Core Web Vitals Assessment: Failed
Largest Contentful Paint (LCP)
1.8 s
Page LoadsGood (≤ 2.5 s)85%Needs Improvement (2.5 s - 4 s)9%Poor (> 4 s)6%75th Percentile - 1.8 sCore Web Vital
Interaction to Next Paint (INP)
223 ms
Page LoadsGood (≤ 200 ms)71%Needs Improvement (200 ms - 500 ms)22%Poor (> 500 ms)7%75th Percentile - 223 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)5%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)76%Needs Improvement (2.5 s - 4 s)15%Poor (> 4 s)9%75th Percentile - 2.5 sCore Web Vital
Interaction to Next Paint (INP)
454 ms
Page LoadsGood (≤ 200 ms)54%Needs Improvement (200 ms - 500 ms)24%Poor (> 500 ms)23%75th Percentile - 454 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)71%Needs Improvement (1.8 s - 3 s)19%Poor (> 3 s)10%75th Percentile - 2 s 
Time to First Byte (TTFB)
1.4 s
Page LoadsGood (≤ 0.8 s)51%Needs Improvement (0.8 s - 1.8 s)32%Poor (> 1.8 s)16%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
49
Performance
87
Accessibility
93
Best Practices
100
SEO
49
Performance
87
Accessibility
93
Best Practices
100
SEO
49 FCP+7LCP+7TBT+9CLS+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
2.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
5.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
940 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
9.6 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more about the Speed Index metric.
  • Captured at Mar 9, 2025, 6:00 PM UTC
  • Emulated Moto G Power with Lighthouse 12.4.0
    Unthrottled CPU/Memory Power: 425 CPU throttling: 1.2x slowdown (Simulated) Screen emulation: 412x823, DPR 1.75 Axe version: 4.10.2
  • Single page session
    This data is taken from a single page session, as opposed to field data summarizing many sessions.
  • Initial page load
  • Slow 4G throttling
    Network throttling: 150 ms TCP RTT, 1,638.4 kb/s throughput (Simulated) Browser location: North America
  • Using HeadlessChromium 133.0.6943.141 with lr
    User agent (network): "Mozilla/5.0 (Linux; Android 11; moto g power (2022)) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/119.0.0.0 Mobile Safari/537.36"
Screenshot
Screenshot
Screenshot
Screenshot
Screenshot
Screenshot
Screenshot
Screenshot
Show audits relevant to:
Diagnostics
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
2,978 ms
2,180 ms
60 ms
/assets/7b4c60e…
(fr.burberry.com)
1,771 ms
1,533 ms
5 ms
https://fr.burberry.com
545 ms
139 ms
10 ms
…pages/_app-630d4f89e284bba8.js
(fr.burberry.com)
382 ms
265 ms
36 ms
…pages/%5B%5B...path%5D%5D-38ff316fb51ea0f1.js
(fr.burberry.com)
163 ms
136 ms
2 ms
…chunks/main-4345e1dcf5903327.js
(fr.burberry.com)
60 ms
54 ms
6 ms
…chunks/1858.1cb60a8f0d64d6ac.js
(fr.burberry.com)
57 ms
52 ms
0 ms
Brightcove
video
294 ms
219 ms
15 ms
…Tc5iqtzRUb_default/index.min.js
(players.brightcove.net)
294 ms
219 ms
15 ms
Unattributable
290 ms
111 ms
0 ms
Unattributable
290 ms
111 ms
0 ms
Optimizely
analytics
175 ms
165 ms
7 ms
/js/174….js
(cdn.optimizely.com)
175 ms
165 ms
7 ms
Optanon
consent-provider
155 ms
103 ms
8 ms
…202403.2.0/otBannerSdk.js
(cdn.cookielaw.org)
155 ms
103 ms
8 ms
New Relic
utility
92 ms
82 ms
2 ms
/nr-spa-1.283.2.min.js
(js-agent.newrelic.com)
92 ms
82 ms
2 ms
Google Tag Manager
tag-manager
77 ms
65 ms
12 ms
/gtm.js?id=…
(www.googletagmanager.com)
77 ms
65 ms
12 ms
Minimize main-thread work 4.3 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to minimize main-thread workTBT
Category
Time Spent
Script Evaluation
3,065 ms
Style & Layout
333 ms
Other
311 ms
Garbage Collection
255 ms
Script Parsing & Compilation
139 ms
Parse HTML & CSS
101 ms
Rendering
47 ms
Largest Contentful Paint element 4,990 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 Richard E. Grant portant un tre…
<img alt="La campagne &quot;It's Always Burberry Weather&quot; avec Richard E. Grant portant u…" src="https://assets.burberry.com/is/image/Burberryltd/B147B6E6-7A29-4DC6-BCB2-4…" sizes="100vw" loading="eager" fetchpriority="high" style="opacity:1">
Phase
% of LCP
Timing
TTFB
12%
600 ms
Load Delay
57%
2,840 ms
Load Time
16%
780 ms
Render Delay
15%
770 ms
Reduce unused JavaScript Potential savings of 754 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
730.5 KiB
466.4 KiB
…chunks/1492.cc0acb0c4b01a5cb.js
(fr.burberry.com)
226.4 KiB
224.2 KiB
…pages/_app-630d4f89e284bba8.js
(fr.burberry.com)
382.5 KiB
196.4 KiB
…chunks/main-4345e1dcf5903327.js
(fr.burberry.com)
66.4 KiB
24.4 KiB
/assets/7b4c60e…
(fr.burberry.com)
55.2 KiB
21.4 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
142.3 KiB
54.5 KiB
/gtm.js?id=…
(www.googletagmanager.com)
142.3 KiB
54.5 KiB
Optimizely
analytics
95.3 KiB
41.6 KiB
/js/174….js
(cdn.optimizely.com)
95.3 KiB
41.6 KiB
Avoid an excessive DOM size 1,886 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,886
Maximum DOM Depth
a.css-11cfnoo > div.e14owicd1 > picture > source
<source sizes="(max-width: 1023px) 100vw, (min-width: 1024px) and (max-width: 1439px) 100…" srcset="https://assets.burberry.com/is/image/Burberryltd/A7843F85-A7B3-4FF1-BF37-D…" media="(max-width: 1023px)">
16
Maximum Child Elements
div#__next > div.css-1np5lhz > div.css-dn5thc > svg.css-2b4713
<svg width="451" height="304" viewBox="0 0 451 304" xmlns="http://www.w3.org/2000/svg" data-testid="ekd-svg" class="css-2b4713 edlyr3p0">
26
Properly size images Potential savings of 393 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
926.2 KiB
392.8 KiB
Campagne dédiée aux cadeaux pour la fête des Mères avec des foulards en soie Bu…
<img alt="Campagne dédiée aux cadeaux pour la fête des Mères avec des foulards en so…" sizes="100vw" loading="lazy" fetchpriority="auto" style="transition: opacity 200ms; opacity: 1;" src="https://assets.burberry.com/is/image/Burberryltd/200F38A7-AA34-4423-AB2B-A…">
…Burberryltd/200F38A7-…?wid=800
(assets.burberry.com)
248.7 KiB
98.8 KiB
Mini sac bowling Check avec fleurs rouges Burberry
<img alt="Mini sac bowling Check avec fleurs rouges Burberry" sizes="100vw" loading="lazy" fetchpriority="auto" style="transition: opacity 200ms; opacity: 1;" src="https://assets.burberry.com/is/image/Burberryltd/741DB068-2103-4DA7-8334-6…">
…Burberryltd/741DB068-…?wid=800
(assets.burberry.com)
204.0 KiB
81.0 KiB
Sac cabas Check avec foulard léger Check et fleurs Burberry
<img alt="Sac cabas Check avec foulard léger Check et fleurs Burberry" sizes="100vw" loading="lazy" fetchpriority="auto" style="transition: opacity 200ms; opacity: 1;" src="https://assets.burberry.com/is/image/Burberryltd/24BE70B6-0DF4-47A1-943D-D…">
…Burberryltd/24BE70B6-…?wid=800
(assets.burberry.com)
126.1 KiB
50.1 KiB
Campagne dédiée aux cadeaux pour la fête des Mères avec le parfum Burberry Godd…
<img alt="Campagne dédiée aux cadeaux pour la fête des Mères avec le parfum Burberry…" sizes="100vw" loading="lazy" fetchpriority="auto" style="transition: opacity 200ms; opacity: 1;" src="https://assets.burberry.com/is/image/Burberryltd/29C7FED6-7704-4CD3-9AEF-6…">
…Burberryltd/29C7FED6-…?wid=800
(assets.burberry.com)
89.2 KiB
35.4 KiB
Portefeuille continental Check Burberry coloris Sand
<img alt="Portefeuille continental Check Burberry coloris Sand" sizes="(max-width: 1023px) 100vw, (min-width: 1024px) and (max-width: 1439px) 100…" loading="lazy" fetchpriority="auto" style="transition: opacity 200ms; opacity: 1;" src="https://assets.burberry.com/is/image/Burberryltd/A7843F85-A7B3-4FF1-BF37-D…" srcset="https://assets.burberry.com/is/image/Burberryltd/A7843F85-A7B3-4FF1-BF37-D…">
…Burberryltd/A7843F85-…?wid=800
(assets.burberry.com)
45.4 KiB
33.8 KiB
Foulard en soie Check Burberry coloris Teacup
<img alt="Foulard en soie Check Burberry coloris Teacup" sizes="(max-width: 1023px) 100vw, (min-width: 1024px) and (max-width: 1439px) 100…" loading="lazy" fetchpriority="auto" style="transition: opacity 200ms; opacity: 1;" src="https://assets.burberry.com/is/image/Burberryltd/A9233EDE-9B39-44CA-B456-2…" srcset="https://assets.burberry.com/is/image/Burberryltd/A9233EDE-9B39-44CA-B456-2…">
…Burberryltd/A9233EDE-…?wid=800
(assets.burberry.com)
30.3 KiB
22.6 KiB
Petit sac Messenger B Clip Burberry coloris sable
<img alt="Petit sac Messenger B Clip Burberry coloris sable" sizes="(max-width: 1023px) 100vw, (min-width: 1024px) and (max-width: 1439px) 100…" loading="lazy" fetchpriority="auto" style="transition: opacity 200ms; opacity: 1;" src="https://assets.burberry.com/is/image/Burberryltd/593C2B62-43B0-4C6C-99FB-2…" srcset="https://assets.burberry.com/is/image/Burberryltd/593C2B62-43B0-4C6C-99FB-2…">
…Burberryltd/593C2B62-…?wid=800
(assets.burberry.com)
29.6 KiB
22.1 KiB
La campagne "It's Always Burberry Weather" avec Richard E. Grant portant un tre…
<img alt="La campagne &quot;It's Always Burberry Weather&quot; avec Richard E. Grant portant u…" src="https://assets.burberry.com/is/image/Burberryltd/B147B6E6-7A29-4DC6-BCB2-4…" sizes="100vw" loading="eager" fetchpriority="high" style="opacity:1">
…Burberryltd/B147B6E6-…?wid=800
(assets.burberry.com)
116.5 KiB
22.0 KiB
Trench Heritage long Chelsea Burberry
<img alt="Trench Heritage long Chelsea Burberry" sizes="(max-width: 1023px) 100vw, (min-width: 1024px) and (max-width: 1439px) 100…" loading="lazy" fetchpriority="auto" style="transition: opacity 200ms; opacity: 1;" src="https://assets.burberry.com/is/image/Burberryltd/F6771F6E-2312-4A82-BA80-E…" srcset="https://assets.burberry.com/is/image/Burberryltd/F6771F6E-2312-4A82-BA80-E…">
…Burberryltd/F6771F6E-…?wid=800
(assets.burberry.com)
18.8 KiB
14.0 KiB
Veste trench en coton contrecollé Burberry coloris Sail
<img alt="Veste trench en coton contrecollé Burberry coloris Sail" sizes="(max-width: 1023px) 100vw, (min-width: 1024px) and (max-width: 1439px) 100…" loading="lazy" fetchpriority="auto" style="transition: opacity 200ms; opacity: 1;" src="https://assets.burberry.com/is/image/Burberryltd/1519A4E4-CD30-42A9-87C0-D…" srcset="https://assets.burberry.com/is/image/Burberryltd/1519A4E4-CD30-42A9-87C0-D…">
…Burberryltd/1519A4E4-…?wid=800
(assets.burberry.com)
17.5 KiB
13.0 KiB
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 61 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
2,504 KiB
…chunks/1663.c3fe609ebba30312.js
(fr.burberry.com)
1m 14s
7 KiB
…chunks/7487.45752b85779191a8.js
(fr.burberry.com)
1m 41s
5 KiB
…chunks/1858.1cb60a8f0d64d6ac.js
(fr.burberry.com)
1m 50s
5 KiB
…axg7x3xyiPKHwugeLb_nX/_ssgManifest.js
(fr.burberry.com)
2m 6s
1 KiB
…axg7x3xyiPKHwugeLb_nX/_buildManifest.js
(fr.burberry.com)
2m 30s
1 KiB
…chunks/4390.a3d4d2d46d1b8d1f.js
(fr.burberry.com)
3m 10s
13 KiB
…chunks/2365.590…ae45fff.js
(fr.burberry.com)
4m 7s
29 KiB
…chunks/3161.19e53ecf66a85db2.js
(fr.burberry.com)
4m 16s
13 KiB
…chunks/6305.100347c6da4df86b.js
(fr.burberry.com)
5m
8 KiB
…chunks/7483.1e5fd3076ab36f77.js
(fr.burberry.com)
5m 13s
21 KiB
…chunks/chat-button.5d206cf0e8920a2d.js
(fr.burberry.com)
5m 21s
1 KiB
…chunks/5980.34af8b4967b03045.js
(fr.burberry.com)
5m 50s
4 KiB
…chunks/1492.cc0acb0c4b01a5cb.js
(fr.burberry.com)
7m 6s
227 KiB
…chunks/6435.96067d7ce2d1aabd.js
(fr.burberry.com)
7m 13s
5 KiB
…chunks/burberry-wipe.92953fc5dec8edaf.js
(fr.burberry.com)
7m 34s
2 KiB
…chunks/7127.66bfd463adae2d60.js
(fr.burberry.com)
7m 35s
8 KiB
…chunks/5490.230b178514a8135f.js
(fr.burberry.com)
7m 44s
9 KiB
…pages/_app-630d4f89e284bba8.js
(fr.burberry.com)
9m 21s
383 KiB
…chunks/1512.4d36ce35ada93b8f.js
(fr.burberry.com)
9m 27s
7 KiB
/assets/7b4c60e…
(fr.burberry.com)
10m
56 KiB
…chunks/bossStyles-e685bd24e6db5bf4.js
(fr.burberry.com)
10m 50s
1 KiB
…pages/%5B%5B...path%5D%5D-38ff316fb51ea0f1.js
(fr.burberry.com)
12m 6s
21 KiB
…boss-assets/8946-4c00c1aabc32bf4f.css
(fr.burberry.com)
13m 1s
6 KiB
…chunks/ekd.5febde7b7302aed5.js
(fr.burberry.com)
13m 32s
1 KiB
…Burberryltd/200F38A7-…?wid=800
(assets.burberry.com)
7d
249 KiB
…Burberryltd/17C679AD-…?wid=800
(assets.burberry.com)
7d
224 KiB
…Burberryltd/0E2F84F9-…?wid=800
(assets.burberry.com)
7d
207 KiB
…Burberryltd/741DB068-…?wid=800
(assets.burberry.com)
7d
205 KiB
…Burberryltd/24BE70B6-…?wid=800
(assets.burberry.com)
7d
127 KiB
…Burberryltd/B147B6E6-…?wid=800
(assets.burberry.com)
7d
117 KiB
…Burberryltd/29C7FED6-…?wid=800
(assets.burberry.com)
7d
90 KiB
…Burberryltd/A7843F85-…?wid=800
(assets.burberry.com)
7d
46 KiB
…Burberryltd/A9233EDE-…?wid=800
(assets.burberry.com)
7d
31 KiB
…Burberryltd/593C2B62-…?wid=800
(assets.burberry.com)
7d
30 KiB
…Burberryltd/F6771F6E-…?wid=800
(assets.burberry.com)
7d
19 KiB
…Burberryltd/1519A4E4-…?wid=800
(assets.burberry.com)
7d
18 KiB
…Burberryltd/4FE9AF02-…?wid=800
(assets.burberry.com)
7d
15 KiB
…Burberryltd/729F8762-…?wid=800
(assets.burberry.com)
7d
15 KiB
…Burberryltd/1F627E5E-…?wid=800
(assets.burberry.com)
7d
11 KiB
…Burberryltd/96ADE6AC-…?wid=800
(assets.burberry.com)
7d
11 KiB
…Burberryltd/995DA0CA-…?wid=800
(assets.burberry.com)
7d
11 KiB
…Burberryltd/0BFA59D4-…?wid=800
(assets.burberry.com)
7d
2 KiB
…Burberryltd/0AE62B15-…?wid=800
(assets.burberry.com)
7d
2 KiB
…oracle-book-medium/oracle-book-medium.woff2
(common.static.burberry.com)
24d 10h 17m 18s
64 KiB
…oracle-book/oracle-book.woff2
(common.static.burberry.com)
24d 10h 17m 18s
60 KiB
…burberry-house-regular/burberry-house-regular.woff2
(common.static.burberry.com)
24d 10h 17m 18s
17 KiB
…chunks/6890.653ff3328c9bf3e0.js
(fr.burberry.com)
25d 17h 42m 26s
3 KiB
…chunks/4885.e5e0f2757e93c734.js
(fr.burberry.com)
25d 19h 31m 22s
10 KiB
…chunks/459.daae1adb65b79fba.js
(fr.burberry.com)
26d 17h 45m 41s
1 KiB
…chunks/7770.0128d3da55acc3f0.js
(fr.burberry.com)
26d 17h 46m 47s
4 KiB
…chunks/webpack-b17c9201f7f50bc4.js
(fr.burberry.com)
26d 19h 13m 41s
4 KiB
…chunks/2181.e18faa67a92ba4c6.js
(fr.burberry.com)
26d 19h 57m 10s
1 KiB
…chunks/main-4345e1dcf5903327.js
(fr.burberry.com)
26d 20h 8s
67 KiB
…chunks/9105.684b53cdb25460dd.js
(fr.burberry.com)
26d 23h 27m 41s
5 KiB
Brightcove
video
223 KiB
…Tc5iqtzRUb_default/index.min.js
(players.brightcove.net)
1m 2s
223 KiB
Optanon
consent-provider
122 KiB
…202403.2.0/otBannerSdk.js
(cdn.cookielaw.org)
1d
109 KiB
/scripttemplates/otSDKStub.js
(cdn.cookielaw.org)
1d
8 KiB
…static/powered_by_logo.svg
(cdn.cookielaw.org)
1d
3 KiB
…e9a655ec-…/Burberry-….png
(cdn.cookielaw.org)
1d
3 KiB
Optimizely
analytics
96 KiB
/js/174….js
(cdn.optimizely.com)
2m
96 KiB
cloudfront.net
22 KiB
/v3.1.4/3c8ksv.js
(dabs7b6g7t59l.cloudfront.net)
None
22 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">
…static/powered_by_logo.svg
(cdn.cookielaw.org)
2.8 KiB
2.8 KiB
Avoid serving legacy JavaScript to modern browsers Potential savings of 7 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. However, many aren't necessary for modern browsers. For your bundled JavaScript, adopt a modern script deployment strategy using module/nomodule feature detection to reduce the amount of code shipped to modern browsers, while retaining support for legacy browsers. Learn how to serve modern JavaScriptLCPFCP
URL
Potential Savings
Optanon
consent-provider
7.2 KiB
…202403.2.0/otBannerSdk.js
(cdn.cookielaw.org)
7.2 KiB
…202403.2.0/otBannerSdk.js:7:7371
(cdn.cookielaw.org)
Array.prototype.fill
burberry.com
1st party
0.2 KiB
…pages/_app-630d4f89e284bba8.js
(fr.burberry.com)
0.1 KiB
…pages/_app-630d4f89e284bba8.js:1:636550
(fr.burberry.com)
@babel/plugin-transform-classes
…chunks/7483.1e5fd3076ab36f77.js
(fr.burberry.com)
0.1 KiB
…chunks/7483.1e5fd3076ab36f77.js:1:10167
(fr.burberry.com)
@babel/plugin-transform-classes
…chunks/1492.cc0acb0c4b01a5cb.js
(fr.burberry.com)
0.0 KiB
…chunks/1492.cc0acb0c4b01a5cb.js:1:10351
(fr.burberry.com)
@babel/plugin-transform-classes
Brightcove
video
0.0 KiB
…Tc5iqtzRUb_default/index.min.js
(players.brightcove.net)
0.0 KiB
…Tc5iqtzRUb_default/index.min.js:1:362860
(players.brightcove.net)
@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
Avoid enormous network payloads Total size was 3,392 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
1,739.3 KiB
…pages/_app-630d4f89e284bba8.js
(fr.burberry.com)
383.4 KiB
…Burberryltd/200F38A7-…?wid=800
(assets.burberry.com)
249.3 KiB
…chunks/1492.cc0acb0c4b01a5cb.js
(fr.burberry.com)
227.2 KiB
…Burberryltd/17C679AD-…?wid=800
(assets.burberry.com)
223.7 KiB
…Burberryltd/0E2F84F9-…?wid=800
(assets.burberry.com)
207.2 KiB
…Burberryltd/741DB068-…?wid=800
(assets.burberry.com)
204.7 KiB
…Burberryltd/24BE70B6-…?wid=800
(assets.burberry.com)
126.7 KiB
…Burberryltd/B147B6E6-…?wid=800
(assets.burberry.com)
117.2 KiB
Brightcove
video
222.7 KiB
…Tc5iqtzRUb_default/index.min.js
(players.brightcove.net)
222.7 KiB
Google Tag Manager
tag-manager
143.4 KiB
/gtm.js?id=…
(www.googletagmanager.com)
143.4 KiB
Avoid long main-thread tasks 11 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,938 ms
…chunks/1492.cc0acb0c4b01a5cb.js
(fr.burberry.com)
17,321 ms
521 ms
/assets/7b4c60e…
(fr.burberry.com)
17,842 ms
474 ms
/assets/7b4c60e…
(fr.burberry.com)
16,989 ms
332 ms
https://fr.burberry.com
3,175 ms
185 ms
/assets/7b4c60e…
(fr.burberry.com)
19,627 ms
181 ms
/assets/7b4c60e…
(fr.burberry.com)
3,039 ms
124 ms
/assets/7b4c60e…
(fr.burberry.com)
18,400 ms
71 ms
https://fr.burberry.com
1,389 ms
50 ms
Optimizely
analytics
161 ms
/js/174….js
(cdn.optimizely.com)
5,018 ms
161 ms
Brightcove
video
130 ms
…Tc5iqtzRUb_default/index.min.js
(players.brightcove.net)
15,227 ms
130 ms
Optanon
consent-provider
68 ms
…202403.2.0/otBannerSdk.js
(cdn.cookielaw.org)
7,023 ms
68 ms
Minimize third-party usage Third-party code blocked the main thread for 210 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
98 KiB
111 ms
/js/174….js
(cdn.optimizely.com)
96 KiB
111 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
78 ms
…Tc5iqtzRUb_default/index.min.js
(players.brightcove.net)
223 KiB
78 ms
…0.15.3/vtt.global.min.js
(vjs.zencdn.net)
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
Optanon
consent-provider
174 KiB
18 ms
…202403.2.0/otBannerSdk.js
(cdn.cookielaw.org)
109 KiB
18 ms
…018e092d-7880-71f2-956f-542266dcf482/fr.json
(cdn.cookielaw.org)
25 KiB
0 ms
…v2/otPcTab.json
(cdn.cookielaw.org)
14 KiB
0 ms
/scripttemplates/otSDKStub.js
(cdn.cookielaw.org)
8 KiB
0 ms
…assets/otCommonStyles.css
(cdn.cookielaw.org)
5 KiB
0 ms
…assets/otCenterRounded.json
(cdn.cookielaw.org)
3 KiB
0 ms
…static/powered_by_logo.svg
(cdn.cookielaw.org)
3 KiB
0 ms
…e9a655ec-…/Burberry-….png
(cdn.cookielaw.org)
3 KiB
0 ms
…c1ba84e4-a534-4a3c-910e-5795061c0f34/c1ba84e4-a534-4a3c-9….json
(cdn.cookielaw.org)
3 KiB
0 ms
…static/ot_guard_logo.svg
(cdn.cookielaw.org)
1 KiB
0 ms
…geo/location
(geolocation.onetrust.com)
0 KiB
0 ms
Google Tag Manager
tag-manager
143 KiB
0 ms
/gtm.js?id=…
(www.googletagmanager.com)
143 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
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
2,114.34 ms
Next.js-hydration
Measure
2,114.34 ms
439.25 ms
bcAdBlockDetect
Measure
3,796.57 ms
469.81 ms
bcInit
Measure
3,819.52 ms
358.44 ms
optimizely:blockBegin
Mark
1,272.79 ms
beforeRender
Mark
2,114.34 ms
afterHydrate
Mark
2,553.60 ms
clearMarks
Mark
2,554.72 ms
clearMarks
Mark
2,554.74 ms
clearMarks
Mark
2,554.75 ms
clearMarks
Mark
2,554.75 ms
bcAdBlockDetectStart
Mark
3,796.57 ms
bcInitStart
Mark
3,819.52 ms
bcInitEnd
Mark
4,177.97 ms
bcAdBlockDetectEnd
Mark
4,266.38 ms
More information about the performance of your application. These numbers don't directly affect the Performance score.
Passed audits (21)
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
Initial server response time was short Root document took 550 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
550 ms
https://fr.burberry.com
550 ms
Avoid multiple page redirects
Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.LCPFCP
Use video formats for animated content
Large GIFs are inefficient for delivering animated content. Consider using MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF to save network bytes. Learn more about efficient video formatsLCPFCP
Remove duplicate modules in JavaScript bundles
Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity. LCPFCP
Preload Largest Contentful Paint image
If the LCP element is dynamically added to the page, you should preload the image in order to improve LCP. Learn more about preloading LCP elements.LCP
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: 1,087.803 ms
Initial Navigation
https://fr.burberry.com
- 1,087.803 ms, 107.16 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 Richard E. Grant portant un tre…
<img alt="La campagne &quot;It's Always Burberry Weather&quot; avec Richard E. Grant portant u…" src="https://assets.burberry.com/is/image/Burberryltd/B147B6E6-7A29-4DC6-BCB2-4…" sizes="100vw" loading="eager" fetchpriority="high" style="opacity:1">
Avoid large layout shifts
These are the largest layout shifts observed on the page. Each table item represents a single layout shift, and shows the element that shifted the most. Below each item are possible root causes that led to the layout shift. Some of these layout shifts may not be included in the CLS metric value due to windowing. Learn how to improve CLSCLS
Uses passive listeners to improve scrolling performance
Consider marking your touch and wheel event listeners as passive to improve your page's scroll performance. Learn more about adopting passive event listeners.
Avoids document.write()
For users on slow connections, external scripts dynamically injected via document.write() can delay page load by tens of seconds. Learn how to avoid document.write().
Avoid non-composited animations
Animations which are not composited can be janky and increase CLS. Learn how to avoid non-composited animationsCLS
Image elements have explicit width and height
Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensionsCLS
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.
87
Accessibility
These checks highlight opportunities to improve the accessibility of your web app. Automatic detection can only detect a subset of issues and does not guarantee the accessibility of your web app, so manual testing is also encouraged.
ARIA
[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.
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.
Names and labels
<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.
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 (27)
Show Hide
[aria-*] attributes match their roles
Each ARIA role supports a specific subset of aria-* attributes. Mismatching these invalidates the aria-* attributes. Learn how to match ARIA attributes to their roles.
[aria-hidden="true"] is not present on the document <body>
Assistive technologies, like screen readers, work inconsistently when aria-hidden="true" is set on the document <body>. Learn how aria-hidden affects the document body.
[role]s have all required [aria-*] attributes
Some ARIA roles have required attributes that describe the state of the element to screen readers. Learn more about roles and required attributes.
[aria-*] attributes are valid and not misspelled
Assistive technologies, like screen readers, can't interpret ARIA attributes with invalid names. Learn more about valid ARIA attributes.
Buttons have an accessible name
When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.
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.
Links are distinguishable without relying on color.
Low-contrast text is difficult or impossible for many users to read. Link text that is discernible improves the experience for users with low vision. Learn how to make links distinguishable.
Links have a discernible name
Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.
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 (27)
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.
<frame> or <iframe> elements have a title
Screen reader users rely on frame titles to describe the contents of frames. Learn more about frame titles.
<html> element has an [xml:lang] attribute with the same base language as the [lang] attribute.
If the webpage does not specify a consistent language, then the screen reader might not announce the page's text correctly. Learn more about the lang attribute.
Input buttons have discernible text.
Adding discernable and accessible text to input buttons may help screen reader users understand the purpose of the input button. Learn more about input buttons.
<input type="image"> elements have [alt] text
When an image is being used as an <input> button, providing alternative text can help screen reader users understand the purpose of the button. Learn about input image alt text.
The document does not use <meta http-equiv="refresh">
Users do not expect a page to refresh automatically, and doing so will move focus back to the top of the page. This may create a frustrating or confusing experience. Learn more about the refresh meta tag.
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.
93
Best Practices
General
Browser errors were logged to the console
Errors logged to the console indicate unresolved problems. They can come from network request failures and other browser concerns. Learn more about this errors in console diagnostic audit
Source
Description
burberry.com
1st party
https://fr.burberry.com:1:0
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
https://players.brightcove.net
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.2.0
core-js
core-js-global@3.41.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
…pages/_app-630d4f89e284bba8.js
(fr.burberry.com)
Large JavaScript file is missing a source map
…chunks/1492.cc0acb0c4b01a5cb.js
(fr.burberry.com)
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
Use a strong HSTS policy
Deployment of the HSTS header significantly reduces the risk of downgrading HTTP connections and eavesdropping attacks. A rollout in stages, starting with a low max-age is recommended. Learn more about using a strong HSTS policy.
Description
Directive
Severity
No `includeSubDomains` directive found
includeSubDomains
Medium
No `preload` directive found
preload
Medium
Invalid syntax
Low
Ensure proper origin isolation with COOP
The Cross-Origin-Opener-Policy (COOP) can be used to isolate the top-level window from other documents such as pop-ups. Learn more about deploying the COOP header.
Description
Directive
Severity
No COOP header found
High
Passed audits (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 (2)
Show Hide
Redirects HTTP traffic to HTTPS
Make sure that you redirect all HTTP traffic to HTTPS in order to enable secure web features for all your users. Learn more.
Mitigate clickjacking with XFO or CSP
The X-Frame-Options (XFO) header or the frame-ancestors directive in the Content-Security-Policy (CSP) header control where a page can be embedded. These can mitigate clickjacking attacks by blocking some or all sites from embedding the page. Learn more about mitigating clickjacking.
100
SEO
These checks ensure that your page is following basic search engine optimization advice. There are many additional factors Lighthouse does not score here that may affect your search ranking, including performance on Core Web Vitals. Learn more about Google Search Essentials.
Additional items to manually check (1)
Show Hide
Structured data is valid
Run the Structured Data Testing Tool and the Structured Data Linter to validate structured data. Learn more about Structured Data.
Run these additional validators on your site to check additional SEO best practices.
Passed audits (10)
Show Hide
Page isn’t blocked from indexing
Search engines are unable to include your pages in search results if they don't have permission to crawl them. Learn more about crawler directives.
Document has a <title> element
The title gives screen reader users an overview of the page, and search engine users rely on it heavily to determine if a page is relevant to their search. Learn more about document titles.
Document has a meta description
Meta descriptions may be included in search results to concisely summarize page content. Learn more about the meta description.
Page has successful HTTP status code
Pages with unsuccessful HTTP status codes may not be indexed properly. Learn more about HTTP status codes.
Links have descriptive text
Descriptive link text helps search engines understand your content. Learn how to make links more accessible.
Links are crawlable
Search engines may use href attributes on links to crawl websites. Ensure that the href attribute of anchor elements links to an appropriate destination, so more pages of the site can be discovered. Learn how to make links crawlable
robots.txt is valid
If your robots.txt file is malformed, crawlers may not be able to understand how you want your website to be crawled or indexed. Learn more about robots.txt.
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.5 s
Page LoadsGood (≤ 2.5 s)90%Needs Improvement (2.5 s - 4 s)6%Poor (> 4 s)4%75th Percentile - 1.5 sCore Web Vital
Interaction to Next Paint (INP)
62 ms
Page LoadsGood (≤ 200 ms)96%Needs Improvement (200 ms - 500 ms)3%Poor (> 500 ms)1%75th Percentile - 62 msCore Web Vital
Cumulative Layout Shift (CLS)
0
Page LoadsGood (≤ 0.1)99%Needs Improvement (0.1 - 0.25)0%Poor (> 0.25)0%75th Percentile - 0Core Web Vital
Other Notable Metrics
First Contentful Paint (FCP)
1.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.8 s
Page LoadsGood (≤ 0.8 s)77%Needs Improvement (0.8 s - 1.8 s)18%Poor (> 1.8 s)5%75th Percentile - 0.8 sExperimental
Latest 28-day collection period
Various desktop devicesMany samples (Chrome UX Report)Full visit durationsVarious network connectionsAll Chrome versions
Core Web Vitals Assessment: Passed
Largest Contentful Paint (LCP)
1.9 s
Page LoadsGood (≤ 2.5 s)85%Needs Improvement (2.5 s - 4 s)10%Poor (> 4 s)5%75th Percentile - 1.9 sCore Web Vital
Interaction to Next Paint (INP)
144 ms
Page LoadsGood (≤ 200 ms)81%Needs Improvement (200 ms - 500 ms)13%Poor (> 500 ms)6%75th Percentile - 144 msCore Web Vital
Cumulative Layout Shift (CLS)
0.03
Page LoadsGood (≤ 0.1)79%Needs Improvement (0.1 - 0.25)4%Poor (> 0.25)16%75th Percentile - 0.03Core Web Vital
Other Notable Metrics
First Contentful Paint (FCP)
1.6 s
Page LoadsGood (≤ 1.8 s)81%Needs Improvement (1.8 s - 3 s)12%Poor (> 3 s)7%75th Percentile - 1.6 s 
Time to First Byte (TTFB)
1.1 s
Page LoadsGood (≤ 0.8 s)61%Needs Improvement (0.8 s - 1.8 s)26%Poor (> 1.8 s)12%75th Percentile - 1.1 sExperimental
Latest 28-day collection period
Various desktop devicesMany samples (Chrome UX Report)Full visit durationsVarious network connectionsAll Chrome versions
Diagnose performance issues
62
Performance
78
Accessibility
93
Best Practices
92
SEO
62
Performance
78
Accessibility
93
Best Practices
92
SEO
62 FCP+10LCP+17TBT+6CLS+25SI+5 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.9 s
Largest Contentful Paint marks the time at which the largest text or image is painted. Learn more about the Largest Contentful Paint metric
Total Blocking Time
620 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
2.4 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more about the Speed Index metric.
  • Captured at Mar 9, 2025, 6:00 PM UTC
  • Emulated Desktop with Lighthouse 12.4.0
    Unthrottled CPU/Memory Power: 312 CPU throttling: 1x slowdown (Simulated) Screen emulation: 1350x940, DPR 1 Axe version: 4.10.2
  • Single page session
    This data is taken from a single page session, as opposed to field data summarizing many sessions.
  • Initial page load
  • Custom throttling
    Network throttling: 40 ms TCP RTT, 10,240 kb/s throughput (Simulated) Browser location: North America
  • Using HeadlessChromium 133.0.6943.141 with lr
    User agent (network): "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/119.0.0.0 Safari/537.36"
Screenshot
Screenshot
Screenshot
Screenshot
Screenshot
Screenshot
Screenshot
Screenshot
Show audits relevant to:
Diagnostics
Reduce JavaScript execution time 2.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
1,734 ms
1,277 ms
34 ms
…chunks/main-4345e1dcf5903327.js
(fr.burberry.com)
872 ms
760 ms
5 ms
https://fr.burberry.com
314 ms
108 ms
5 ms
…pages/_app-630d4f89e284bba8.js
(fr.burberry.com)
251 ms
164 ms
19 ms
/assets/7b4c60e…
(fr.burberry.com)
206 ms
176 ms
3 ms
…pages/%5B%5B...path%5D%5D-38ff316fb51ea0f1.js
(fr.burberry.com)
92 ms
69 ms
1 ms
Unattributable
427 ms
89 ms
0 ms
Unattributable
427 ms
89 ms
0 ms
Brightcove
video
346 ms
252 ms
12 ms
…Tc5iqtzRUb_default/index.min.js
(players.brightcove.net)
346 ms
252 ms
12 ms
Optanon
consent-provider
135 ms
86 ms
7 ms
…202403.2.0/otBannerSdk.js
(cdn.cookielaw.org)
135 ms
86 ms
7 ms
Optimizely
analytics
108 ms
100 ms
6 ms
/js/174….js
(cdn.optimizely.com)
108 ms
100 ms
6 ms
Google Tag Manager
tag-manager
88 ms
75 ms
10 ms
/gtm.js?id=…
(www.googletagmanager.com)
88 ms
75 ms
10 ms
New Relic
utility
60 ms
56 ms
2 ms
/nr-spa-1.283.2.min.js
(js-agent.newrelic.com)
60 ms
56 ms
2 ms
Minimize main-thread work 3.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,049 ms
Garbage Collection
276 ms
Style & Layout
268 ms
Other
253 ms
Script Parsing & Compilation
98 ms
Parse HTML & CSS
70 ms
Rendering
37 ms
Largest Contentful Paint element 1,910 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 Richard E. Grant portant un tre…
<img alt="La campagne &quot;It's Always Burberry Weather&quot; avec Richard E. Grant portant u…" src="https://assets.burberry.com/is/image/Burberryltd/25CAA84B-35B8-4D9B-A54F-3…" sizes="100vw" loading="eager" fetchpriority="high" style="opacity:1">
Phase
% of LCP
Timing
TTFB
8%
160 ms
Load Delay
56%
1,060 ms
Load Time
11%
210 ms
Render Delay
25%
480 ms
Reduce unused JavaScript Potential savings of 754 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
730.5 KiB
466.4 KiB
…chunks/1492.cc0acb0c4b01a5cb.js
(fr.burberry.com)
226.4 KiB
224.2 KiB
…pages/_app-630d4f89e284bba8.js
(fr.burberry.com)
382.5 KiB
196.1 KiB
…chunks/main-4345e1dcf5903327.js
(fr.burberry.com)
66.4 KiB
24.5 KiB
/assets/7b4c60e…
(fr.burberry.com)
55.2 KiB
21.6 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
142.3 KiB
54.5 KiB
/gtm.js?id=…
(www.googletagmanager.com)
142.3 KiB
54.5 KiB
Optimizely
analytics
95.3 KiB
41.6 KiB
/js/174….js
(cdn.optimizely.com)
95.3 KiB
41.6 KiB
Avoid an excessive DOM size 2,334 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,334
Maximum DOM Depth
a.css-11cfnoo > div.e14owicd1 > picture > source
<source sizes="(max-width: 1023px) 100vw, (min-width: 1024px) and (max-width: 1439px) 100…" srcset="https://assets.burberry.com/is/image/Burberryltd/A7843F85-A7B3-4FF1-BF37-D…" media="(max-width: 1023px)">
16
Maximum Child Elements
div#__next > div.css-1np5lhz > div.css-dn5thc > svg.css-2b4713
<svg width="451" height="304" viewBox="0 0 451 304" xmlns="http://www.w3.org/2000/svg" data-testid="ekd-svg" class="css-2b4713 edlyr3p0">
26
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 63 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
4,441 KiB
…chunks/7487.45752b85779191a8.js
(fr.burberry.com)
1m 39s
5 KiB
…axg7x3xyiPKHwugeLb_nX/_buildManifest.js
(fr.burberry.com)
2m 11s
1 KiB
…chunks/4390.a3d4d2d46d1b8d1f.js
(fr.burberry.com)
2m 22s
13 KiB
…axg7x3xyiPKHwugeLb_nX/_ssgManifest.js
(fr.burberry.com)
2m 22s
1 KiB
…chunks/6305.100347c6da4df86b.js
(fr.burberry.com)
2m 59s
8 KiB
…chunks/5980.34af8b4967b03045.js
(fr.burberry.com)
4m 40s
4 KiB
…chunks/chat-button.5d206cf0e8920a2d.js
(fr.burberry.com)
4m 53s
1 KiB
…chunks/3161.19e53ecf66a85db2.js
(fr.burberry.com)
5m 5s
13 KiB
…chunks/2365.590…ae45fff.js
(fr.burberry.com)
5m 35s
29 KiB
…chunks/7483.1e5fd3076ab36f77.js
(fr.burberry.com)
5m 52s
21 KiB
…chunks/6435.96067d7ce2d1aabd.js
(fr.burberry.com)
6m 14s
5 KiB
…chunks/burberry-wipe.92953fc5dec8edaf.js
(fr.burberry.com)
6m 39s
2 KiB
…chunks/1492.cc0acb0c4b01a5cb.js
(fr.burberry.com)
7m 20s
227 KiB
…pages/_app-630d4f89e284bba8.js
(fr.burberry.com)
7m 54s
383 KiB
…chunks/5490.230b178514a8135f.js
(fr.burberry.com)
8m 28s
9 KiB
…chunks/7127.66bfd463adae2d60.js
(fr.burberry.com)
8m 34s
8 KiB
/assets/7b4c60e…
(fr.burberry.com)
10m
56 KiB
…chunks/check-reveal.b831a502e3a5f5d9.js
(fr.burberry.com)
10m 9s
2 KiB
…chunks/bossStyles-e685bd24e6db5bf4.js
(fr.burberry.com)
10m 44s
1 KiB
…pages/%5B%5B...path%5D%5D-38ff316fb51ea0f1.js
(fr.burberry.com)
10m 53s
21 KiB
…chunks/1512.4d36ce35ada93b8f.js
(fr.burberry.com)
10m 53s
7 KiB
…chunks/ekd.5febde7b7302aed5.js
(fr.burberry.com)
11m 30s
1 KiB
…boss-assets/8946-4c00c1aabc32bf4f.css
(fr.burberry.com)
12m 21s
6 KiB
…chunks/1858.1cb60a8f0d64d6ac.js
(fr.burberry.com)
13m 8s
5 KiB
…chunks/1663.c3fe609ebba30312.js
(fr.burberry.com)
13m 55s
7 KiB
…burberry-house-regular/burberry-house-regular.woff2
(common.static.burberry.com)
4d 2h 14m 35s
17 KiB
…Burberryltd/61B7210E-…?wid=1366
(assets.burberry.com)
7d
719 KiB
…Burberryltd/E4809B97-…?wid=1366
(assets.burberry.com)
7d
609 KiB
…Burberryltd/B6F3BDF3-…?wid=1366
(assets.burberry.com)
7d
476 KiB
…Burberryltd/6165B15C-…?wid=1366
(assets.burberry.com)
7d
352 KiB
…Burberryltd/17C679AD-…?wid=800
(assets.burberry.com)
7d
224 KiB
…Burberryltd/0E2F84F9-…?wid=800
(assets.burberry.com)
7d
207 KiB
…Burberryltd/A7843F85-…?wid=1366
(assets.burberry.com)
7d
133 KiB
…Burberryltd/25CAA84B-…?wid=1366
(assets.burberry.com)
7d
121 KiB
…Burberryltd/3469BA15-…?wid=1366
(assets.burberry.com)
7d
90 KiB
…Burberryltd/593C2B62-…?wid=1366
(assets.burberry.com)
7d
82 KiB
…Burberryltd/A9233EDE-…?wid=1366
(assets.burberry.com)
7d
70 KiB
…Burberryltd/729F8762-…?wid=1366
(assets.burberry.com)
7d
46 KiB
…Burberryltd/1519A4E4-…?wid=1366
(assets.burberry.com)
7d
45 KiB
…Burberryltd/4FE9AF02-…?wid=1366
(assets.burberry.com)
7d
42 KiB
…Burberryltd/F6771F6E-…?wid=1366
(assets.burberry.com)
7d
42 KiB
…Burberryltd/995DA0CA-…?wid=1366
(assets.burberry.com)
7d
41 KiB
…Burberryltd/1F627E5E-…?wid=1366
(assets.burberry.com)
7d
31 KiB
…Burberryltd/96ADE6AC-…?wid=1366
(assets.burberry.com)
7d
28 KiB
…Burberryltd/0BFA59D4-…?wid=1366
(assets.burberry.com)
7d
5 KiB
…Burberryltd/0AE62B15-…?wid=1366
(assets.burberry.com)
7d
4 KiB
…oracle-book-medium/oracle-book-medium.woff2
(common.static.burberry.com)
25d 5h 46m
64 KiB
…oracle-book/oracle-book.woff2
(common.static.burberry.com)
25d 5h 46m
60 KiB
…chunks/459.daae1adb65b79fba.js
(fr.burberry.com)
25d 18h 4s
1 KiB
…chunks/4885.e5e0f2757e93c734.js
(fr.burberry.com)
25d 19h 29m 52s
10 KiB
…chunks/main-4345e1dcf5903327.js
(fr.burberry.com)
25d 19h 40m 28s
67 KiB
…chunks/2181.e18faa67a92ba4c6.js
(fr.burberry.com)
25d 21h 15m 47s
1 KiB
…chunks/7770.0128d3da55acc3f0.js
(fr.burberry.com)
26d 17h 47m
4 KiB
…chunks/webpack-b17c9201f7f50bc4.js
(fr.burberry.com)
26d 19h 14m 33s
4 KiB
…chunks/9105.684b53cdb25460dd.js
(fr.burberry.com)
26d 22h 17m 19s
5 KiB
…chunks/6890.653ff3328c9bf3e0.js
(fr.burberry.com)
29d 13h 48m 41s
3 KiB
Brightcove
video
223 KiB
…Tc5iqtzRUb_default/index.min.js
(players.brightcove.net)
40s
223 KiB
Optanon
consent-provider
122 KiB
…202403.2.0/otBannerSdk.js
(cdn.cookielaw.org)
1d
109 KiB
/scripttemplates/otSDKStub.js
(cdn.cookielaw.org)
1d
8 KiB
…static/powered_by_logo.svg
(cdn.cookielaw.org)
1d
3 KiB
…e9a655ec-…/Burberry-….png
(cdn.cookielaw.org)
1d
3 KiB
Optimizely
analytics
96 KiB
/js/174….js
(cdn.optimizely.com)
2m
96 KiB
cloudfront.net
23 KiB
/v3.1.4/3c8ksv.js
(dabs7b6g7t59l.cloudfront.net)
None
23 KiB
Properly size images Potential savings of 2,576 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
3,152.9 KiB
2,575.8 KiB
Campagne dédiée aux cadeaux pour la fête des Mères avec des foulards en soie Bu…
<img alt="Campagne dédiée aux cadeaux pour la fête des Mères avec des foulards en so…" sizes="100vw" loading="lazy" fetchpriority="auto" style="transition: opacity 200ms; opacity: 1;" src="https://assets.burberry.com/is/image/Burberryltd/61B7210E-5DE3-4753-9073-4…">
…Burberryltd/61B7210E-…?wid=1366
(assets.burberry.com)
718.5 KiB
662.4 KiB
Mini sac bowling Check avec fleurs rouges Burberry
<img alt="Mini sac bowling Check avec fleurs rouges Burberry" sizes="100vw" loading="lazy" fetchpriority="auto" style="transition: opacity 200ms; opacity: 1;" src="https://assets.burberry.com/is/image/Burberryltd/E4809B97-741C-4931-9E51-3…">
…Burberryltd/E4809B97-…?wid=1366
(assets.burberry.com)
608.6 KiB
561.1 KiB
Sac cabas Check avec foulard léger Check et fleurs Burberry
<img alt="Sac cabas Check avec foulard léger Check et fleurs Burberry" sizes="100vw" loading="lazy" fetchpriority="auto" style="transition: opacity 200ms; opacity: 1;" src="https://assets.burberry.com/is/image/Burberryltd/B6F3BDF3-B0D8-4473-9538-A…">
…Burberryltd/B6F3BDF3-…?wid=1366
(assets.burberry.com)
475.2 KiB
438.1 KiB
Campagne dédiée aux cadeaux pour la fête des Mères avec le parfum Burberry Godd…
<img alt="Campagne dédiée aux cadeaux pour la fête des Mères avec le parfum Burberry…" sizes="100vw" loading="lazy" fetchpriority="auto" style="transition: opacity 200ms; opacity: 1;" src="https://assets.burberry.com/is/image/Burberryltd/6165B15C-6002-4D7E-9436-8…">
…Burberryltd/6165B15C-…?wid=1366
(assets.burberry.com)
351.4 KiB
324.0 KiB
Portefeuille continental Check Burberry coloris Sand
<img alt="Portefeuille continental Check Burberry coloris Sand" sizes="(max-width: 1023px) 100vw, (min-width: 1024px) and (max-width: 1439px) 100…" loading="lazy" fetchpriority="auto" style="transition: opacity 200ms; opacity: 1;" src="https://assets.burberry.com/is/image/Burberryltd/A7843F85-A7B3-4FF1-BF37-D…" srcset="https://assets.burberry.com/is/image/Burberryltd/A7843F85-A7B3-4FF1-BF37-D…">
…Burberryltd/A7843F85-…?wid=1366
(assets.burberry.com)
131.9 KiB
122.0 KiB
Petit sac Messenger B Clip Burberry coloris sable
<img alt="Petit sac Messenger B Clip Burberry coloris sable" sizes="(max-width: 1023px) 100vw, (min-width: 1024px) and (max-width: 1439px) 100…" loading="lazy" fetchpriority="auto" style="transition: opacity 200ms; opacity: 1;" src="https://assets.burberry.com/is/image/Burberryltd/593C2B62-43B0-4C6C-99FB-2…" srcset="https://assets.burberry.com/is/image/Burberryltd/593C2B62-43B0-4C6C-99FB-2…">
…Burberryltd/593C2B62-…?wid=1366
(assets.burberry.com)
81.6 KiB
75.5 KiB
Deux sneakers Terrace Check Burberry en noir et blanc
<img alt="Deux sneakers Terrace Check Burberry en noir et blanc" sizes="(max-width: 1023px) 100vw, (min-width: 1024px) and (max-width: 1439px) 50v…" loading="lazy" fetchpriority="auto" style="transition: opacity 200ms; opacity: 1;" src="https://assets.burberry.com/is/image/Burberryltd/17C679AD-6EE2-4FEF-ADAA-F…" srcset="https://assets.burberry.com/is/image/Burberryltd/17C679AD-6EE2-4FEF-ADAA-F…">
…Burberryltd/17C679AD-…?wid=800
(assets.burberry.com)
223.1 KiB
67.7 KiB
Foulard en soie Check Burberry coloris Teacup
<img alt="Foulard en soie Check Burberry coloris Teacup" sizes="(max-width: 1023px) 100vw, (min-width: 1024px) and (max-width: 1439px) 100…" loading="lazy" fetchpriority="auto" style="transition: opacity 200ms; opacity: 1;" src="https://assets.burberry.com/is/image/Burberryltd/A9233EDE-9B39-44CA-B456-2…" srcset="https://assets.burberry.com/is/image/Burberryltd/A9233EDE-9B39-44CA-B456-2…">
…Burberryltd/A9233EDE-…?wid=1366
(assets.burberry.com)
69.0 KiB
63.9 KiB
Mini sac à carreaux Burberry Check coloris sable
<img alt="Mini sac à carreaux Burberry Check coloris sable" sizes="(max-width: 1023px) 100vw, (min-width: 1024px) and (max-width: 1439px) 50v…" loading="lazy" fetchpriority="auto" style="transition: opacity 200ms; opacity: 1;" src="https://assets.burberry.com/is/image/Burberryltd/0E2F84F9-089B-48E0-992B-8…" srcset="https://assets.burberry.com/is/image/Burberryltd/0E2F84F9-089B-48E0-992B-8…">
…Burberryltd/0E2F84F9-…?wid=800
(assets.burberry.com)
206.6 KiB
62.6 KiB
Veste trench en coton contrecollé Burberry coloris Sail
<img alt="Veste trench en coton contrecollé Burberry coloris Sail" sizes="(max-width: 1023px) 100vw, (min-width: 1024px) and (max-width: 1439px) 100…" loading="lazy" fetchpriority="auto" style="transition: opacity 200ms; opacity: 1;" src="https://assets.burberry.com/is/image/Burberryltd/1519A4E4-CD30-42A9-87C0-D…" srcset="https://assets.burberry.com/is/image/Burberryltd/1519A4E4-CD30-42A9-87C0-D…">
…Burberryltd/1519A4E4-…?wid=1366
(assets.burberry.com)
44.2 KiB
40.9 KiB
Sac épaule B Clip Burberry coloris Hebden
<img alt="Sac épaule B Clip Burberry coloris Hebden" sizes="(max-width: 1023px) 100vw, (min-width: 1024px) and (max-width: 1439px) 100…" loading="lazy" fetchpriority="auto" style="transition: opacity 200ms; opacity: 1;" src="https://assets.burberry.com/is/image/Burberryltd/4FE9AF02-EDF3-4D53-9606-4…" srcset="https://assets.burberry.com/is/image/Burberryltd/4FE9AF02-EDF3-4D53-9606-4…">
…Burberryltd/4FE9AF02-…?wid=1366
(assets.burberry.com)
41.3 KiB
38.2 KiB
Trench Heritage long Chelsea Burberry
<img alt="Trench Heritage long Chelsea Burberry" sizes="(max-width: 1023px) 100vw, (min-width: 1024px) and (max-width: 1439px) 100…" loading="lazy" fetchpriority="auto" style="transition: opacity 200ms; opacity: 1;" src="https://assets.burberry.com/is/image/Burberryltd/F6771F6E-2312-4A82-BA80-E…" srcset="https://assets.burberry.com/is/image/Burberryltd/F6771F6E-2312-4A82-BA80-E…">
…Burberryltd/F6771F6E-…?wid=1366
(assets.burberry.com)
41.2 KiB
38.1 KiB
Débardeur Festival en coton mélangé Burberry coloris Wisteria
<img alt="Débardeur Festival en coton mélangé Burberry coloris Wisteria" sizes="(max-width: 1023px) 100vw, (min-width: 1024px) and (max-width: 1439px) 100…" loading="lazy" fetchpriority="auto" style="transition: opacity 200ms; opacity: 1;" src="https://assets.burberry.com/is/image/Burberryltd/995DA0CA-20A9-474F-A603-8…" srcset="https://assets.burberry.com/is/image/Burberryltd/995DA0CA-20A9-474F-A603-8…">
…Burberryltd/995DA0CA-…?wid=1366
(assets.burberry.com)
40.0 KiB
37.0 KiB
Polo noir en coton Burberry
<img alt="Polo noir en coton Burberry" sizes="(max-width: 1023px) 100vw, (min-width: 1024px) and (max-width: 1439px) 100…" loading="lazy" fetchpriority="auto" style="transition: opacity 200ms; opacity: 1;" src="https://assets.burberry.com/is/image/Burberryltd/1F627E5E-441B-4492-96E7-2…" srcset="https://assets.burberry.com/is/image/Burberryltd/1F627E5E-441B-4492-96E7-2…">
…Burberryltd/1F627E5E-…?wid=1366
(assets.burberry.com)
30.5 KiB
28.2 KiB
div#video-player > div.css-l4apfs > 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…">
…Burberryltd/3469BA15-…?wid=1366
(assets.burberry.com)
89.8 KiB
16.0 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">
…static/powered_by_logo.svg
(cdn.cookielaw.org)
2.8 KiB
2.8 KiB
Avoid serving legacy JavaScript to modern browsers Potential savings of 7 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. However, many aren't necessary for modern browsers. For your bundled JavaScript, adopt a modern script deployment strategy using module/nomodule feature detection to reduce the amount of code shipped to modern browsers, while retaining support for legacy browsers. Learn how to serve modern JavaScriptLCPFCP
URL
Potential Savings
Optanon
consent-provider
7.2 KiB
…202403.2.0/otBannerSdk.js
(cdn.cookielaw.org)
7.2 KiB
…202403.2.0/otBannerSdk.js:7:7371
(cdn.cookielaw.org)
Array.prototype.fill
burberry.com
1st party
0.2 KiB
…pages/_app-630d4f89e284bba8.js
(fr.burberry.com)
0.1 KiB
…pages/_app-630d4f89e284bba8.js:1:636550
(fr.burberry.com)
@babel/plugin-transform-classes
…chunks/7483.1e5fd3076ab36f77.js
(fr.burberry.com)
0.1 KiB
…chunks/7483.1e5fd3076ab36f77.js:1:10167
(fr.burberry.com)
@babel/plugin-transform-classes
…chunks/1492.cc0acb0c4b01a5cb.js
(fr.burberry.com)
0.0 KiB
…chunks/1492.cc0acb0c4b01a5cb.js:1:10351
(fr.burberry.com)
@babel/plugin-transform-classes
Brightcove
video
0.0 KiB
…Tc5iqtzRUb_default/index.min.js
(players.brightcove.net)
0.0 KiB
…Tc5iqtzRUb_default/index.min.js:1:362860
(players.brightcove.net)
@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 5,350 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
3,197.6 KiB
…Burberryltd/61B7210E-…?wid=1366
(assets.burberry.com)
719.1 KiB
…Burberryltd/E4809B97-…?wid=1366
(assets.burberry.com)
609.2 KiB
…Burberryltd/B6F3BDF3-…?wid=1366
(assets.burberry.com)
475.8 KiB
…pages/_app-630d4f89e284bba8.js
(fr.burberry.com)
383.4 KiB
…Burberryltd/6165B15C-…?wid=1366
(assets.burberry.com)
352.0 KiB
…chunks/1492.cc0acb0c4b01a5cb.js
(fr.burberry.com)
227.2 KiB
…Burberryltd/17C679AD-…?wid=800
(assets.burberry.com)
223.7 KiB
…Burberryltd/0E2F84F9-…?wid=800
(assets.burberry.com)
207.2 KiB
Brightcove
video
222.7 KiB
…Tc5iqtzRUb_default/index.min.js
(players.brightcove.net)
222.7 KiB
Google Tag Manager
tag-manager
143.4 KiB
/gtm.js?id=…
(www.googletagmanager.com)
143.4 KiB
Avoid long main-thread tasks 7 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
496 ms
…chunks/main-4345e1dcf5903327.js
(fr.burberry.com)
3,436 ms
213 ms
…chunks/main-4345e1dcf5903327.js
(fr.burberry.com)
2,826 ms
198 ms
/assets/7b4c60e…
(fr.burberry.com)
670 ms
85 ms
Optimizely
analytics
403 ms
/js/174….js
(cdn.optimizely.com)
3,024 ms
403 ms
Brightcove
video
151 ms
…Tc5iqtzRUb_default/index.min.js
(players.brightcove.net)
2,512 ms
151 ms
Unattributable
151 ms
Unattributable
519 ms
151 ms
Optanon
consent-provider
60 ms
…202403.2.0/otBannerSdk.js
(cdn.cookielaw.org)
1,275 ms
60 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
Brightcove
video
252 KiB
97 ms
…Tc5iqtzRUb_default/index.min.js
(players.brightcove.net)
223 KiB
97 ms
…videos/636…
(edge.api.brightcove.com)
11 KiB
0 ms
…0.15.3/vtt.global.min.js
(vjs.zencdn.net)
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
98 KiB
85 ms
/js/174….js
(cdn.optimizely.com)
96 KiB
85 ms
/client_storage/a174….html
(a17489381590.cdn-pci.optimizely.com)
1 KiB
0 ms
/v1/events
(logx.optimizely.com)
1 KiB
0 ms
Optanon
consent-provider
174 KiB
10 ms
…202403.2.0/otBannerSdk.js
(cdn.cookielaw.org)
109 KiB
10 ms
…018e092d-7880-71f2-956f-542266dcf482/fr.json
(cdn.cookielaw.org)
25 KiB
0 ms
…v2/otPcTab.json
(cdn.cookielaw.org)
14 KiB
0 ms
/scripttemplates/otSDKStub.js
(cdn.cookielaw.org)
8 KiB
0 ms
…assets/otCommonStyles.css
(cdn.cookielaw.org)
5 KiB
0 ms
…assets/otCenterRounded.json
(cdn.cookielaw.org)
3 KiB
0 ms
…static/powered_by_logo.svg
(cdn.cookielaw.org)
3 KiB
0 ms
…e9a655ec-…/Burberry-….png
(cdn.cookielaw.org)
3 KiB
0 ms
…c1ba84e4-a534-4a3c-910e-5795061c0f34/c1ba84e4-a534-4a3c-9….json
(cdn.cookielaw.org)
3 KiB
0 ms
…static/ot_guard_logo.svg
(cdn.cookielaw.org)
1 KiB
0 ms
…geo/location
(geolocation.onetrust.com)
0 KiB
0 ms
Google Tag Manager
tag-manager
143 KiB
0 ms
/gtm.js?id=…
(www.googletagmanager.com)
143 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 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
1,316.04 ms
Next.js-hydration
Measure
1,316.04 ms
338.88 ms
bcAdBlockDetect
Measure
2,509.47 ms
507.49 ms
bcInit
Measure
2,740.20 ms
140.93 ms
bcInit
Measure
2,740.20 ms
161.90 ms
bcInit
Measure
2,740.20 ms
178.05 ms
optimizely:blockBegin
Mark
945.51 ms
beforeRender
Mark
1,316.04 ms
afterHydrate
Mark
1,654.92 ms
clearMarks
Mark
1,655.19 ms
clearMarks
Mark
1,655.19 ms
clearMarks
Mark
1,655.19 ms
clearMarks
Mark
1,655.20 ms
bcAdBlockDetectStart
Mark
2,509.47 ms
bcInitStart
Mark
2,528.96 ms
bcInitStart
Mark
2,688.10 ms
bcInitStart
Mark
2,740.20 ms
bcInitEnd
Mark
2,881.13 ms
bcInitEnd
Mark
2,902.10 ms
bcInitEnd
Mark
2,918.25 ms
bcAdBlockDetectEnd
Mark
3,016.96 ms
More information about the performance of your application. These numbers don't directly affect the Performance score.
Passed audits (21)
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
Initial server response time was short Root document took 490 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
490 ms
https://fr.burberry.com
490 ms
Avoid multiple page redirects
Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.LCPFCP
Use video formats for animated content
Large GIFs are inefficient for delivering animated content. Consider using MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF to save network bytes. Learn more about efficient video formatsLCPFCP
Remove duplicate modules in JavaScript bundles
Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity. LCPFCP
Preload Largest Contentful Paint image
If the LCP element is dynamically added to the page, you should preload the image in order to improve LCP. Learn more about preloading LCP elements.LCP
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: 631.133 ms
Initial Navigation
https://fr.burberry.com
- 631.133 ms, 108.29 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 Richard E. Grant portant un tre…
<img alt="La campagne &quot;It's Always Burberry Weather&quot; avec Richard E. Grant portant u…" src="https://assets.burberry.com/is/image/Burberryltd/25CAA84B-35B8-4D9B-A54F-3…" sizes="100vw" loading="eager" fetchpriority="high" style="opacity:1">
Avoid large layout shifts
These are the largest layout shifts observed on the page. Each table item represents a single layout shift, and shows the element that shifted the most. Below each item are possible root causes that led to the layout shift. Some of these layout shifts may not be included in the CLS metric value due to windowing. Learn how to improve CLSCLS
Uses passive listeners to improve scrolling performance
Consider marking your touch and wheel event listeners as passive to improve your page's scroll performance. Learn more about adopting passive event listeners.
Avoids document.write()
For users on slow connections, external scripts dynamically injected via document.write() can delay page load by tens of seconds. Learn how to avoid document.write().
Avoid non-composited animations
Animations which are not composited can be janky and increase CLS. Learn how to avoid non-composited animationsCLS
Image elements have explicit width and height
Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensionsCLS
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.
78
Accessibility
These checks highlight opportunities to improve the accessibility of your web app. Automatic detection can only detect a subset of issues and does not guarantee the accessibility of your web app, so manual testing is also encouraged.
ARIA
[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.exuws741 > section#cs2b16a991b708c-position-0 > div#carousel-pagination-controls > button.css-3dcfz3
<button aria-label="" class="css-3dcfz3 e1o4l6710">
div.exuws741 > section#cs229a5d675a052-position-0 > div#carousel-pagination-controls > button.css-3dcfz3
<button aria-label="" class="css-3dcfz3 e1o4l6710">
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-l4apfs > 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-l4apfs > 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…">
<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.
Links are distinguishable without relying on color.
Low-contrast text is difficult or impossible for many users to read. Link text that is discernible improves the experience for users with low vision. Learn how to make links distinguishable.
Links have a discernible name
Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.
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 (27)
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.
<frame> or <iframe> elements have a title
Screen reader users rely on frame titles to describe the contents of frames. Learn more about frame titles.
<html> element has an [xml:lang] attribute with the same base language as the [lang] attribute.
If the webpage does not specify a consistent language, then the screen reader might not announce the page's text correctly. Learn more about the lang attribute.
Input buttons have discernible text.
Adding discernable and accessible text to input buttons may help screen reader users understand the purpose of the input button. Learn more about input buttons.
<input type="image"> elements have [alt] text
When an image is being used as an <input> button, providing alternative text can help screen reader users understand the purpose of the button. Learn about input image alt text.
The document does not use <meta http-equiv="refresh">
Users do not expect a page to refresh automatically, and doing so will move focus back to the top of the page. This may create a frustrating or confusing experience. Learn more about the refresh meta tag.
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.
93
Best Practices
General
Browser errors were logged to the console
Errors logged to the console indicate unresolved problems. They can come from network request failures and other browser concerns. Learn more about this errors in console diagnostic audit
Source
Description
Brightcove
video
…Tc5iqtzRUb_default/index.min.js:1:364493
(players.brightcove.net)
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'".
…Tc5iqtzRUb_default/index.min.js:1:364493
(players.brightcove.net)
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
https://fr.burberry.com:1:0
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
https://players.brightcove.net
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.2.0
core-js
core-js-global@3.41.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
…pages/_app-630d4f89e284bba8.js
(fr.burberry.com)
Large JavaScript file is missing a source map
…chunks/1492.cc0acb0c4b01a5cb.js
(fr.burberry.com)
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
Use a strong HSTS policy
Deployment of the HSTS header significantly reduces the risk of downgrading HTTP connections and eavesdropping attacks. A rollout in stages, starting with a low max-age is recommended. Learn more about using a strong HSTS policy.
Description
Directive
Severity
No `includeSubDomains` directive found
includeSubDomains
Medium
No `preload` directive found
preload
Medium
Invalid syntax
Low
Ensure proper origin isolation with COOP
The Cross-Origin-Opener-Policy (COOP) can be used to isolate the top-level window from other documents such as pop-ups. Learn more about deploying the COOP header.
Description
Directive
Severity
No COOP header found
High
Passed audits (11)
Show Hide
Uses HTTPS
All sites should be protected with HTTPS, even ones that don't handle sensitive data. This includes avoiding mixed content, where some resources are loaded over HTTP despite the initial request being served over HTTPS. HTTPS prevents intruders from tampering with or passively listening in on the communications between your app and your users, and is a prerequisite for HTTP/2 and many new web platform APIs. Learn more about HTTPS.
Avoids 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 (3)
Show Hide
Redirects HTTP traffic to HTTPS
Make sure that you redirect all HTTP traffic to HTTPS in order to enable secure web features for all your users. Learn more.
Mitigate clickjacking with XFO or CSP
The X-Frame-Options (XFO) header or the frame-ancestors directive in the Content-Security-Policy (CSP) header control where a page can be embedded. These can mitigate clickjacking attacks by blocking some or all sites from embedding the page. Learn more about mitigating clickjacking.
Document uses legible font sizes
Font sizes less than 12px are too small to be legible and require mobile visitors to “pinch to zoom” in order to read. Strive to have >60% of page text ≥12px. Learn more about legible font sizes.
92
SEO
These checks ensure that your page is following basic search engine optimization advice. There are many additional factors Lighthouse does not score here that may affect your search ranking, including performance on Core Web Vitals. Learn more about Google Search Essentials.
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-l4apfs > 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-l4apfs > 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 the Structured Data Testing Tool and the Structured Data Linter to validate structured data. Learn more about Structured Data.
Run these additional validators on your site to check additional SEO best practices.
Passed audits (9)
Show Hide
Page isn’t blocked from indexing
Search engines are unable to include your pages in search results if they don't have permission to crawl them. Learn more about crawler directives.
Document has a <title> element
The title gives screen reader users an overview of the page, and search engine users rely on it heavily to determine if a page is relevant to their search. Learn more about document titles.
Document has a meta description
Meta descriptions may be included in search results to concisely summarize page content. Learn more about the meta description.
Page has successful HTTP status code
Pages with unsuccessful HTTP status codes may not be indexed properly. Learn more about HTTP status codes.
Links have descriptive text
Descriptive link text helps search engines understand your content. Learn how to make links more accessible.
Links are crawlable
Search engines may use href attributes on links to crawl websites. Ensure that the href attribute of anchor elements links to an appropriate destination, so more pages of the site can be discovered. Learn how to make links crawlable
robots.txt is valid
If your robots.txt file is malformed, crawlers may not be able to understand how you want your website to be crawled or indexed. Learn more about robots.txt.
Document has a valid hreflang
hreflang links tell search engines what version of a page they should list in search results for a given language or region. Learn more about hreflang.
Document has a valid rel=canonical
Canonical links suggest which URL to show in search results. Learn more about canonical links.