PageSpeed Insights logo
PageSpeed Insights
PageSpeed Insights
This site uses cookies from Google to deliver its services and to analyze traffic.
Report from Mar 2, 2025, 8:17:46 AM
Discover what your real users are experiencing
Core Web Vitals Assessment: Failed
Largest Contentful Paint (LCP)
2.5 s
Page LoadsGood (≤ 2.5 s)75%Needs Improvement (2.5 s - 4 s)16%Poor (> 4 s)10%75th Percentile - 2.5 sCore Web Vital
Interaction to Next Paint (INP)
311 ms
Page LoadsGood (≤ 200 ms)54%Needs Improvement (200 ms - 500 ms)34%Poor (> 500 ms)12%75th Percentile - 311 msCore Web Vital
Cumulative Layout Shift (CLS)
0.1
Page LoadsGood (≤ 0.1)64%Needs Improvement (0.1 - 0.25)34%Poor (> 0.25)2%75th Percentile - 0.1Core Web Vital
Other Notable Metrics
First Contentful Paint (FCP)
2.1 s
Page LoadsGood (≤ 1.8 s)66%Needs Improvement (1.8 s - 3 s)21%Poor (> 3 s)13%75th Percentile - 2.1 s 
Time to First Byte (TTFB)
1.3 s
Page LoadsGood (≤ 0.8 s)48%Needs Improvement (0.8 s - 1.8 s)39%Poor (> 1.8 s)13%75th Percentile - 1.3 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.7 s
Page LoadsGood (≤ 2.5 s)72%Needs Improvement (2.5 s - 4 s)17%Poor (> 4 s)11%75th Percentile - 2.7 sCore Web Vital
Interaction to Next Paint (INP)
328 ms
Page LoadsGood (≤ 200 ms)57%Needs Improvement (200 ms - 500 ms)28%Poor (> 500 ms)15%75th Percentile - 328 msCore Web Vital
Cumulative Layout Shift (CLS)
0.09
Page LoadsGood (≤ 0.1)77%Needs Improvement (0.1 - 0.25)15%Poor (> 0.25)8%75th Percentile - 0.09Core Web Vital
Other Notable Metrics
First Contentful Paint (FCP)
2.3 s
Page LoadsGood (≤ 1.8 s)62%Needs Improvement (1.8 s - 3 s)23%Poor (> 3 s)14%75th Percentile - 2.3 s 
Time to First Byte (TTFB)
1.4 s
Page LoadsGood (≤ 0.8 s)32%Needs Improvement (0.8 s - 1.8 s)55%Poor (> 1.8 s)14%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
29 FCP+1LCP+1TBT+3CLS+22SI+3 Performance
Values are estimated and may vary. The performance score is calculated directly from these metrics.See calculator.
0–49 50–89 90–100
Final Screenshot
Metrics
First Contentful Paint
5.6 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
7.1 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
1,810 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.114
Cumulative Layout Shift measures the movement of visible elements within the viewport. Learn more about the Cumulative Layout Shift metric.
Speed Index
7.5 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more about the Speed Index metric.
  • Captured at Mar 2, 2025, 8:17 AM UTC
  • Emulated Moto G Power with Lighthouse 12.2.3
    Unthrottled CPU/Memory Power: 458 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.126 with lr
    User agent (network): "Mozilla/5.0 (Linux; Android 11; moto g power (2022)) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/119.0.0.0 Mobile Safari/537.36"
Screenshot
Screenshot
Screenshot
Screenshot
Screenshot
Screenshot
Screenshot
Screenshot
Show audits relevant to:
Diagnostics
Minimize main-thread work 5.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 minimize main-thread workTBT
Category
Time Spent
Script Evaluation
3,824 ms
Other
450 ms
Style & Layout
338 ms
Garbage Collection
190 ms
Script Parsing & Compilation
114 ms
Parse HTML & CSS
68 ms
Rendering
56 ms
Reduce the impact of third-party code Third-party code blocked the main thread for 1,900 ms
Third-party code can significantly impact load performance. Limit the number of redundant third-party providers and try to load third-party code after your page has primarily finished loading. Learn how to minimize third-party impact.TBT
Third-Party
Transfer Size
Main-Thread Blocking Time
Google Tag Manager
tag-manager
582 KiB
1,576 ms
/gtm.js?id=GTM-5VWCDN
(www.googletagmanager.com)
151 KiB
1,387 ms
/gtag/js?id=…
(www.googletagmanager.com)
137 KiB
135 ms
/gtag/destination?id=…
(www.googletagmanager.com)
101 KiB
31 ms
/gtag/destination?id=…
(www.googletagmanager.com)
94 KiB
21 ms
/gtag/destination?id=…
(www.googletagmanager.com)
96 KiB
2 ms
2 KiB
0 ms
farfetch-contents.com
1,860 KiB
327 ms
…mobile/77155.client.d086cd5….esnext.js
(cdn-static.farfetch-contents.com)
7 KiB
135 ms
…mobile/32381.client.70e6329….esnext.js
(cdn-static.farfetch-contents.com)
1 KiB
66 ms
…sdks/coralogix-browser-sdk-1.4.6.js
(cdn-static.farfetch-contents.com)
139 KiB
60 ms
…mobile/83217.client.aef13ed….esnext.js
(cdn-static.farfetch-contents.com)
53 KiB
32 ms
…mobile/58288.client.ed5664c….esnext.js
(cdn-static.farfetch-contents.com)
26 KiB
32 ms
…mobile/45762.client.0a5ba7c….esnext.js
(cdn-static.farfetch-contents.com)
221 KiB
1 ms
…vitorino/vitorino.min.js
(cdn-static.farfetch-contents.com)
5 KiB
1 ms
…js/cpuMonitor.v3.js
(cdn-static.farfetch-contents.com)
3 KiB
0 ms
…js/eventManager.min.js
(cdn-static.farfetch-contents.com)
1 KiB
0 ms
…mobile/61181.client.d6268ee….esnext.js
(cdn-static.farfetch-contents.com)
38 KiB
0 ms
…mobile/runtime.client.1a9d587….esnext.js
(cdn-static.farfetch-contents.com)
12 KiB
0 ms
…mobile/803.client.6d5f2b2….esnext.js
(cdn-static.farfetch-contents.com)
29 KiB
0 ms
…js/setRUMUse….v1.js
(cdn-static.farfetch-contents.com)
1 KiB
0 ms
…mobile/6302.client.623d635….esnext.js
(cdn-static.farfetch-contents.com)
21 KiB
0 ms
…mobile/89706.client.837ad6d….esnext.js
(cdn-static.farfetch-contents.com)
17 KiB
0 ms
…mobile/97581.client.9aa1008….esnext.js
(cdn-static.farfetch-contents.com)
7 KiB
0 ms
…mobile/92879.client.ce4f36a….esnext.js
(cdn-static.farfetch-contents.com)
5 KiB
0 ms
…mobile/61349.client.1ebdccd….esnext.js
(cdn-static.farfetch-contents.com)
8 KiB
0 ms
…mobile/71171.client.3c4f984….esnext.js
(cdn-static.farfetch-contents.com)
6 KiB
0 ms
…mobile/94515.client.c486f95….esnext.js
(cdn-static.farfetch-contents.com)
4 KiB
0 ms
…mobile/31131.client.636a5e8….esnext.js
(cdn-static.farfetch-contents.com)
5 KiB
0 ms
…mobile/68419.client.fef9532….esnext.js
(cdn-static.farfetch-contents.com)
5 KiB
0 ms
…mobile/23479.client.e8b4f9f….esnext.js
(cdn-static.farfetch-contents.com)
4 KiB
0 ms
…mobile/42512.client.69ba4cf….esnext.js
(cdn-static.farfetch-contents.com)
4 KiB
0 ms
…mobile/63834.client.765803d….esnext.js
(cdn-static.farfetch-contents.com)
4 KiB
0 ms
…content/default.client.5e6f1e8….esnext.js
(cdn-static.farfetch-contents.com)
6 KiB
0 ms
…mobile/57864.client.31fed96….esnext.js
(cdn-static.farfetch-contents.com)
4 KiB
0 ms
…mobile/97750.client.2951143….esnext.js
(cdn-static.farfetch-contents.com)
3 KiB
0 ms
674 KiB
0 ms
…23/26571023_56846878_600.jpg
(cdn-images.farfetch-contents.com)
69 KiB
0 ms
66 KiB
0 ms
54 KiB
0 ms
…v2.00/FarfetchB….woff2
(cdn-static.farfetch-contents.com)
50 KiB
0 ms
…v2.00/FarfetchBasis-Bold.woff2
(cdn-static.farfetch-contents.com)
49 KiB
0 ms
37 KiB
0 ms
…fr-FR/translation.3ccca8a….json
(cdn-static.farfetch-contents.com)
34 KiB
0 ms
…v2.00/NimbusSan….woff2
(cdn-static.farfetch-contents.com)
34 KiB
0 ms
31 KiB
0 ms
29 KiB
0 ms
25 KiB
0 ms
…02/26930402_58209728_600.jpg
(cdn-images.farfetch-contents.com)
15 KiB
0 ms
…mobile/18569.client.d148c2b….esnext.js
(cdn-static.farfetch-contents.com)
11 KiB
0 ms
…third-parties/gtm_iframe.v19.html
(cdn-static.farfetch-contents.com)
9 KiB
0 ms
…75/29074275_58211231_600.jpg
(cdn-images.farfetch-contents.com)
7 KiB
0 ms
…mobile/71893.client.bf3d28f….esnext.js
(cdn-static.farfetch-contents.com)
6 KiB
0 ms
…mobile/GdprBanner.client.fa70789….esnext.js
(cdn-static.farfetch-contents.com)
5 KiB
0 ms
…mobile/45762.client.9781f7a….css
(cdn-static.farfetch-contents.com)
5 KiB
0 ms
…content/default.client.de5e4d9….css
(cdn-static.farfetch-contents.com)
3 KiB
0 ms
…mobile/71893.client.b5076b5….css
(cdn-static.farfetch-contents.com)
2 KiB
0 ms
…mobile/56683.client.3b099b0….css
(cdn-static.farfetch-contents.com)
2 KiB
0 ms
…mobile/7120.client.4b671fa….esnext.js
(cdn-static.farfetch-contents.com)
1 KiB
0 ms
…mobile/77053.client.b027ce6….esnext.js
(cdn-static.farfetch-contents.com)
1 KiB
0 ms
…mobile/90019.client.d2278ea….esnext.js
(cdn-static.farfetch-contents.com)
1 KiB
0 ms
…mobile/27762.client.8895680….esnext.js
(cdn-static.farfetch-contents.com)
1 KiB
0 ms
…mobile/26877.client.400aab3….css
(cdn-static.farfetch-contents.com)
1 KiB
0 ms
mPulse
analytics
50 KiB
0 ms
50 KiB
0 ms
/api/config.json?key=…
(c.go-mpulse.net)
0 KiB
0 ms
Forter
utility
175 KiB
0 ms
…0c0275c12bca/script.js
(0c0275c12bca.cdn4.forter.com)
173 KiB
0 ms
…907af83…/wpt.json
(cdn0.forter.com)
1 KiB
0 ms
0 KiB
0 ms
0 KiB
0 ms
0 KiB
0 ms
/prop.json
(907af830a9684a9e97d7e81df021b726-0c0275c12bca.cdn.forter.com)
0 KiB
0 ms
/events
(cdn3.forter.com)
0 KiB
0 ms
Google Analytics
analytics
23 KiB
0 ms
/analytics.js
(www.google-analytics.com)
21 KiB
0 ms
/j/collect?v=…
(www.google-analytics.com)
1 KiB
0 ms
/g/collect?v=…
(www.google-analytics.com)
1 KiB
0 ms
farfetch.net
18 KiB
0 ms
…marketing/trackings
(api.farfetch.net)
18 KiB
0 ms
Riskified
utility
17 KiB
0 ms
15 KiB
0 ms
/v2/client_infos
(c.riskified.com)
1 KiB
0 ms
/img/image-l.gif?t=…
(img.riskified.com)
0 KiB
0 ms
/img/image-l.gif?t=…
(img.riskified.com)
0 KiB
0 ms
/img/image-l.gif?t=…
(img.riskified.com)
0 KiB
0 ms
/img/image-l.gif?t=…
(img.riskified.com)
0 KiB
0 ms
/img/image-l.gif?t=…
(img.riskified.com)
0 KiB
0 ms
Bing Ads
ad
17 KiB
0 ms
/bat.js
(bat.bing.com)
15 KiB
0 ms
/action/0?ti=…
(bat.bing.com)
1 KiB
0 ms
…action/4008469.js
(bat.bing.com)
1 KiB
0 ms
rum-ingress-coralogix.com
1 KiB
0 ms
…v1beta/logs
(ingress.eu2.rum-ingress-coralogix.com)
1 KiB
0 ms
Google/Doubleclick Ads
ad
1 KiB
0 ms
1 KiB
0 ms
…conversion/992…?random=…
(pagead2.googlesyndication.com)
1 KiB
0 ms
/ccm/collect?en=…
(pagead2.googlesyndication.com)
0 KiB
0 ms
cloudfront.net
0 KiB
0 ms
/events
(d2o5idwacg3gyw.cloudfront.net)
0 KiB
0 ms
Reduce JavaScript execution time 3.7 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
Google Tag Manager
tag-manager
2,134 ms
1,916 ms
50 ms
/gtm.js?id=GTM-5VWCDN
(www.googletagmanager.com)
1,735 ms
1,550 ms
20 ms
/gtag/js?id=…
(www.googletagmanager.com)
191 ms
178 ms
12 ms
/gtag/destination?id=…
(www.googletagmanager.com)
82 ms
75 ms
7 ms
/gtag/destination?id=…
(www.googletagmanager.com)
72 ms
66 ms
6 ms
/gtag/destination?id=…
(www.googletagmanager.com)
53 ms
48 ms
5 ms
farfetch.com
1st party
1,105 ms
660 ms
17 ms
…FhcGb/CJxVQQB
(www.farfetch.com)
569 ms
556 ms
9 ms
…men/items.aspx
(www.farfetch.com)
484 ms
52 ms
8 ms
52 ms
52 ms
0 ms
farfetch-contents.com
705 ms
608 ms
18 ms
…mobile/77155.client.d086cd5….esnext.js
(cdn-static.farfetch-contents.com)
199 ms
198 ms
0 ms
…sdks/coralogix-browser-sdk-1.4.6.js
(cdn-static.farfetch-contents.com)
145 ms
118 ms
15 ms
…mobile/32381.client.70e6329….esnext.js
(cdn-static.farfetch-contents.com)
116 ms
115 ms
0 ms
…mobile/45762.client.0a5ba7c….esnext.js
(cdn-static.farfetch-contents.com)
91 ms
79 ms
2 ms
…mobile/58288.client.ed5664c….esnext.js
(cdn-static.farfetch-contents.com)
87 ms
83 ms
0 ms
…mobile/83217.client.aef13ed….esnext.js
(cdn-static.farfetch-contents.com)
67 ms
14 ms
1 ms
Unattributable
539 ms
141 ms
0 ms
Unattributable
352 ms
65 ms
0 ms
(program):2
186 ms
76 ms
0 ms
Forter
utility
255 ms
245 ms
7 ms
…0c0275c12bca/script.js
(0c0275c12bca.cdn4.forter.com)
255 ms
245 ms
7 ms
Riskified
utility
61 ms
57 ms
1 ms
61 ms
57 ms
1 ms
Largest Contentful Paint element 7,110 ms
This is the largest contentful element painted within the viewport. Learn more about the Largest Contentful Paint elementLCP
Element
2025-02-26_MW_WEBAPP_NEW SEASON_PRE-S_MULTIBRAND_MULTICATEGORY_IMG
<img alt="2025-02-26_MW_WEBAPP_NEW SEASON_PRE-S_MULTIBRAND_MULTICATEGORY_IMG" src="https://cdn-static.farfetch-contents.com/cms-ccloud/caas/v1/media/10405412…" loading="eager" data-component="Picture" class="_e38d27 emzgpi21 ltr-1i0wvsb" data-ffref="inspirationModule|10405434|3|02/26/2025 08:50:26|10405412|2|02/26/2025 08:…">
Phase
% of LCP
Timing
TTFB
8%
600 ms
Load Delay
83%
5,880 ms
Load Time
3%
220 ms
Render Delay
6%
410 ms
Avoid large layout shifts 7 layout shifts found
These are the largest layout shifts observed on the page. Each table item represents a single layout shift, and shows the element that shifted the most. Below each item are possible root causes that led to the layout shift. Some of these layout shifts may not be included in the CLS metric value due to windowing. Learn how to improve CLSCLS
Element
Layout shift score
L'essence de la saison Explorez les essentiels printaniers signés Studio Nicho…
<main id="content">
0.075
Nous utilisons des cookies pour optimiser votre expérience utilisateur, vous pr…
<div data-testid="gdpr-banner-mobile" class="ltr-1bjxu8v em3ogft0">
0.014
Nous utilisons des cookies pour optimiser votre expérience utilisateur, vous pr…
<div data-testid="gdpr-banner-mobile" class="ltr-1bjxu8v em3ogft0">
0.013
Nous utilisons des cookies pour optimiser votre expérience utilisateur, vous pr…
<div data-testid="gdpr-banner-mobile" class="ltr-1bjxu8v em3ogft0">
0.006
Nous utilisons des cookies pour optimiser votre expérience utilisateur, vous pr…
<div data-testid="gdpr-banner-mobile" class="ltr-1bjxu8v em3ogft0">
0.006
Nous utilisons des cookies pour optimiser votre expérience utilisateur, vous pr…
<div class="ltr-qhbstx e1depnvi0">
0.000
div#headerTopArea > div#App banner > button.ltr-bopzjq > ::before
<::before>
0.000
Reduce unused JavaScript Potential savings of 563 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
ReactIf you are not server-side rendering, split your JavaScript bundles with React.lazy(). Otherwise, code-split using a third-party library such as loadable-components.
URL
Transfer Size
Potential Savings
Google Tag Manager
tag-manager
573.8 KiB
255.1 KiB
/gtag/destination?id=…
(www.googletagmanager.com)
95.1 KiB
58.3 KiB
/gtag/js?id=…
(www.googletagmanager.com)
136.0 KiB
53.6 KiB
/gtag/destination?id=…
(www.googletagmanager.com)
100.2 KiB
50.1 KiB
/gtag/destination?id=…
(www.googletagmanager.com)
92.5 KiB
47.3 KiB
/gtm.js?id=GTM-5VWCDN
(www.googletagmanager.com)
150.0 KiB
45.9 KiB
farfetch-contents.com
448.1 KiB
214.8 KiB
…sdks/coralogix-browser-sdk-1.4.6.js
(cdn-static.farfetch-contents.com)
138.4 KiB
85.5 KiB
…mobile/45762.client.0a5ba7c….esnext.js
(cdn-static.farfetch-contents.com)
220.4 KiB
75.4 KiB
…mobile/61181.client.d6268ee….esnext.js
(cdn-static.farfetch-contents.com)
37.1 KiB
29.7 KiB
…mobile/83217.client.aef13ed….esnext.js
(cdn-static.farfetch-contents.com)
52.2 KiB
24.2 KiB
Forter
utility
172.2 KiB
61.5 KiB
…0c0275c12bca/script.js
(0c0275c12bca.cdn4.forter.com)
172.2 KiB
61.5 KiB
mPulse
analytics
49.1 KiB
31.9 KiB
49.1 KiB
31.9 KiB
Eliminate render-blocking resources Potential savings of 910 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles. Learn how to eliminate render-blocking resources.LCPFCP
URL
Transfer Size
Potential Savings
farfetch-contents.com
149.6 KiB
1,660 ms
…mobile/45762.client.9781f7a….css
(cdn-static.farfetch-contents.com)
4.6 KiB
760 ms
…content/default.client.de5e4d9….css
(cdn-static.farfetch-contents.com)
3.0 KiB
150 ms
…sdks/coralogix-browser-sdk-1.4.6.js
(cdn-static.farfetch-contents.com)
139.1 KiB
610 ms
…js/cpuMonitor.v3.js
(cdn-static.farfetch-contents.com)
2.8 KiB
150 ms
Serve images in next-gen formats Potential savings of 728 KiB
Image formats like WebP and AVIF often provide better compression than PNG or JPEG, which means faster downloads and less data consumption. Learn more about modern image formats.LCPFCP
URL
Resource Size
Potential Savings
farfetch-contents.com
886.7 KiB
727.9 KiB
2025-02-19_MW_WEBAPP_SHIRTS_PRE-S_MULTIBRAND_SHIRTS
<img data-component="Picture" alt="2025-02-19_MW_WEBAPP_SHIRTS_PRE-S_MULTIBRAND_SHIRTS" loading="lazy" class="emzgpi21 ltr-1i0wvsb">
673.0 KiB
644.4 KiB
65.3 KiB
28.0 KiB
2025-02-05_MW_WEBAPP_SHIRTS_PRE-S_MULTIBRAND_SHIRTS_IMG
<img data-component="Picture" alt="2025-02-05_MW_WEBAPP_SHIRTS_PRE-S_MULTIBRAND_SHIRTS_IMG" loading="lazy" class="emzgpi21 ltr-1i0wvsb">
53.3 KiB
17.6 KiB
2025-02-05_MW_WEBAPP_PRADA_PRE-S_PRADA_MULTICATEGORY_img
<img data-component="Picture" alt="2025-02-05_MW_WEBAPP_PRADA_PRE-S_PRADA_MULTICATEGORY_img" loading="lazy" class="emzgpi21 ltr-1i0wvsb">
36.9 KiB
13.7 KiB
2025-02-26_MW_WEBAPP_NEW SEASON_PRE-S_MULTIBRAND_MULTICATEGORY_IMG
<img alt="2025-02-26_MW_WEBAPP_NEW SEASON_PRE-S_MULTIBRAND_MULTICATEGORY_IMG" src="https://cdn-static.farfetch-contents.com/cms-ccloud/caas/v1/media/10405412…" loading="eager" data-component="Picture" class="_e38d27 emzgpi21 ltr-1i0wvsb" data-ffref="inspirationModule|10405434|3|02/26/2025 08:50:26|10405412|2|02/26/2025 08:…">
29.9 KiB
12.7 KiB
2025-02-05_MW_WEBAPP_PRADA_PRE-S_PRADA_MULTICATEGORY_IMG
<img data-component="Picture" alt="2025-02-05_MW_WEBAPP_PRADA_PRE-S_PRADA_MULTICATEGORY_IMG" loading="lazy" class="emzgpi21 ltr-1i0wvsb">
28.2 KiB
11.5 KiB
Properly size images Potential savings of 37 KiB
Serve images that are appropriately-sized to save cellular data and improve load time. Learn how to size images.LCPFCP
URL
Resource Size
Potential Savings
farfetch-contents.com
68.9 KiB
36.7 KiB
t-shirt à motif Barocco en jacquard
<img alt="t-shirt à motif Barocco en jacquard" srcset="https://cdn-images.farfetch-contents.com/26/57/10/23/26571023_56846878_600…" loading="eager" sizes=" (max-width: 35.9375em) 480px, (min-width: 36em) and (max-width: 5…" width="300" height="400" data-component="ProductCardImageSecondary" data-testid="product-image" class="ltr-io0g65">
…23/26571023_56846878_600.jpg
(cdn-images.farfetch-contents.com)
68.9 KiB
36.7 KiB
Avoid an excessive DOM size 986 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
ReactConsider using a "windowing" library like react-window to minimize the number of DOM nodes created if you are rendering many repeated elements on the page. Learn more. Also, minimize unnecessary re-renders using shouldComponentUpdate, PureComponent, or React.memo and skip effects only until certain dependencies have changed if you are using the Effect hook to improve runtime performance.
Statistic
Element
Value
Total DOM Elements
986
Maximum DOM Depth
t-shirt à motif Barocco en jacquard
<img alt="t-shirt à motif Barocco en jacquard" srcset="https://cdn-images.farfetch-contents.com/26/57/10/23/26571023_56846878_600…" loading="eager" sizes=" (max-width: 35.9375em) 480px, (min-width: 36em) and (max-width: 5…" width="300" height="400" data-component="ProductCardImageSecondary" data-testid="product-image" class="ltr-io0g65">
17
Maximum Child Elements
Mode femmeMode hommeMode enfantNouveautésNouveautés du jourNouveautés classique…
<nav id="unstructured_navigation" style="display:none">
175
Serve static assets with an efficient cache policy 59 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more about efficient cache policies.
URL
Cache TTL
Transfer Size
farfetch-contents.com
1,725 KiB
…vitorino/vitorino.min.js
(cdn-static.farfetch-contents.com)
5m
5 KiB
15m
25 KiB
30d
674 KiB
…mobile/45762.client.0a5ba7c….esnext.js
(cdn-static.farfetch-contents.com)
30d
221 KiB
…sdks/coralogix-browser-sdk-1.4.6.js
(cdn-static.farfetch-contents.com)
30d
139 KiB
30d
66 KiB
30d
54 KiB
…mobile/83217.client.aef13ed….esnext.js
(cdn-static.farfetch-contents.com)
30d
53 KiB
…v2.00/FarfetchB….woff2
(cdn-static.farfetch-contents.com)
30d
50 KiB
…v2.00/FarfetchBasis-Bold.woff2
(cdn-static.farfetch-contents.com)
30d
49 KiB
…mobile/61181.client.d6268ee….esnext.js
(cdn-static.farfetch-contents.com)
30d
38 KiB
30d
37 KiB
…v2.00/NimbusSan….woff2
(cdn-static.farfetch-contents.com)
30d
34 KiB
30d
31 KiB
30d
29 KiB
…mobile/803.client.6d5f2b2….esnext.js
(cdn-static.farfetch-contents.com)
30d
29 KiB
…mobile/58288.client.ed5664c….esnext.js
(cdn-static.farfetch-contents.com)
30d
26 KiB
…mobile/6302.client.623d635….esnext.js
(cdn-static.farfetch-contents.com)
30d
21 KiB
…mobile/89706.client.837ad6d….esnext.js
(cdn-static.farfetch-contents.com)
30d
17 KiB
…mobile/runtime.client.1a9d587….esnext.js
(cdn-static.farfetch-contents.com)
30d
12 KiB
…mobile/18569.client.d148c2b….esnext.js
(cdn-static.farfetch-contents.com)
30d
11 KiB
…mobile/61349.client.1ebdccd….esnext.js
(cdn-static.farfetch-contents.com)
30d
8 KiB
…mobile/77155.client.d086cd5….esnext.js
(cdn-static.farfetch-contents.com)
30d
7 KiB
…mobile/97581.client.9aa1008….esnext.js
(cdn-static.farfetch-contents.com)
30d
7 KiB
…mobile/71171.client.3c4f984….esnext.js
(cdn-static.farfetch-contents.com)
30d
6 KiB
…content/default.client.5e6f1e8….esnext.js
(cdn-static.farfetch-contents.com)
30d
6 KiB
…mobile/71893.client.bf3d28f….esnext.js
(cdn-static.farfetch-contents.com)
30d
6 KiB
…mobile/31131.client.636a5e8….esnext.js
(cdn-static.farfetch-contents.com)
30d
5 KiB
…mobile/GdprBanner.client.fa70789….esnext.js
(cdn-static.farfetch-contents.com)
30d
5 KiB
…mobile/92879.client.ce4f36a….esnext.js
(cdn-static.farfetch-contents.com)
30d
5 KiB
…mobile/68419.client.fef9532….esnext.js
(cdn-static.farfetch-contents.com)
30d
5 KiB
…mobile/45762.client.9781f7a….css
(cdn-static.farfetch-contents.com)
30d
5 KiB
…mobile/63834.client.765803d….esnext.js
(cdn-static.farfetch-contents.com)
30d
4 KiB
…mobile/42512.client.69ba4cf….esnext.js
(cdn-static.farfetch-contents.com)
30d
4 KiB
…mobile/94515.client.c486f95….esnext.js
(cdn-static.farfetch-contents.com)
30d
4 KiB
…mobile/23479.client.e8b4f9f….esnext.js
(cdn-static.farfetch-contents.com)
30d
4 KiB
…mobile/57864.client.31fed96….esnext.js
(cdn-static.farfetch-contents.com)
30d
4 KiB
…content/default.client.de5e4d9….css
(cdn-static.farfetch-contents.com)
30d
3 KiB
…js/cpuMonitor.v3.js
(cdn-static.farfetch-contents.com)
30d
3 KiB
…mobile/97750.client.2951143….esnext.js
(cdn-static.farfetch-contents.com)
30d
3 KiB
…mobile/71893.client.b5076b5….css
(cdn-static.farfetch-contents.com)
30d
2 KiB
…mobile/56683.client.3b099b0….css
(cdn-static.farfetch-contents.com)
30d
2 KiB
…mobile/7120.client.4b671fa….esnext.js
(cdn-static.farfetch-contents.com)
30d
1 KiB
…mobile/77053.client.b027ce6….esnext.js
(cdn-static.farfetch-contents.com)
30d
1 KiB
…mobile/32381.client.70e6329….esnext.js
(cdn-static.farfetch-contents.com)
30d
1 KiB
…mobile/90019.client.d2278ea….esnext.js
(cdn-static.farfetch-contents.com)
30d
1 KiB
…js/eventManager.min.js
(cdn-static.farfetch-contents.com)
30d
1 KiB
…mobile/27762.client.8895680….esnext.js
(cdn-static.farfetch-contents.com)
30d
1 KiB
…js/setRUMUse….v1.js
(cdn-static.farfetch-contents.com)
30d
1 KiB
…mobile/26877.client.400aab3….css
(cdn-static.farfetch-contents.com)
30d
1 KiB
farfetch.com
1st party
106 KiB
…FhcGb/CJxVQQB
(www.farfetch.com)
6h
106 KiB
mPulse
analytics
50 KiB
7d
50 KiB
Google Analytics
analytics
21 KiB
/analytics.js
(www.google-analytics.com)
2h
21 KiB
Riskified
utility
16 KiB
/img/image-l.gif?t=…
(img.riskified.com)
None
0 KiB
/img/image-l.gif?t=…
(img.riskified.com)
None
0 KiB
/img/image-l.gif?t=…
(img.riskified.com)
None
0 KiB
/img/image-l.gif?t=…
(img.riskified.com)
None
0 KiB
/img/image-l.gif?t=…
(img.riskified.com)
None
0 KiB
10m
15 KiB
Avoid serving legacy JavaScript to modern browsers Potential savings of 16 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. However, many aren't necessary for modern browsers. For your bundled JavaScript, adopt a modern script deployment strategy using module/nomodule feature detection to reduce the amount of code shipped to modern browsers, while retaining support for legacy browsers. Learn how to use modern JavaScriptLCPFCP
URL
Potential Savings
farfetch-contents.com
16.4 KiB
…sdks/coralogix-browser-sdk-1.4.6.js
(cdn-static.farfetch-contents.com)
8.5 KiB
…sdks/coralogix-browser-sdk-1.4.6.js:1:317437
(cdn-static.farfetch-contents.com)
Array.from
…mobile/89706.client.837ad6d….esnext.js
(cdn-static.farfetch-contents.com)
7.8 KiB
Array.isArray
…mobile/45762.client.0a5ba7c….esnext.js
(cdn-static.farfetch-contents.com)
0.1 KiB
@babel/plugin-transform-classes
…mobile/83217.client.aef13ed….esnext.js
(cdn-static.farfetch-contents.com)
0.0 KiB
@babel/plugin-transform-classes
Avoid 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().
Source
farfetch.com
1st party
…men/items.aspx:92:1215
(www.farfetch.com)
Avoid enormous network payloads Total size was 2,957 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
farfetch-contents.com
1,033.8 KiB
673.6 KiB
…mobile/45762.client.0a5ba7c….esnext.js
(cdn-static.farfetch-contents.com)
221.1 KiB
…sdks/coralogix-browser-sdk-1.4.6.js
(cdn-static.farfetch-contents.com)
139.1 KiB
Google Tag Manager
tag-manager
579.3 KiB
/gtm.js?id=GTM-5VWCDN
(www.googletagmanager.com)
151.1 KiB
/gtag/js?id=…
(www.googletagmanager.com)
137.1 KiB
/gtag/destination?id=…
(www.googletagmanager.com)
101.3 KiB
/gtag/destination?id=…
(www.googletagmanager.com)
96.2 KiB
/gtag/destination?id=…
(www.googletagmanager.com)
93.6 KiB
Forter
utility
173.0 KiB
…0c0275c12bca/script.js
(0c0275c12bca.cdn4.forter.com)
173.0 KiB
farfetch.com
1st party
106.4 KiB
…FhcGb/CJxVQQB
(www.farfetch.com)
106.4 KiB
Avoid long main-thread tasks 16 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay. Learn how to avoid long main-thread tasksTBT
URL
Start Time
Duration
Google Tag Manager
tag-manager
2,063 ms
/gtm.js?id=GTM-5VWCDN
(www.googletagmanager.com)
11,073 ms
1,281 ms
/gtm.js?id=GTM-5VWCDN
(www.googletagmanager.com)
7,482 ms
225 ms
/gtag/js?id=…
(www.googletagmanager.com)
19,142 ms
185 ms
/gtm.js?id=GTM-5VWCDN
(www.googletagmanager.com)
16,455 ms
93 ms
/gtag/destination?id=…
(www.googletagmanager.com)
20,077 ms
81 ms
/gtm.js?id=GTM-5VWCDN
(www.googletagmanager.com)
7,407 ms
75 ms
/gtag/destination?id=…
(www.googletagmanager.com)
20,827 ms
71 ms
/gtag/destination?id=…
(www.googletagmanager.com)
21,877 ms
52 ms
farfetch-contents.com
558 ms
…mobile/77155.client.d086cd5….esnext.js
(cdn-static.farfetch-contents.com)
8,982 ms
185 ms
…mobile/32381.client.70e6329….esnext.js
(cdn-static.farfetch-contents.com)
16,291 ms
116 ms
…sdks/coralogix-browser-sdk-1.4.6.js
(cdn-static.farfetch-contents.com)
4,078 ms
110 ms
…vitorino/vitorino.min.js
(cdn-static.farfetch-contents.com)
16,209 ms
82 ms
…js/cpuMonitor.v3.js
(cdn-static.farfetch-contents.com)
4,188 ms
65 ms
farfetch.com
1st party
550 ms
…FhcGb/CJxVQQB
(www.farfetch.com)
4,253 ms
442 ms
…FhcGb/CJxVQQB
(www.farfetch.com)
8,925 ms
57 ms
…FhcGb/CJxVQQB
(www.farfetch.com)
5,146 ms
51 ms
Initial server response time was short Root document took 530 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
ReactIf you are server-side rendering any React components, consider using renderToPipeableStream() or renderToStaticNodeStream() to allow the client to receive and hydrate different parts of the markup instead of all at once. Learn more.
URL
Time Spent
farfetch.com
1st party
530 ms
…men/items.aspx
(www.farfetch.com)
530 ms
User Timing marks and measures 14 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.
ReactUse the React DevTools Profiler, which makes use of the Profiler API, to measure the rendering performance of your components. Learn more.
Name
Type
Start Time
Duration
TL Getting uv marker
Measure
1,767.21 ms
1,804.40 ms
TL Creating SDKs marker
Measure
3,571.80 ms
2.82 ms
TL Queues marker
Measure
3,574.98 ms
7.45 ms
TL Window obj marker
Measure
3,582.56 ms
6.01 ms
TL - Start Bootstrap
Mark
1,765.58 ms
TL - Start getting uv
Mark
1,767.21 ms
TL - End getting uv
Mark
3,571.60 ms
TL - Start creating sdks
Mark
3,571.80 ms
TL - End creating sdks
Mark
3,574.61 ms
TL - End Bootstrap
Mark
3,574.83 ms
TL - Start creating queues
Mark
3,574.98 ms
TL - End creating queues
Mark
3,582.43 ms
TL - Start filling window obj
Mark
3,582.56 ms
TL - End filling window obj
Mark
3,588.57 ms
Avoid non-composited animations 2 animated elements found
Animations which are not composited can be janky and increase CLS. Learn how to avoid non-composited animationsCLS
Element
Name
Passez à l’application pour une expérience optimale Ouvrir
<div role="banner" id="App banner" aria-label="App banner" data-testid="appBannerModule" class="ltr-6g235p ew1fhs50">
Unsupported CSS Property: visibility
visibility
Unsupported CSS Property: height
height
Nous utilisons des cookies pour optimiser votre expérience utilisateur, vous pr…
<div data-testid="gdpr-banner-mobile" class="ltr-1bjxu8v em3ogft0">
Unsupported CSS Property: max-height
max-height
Avoid chaining critical requests 35 chains found
The Critical Request Chains below show you what resources are loaded with a high priority. Consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load. Learn how to avoid chaining critical requests.
Maximum critical path latency: 1,950.822 ms
Initial Navigation
…men/items.aspx
(www.farfetch.com)
…js/eventManager.min.js
(cdn-static.farfetch-contents.com)
- 712.715 ms, 0.83 KiB
…mobile/runtime.client.1a9d587….esnext.js
(cdn-static.farfetch-contents.com)
- 200.053 ms, 12.26 KiB
…mobile/45762.client.0a5ba7c….esnext.js
(cdn-static.farfetch-contents.com)
- 208.287 ms, 221.07 KiB
…mobile/61181.client.d6268ee….esnext.js
(cdn-static.farfetch-contents.com)
- 162.607 ms, 37.78 KiB
…mobile/68419.client.fef9532….esnext.js
(cdn-static.farfetch-contents.com)
- 217.339 ms, 4.89 KiB
…mobile/31131.client.636a5e8….esnext.js
(cdn-static.farfetch-contents.com)
- 190.686 ms, 5.38 KiB
…mobile/42512.client.69ba4cf….esnext.js
(cdn-static.farfetch-contents.com)
- 163.152 ms, 4.19 KiB
…mobile/89706.client.837ad6d….esnext.js
(cdn-static.farfetch-contents.com)
- 218.972 ms, 16.93 KiB
…mobile/83217.client.aef13ed….esnext.js
(cdn-static.farfetch-contents.com)
- 215.522 ms, 52.92 KiB
…mobile/61349.client.1ebdccd….esnext.js
(cdn-static.farfetch-contents.com)
- 208.02 ms, 8.30 KiB
…mobile/45762.client.9781f7a….css
(cdn-static.farfetch-contents.com)
- 194.181 ms, 4.64 KiB
…mobile/97581.client.9aa1008….esnext.js
(cdn-static.farfetch-contents.com)
- 292.811 ms, 6.55 KiB
…mobile/77155.client.d086cd5….esnext.js
(cdn-static.farfetch-contents.com)
- 186.95 ms, 7.45 KiB
…mobile/92879.client.ce4f36a….esnext.js
(cdn-static.farfetch-contents.com)
- 680.363 ms, 4.93 KiB
…mobile/94515.client.c486f95….esnext.js
(cdn-static.farfetch-contents.com)
- 201.266 ms, 4.03 KiB
…mobile/58288.client.ed5664c….esnext.js
(cdn-static.farfetch-contents.com)
- 205.489 ms, 26.33 KiB
…mobile/23479.client.e8b4f9f….esnext.js
(cdn-static.farfetch-contents.com)
- 228.063 ms, 3.79 KiB
…mobile/6302.client.623d635….esnext.js
(cdn-static.farfetch-contents.com)
- 199.785 ms, 21.24 KiB
…mobile/97750.client.2951143….esnext.js
(cdn-static.farfetch-contents.com)
- 194.986 ms, 2.75 KiB
…mobile/63834.client.765803d….esnext.js
(cdn-static.farfetch-contents.com)
- 190.673 ms, 4.22 KiB
…mobile/57864.client.31fed96….esnext.js
(cdn-static.farfetch-contents.com)
- 196.189 ms, 3.70 KiB
…content/default.client.de5e4d9….css
(cdn-static.farfetch-contents.com)
- 687.447 ms, 3.01 KiB
…mobile/803.client.6d5f2b2….esnext.js
(cdn-static.farfetch-contents.com)
- 189.086 ms, 28.63 KiB
…mobile/71171.client.3c4f984….esnext.js
(cdn-static.farfetch-contents.com)
- 194.888 ms, 6.46 KiB
…content/default.client.5e6f1e8….esnext.js
(cdn-static.farfetch-contents.com)
- 176.221 ms, 6.24 KiB
…FhcGb/CJxVQQB
(www.farfetch.com)
- 71.283 ms, 106.44 KiB
…mobile/71893.client.b5076b5….css
(cdn-static.farfetch-contents.com)
- 131.012 ms, 2.43 KiB
…mobile/26877.client.400aab3….css
(cdn-static.farfetch-contents.com)
- 188.765 ms, 0.71 KiB
…mobile/56683.client.3b099b0….css
(cdn-static.farfetch-contents.com)
- 668.962 ms, 1.92 KiB
…sdks/coralogix-browser-sdk-1.4.6.js
(cdn-static.farfetch-contents.com)
- 191.134 ms, 139.14 KiB
…v2.00/NimbusSan….woff2
(cdn-static.farfetch-contents.com)
- 66.935 ms, 33.59 KiB
…v2.00/FarfetchB….woff2
(cdn-static.farfetch-contents.com)
- 41.98 ms, 50.11 KiB
…js/cpuMonitor.v3.js
(cdn-static.farfetch-contents.com)
- 191.821 ms, 2.76 KiB
…v2.00/FarfetchBasis-Bold.woff2
(cdn-static.farfetch-contents.com)
- 316.758 ms, 48.97 KiB
…js/setRUMUse….v1.js
(cdn-static.farfetch-contents.com)
- 217.455 ms, 0.75 KiB
More information about the performance of your application. These numbers don't directly affect the Performance score.
Passed audits (17)
Show Hide
Defer offscreen images
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive. Learn how to defer offscreen images.LCPFCP
Minify CSS
Minifying CSS files can reduce network payload sizes. Learn how to minify CSS.LCPFCP
ReactIf your build system minifies CSS files automatically, ensure that you are deploying the production build of your application. You can check this with the React Developer Tools extension. Learn more.
Minify JavaScript
Minifying JavaScript files can reduce payload sizes and script parse time. Learn how to minify JavaScript.LCPFCP
ReactIf your build system minifies JS files automatically, ensure that you are deploying the production build of your application. You can check this with the React Developer Tools extension. Learn more.
Reduce unused CSS
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
Efficiently encode images
Optimized images load faster and consume less cellular data. Learn how to efficiently encode images.LCPFCP
Enable text compression
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. Learn more about text compression.LCPFCP
Preconnect to required origins
Warnings:
  • A `<link rel=preconnect>` was found for "https://dd6zx4ibq538k.cloudfront.net" but was not used by the browser. Only use `preconnect` for important origins that the page will certainly request.
  • A `<link rel=preconnect>` was found for "https://securepubads.g.doubleclick.net" but was not used by the browser. Only use `preconnect` for important origins that the page will certainly request.
  • A `<link rel=preconnect>` was found for "https://c.bannerflow.net" but was not used by the browser. Only use `preconnect` for important origins that the page will certainly request.
  • A `<link rel=preconnect>` was found for "https://adservice.google.com" but was not used by the browser. Only use `preconnect` for important origins that the page will certainly request.
  • More than 2 `<link rel=preconnect>` connections were found. These should be used sparingly and only to the most important origins.
Consider adding preconnect or dns-prefetch resource hints to establish early connections to important third-party origins. Learn how to preconnect to required origins.LCPFCP
Avoid multiple page redirects
Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.LCPFCP
ReactIf you are using React Router, minimize usage of the <Redirect> component for route navigations.
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
All text remains visible during webfont loads
Leverage the font-display CSS feature to ensure text is user-visible while webfonts are loading. Learn more about font-display.
Lazy load third-party resources with facades
Some third-party embeds can be lazy loaded. Consider replacing them with a facade until they are required. Learn how to defer third-parties with a facade.TBT
Largest Contentful Paint image was not lazily loaded
Above-the-fold images that are lazily loaded render later in the page lifecycle, which can delay the largest contentful paint. Learn more about optimal lazy loading.LCP
Uses passive listeners to improve scrolling performance
Consider marking your touch and wheel event listeners as passive to improve your page's scroll performance. Learn more about adopting passive event listeners.
Image elements have explicit width and height
Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensionsCLS
Has a <meta name="viewport"> tag with width or initial-scale
A <meta name="viewport"> not only optimizes your app for mobile screen sizes, but also prevents a 300 millisecond delay to user input. Learn more about using the viewport meta tag.
These checks highlight opportunities to improve the accessibility of your web app. Automatic detection can only detect a subset of issues and does not guarantee the accessibility of your web app, so manual testing is also encouraged.
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 have valid values
Assistive technologies, like screen readers, can't interpret ARIA attributes with invalid values. Learn more about valid values for ARIA attributes.
[aria-*] attributes are valid and not misspelled
Assistive technologies, like screen readers, can't interpret ARIA attributes with invalid names. Learn more about valid ARIA attributes.
Buttons have an accessible name
When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.
Image elements have [alt] attributes
Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the alt attribute.
[user-scalable="no"] is not used in the <meta name="viewport"> element and the [maximum-scale] attribute is not less than 5.
Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a web page. Learn more about the viewport meta tag.
ARIA attributes are used as specified for the element's role
Some ARIA attributes are only allowed on an element under certain conditions. Learn more about conditional ARIA attributes.
[aria-hidden="true"] elements do not contain focusable descendents
Focusable descendents within an [aria-hidden="true"] element prevent those interactive elements from being available to users of assistive technologies like screen readers. Learn how aria-hidden affects focusable elements.
Elements use only permitted ARIA attributes
Using ARIA attributes in roles where they are prohibited can mean that important information is not communicated to users of assistive technologies. Learn more about prohibited ARIA roles.
[role] values are valid
ARIA roles must have valid values in order to perform their intended accessibility functions. Learn more about valid ARIA roles.
Background and foreground colors have a sufficient contrast ratio
Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.
Document has a <title> element
The title gives screen reader users an overview of the page, and search engine users rely on it heavily to determine if a page is relevant to their search. Learn more about document titles.
<html> element has a [lang] attribute
If a page doesn't specify a lang attribute, a screen reader assumes that the page is in the default language that the user chose when setting up the screen reader. If the page isn't actually in the default language, then the screen reader might not announce the page's text correctly. Learn more about the lang attribute.
<html> element has a valid value for its [lang] attribute
Specifying a valid BCP 47 language helps screen readers announce text properly. Learn how to use the lang attribute.
Form elements have associated labels
Labels ensure that form controls are announced properly by assistive technologies, like screen readers. Learn more about form element labels.
Lists contain only <li> elements and script supporting elements (<script> and <template>).
Screen readers have a specific way of announcing lists. Ensuring proper list structure aids screen reader output. Learn more about proper list structure.
List items (<li>) are contained within <ul>, <ol> or <menu> parent elements
Screen readers require list items (<li>) to be contained within a parent <ul>, <ol> or <menu> to be announced properly. Learn more about proper list structure.
No element has a [tabindex] value greater than 0
A value greater than 0 implies an explicit navigation ordering. Although technically valid, this often creates frustrating experiences for users who rely on assistive technologies. Learn more about the tabindex attribute.
Touch targets have sufficient size and spacing.
Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.
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 (30)
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.
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 input fields have accessible names
When an input field doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn more about input field labels.
ARIA meter elements have accessible names
When a meter element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn how to name meter elements.
ARIA progressbar elements have accessible names
When a progressbar element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn how to label progressbar elements.
Elements with an ARIA [role] that require children to contain a specific [role] have all required children.
Some ARIA parent roles must contain specific child roles to perform their intended accessibility functions. Learn more about roles and required children elements.
[role]s are contained by their required parent element
Some ARIA child roles must be contained by specific parent roles to properly perform their intended accessibility functions. Learn more about ARIA roles and required parent element.
Elements with the role=text attribute do not have focusable descendents.
Adding role=text around a text node split by markup enables VoiceOver to treat it as one phrase, but the element's focusable descendents will not be announced. Learn more about the role=text attribute.
ARIA toggle fields have accessible names
When a toggle field doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn more about toggle fields.
ARIA tooltip elements have accessible names
When a tooltip element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn how to name tooltip elements.
ARIA treeitem elements have accessible names
When a treeitem element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn more about labeling treeitem elements.
The page contains a heading, skip link, or landmark region
Adding ways to bypass repetitive content lets keyboard users navigate the page more efficiently. Learn more about bypass blocks.
<dl>'s contain only properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements.
When definition lists are not properly marked up, screen readers may produce confusing or inaccurate output. Learn how to structure definition lists correctly.
Definition list items are wrapped in <dl> elements
Definition list items (<dt> and <dd>) must be wrapped in a parent <dl> element to ensure that screen readers can properly announce them. Learn how to structure definition lists correctly.
ARIA IDs are unique
The value of an ARIA ID must be unique to prevent other instances from being overlooked by assistive technologies. Learn how to fix duplicate ARIA IDs.
No form fields have multiple labels
Form fields with multiple labels can be confusingly announced by assistive technologies like screen readers which use either the first, the last, or all of the labels. Learn how to use form labels.
<frame> or <iframe> elements have a title
Screen reader users rely on frame titles to describe the contents of frames. Learn more about frame titles.
<html> element has an [xml:lang] attribute with the same base language as the [lang] attribute.
If the webpage does not specify a consistent language, then the screen reader might not announce the page's text correctly. Learn more about the lang attribute.
Input buttons have discernible text.
Adding discernable and accessible text to input buttons may help screen reader users understand the purpose of the input button. Learn more about input buttons.
<input type="image"> elements have [alt] text
When an image is being used as an <input> button, providing alternative text can help screen reader users understand the purpose of the button. Learn about input image alt text.
The document does not use <meta http-equiv="refresh">
Users do not expect a page to refresh automatically, and doing so will move focus back to the top of the page. This may create a frustrating or confusing experience. Learn more about the refresh meta tag.
<object> elements have alternate text
Screen readers cannot translate non-text content. Adding alternate text to <object> elements helps screen readers convey meaning to users. Learn more about alt text for object elements.
Select elements have associated label elements.
Form elements without effective labels can create frustrating experiences for screen reader users. Learn more about the select element.
Tables have different content in the summary attribute and <caption>.
The summary attribute should describe the table structure, while <caption> should have the onscreen title. Accurate table mark-up helps users of screen readers. Learn more about summary and caption.
Cells in a <table> element that use the [headers] attribute refer to table cells within the same table.
Screen readers have features to make navigating tables easier. Ensuring <td> cells using the [headers] attribute only refer to other cells in the same table may improve the experience for screen reader users. Learn more about the headers attribute.
<th> elements and elements with [role="columnheader"/"rowheader"] have data cells they describe.
Screen readers have features to make navigating tables easier. Ensuring table headers always refer to some set of cells may improve the experience for screen reader users. Learn more about table headers.
[lang] attributes have a valid value
Specifying a valid BCP 47 language on elements helps ensure that text is pronounced correctly by a screen reader. Learn how to use the lang attribute.
<video> elements contain a <track> element with [kind="captions"]
When a video provides a caption it is easier for deaf and hearing impaired users to access its information. Learn more about video captions.
General
Uses deprecated APIs 1 warning found
Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs.
Deprecation / Warning
Source
mPulse
analytics
UnloadHandler
Browser errors were logged to the console
Errors logged to the console indicate unresolved problems. They can come from network request failures and other browser concerns. Learn more about this errors in console diagnostic audit
Source
Description
farfetch.com
1st party
…men/items.aspx:1:0
(www.farfetch.com)
Refused to execute script from 'https://pagead2.googlesyndication.com/pagead/conversion/992356468/?random=1740903475625&cv=11&fst=1740903475625&bg=ffffff&guid=ON&async=1&gtm=45be52q0v871604564z872394093za201zb887643346&gcs=G101&gcd=13q3r3q3q5l1&dma_cps=-&dma=0&tag_exp=101732282~101732284~102015666~102067808~102482433~102539968~102558064~102587591~102605417~102640600~102658453~102717421~102732003&u_w=412&u_h=823&url=https%3A%2F%2Fwww.farfetch.com%2Ffr%2Fshopping%2Fmen%2Fitems.aspx&label=hCbTCPPi3a8BEPTQmNkD&hn=www.googleadservices.com&frm=0&tiba=V%C3%AAtements%20de%20cr%C3%A9ateur%20pour%20homme%20%7C%20FARFETCH%20France&value=0&bttype=purchase&npa=1&pscdl=denied&_tu=Cg&uaa=&uab=64&uafvl=Not(A%253ABrand%3B99.0.0.0%7CHeadlessChrome%3B133.0.6943.126%7CChromium%3B133.0.6943.126&uamb=1&uam=moto%20g%20power%20(2022)&uap=Android&uapv=11.0&uaw=0&fdr=Cw&rfmt=3&fmt=4' because its MIME type ('text/html') is not executable, and strict MIME type checking is enabled.
Detected JavaScript libraries
All front-end JavaScript libraries detected on the page. Learn more about this JavaScript library detection diagnostic audit.
Name
Version
React
boomerang.js
1.720.0
core-js
core-js-global@3.32.0
Trust and Safety
Ensure CSP is effective against XSS attacks
A strong Content Security Policy (CSP) significantly reduces the risk of cross-site scripting (XSS) attacks. Learn how to use a CSP to prevent XSS
Description
Directive
Severity
`script-src` directive is missing. This can allow the execution of unsafe scripts.
script-src
High
Missing `object-src` allows the injection of plugins that execute unsafe scripts. Consider setting `object-src` to `'none'` if you can.
object-src
High
Passed audits (13)
Show Hide
Uses HTTPS
All sites should be protected with HTTPS, even ones that don't handle sensitive data. This includes avoiding mixed content, where some resources are loaded over HTTP despite the initial request being served over HTTPS. HTTPS prevents intruders from tampering with or passively listening in on the communications between your app and your users, and is a prerequisite for HTTP/2 and many new web platform APIs. Learn more about HTTPS.
Avoids 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.
No issues in the Issues panel in Chrome Devtools
Issues logged to the Issues panel in Chrome Devtools indicate unresolved problems. They can come from network request failures, insufficient security controls, and other browser concerns. Open up the Issues panel in Chrome DevTools for more details on each issue.
Page has valid source maps
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
farfetch-contents.com
SyntaxError: Unexpected token '/', "/*! For li"... is not valid JSON
Riskified
utility
…ZmFyZmV0Y2guY29t/NWJjNzc3Z…
(beacon.riskified.com)
Warning: missing 1 item in `.sourcesContent`
Forter
utility
…0c0275c12bca/script.js
(0c0275c12bca.cdn4.forter.com)
Could not resolve map url: https://cdn4.forter.com/map/suid/0c0275c12bca/77058597234
Not applicable (1)
Show Hide
Redirects HTTP traffic to HTTPS
Make sure that you redirect all HTTP traffic to HTTPS in order to enable secure web features for all your users. Learn more.
These checks ensure that your page is following basic search engine optimization advice. There are many additional factors Lighthouse does not score here that may affect your search ranking, including performance on Core Web Vitals. Learn more about Google Search Essentials.
Additional items to manually check (1)
Show Hide
Structured data is valid
Run these additional validators on your site to check additional SEO best practices.
Passed audits (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 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.6 s
Page LoadsGood (≤ 2.5 s)92%Needs Improvement (2.5 s - 4 s)5%Poor (> 4 s)3%75th Percentile - 1.6 sCore Web Vital
Interaction to Next Paint (INP)
87 ms
Page LoadsGood (≤ 200 ms)91%Needs Improvement (200 ms - 500 ms)7%Poor (> 500 ms)2%75th Percentile - 87 msCore Web Vital
Cumulative Layout Shift (CLS)
0
Page LoadsGood (≤ 0.1)94%Needs Improvement (0.1 - 0.25)5%Poor (> 0.25)2%75th Percentile - 0Core Web Vital
Other Notable Metrics
First Contentful Paint (FCP)
1.5 s
Page LoadsGood (≤ 1.8 s)84%Needs Improvement (1.8 s - 3 s)12%Poor (> 3 s)4%75th Percentile - 1.5 s 
Time to First Byte (TTFB)
1.1 s
Page LoadsGood (≤ 0.8 s)54%Needs Improvement (0.8 s - 1.8 s)40%Poor (> 1.8 s)6%75th Percentile - 1.1 sExperimental
Latest 28-day collection period
Various desktop devicesMany samples (Chrome UX Report)Full visit durationsVarious network connectionsAll Chrome versions
Core Web Vitals Assessment: Passed
Largest Contentful Paint (LCP)
2.1 s
Page LoadsGood (≤ 2.5 s)82%Needs Improvement (2.5 s - 4 s)12%Poor (> 4 s)5%75th Percentile - 2.1 sCore Web Vital
Interaction to Next Paint (INP)
115 ms
Page LoadsGood (≤ 200 ms)88%Needs Improvement (200 ms - 500 ms)9%Poor (> 500 ms)3%75th Percentile - 115 msCore Web Vital
Cumulative Layout Shift (CLS)
0.01
Page LoadsGood (≤ 0.1)87%Needs Improvement (0.1 - 0.25)7%Poor (> 0.25)5%75th Percentile - 0.01Core Web Vital
Other Notable Metrics
First Contentful Paint (FCP)
1.7 s
Page LoadsGood (≤ 1.8 s)81%Needs Improvement (1.8 s - 3 s)16%Poor (> 3 s)4%75th Percentile - 1.7 s 
Time to First Byte (TTFB)
1.2 s
Page LoadsGood (≤ 0.8 s)35%Needs Improvement (0.8 s - 1.8 s)58%Poor (> 1.8 s)7%75th Percentile - 1.2 sExperimental
Latest 28-day collection period
Various desktop devicesMany samples (Chrome UX Report)Full visit durationsVarious network connectionsAll Chrome versions
Diagnose performance issues
58 FCP+7LCP+21TBT+1CLS+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
1.2 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.4 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
1,210 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 2, 2025, 8:17 AM UTC
  • Emulated Desktop with Lighthouse 12.2.3
    Unthrottled CPU/Memory Power: 294 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.126 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.3 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to reduce Javascript execution time.TBT
URL
Total CPU Time
Script Evaluation
Script Parse
Google Tag Manager
tag-manager
1,264 ms
1,179 ms
27 ms
/gtm.js?id=GTM-5VWCDN
(www.googletagmanager.com)
1,096 ms
1,025 ms
14 ms
/gtag/js?id=…
(www.googletagmanager.com)
111 ms
103 ms
7 ms
/gtag/destination?id=…
(www.googletagmanager.com)
57 ms
50 ms
7 ms
farfetch.com
1st party
758 ms
372 ms
12 ms
…men/items.aspx
(www.farfetch.com)
388 ms
45 ms
7 ms
…FhcGb/CJxVQQB
(www.farfetch.com)
371 ms
328 ms
6 ms
Unattributable
650 ms
107 ms
0 ms
Unattributable
485 ms
41 ms
0 ms
(program):2
165 ms
66 ms
0 ms
farfetch-contents.com
370 ms
353 ms
10 ms
…desktop/57333.client.cf211d6….esnext.js
(cdn-static.farfetch-contents.com)
151 ms
151 ms
0 ms
…desktop/74873.client.31b77ef….esnext.js
(cdn-static.farfetch-contents.com)
113 ms
113 ms
0 ms
…sdks/coralogix-browser-sdk-1.4.6.js
(cdn-static.farfetch-contents.com)
106 ms
90 ms
10 ms
Forter
utility
200 ms
191 ms
6 ms
…0c0275c12bca/script.js
(0c0275c12bca.cdn4.forter.com)
200 ms
191 ms
6 ms
Riskified
utility
56 ms
53 ms
1 ms
56 ms
53 ms
1 ms
Minimize main-thread work 3.7 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,554 ms
Other
408 ms
Garbage Collection
276 ms
Style & Layout
257 ms
Script Parsing & Compilation
88 ms
Parse HTML & CSS
54 ms
Rendering
48 ms
Reduce the impact of third-party code Third-party code blocked the main thread for 1,070 ms
Third-party code can significantly impact load performance. Limit the number of redundant third-party providers and try to load third-party code after your page has primarily finished loading. Learn how to minimize third-party impact.TBT
Third-Party
Transfer Size
Main-Thread Blocking Time
Google Tag Manager
tag-manager
579 KiB
875 ms
/gtm.js?id=GTM-5VWCDN
(www.googletagmanager.com)
151 KiB
810 ms
/gtag/js?id=…
(www.googletagmanager.com)
137 KiB
59 ms
/gtag/destination?id=…
(www.googletagmanager.com)
91 KiB
6 ms
/gtag/destination?id=…
(www.googletagmanager.com)
101 KiB
0 ms
/gtag/destination?id=…
(www.googletagmanager.com)
96 KiB
0 ms
2 KiB
0 ms
/td?id=…
(www.googletagmanager.com)
1 KiB
0 ms
farfetch-contents.com
1,843 KiB
192 ms
…desktop/57333.client.cf211d6….esnext.js
(cdn-static.farfetch-contents.com)
9 KiB
83 ms
…desktop/74873.client.31b77ef….esnext.js
(cdn-static.farfetch-contents.com)
29 KiB
54 ms
…sdks/coralogix-browser-sdk-1.4.6.js
(cdn-static.farfetch-contents.com)
139 KiB
28 ms
…desktop/55438.client.4193610….esnext.js
(cdn-static.farfetch-contents.com)
71 KiB
24 ms
…vitorino/vitorino.min.js
(cdn-static.farfetch-contents.com)
5 KiB
2 ms
…desktop/10210.client.6874aa1….esnext.js
(cdn-static.farfetch-contents.com)
228 KiB
1 ms
674 KiB
0 ms
…23/26571023_56846878_600.jpg
(cdn-images.farfetch-contents.com)
69 KiB
0 ms
66 KiB
0 ms
54 KiB
0 ms
…v2.00/FarfetchB….woff2
(cdn-static.farfetch-contents.com)
50 KiB
0 ms
…v2.00/FarfetchBasis-Bold.woff2
(cdn-static.farfetch-contents.com)
49 KiB
0 ms
…desktop/83627.client.9d013c5….esnext.js
(cdn-static.farfetch-contents.com)
37 KiB
0 ms
37 KiB
0 ms
…fr-FR/translation.3ccca8a….json
(cdn-static.farfetch-contents.com)
34 KiB
0 ms
…v2.00/NimbusSan….woff2
(cdn-static.farfetch-contents.com)
34 KiB
0 ms
29 KiB
0 ms
…desktop/803.client.8138d91….esnext.js
(cdn-static.farfetch-contents.com)
27 KiB
0 ms
25 KiB
0 ms
…desktop/89706.client.73bdaae….esnext.js
(cdn-static.farfetch-contents.com)
17 KiB
0 ms
…02/26930402_58209728_600.jpg
(cdn-images.farfetch-contents.com)
15 KiB
0 ms
…desktop/63309.client.432c8dd….esnext.js
(cdn-static.farfetch-contents.com)
15 KiB
0 ms
…desktop/runtime.client.f3273a0….esnext.js
(cdn-static.farfetch-contents.com)
12 KiB
0 ms
…content/default.client.832b49e….esnext.js
(cdn-static.farfetch-contents.com)
10 KiB
0 ms
…third-parties/gtm_iframe.v19.html
(cdn-static.farfetch-contents.com)
9 KiB
0 ms
…desktop/47577.client.40dce4a….esnext.js
(cdn-static.farfetch-contents.com)
9 KiB
0 ms
…75/29074275_58211231_600.jpg
(cdn-images.farfetch-contents.com)
7 KiB
0 ms
…desktop/97581.client.06aa5b6….esnext.js
(cdn-static.farfetch-contents.com)
6 KiB
0 ms
…desktop/71893.client.8033605….esnext.js
(cdn-static.farfetch-contents.com)
6 KiB
0 ms
…desktop/64738.client.3a90818….esnext.js
(cdn-static.farfetch-contents.com)
5 KiB
0 ms
…desktop/78626.client.b9cbbc5….esnext.js
(cdn-static.farfetch-contents.com)
5 KiB
0 ms
…desktop/2316.client.8b33843….esnext.js
(cdn-static.farfetch-contents.com)
5 KiB
0 ms
…desktop/66264.client.342f429….esnext.js
(cdn-static.farfetch-contents.com)
5 KiB
0 ms
…desktop/10210.client.b15253c….css
(cdn-static.farfetch-contents.com)
5 KiB
0 ms
…desktop/96451.client.6d7cba9….esnext.js
(cdn-static.farfetch-contents.com)
4 KiB
0 ms
…desktop/GdprBanner.client.e13a52e….esnext.js
(cdn-static.farfetch-contents.com)
4 KiB
0 ms
…desktop/42512.client.eb0746b….esnext.js
(cdn-static.farfetch-contents.com)
4 KiB
0 ms
…desktop/63834.client.555f284….esnext.js
(cdn-static.farfetch-contents.com)
4 KiB
0 ms
…desktop/44119.client.20f3f1b….esnext.js
(cdn-static.farfetch-contents.com)
4 KiB
0 ms
…desktop/57864.client.b68907d….esnext.js
(cdn-static.farfetch-contents.com)
4 KiB
0 ms
…desktop/71893.client.083370f….css
(cdn-static.farfetch-contents.com)
3 KiB
0 ms
…content/default.client.84f6fa3….css
(cdn-static.farfetch-contents.com)
3 KiB
0 ms
…desktop/49408.client.df2659a….esnext.js
(cdn-static.farfetch-contents.com)
3 KiB
0 ms
…js/cpuMonitor.v3.js
(cdn-static.farfetch-contents.com)
3 KiB
0 ms
…desktop/69071.client.e964274….css
(cdn-static.farfetch-contents.com)
2 KiB
0 ms
…desktop/7120.client.ab61886….esnext.js
(cdn-static.farfetch-contents.com)
1 KiB
0 ms
…desktop/77053.client.faa76a7….esnext.js
(cdn-static.farfetch-contents.com)
1 KiB
0 ms
…js/setRUMUse….v1.js
(cdn-static.farfetch-contents.com)
1 KiB
0 ms
…js/eventManager.min.js
(cdn-static.farfetch-contents.com)
1 KiB
0 ms
…desktop/32381.client.4553644….esnext.js
(cdn-static.farfetch-contents.com)
1 KiB
0 ms
…desktop/90019.client.ea20398….esnext.js
(cdn-static.farfetch-contents.com)
1 KiB
0 ms
…desktop/27762.client.90582b5….esnext.js
(cdn-static.farfetch-contents.com)
1 KiB
0 ms
…desktop/26877.client.d2cbfdd….css
(cdn-static.farfetch-contents.com)
1 KiB
0 ms
mPulse
analytics
50 KiB
0 ms
50 KiB
0 ms
/api/config.json?key=…
(c.go-mpulse.net)
0 KiB
0 ms
Forter
utility
175 KiB
0 ms
…0c0275c12bca/script.js
(0c0275c12bca.cdn4.forter.com)
173 KiB
0 ms
…9d0398e…/wpt.json
(cdn0.forter.com)
1 KiB
0 ms
0 KiB
0 ms
0 KiB
0 ms
0 KiB
0 ms
/prop.json
(9d0398ed763740c38afb536d290e466f-0c0275c12bca.cdn.forter.com)
0 KiB
0 ms
/events
(cdn3.forter.com)
0 KiB
0 ms
Other Google APIs/SDKs
utility
87 KiB
0 ms
/gsi/client
(accounts.google.com)
86 KiB
0 ms
/gsi/style
(accounts.google.com)
1 KiB
0 ms
Google Analytics
analytics
23 KiB
0 ms
/analytics.js
(www.google-analytics.com)
21 KiB
0 ms
/j/collect?v=…
(www.google-analytics.com)
1 KiB
0 ms
/g/collect?v=…
(www.google-analytics.com)
1 KiB
0 ms
Riskified
utility
17 KiB
0 ms
15 KiB
0 ms
/v2/client_infos
(c.riskified.com)
1 KiB
0 ms
/img/image-l.gif?t=…
(img.riskified.com)
0 KiB
0 ms
/img/image-l.gif?t=…
(img.riskified.com)
0 KiB
0 ms
/img/image-l.gif?t=…
(img.riskified.com)
0 KiB
0 ms
/img/image-l.gif?t=…
(img.riskified.com)
0 KiB
0 ms
/img/image-l.gif?t=…
(img.riskified.com)
0 KiB
0 ms
Bing Ads
ad
17 KiB
0 ms
/bat.js
(bat.bing.com)
15 KiB
0 ms
/action/0?ti=…
(bat.bing.com)
1 KiB
0 ms
…action/4008469.js
(bat.bing.com)
1 KiB
0 ms
farfetch.net
16 KiB
0 ms
…marketing/trackings
(api.farfetch.net)
16 KiB
0 ms
Google/Doubleclick Ads
ad
2 KiB
0 ms
1 KiB
0 ms
1 KiB
0 ms
…conversion/992…?random=…
(pagead2.googlesyndication.com)
1 KiB
0 ms
/ccm/collect?en=…
(pagead2.googlesyndication.com)
0 KiB
0 ms
rum-ingress-coralogix.com
2 KiB
0 ms
…v1beta/logs
(ingress.eu2.rum-ingress-coralogix.com)
2 KiB
0 ms
cloudfront.net
0 KiB
0 ms
/events
(d2o5idwacg3gyw.cloudfront.net)
0 KiB
0 ms
Reduce unused JavaScript Potential savings of 631 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
ReactIf you are not server-side rendering, split your JavaScript bundles with React.lazy(). Otherwise, code-split using a third-party library such as loadable-components.
URL
Transfer Size
Potential Savings
Google Tag Manager
tag-manager
571.0 KiB
251.7 KiB
/gtag/destination?id=…
(www.googletagmanager.com)
94.9 KiB
58.2 KiB
/gtag/js?id=…
(www.googletagmanager.com)
136.0 KiB
53.6 KiB
/gtag/destination?id=…
(www.googletagmanager.com)
100.3 KiB
50.1 KiB
/gtm.js?id=GTM-5VWCDN
(www.googletagmanager.com)
150.0 KiB
45.9 KiB
/gtag/destination?id=…
(www.googletagmanager.com)
89.7 KiB
43.9 KiB
farfetch-contents.com
473.1 KiB
223.1 KiB
…sdks/coralogix-browser-sdk-1.4.6.js
(cdn-static.farfetch-contents.com)
138.4 KiB
85.3 KiB
…desktop/10210.client.6874aa1….esnext.js
(cdn-static.farfetch-contents.com)
227.5 KiB
80.3 KiB
…desktop/83627.client.9d013c5….esnext.js
(cdn-static.farfetch-contents.com)
36.8 KiB
29.5 KiB
…desktop/55438.client.4193610….esnext.js
(cdn-static.farfetch-contents.com)
70.5 KiB
28.0 KiB
Other Google APIs/SDKs
utility
85.0 KiB
63.3 KiB
/gsi/client
(accounts.google.com)
85.0 KiB
63.3 KiB
Forter
utility
172.0 KiB
61.5 KiB
…0c0275c12bca/script.js
(0c0275c12bca.cdn4.forter.com)
172.0 KiB
61.5 KiB
mPulse
analytics
49.1 KiB
31.9 KiB
49.1 KiB
31.9 KiB
Eliminate render-blocking resources Potential savings of 130 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles. Learn how to eliminate render-blocking resources.LCPFCP
URL
Transfer Size
Potential Savings
farfetch-contents.com
143.8 KiB
330 ms
…desktop/10210.client.b15253c….css
(cdn-static.farfetch-contents.com)
4.7 KiB
210 ms
…sdks/coralogix-browser-sdk-1.4.6.js
(cdn-static.farfetch-contents.com)
139.1 KiB
130 ms
Properly size images Potential savings of 605 KiB
Serve images that are appropriately-sized to save cellular data and improve load time. Learn how to size images.LCPFCP
URL
Resource Size
Potential Savings
farfetch-contents.com
940.6 KiB
605.5 KiB
2025-02-19_MW_WEBAPP_SHIRTS_PRE-S_MULTIBRAND_SHIRTS
<img data-component="Picture" alt="2025-02-19_MW_WEBAPP_SHIRTS_PRE-S_MULTIBRAND_SHIRTS" loading="lazy" class="emzgpi21 ltr-1i0wvsb">
673.0 KiB
424.2 KiB
t-shirt à motif Barocco en jacquard
<img alt="t-shirt à motif Barocco en jacquard" srcset="https://cdn-images.farfetch-contents.com/26/57/10/23/26571023_56846878_600…" loading="eager" sizes=" (max-width: 35.9375em) 480px, (min-width: 36em) and (max-width: 5…" width="300" height="400" data-component="ProductCardImageSecondary" data-testid="product-image" class="ltr-io0g65">
…23/26571023_56846878_600.jpg
(cdn-images.farfetch-contents.com)
68.9 KiB
56.6 KiB
2025-02-26_MW_WEBAPP_NEW SEASON_PRE-S_MULTIBRAND_MULTICATEGORY_IMG
<img alt="2025-02-26_MW_WEBAPP_NEW SEASON_PRE-S_MULTIBRAND_MULTICATEGORY_IMG" src="https://cdn-static.farfetch-contents.com/cms-ccloud/caas/v1/media/10405412…" loading="eager" data-component="Picture" class="_e38d27 emzgpi21 ltr-1i0wvsb" data-ffref="inspirationModule|10405434|3|02/26/2025 08:50:26|10405412|2|02/26/2025 08:…">
65.3 KiB
37.8 KiB
2025-02-05_MW_WEBAPP_SHIRTS_PRE-S_MULTIBRAND_SHIRTS_IMG
<img data-component="Picture" alt="2025-02-05_MW_WEBAPP_SHIRTS_PRE-S_MULTIBRAND_SHIRTS_IMG" loading="lazy" class="emzgpi21 ltr-1i0wvsb">
53.3 KiB
33.6 KiB
2025-02-05_MW_WEBAPP_PRADA_PRE-S_PRADA_MULTICATEGORY_img
<img data-component="Picture" alt="2025-02-05_MW_WEBAPP_PRADA_PRE-S_PRADA_MULTICATEGORY_img" loading="lazy" class="emzgpi21 ltr-1i0wvsb">
36.9 KiB
23.3 KiB
2025-02-05_MW_WEBAPP_PRADA_PRE-S_PRADA_MULTICATEGORY_IMG
<img data-component="Picture" alt="2025-02-05_MW_WEBAPP_PRADA_PRE-S_PRADA_MULTICATEGORY_IMG" loading="lazy" class="emzgpi21 ltr-1i0wvsb">
28.2 KiB
17.8 KiB
pantalon Timeo
<img alt="pantalon Timeo" srcset="https://cdn-images.farfetch-contents.com/26/93/04/02/26930402_58209728_600…" loading="eager" sizes=" (max-width: 35.9375em) 480px, (min-width: 36em) and (max-width: 5…" width="300" height="400" data-component="ProductCardImageSecondary" data-testid="product-image" class="ltr-io0g65">
…02/26930402_58209728_600.jpg
(cdn-images.farfetch-contents.com)
14.9 KiB
12.3 KiB
Serve images in next-gen formats Potential savings of 776 KiB
Image formats like WebP and AVIF often provide better compression than PNG or JPEG, which means faster downloads and less data consumption. Learn more about modern image formats.LCPFCP
URL
Resource Size
Potential Savings
farfetch-contents.com
856.8 KiB
715.2 KiB
2025-02-19_MW_WEBAPP_SHIRTS_PRE-S_MULTIBRAND_SHIRTS
<img data-component="Picture" alt="2025-02-19_MW_WEBAPP_SHIRTS_PRE-S_MULTIBRAND_SHIRTS" loading="lazy" class="emzgpi21 ltr-1i0wvsb">
673.0 KiB
644.4 KiB
2025-02-26_MW_WEBAPP_NEW SEASON_PRE-S_MULTIBRAND_MULTICATEGORY_IMG
<img alt="2025-02-26_MW_WEBAPP_NEW SEASON_PRE-S_MULTIBRAND_MULTICATEGORY_IMG" src="https://cdn-static.farfetch-contents.com/cms-ccloud/caas/v1/media/10405412…" loading="eager" data-component="Picture" class="_e38d27 emzgpi21 ltr-1i0wvsb" data-ffref="inspirationModule|10405434|3|02/26/2025 08:50:26|10405412|2|02/26/2025 08:…">
65.3 KiB
28.0 KiB
2025-02-05_MW_WEBAPP_SHIRTS_PRE-S_MULTIBRAND_SHIRTS_IMG
<img data-component="Picture" alt="2025-02-05_MW_WEBAPP_SHIRTS_PRE-S_MULTIBRAND_SHIRTS_IMG" loading="lazy" class="emzgpi21 ltr-1i0wvsb">
53.3 KiB
17.6 KiB
2025-02-05_MW_WEBAPP_PRADA_PRE-S_PRADA_MULTICATEGORY_img
<img data-component="Picture" alt="2025-02-05_MW_WEBAPP_PRADA_PRE-S_PRADA_MULTICATEGORY_img" loading="lazy" class="emzgpi21 ltr-1i0wvsb">
36.9 KiB
13.7 KiB
2025-02-05_MW_WEBAPP_PRADA_PRE-S_PRADA_MULTICATEGORY_IMG
<img data-component="Picture" alt="2025-02-05_MW_WEBAPP_PRADA_PRE-S_PRADA_MULTICATEGORY_IMG" loading="lazy" class="emzgpi21 ltr-1i0wvsb">
28.2 KiB
11.5 KiB
Unattributable
64.3 KiB
61.3 KiB
64.3 KiB
61.3 KiB
Avoid an excessive DOM size 1,700 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
ReactConsider using a "windowing" library like react-window to minimize the number of DOM nodes created if you are rendering many repeated elements on the page. Learn more. Also, minimize unnecessary re-renders using shouldComponentUpdate, PureComponent, or React.memo and skip effects only until certain dependencies have changed if you are using the Effect hook to improve runtime performance.
Statistic
Element
Value
Total DOM Elements
1,700
Maximum DOM Depth
div._d976b5 > div.ltr-1oxxr28 > picture.ltr-1fuafqq > source
<source media="(min-width: 1800px)" srcset="https://cdn-static.farfetch-contents.com/cms-ccloud/caas/v1/media/10396612…">
15
Maximum Child Elements
body.bob > div#root > svg.ltr-53y788
<svg class="ltr-53y788" data-testid="sprite" aria-hidden="true" focusable="false" xmlns="http://www.w3.org/2000/svg">
173
Serve static assets with an efficient cache policy 57 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more about efficient cache policies.
URL
Cache TTL
Transfer Size
farfetch-contents.com
1,709 KiB
…vitorino/vitorino.min.js
(cdn-static.farfetch-contents.com)
5m
5 KiB
15m
25 KiB
30d
674 KiB
…desktop/10210.client.6874aa1….esnext.js
(cdn-static.farfetch-contents.com)
30d
228 KiB
…sdks/coralogix-browser-sdk-1.4.6.js
(cdn-static.farfetch-contents.com)
30d
139 KiB
…desktop/55438.client.4193610….esnext.js
(cdn-static.farfetch-contents.com)
30d
71 KiB
30d
66 KiB
30d
54 KiB
…v2.00/FarfetchB….woff2
(cdn-static.farfetch-contents.com)
30d
50 KiB
…v2.00/FarfetchBasis-Bold.woff2
(cdn-static.farfetch-contents.com)
30d
49 KiB
…desktop/83627.client.9d013c5….esnext.js
(cdn-static.farfetch-contents.com)
30d
37 KiB
30d
37 KiB
…v2.00/NimbusSan….woff2
(cdn-static.farfetch-contents.com)
30d
34 KiB
30d
29 KiB
…desktop/74873.client.31b77ef….esnext.js
(cdn-static.farfetch-contents.com)
30d
29 KiB
…desktop/803.client.8138d91….esnext.js
(cdn-static.farfetch-contents.com)
30d
27 KiB
…desktop/89706.client.73bdaae….esnext.js
(cdn-static.farfetch-contents.com)
30d
17 KiB
…desktop/63309.client.432c8dd….esnext.js
(cdn-static.farfetch-contents.com)
30d
15 KiB
…desktop/runtime.client.f3273a0….esnext.js
(cdn-static.farfetch-contents.com)
30d
12 KiB
…content/default.client.832b49e….esnext.js
(cdn-static.farfetch-contents.com)
30d
10 KiB
…desktop/47577.client.40dce4a….esnext.js
(cdn-static.farfetch-contents.com)
30d
9 KiB
…desktop/57333.client.cf211d6….esnext.js
(cdn-static.farfetch-contents.com)
30d
9 KiB
…desktop/97581.client.06aa5b6….esnext.js
(cdn-static.farfetch-contents.com)
30d
6 KiB
…desktop/71893.client.8033605….esnext.js
(cdn-static.farfetch-contents.com)
30d
6 KiB
…desktop/64738.client.3a90818….esnext.js
(cdn-static.farfetch-contents.com)
30d
5 KiB
…desktop/78626.client.b9cbbc5….esnext.js
(cdn-static.farfetch-contents.com)
30d
5 KiB
…desktop/2316.client.8b33843….esnext.js
(cdn-static.farfetch-contents.com)
30d
5 KiB
…desktop/66264.client.342f429….esnext.js
(cdn-static.farfetch-contents.com)
30d
5 KiB
…desktop/10210.client.b15253c….css
(cdn-static.farfetch-contents.com)
30d
5 KiB
…desktop/96451.client.6d7cba9….esnext.js
(cdn-static.farfetch-contents.com)
30d
4 KiB
…desktop/GdprBanner.client.e13a52e….esnext.js
(cdn-static.farfetch-contents.com)
30d
4 KiB
…desktop/42512.client.eb0746b….esnext.js
(cdn-static.farfetch-contents.com)
30d
4 KiB
…desktop/63834.client.555f284….esnext.js
(cdn-static.farfetch-contents.com)
30d
4 KiB
…desktop/44119.client.20f3f1b….esnext.js
(cdn-static.farfetch-contents.com)
30d
4 KiB
…desktop/57864.client.b68907d….esnext.js
(cdn-static.farfetch-contents.com)
30d
4 KiB
…desktop/71893.client.083370f….css
(cdn-static.farfetch-contents.com)
30d
3 KiB
…content/default.client.84f6fa3….css
(cdn-static.farfetch-contents.com)
30d
3 KiB
…desktop/49408.client.df2659a….esnext.js
(cdn-static.farfetch-contents.com)
30d
3 KiB
…js/cpuMonitor.v3.js
(cdn-static.farfetch-contents.com)
30d
3 KiB
…desktop/69071.client.e964274….css
(cdn-static.farfetch-contents.com)
30d
2 KiB
…desktop/7120.client.ab61886….esnext.js
(cdn-static.farfetch-contents.com)
30d
1 KiB
…desktop/77053.client.faa76a7….esnext.js
(cdn-static.farfetch-contents.com)
30d
1 KiB
…js/setRUMUse….v1.js
(cdn-static.farfetch-contents.com)
30d
1 KiB
…js/eventManager.min.js
(cdn-static.farfetch-contents.com)
30d
1 KiB
…desktop/32381.client.4553644….esnext.js
(cdn-static.farfetch-contents.com)
30d
1 KiB
…desktop/90019.client.ea20398….esnext.js
(cdn-static.farfetch-contents.com)
30d
1 KiB
…desktop/27762.client.90582b5….esnext.js
(cdn-static.farfetch-contents.com)
30d
1 KiB
…desktop/26877.client.d2cbfdd….css
(cdn-static.farfetch-contents.com)
30d
1 KiB
farfetch.com
1st party
111 KiB
…FhcGb/CJxVQQB
(www.farfetch.com)
6h
111 KiB
mPulse
analytics
50 KiB
7d
50 KiB
Google Analytics
analytics
21 KiB
/analytics.js
(www.google-analytics.com)
2h
21 KiB
Riskified
utility
16 KiB
/img/image-l.gif?t=…
(img.riskified.com)
None
0 KiB
/img/image-l.gif?t=…
(img.riskified.com)
None
0 KiB
/img/image-l.gif?t=…
(img.riskified.com)
None
0 KiB
/img/image-l.gif?t=…
(img.riskified.com)
None
0 KiB
/img/image-l.gif?t=…
(img.riskified.com)
None
0 KiB
10m
15 KiB
Avoid serving legacy JavaScript to modern browsers Potential savings of 16 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. However, many aren't necessary for modern browsers. For your bundled JavaScript, adopt a modern script deployment strategy using module/nomodule feature detection to reduce the amount of code shipped to modern browsers, while retaining support for legacy browsers. Learn how to use modern JavaScriptLCPFCP
URL
Potential Savings
farfetch-contents.com
16.4 KiB
…sdks/coralogix-browser-sdk-1.4.6.js
(cdn-static.farfetch-contents.com)
8.5 KiB
…sdks/coralogix-browser-sdk-1.4.6.js:1:317437
(cdn-static.farfetch-contents.com)
Array.from
…desktop/89706.client.73bdaae….esnext.js
(cdn-static.farfetch-contents.com)
7.7 KiB
Array.isArray
…desktop/10210.client.6874aa1….esnext.js
(cdn-static.farfetch-contents.com)
0.1 KiB
@babel/plugin-transform-classes
…desktop/55438.client.4193610….esnext.js
(cdn-static.farfetch-contents.com)
0.0 KiB
@babel/plugin-transform-classes
Avoid 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().
Source
farfetch.com
1st party
…men/items.aspx:92:1215
(www.farfetch.com)
Avoid enormous network payloads Total size was 3,113 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
farfetch-contents.com
1,040.9 KiB
673.6 KiB
…desktop/10210.client.6874aa1….esnext.js
(cdn-static.farfetch-contents.com)
228.2 KiB
…sdks/coralogix-browser-sdk-1.4.6.js
(cdn-static.farfetch-contents.com)
139.1 KiB
Google Tag Manager
tag-manager
485.6 KiB
/gtm.js?id=GTM-5VWCDN
(www.googletagmanager.com)
151.1 KiB
/gtag/js?id=…
(www.googletagmanager.com)
137.1 KiB
/gtag/destination?id=…
(www.googletagmanager.com)
101.4 KiB
/gtag/destination?id=…
(www.googletagmanager.com)
96.0 KiB
farfetch.com
1st party
271.2 KiB
…men/items.aspx
(www.farfetch.com)
159.9 KiB
…FhcGb/CJxVQQB
(www.farfetch.com)
111.3 KiB
Forter
utility
172.8 KiB
…0c0275c12bca/script.js
(0c0275c12bca.cdn4.forter.com)
172.8 KiB
Avoid long main-thread tasks 12 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay. Learn how to avoid long main-thread tasksTBT
URL
Start Time
Duration
Google Tag Manager
tag-manager
1,182 ms
/gtm.js?id=GTM-5VWCDN
(www.googletagmanager.com)
2,293 ms
813 ms
/gtm.js?id=GTM-5VWCDN
(www.googletagmanager.com)
1,771 ms
124 ms
/gtag/js?id=…
(www.googletagmanager.com)
4,099 ms
109 ms
/gtm.js?id=GTM-5VWCDN
(www.googletagmanager.com)
3,506 ms
80 ms
/gtag/destination?id=…
(www.googletagmanager.com)
4,418 ms
56 ms
farfetch.com
1st party
420 ms
…FhcGb/CJxVQQB
(www.farfetch.com)
1,114 ms
279 ms
…FhcGb/CJxVQQB
(www.farfetch.com)
1,895 ms
85 ms
…men/items.aspx
(www.farfetch.com)
433 ms
56 ms
farfetch-contents.com
317 ms
…desktop/57333.client.cf211d6….esnext.js
(cdn-static.farfetch-contents.com)
1,998 ms
133 ms
…vitorino/vitorino.min.js
(cdn-static.farfetch-contents.com)
3,273 ms
106 ms
…sdks/coralogix-browser-sdk-1.4.6.js
(cdn-static.farfetch-contents.com)
987 ms
78 ms
Unattributable
157 ms
Unattributable
617 ms
157 ms
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
ReactIf you are server-side rendering any React components, consider using renderToPipeableStream() or renderToStaticNodeStream() to allow the client to receive and hydrate different parts of the markup instead of all at once. Learn more.
URL
Time Spent
farfetch.com
1st party
550 ms
…men/items.aspx
(www.farfetch.com)
550 ms
User Timing marks and measures 14 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.
ReactUse the React DevTools Profiler, which makes use of the Profiler API, to measure the rendering performance of your components. Learn more.
Name
Type
Start Time
Duration
TL Getting uv marker
Measure
2,524.09 ms
947.04 ms
TL Creating SDKs marker
Measure
3,471.27 ms
1.56 ms
TL Queues marker
Measure
3,473.04 ms
6.83 ms
TL Window obj marker
Measure
3,479.96 ms
3.73 ms
TL - Start Bootstrap
Mark
2,523.49 ms
TL - Start getting uv
Mark
2,524.09 ms
TL - End getting uv
Mark
3,471.13 ms
TL - Start creating sdks
Mark
3,471.27 ms
TL - End creating sdks
Mark
3,472.83 ms
TL - End Bootstrap
Mark
3,472.95 ms
TL - Start creating queues
Mark
3,473.04 ms
TL - End creating queues
Mark
3,479.87 ms
TL - Start filling window obj
Mark
3,479.96 ms
TL - End filling window obj
Mark
3,483.69 ms
Avoid large layout shifts 1 layout shift found
These are the largest layout shifts observed on the page. Each table item represents a single layout shift, and shows the element that shifted the most. Below each item are possible root causes that led to the layout shift. Some of these layout shifts may not be included in the CLS metric value due to windowing. Learn how to improve CLSCLS
Element
Layout shift score
0.000
…FhcGb/CJxVQQB
(www.farfetch.com)
A late network request adjusted the page layout
…desktop/71893.client.083370f….css
(cdn-static.farfetch-contents.com)
A late network request adjusted the page layout
…js/cpuMonitor.v3.js
(cdn-static.farfetch-contents.com)
A late network request adjusted the page layout
…js/eventManager.min.js
(cdn-static.farfetch-contents.com)
A late network request adjusted the page layout
…js/setRUMUse….v1.js
(cdn-static.farfetch-contents.com)
A late network request adjusted the page layout
Avoid chaining critical requests 34 chains found
The Critical Request Chains below show you what resources are loaded with a high priority. Consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load. Learn how to avoid chaining critical requests.
Maximum critical path latency: 2,080.85 ms
Initial Navigation
…men/items.aspx
(www.farfetch.com)
…js/eventManager.min.js
(cdn-static.farfetch-contents.com)
- 331.499 ms, 0.88 KiB
…desktop/runtime.client.f3273a0….esnext.js
(cdn-static.farfetch-contents.com)
- 197.626 ms, 12.19 KiB
…desktop/10210.client.6874aa1….esnext.js
(cdn-static.farfetch-contents.com)
- 271.801 ms, 228.18 KiB
…desktop/83627.client.9d013c5….esnext.js
(cdn-static.farfetch-contents.com)
- 170.93 ms, 37.50 KiB
…desktop/57333.client.cf211d6….esnext.js
(cdn-static.farfetch-contents.com)
- 351.824 ms, 8.78 KiB
…desktop/2316.client.8b33843….esnext.js
(cdn-static.farfetch-contents.com)
- 258.595 ms, 5.10 KiB
…desktop/64738.client.3a90818….esnext.js
(cdn-static.farfetch-contents.com)
- 150.088 ms, 5.33 KiB
…desktop/42512.client.eb0746b….esnext.js
(cdn-static.farfetch-contents.com)
- 259.015 ms, 4.19 KiB
…desktop/89706.client.73bdaae….esnext.js
(cdn-static.farfetch-contents.com)
- 212.023 ms, 16.93 KiB
…desktop/55438.client.4193610….esnext.js
(cdn-static.farfetch-contents.com)
- 193.552 ms, 71.16 KiB
…desktop/10210.client.b15253c….css
(cdn-static.farfetch-contents.com)
- 184.729 ms, 4.68 KiB
…desktop/78626.client.b9cbbc5….esnext.js
(cdn-static.farfetch-contents.com)
- 264.203 ms, 5.17 KiB
…desktop/97581.client.06aa5b6….esnext.js
(cdn-static.farfetch-contents.com)
- 223.78 ms, 6.44 KiB
…desktop/44119.client.20f3f1b….esnext.js
(cdn-static.farfetch-contents.com)
- 263.344 ms, 4.08 KiB
…desktop/74873.client.31b77ef….esnext.js
(cdn-static.farfetch-contents.com)
- 423.93 ms, 28.60 KiB
…desktop/96451.client.6d7cba9….esnext.js
(cdn-static.farfetch-contents.com)
- 262.462 ms, 4.44 KiB
…desktop/63309.client.432c8dd….esnext.js
(cdn-static.farfetch-contents.com)
- 373.96 ms, 14.60 KiB
…desktop/49408.client.df2659a….esnext.js
(cdn-static.farfetch-contents.com)
- 168.663 ms, 2.82 KiB
…desktop/63834.client.555f284….esnext.js
(cdn-static.farfetch-contents.com)
- 200.443 ms, 4.18 KiB
…desktop/57864.client.b68907d….esnext.js
(cdn-static.farfetch-contents.com)
- 169.004 ms, 3.70 KiB
…desktop/66264.client.342f429….esnext.js
(cdn-static.farfetch-contents.com)
- 172.516 ms, 4.76 KiB
…content/default.client.84f6fa3….css
(cdn-static.farfetch-contents.com)
- 193.758 ms, 3.21 KiB
…desktop/803.client.8138d91….esnext.js
(cdn-static.farfetch-contents.com)
- 262.743 ms, 26.63 KiB
…content/default.client.832b49e….esnext.js
(cdn-static.farfetch-contents.com)
- 191.812 ms, 10.42 KiB
…FhcGb/CJxVQQB
(www.farfetch.com)
- 210.346 ms, 111.32 KiB
…desktop/71893.client.083370f….css
(cdn-static.farfetch-contents.com)
- 496.463 ms, 3.29 KiB
…desktop/26877.client.d2cbfdd….css
(cdn-static.farfetch-contents.com)
- 252.747 ms, 0.73 KiB
…desktop/69071.client.e964274….css
(cdn-static.farfetch-contents.com)
- 174.038 ms, 2.20 KiB
…sdks/coralogix-browser-sdk-1.4.6.js
(cdn-static.farfetch-contents.com)
- 264.817 ms, 139.10 KiB
…v2.00/NimbusSan….woff2
(cdn-static.farfetch-contents.com)
- 50.775 ms, 33.59 KiB
…v2.00/FarfetchB….woff2
(cdn-static.farfetch-contents.com)
- 68.106 ms, 50.11 KiB
…v2.00/FarfetchBasis-Bold.woff2
(cdn-static.farfetch-contents.com)
- 43.457 ms, 48.97 KiB
…js/cpuMonitor.v3.js
(cdn-static.farfetch-contents.com)
- 349.402 ms, 2.76 KiB
…js/setRUMUse….v1.js
(cdn-static.farfetch-contents.com)
- 331.079 ms, 0.88 KiB
More information about the performance of your application. These numbers don't directly affect the Performance score.
Passed audits (19)
Show Hide
Defer offscreen images
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive. Learn how to defer offscreen images.LCPFCP
Minify CSS
Minifying CSS files can reduce network payload sizes. Learn how to minify CSS.LCPFCP
ReactIf your build system minifies CSS files automatically, ensure that you are deploying the production build of your application. You can check this with the React Developer Tools extension. Learn more.
Minify JavaScript
Minifying JavaScript files can reduce payload sizes and script parse time. Learn how to minify JavaScript.LCPFCP
ReactIf your build system minifies JS files automatically, ensure that you are deploying the production build of your application. You can check this with the React Developer Tools extension. Learn more.
Reduce unused CSS
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
Efficiently encode images
Optimized images load faster and consume less cellular data. Learn how to efficiently encode images.LCPFCP
Enable text compression
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. Learn more about text compression.LCPFCP
Preconnect to required origins
Warnings:
  • A `<link rel=preconnect>` was found for "https://dd6zx4ibq538k.cloudfront.net" but was not used by the browser. Only use `preconnect` for important origins that the page will certainly request.
  • A `<link rel=preconnect>` was found for "https://securepubads.g.doubleclick.net" but was not used by the browser. Only use `preconnect` for important origins that the page will certainly request.
  • A `<link rel=preconnect>` was found for "https://c.bannerflow.net" but was not used by the browser. Only use `preconnect` for important origins that the page will certainly request.
  • A `<link rel=preconnect>` was found for "https://adservice.google.com" but was not used by the browser. Only use `preconnect` for important origins that the page will certainly request.
  • More than 2 `<link rel=preconnect>` connections were found. These should be used sparingly and only to the most important origins.
Consider adding preconnect or dns-prefetch resource hints to establish early connections to important third-party origins. Learn how to preconnect to required origins.LCPFCP
Avoid multiple page redirects
Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.LCPFCP
ReactIf you are using React Router, minimize usage of the <Redirect> component for route navigations.
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
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 element
This is the largest contentful element painted within the viewport. Learn more about the Largest Contentful Paint elementLCP
Largest Contentful Paint image was not lazily loaded
Above-the-fold images that are lazily loaded render later in the page lifecycle, which can delay the largest contentful paint. Learn more about optimal lazy loading.LCP
Uses passive listeners to improve scrolling performance
Consider marking your touch and wheel event listeners as passive to improve your page's scroll performance. Learn more about adopting passive event listeners.
Avoid non-composited animations
Animations which are not composited can be janky and increase CLS. Learn how to avoid non-composited animationsCLS
Image elements have explicit width and height
Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensionsCLS
Has a <meta name="viewport"> tag with width or initial-scale
A <meta name="viewport"> not only optimizes your app for mobile screen sizes, but also prevents a 300 millisecond delay to user input. Learn more about using the viewport meta tag.
These checks highlight opportunities to improve the accessibility of your web app. Automatic detection can only detect a subset of issues and does not guarantee the accessibility of your web app, so manual testing is also encouraged.
Best practices
Touch targets do not have sufficient size or spacing.
Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.
Failing Elements
Promotions
<a tabindex="0" aria-expanded="false" aria-controls="meganav" role="button" data-ffref="hd_mnav" data-nav="Sale" href="/fr/shopping/men/sale/all/items.aspx" data-component="NavBarItemLink" class="ltr-k0ippd e13n4l871">
Aller au début du Meganav.
<button aria-label="Aller au début du Meganav." flow="next" aria-disabled="false" data-component="NavArrow" class="ltr-1tcgfu6" data-loading="false">
These items highlight common accessibility best practices.
Additional items to manually check (10)
Show Hide
Interactive controls are keyboard focusable
Custom interactive controls are keyboard focusable and display a focus indicator. Learn how to make custom controls focusable.
Interactive elements indicate their purpose and state
Interactive elements, such as links and buttons, should indicate their state and be distinguishable from non-interactive elements. Learn how to decorate interactive elements with affordance hints.
The page has a logical tab order
Tabbing through the page follows the visual layout. Users cannot focus elements that are offscreen. Learn more about logical tab ordering.
Visual order on the page follows DOM order
DOM order matches the visual order, improving navigation for assistive technology. Learn more about DOM and visual ordering.
User focus is not accidentally trapped in a region
A user can tab into and out of any control or region without accidentally trapping their focus. Learn how to avoid focus traps.
The user's focus is directed to new content added to the page
If new content, such as a dialog, is added to the page, the user's focus is directed to it. Learn how to direct focus to new content.
HTML5 landmark elements are used to improve navigation
Landmark elements (<main>, <nav>, etc.) are used to improve the keyboard navigation of the page for assistive technology. Learn more about landmark elements.
Offscreen content is hidden from assistive technology
Offscreen content is hidden with display: none or aria-hidden=true. Learn how to properly hide offscreen content.
Custom controls have associated labels
Custom interactive controls have associated labels, provided by aria-label or aria-labelledby. Learn more about custom controls and labels.
Custom controls have ARIA roles
Custom interactive controls have appropriate ARIA roles. Learn how to add roles to custom controls.
These items address areas which an automated testing tool cannot cover. Learn more in our guide on conducting an accessibility review.
Passed audits (26)
Show Hide
[aria-*] attributes match their roles
Each ARIA role supports a specific subset of aria-* attributes. Mismatching these invalidates the aria-* attributes. Learn how to match ARIA attributes to their roles.
[aria-hidden="true"] is not present on the document <body>
Assistive technologies, like screen readers, work inconsistently when aria-hidden="true" is set on the document <body>. Learn how aria-hidden affects the document body.
[role]s have all required [aria-*] attributes
Some ARIA roles have required attributes that describe the state of the element to screen readers. Learn more about roles and required attributes.
[aria-*] attributes have valid values
Assistive technologies, like screen readers, can't interpret ARIA attributes with invalid values. Learn more about valid values for ARIA attributes.
[aria-*] attributes are valid and not misspelled
Assistive technologies, like screen readers, can't interpret ARIA attributes with invalid names. Learn more about valid ARIA attributes.
Buttons have an accessible name
When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.
Image elements have [alt] attributes
Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the alt attribute.
[user-scalable="no"] is not used in the <meta name="viewport"> element and the [maximum-scale] attribute is not less than 5.
Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a web page. Learn more about the viewport meta tag.
ARIA attributes are used as specified for the element's role
Some ARIA attributes are only allowed on an element under certain conditions. Learn more about conditional ARIA attributes.
[aria-hidden="true"] elements do not contain focusable descendents
Focusable descendents within an [aria-hidden="true"] element prevent those interactive elements from being available to users of assistive technologies like screen readers. Learn how aria-hidden affects focusable elements.
Elements use only permitted ARIA attributes
Using ARIA attributes in roles where they are prohibited can mean that important information is not communicated to users of assistive technologies. Learn more about prohibited ARIA roles.
[role] values are valid
ARIA roles must have valid values in order to perform their intended accessibility functions. Learn more about valid ARIA roles.
Background and foreground colors have a sufficient contrast ratio
Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.
Document has a <title> element
The title gives screen reader users an overview of the page, and search engine users rely on it heavily to determine if a page is relevant to their search. Learn more about document titles.
<html> element has a [lang] attribute
If a page doesn't specify a lang attribute, a screen reader assumes that the page is in the default language that the user chose when setting up the screen reader. If the page isn't actually in the default language, then the screen reader might not announce the page's text correctly. Learn more about the lang attribute.
<html> element has a valid value for its [lang] attribute
Specifying a valid BCP 47 language helps screen readers announce text properly. Learn how to use the lang attribute.
Form elements have associated labels
Labels ensure that form controls are announced properly by assistive technologies, like screen readers. Learn more about form element labels.
Lists contain only <li> elements and script supporting elements (<script> and <template>).
Screen readers have a specific way of announcing lists. Ensuring proper list structure aids screen reader output. Learn more about proper list structure.
List items (<li>) are contained within <ul>, <ol> or <menu> parent elements
Screen readers require list items (<li>) to be contained within a parent <ul>, <ol> or <menu> to be announced properly. Learn more about proper list structure.
No element has a [tabindex] value greater than 0
A value greater than 0 implies an explicit navigation ordering. Although technically valid, this often creates frustrating experiences for users who rely on assistive technologies. Learn more about the tabindex attribute.
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 (30)
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.
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 input fields have accessible names
When an input field doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn more about input field labels.
ARIA meter elements have accessible names
When a meter element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn how to name meter elements.
ARIA progressbar elements have accessible names
When a progressbar element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn how to label progressbar elements.
Elements with an ARIA [role] that require children to contain a specific [role] have all required children.
Some ARIA parent roles must contain specific child roles to perform their intended accessibility functions. Learn more about roles and required children elements.
[role]s are contained by their required parent element
Some ARIA child roles must be contained by specific parent roles to properly perform their intended accessibility functions. Learn more about ARIA roles and required parent element.
Elements with the role=text attribute do not have focusable descendents.
Adding role=text around a text node split by markup enables VoiceOver to treat it as one phrase, but the element's focusable descendents will not be announced. Learn more about the role=text attribute.
ARIA toggle fields have accessible names
When a toggle field doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn more about toggle fields.
ARIA tooltip elements have accessible names
When a tooltip element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn how to name tooltip elements.
ARIA treeitem elements have accessible names
When a treeitem element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn more about labeling treeitem elements.
The page contains a heading, skip link, or landmark region
Adding ways to bypass repetitive content lets keyboard users navigate the page more efficiently. Learn more about bypass blocks.
<dl>'s contain only properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements.
When definition lists are not properly marked up, screen readers may produce confusing or inaccurate output. Learn how to structure definition lists correctly.
Definition list items are wrapped in <dl> elements
Definition list items (<dt> and <dd>) must be wrapped in a parent <dl> element to ensure that screen readers can properly announce them. Learn how to structure definition lists correctly.
ARIA IDs are unique
The value of an ARIA ID must be unique to prevent other instances from being overlooked by assistive technologies. Learn how to fix duplicate ARIA IDs.
No form fields have multiple labels
Form fields with multiple labels can be confusingly announced by assistive technologies like screen readers which use either the first, the last, or all of the labels. Learn how to use form labels.
<frame> or <iframe> elements have a title
Screen reader users rely on frame titles to describe the contents of frames. Learn more about frame titles.
<html> element has an [xml:lang] attribute with the same base language as the [lang] attribute.
If the webpage does not specify a consistent language, then the screen reader might not announce the page's text correctly. Learn more about the lang attribute.
Input buttons have discernible text.
Adding discernable and accessible text to input buttons may help screen reader users understand the purpose of the input button. Learn more about input buttons.
<input type="image"> elements have [alt] text
When an image is being used as an <input> button, providing alternative text can help screen reader users understand the purpose of the button. Learn about input image alt text.
The document does not use <meta http-equiv="refresh">
Users do not expect a page to refresh automatically, and doing so will move focus back to the top of the page. This may create a frustrating or confusing experience. Learn more about the refresh meta tag.
<object> elements have alternate text
Screen readers cannot translate non-text content. Adding alternate text to <object> elements helps screen readers convey meaning to users. Learn more about alt text for object elements.
Select elements have associated label elements.
Form elements without effective labels can create frustrating experiences for screen reader users. Learn more about the select element.
Tables have different content in the summary attribute and <caption>.
The summary attribute should describe the table structure, while <caption> should have the onscreen title. Accurate table mark-up helps users of screen readers. Learn more about summary and caption.
Cells in a <table> element that use the [headers] attribute refer to table cells within the same table.
Screen readers have features to make navigating tables easier. Ensuring <td> cells using the [headers] attribute only refer to other cells in the same table may improve the experience for screen reader users. Learn more about the headers attribute.
<th> elements and elements with [role="columnheader"/"rowheader"] have data cells they describe.
Screen readers have features to make navigating tables easier. Ensuring table headers always refer to some set of cells may improve the experience for screen reader users. Learn more about table headers.
[lang] attributes have a valid value
Specifying a valid BCP 47 language on elements helps ensure that text is pronounced correctly by a screen reader. Learn how to use the lang attribute.
<video> elements contain a <track> element with [kind="captions"]
When a video provides a caption it is easier for deaf and hearing impaired users to access its information. Learn more about video captions.
General
Uses deprecated APIs 1 warning found
Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs.
Deprecation / Warning
Source
mPulse
analytics
UnloadHandler
Browser errors were logged to the console
Errors logged to the console indicate unresolved problems. They can come from network request failures and other browser concerns. Learn more about this errors in console diagnostic audit
Source
Description
farfetch-contents.com
…sdks/coralogix-browser-sdk-1.4.6.js:1:141221
(cdn-static.farfetch-contents.com)
[GSI_LOGGER]: FedCM get() rejects with NetworkError: Error retrieving a token.
farfetch.com
1st party
…men/items.aspx:1:0
(www.farfetch.com)
Refused to execute script from 'https://pagead2.googlesyndication.com/pagead/conversion/992356468/?random=1740903475061&cv=11&fst=1740903475061&bg=ffffff&guid=ON&async=1&gtm=45be52q0v871604564z872394093za201zb887643346&gcs=G101&gcd=13q3r3q3q5l1&dma_cps=-&dma=0&tag_exp=101732279~101732281~102067808~102482433~102539968~102558064~102587591~102605417~102640600~102658453~102717422~102732003&u_w=800&u_h=600&url=https%3A%2F%2Fwww.farfetch.com%2Ffr%2Fshopping%2Fmen%2Fitems.aspx&label=hCbTCPPi3a8BEPTQmNkD&hn=www.googleadservices.com&frm=0&tiba=V%C3%AAtements%20de%20cr%C3%A9ateur%20pour%20homme%20%7C%20FARFETCH%20France&value=0&bttype=purchase&npa=1&pscdl=denied&_tu=Cg&uaa=x86&uab=64&uafvl=Not(A%253ABrand%3B99.0.0.0%7CHeadlessChrome%3B133.0.6943.126%7CChromium%3B133.0.6943.126&uamb=0&uam=&uap=macOS&uapv=10.15.7&uaw=0&fdr=Cw&rfmt=3&fmt=4' because its MIME type ('text/html') is not executable, and strict MIME type checking is enabled.
…men/items.aspx:1:0
(www.farfetch.com)
The fetch of the config file resulted in a network error: ERR_NAME_NOT_RESOLVED
…men/items.aspx:1:0
(www.farfetch.com)
The provider's FedCM config file fetch resulted in an error response code.
Detected JavaScript libraries
All front-end JavaScript libraries detected on the page. Learn more about this JavaScript library detection diagnostic audit.
Name
Version
React
boomerang.js
1.720.0
core-js
core-js-global@3.32.0
Trust and Safety
Ensure CSP is effective against XSS attacks
A strong Content Security Policy (CSP) significantly reduces the risk of cross-site scripting (XSS) attacks. Learn how to use a CSP to prevent XSS
Description
Directive
Severity
`script-src` directive is missing. This can allow the execution of unsafe scripts.
script-src
High
Missing `object-src` allows the injection of plugins that execute unsafe scripts. Consider setting `object-src` to `'none'` if you can.
object-src
High
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 third-party cookies
Chrome is moving towards a new experience that allows users to choose to browse without third-party cookies. Learn more about third-party cookies.
Allows users to paste into input fields
Preventing input pasting is a bad practice for the UX, and weakens security by blocking password managers.Learn more about user-friendly input fields.
Avoids requesting the geolocation permission on page load
Users are mistrustful of or confused by sites that request their location without context. Consider tying the request to a user action instead. Learn more about the geolocation permission.
Avoids requesting the notification permission on page load
Users are mistrustful of or confused by sites that request to send notifications without context. Consider tying the request to user gestures instead. Learn more about responsibly getting permission for notifications.
Displays images with correct aspect ratio
Image display dimensions should match natural aspect ratio. Learn more about image aspect ratio.
Serves images with appropriate resolution
Image natural dimensions should be proportional to the display size and the pixel ratio to maximize image clarity. Learn how to provide responsive images.
Has a <meta name="viewport"> tag with width or initial-scale
A <meta name="viewport"> not only optimizes your app for mobile screen sizes, but also prevents a 300 millisecond delay to user input. Learn more about using the viewport meta tag.
Page has the HTML doctype
Specifying a doctype prevents the browser from switching to quirks-mode. Learn more about the doctype declaration.
Properly defines charset
A character encoding declaration is required. It can be done with a <meta> tag in the first 1024 bytes of the HTML or in the Content-Type HTTP response header. Learn more about declaring the character encoding.
No issues in the Issues panel in Chrome Devtools
Issues logged to the Issues panel in Chrome Devtools indicate unresolved problems. They can come from network request failures, insufficient security controls, and other browser concerns. Open up the Issues panel in Chrome DevTools for more details on each issue.
Page has valid source maps
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
farfetch-contents.com
SyntaxError: Unexpected token '/', "/*! For li"... is not valid JSON
Riskified
utility
…ZmFyZmV0Y2guY29t/ZjJhOTcxM…
(beacon.riskified.com)
Warning: missing 1 item in `.sourcesContent`
Forter
utility
…0c0275c12bca/script.js
(0c0275c12bca.cdn4.forter.com)
Could not resolve map url: https://cdn4.forter.com/map/suid/0c0275c12bca/15091766834
Not applicable (2)
Show Hide
Redirects HTTP traffic to HTTPS
Make sure that you redirect all HTTP traffic to HTTPS in order to enable secure web features for all your users. Learn more.
Document uses legible font sizes
Font sizes less than 12px are too small to be legible and require mobile visitors to “pinch to zoom” in order to read. Strive to have >60% of page text ≥12px. Learn more about legible font sizes.
These checks ensure that your page is following basic search engine optimization advice. There are many additional factors Lighthouse does not score here that may affect your search ranking, including performance on Core Web Vitals. Learn more about Google Search Essentials.
Additional items to manually check (1)
Show Hide
Structured data is valid
Run these additional validators on your site to check additional SEO best practices.
Passed audits (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 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.