PageSpeed Insights logo
PageSpeed Insights
PageSpeed Insights
This site uses cookies from Google to deliver its services and to analyze traffic.
Report from Feb 12, 2025, 6:00:52 PM
Discover what your real users are experiencing
Core Web Vitals Assessment: Failed
Largest Contentful Paint (LCP)
3.1 s
Page LoadsGood (≤ 2.5 s)67%Needs Improvement (2.5 s - 4 s)14%Poor (> 4 s)19%75th Percentile - 3.1 sCore Web Vital
Interaction to Next Paint (INP)
280 ms
Page LoadsGood (≤ 200 ms)64%Needs Improvement (200 ms - 500 ms)25%Poor (> 500 ms)11%75th Percentile - 280 msCore Web Vital
Cumulative Layout Shift (CLS)
0.36
Page LoadsGood (≤ 0.1)47%Needs Improvement (0.1 - 0.25)18%Poor (> 0.25)35%75th Percentile - 0.36Core Web Vital
Other Notable Metrics
First Contentful Paint (FCP)
2.9 s
Page LoadsGood (≤ 1.8 s)53%Needs Improvement (1.8 s - 3 s)23%Poor (> 3 s)24%75th Percentile - 2.9 s 
Time to First Byte (TTFB)
1.5 s
Page LoadsGood (≤ 0.8 s)42%Needs Improvement (0.8 s - 1.8 s)39%Poor (> 1.8 s)19%75th Percentile - 1.5 sExperimental
Latest 28-day collection period
Various mobile devicesMany samples (Chrome UX Report)Full visit durationsVarious network connectionsAll Chrome versions
Core Web Vitals Assessment: Failed
Largest Contentful Paint (LCP)
2.5 s
Page LoadsGood (≤ 2.5 s)74%Needs Improvement (2.5 s - 4 s)16%Poor (> 4 s)10%75th Percentile - 2.5 sCore Web Vital
Interaction to Next Paint (INP)
312 ms
Page LoadsGood (≤ 200 ms)59%Needs Improvement (200 ms - 500 ms)28%Poor (> 500 ms)14%75th Percentile - 312 msCore Web Vital
Cumulative Layout Shift (CLS)
0.09
Page LoadsGood (≤ 0.1)76%Needs Improvement (0.1 - 0.25)16%Poor (> 0.25)8%75th Percentile - 0.09Core Web Vital
Other Notable Metrics
First Contentful Paint (FCP)
2.2 s
Page LoadsGood (≤ 1.8 s)64%Needs Improvement (1.8 s - 3 s)23%Poor (> 3 s)13%75th Percentile - 2.2 s 
Time to First Byte (TTFB)
1.3 s
Page LoadsGood (≤ 0.8 s)37%Needs Improvement (0.8 s - 1.8 s)51%Poor (> 1.8 s)12%75th Percentile - 1.3 sExperimental
Latest 28-day collection period
Various mobile devicesMany samples (Chrome UX Report)Full visit durationsVarious network connectionsAll Chrome versions
Diagnose performance issues
13
Performance
100
Accessibility
79
Best Practices
100
SEO
13
Performance
100
Accessibility
79
Best Practices
100
SEO
13 FCP+1LCP+1TBT+4CLS+6SI+2 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.5 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
8.2 s
Largest Contentful Paint marks the time at which the largest text or image is painted. Learn more about the Largest Contentful Paint metric
Total Blocking Time
1,550 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.407
Cumulative Layout Shift measures the movement of visible elements within the viewport. Learn more about the Cumulative Layout Shift metric.
Speed Index
8.8 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more about the Speed Index metric.
  • Captured at Feb 12, 2025, 6:00 PM UTC
  • Emulated Moto G Power with Lighthouse 12.2.3
    Unthrottled CPU/Memory Power: 366 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 131.0.6778.264 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
Avoid large layout shifts 5 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
NE PERDEZ PAS LE FIL Abonnez-vous pour recevoir des promotions, des sélections…
<div class="ltr-47c8sr e11lms100">
0.332
…sdks/coralogix-browser-sdk-1.4.6.js
(cdn-static.farfetch-contents.com)
A late network request adjusted the page layout
…content/default.client.de5e4d9….css
(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
Choisissez une section MODE FEMME MODE HOMME MODE ENFANT PASSER COMMANDE V…
<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.027
Nous utilisons des cookies pour optimiser votre expérience utilisateur, vous pr…
<div data-testid="gdpr-banner-mobile" class="ltr-1bjxu8v em3ogft0">
0.018
MODE FEMME
<p class="_bdc4ef ltr-1ri59hw-Display" data-component="Display">
0.001
Reduce JavaScript execution time 5.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
2,601 ms
2,476 ms
45 ms
/gtm.js?id=GTM-5VWCDN
(www.googletagmanager.com)
2,165 ms
2,066 ms
21 ms
/gtag/js?id=…
(www.googletagmanager.com)
222 ms
212 ms
9 ms
/gtag/destination?id=…
(www.googletagmanager.com)
128 ms
119 ms
8 ms
/gtag/destination?id=…
(www.googletagmanager.com)
87 ms
79 ms
7 ms
farfetch.com
1st party
1,644 ms
1,319 ms
20 ms
…OwlZC/30ZUWk
(www.farfetch.com)
1,169 ms
1,157 ms
9 ms
/fr/
(www.farfetch.com)
387 ms
75 ms
11 ms
…UniversalVariable/GetUniversalVariableUserScript?pageType=…
(www.farfetch.com)
88 ms
87 ms
0 ms
farfetch-contents.com
919 ms
839 ms
17 ms
…mobile/27762.client.8895680….esnext.js
(cdn-static.farfetch-contents.com)
259 ms
259 ms
0 ms
…mobile/45762.client.6a3ab20….esnext.js
(cdn-static.farfetch-contents.com)
218 ms
204 ms
2 ms
…sdks/coralogix-browser-sdk-1.4.6.js
(cdn-static.farfetch-contents.com)
179 ms
153 ms
14 ms
…mobile/58288.client.fdab203….esnext.js
(cdn-static.farfetch-contents.com)
117 ms
113 ms
0 ms
…mobile/83217.client.3c13aee….esnext.js
(cdn-static.farfetch-contents.com)
77 ms
43 ms
1 ms
…mobile/32381.client.70e6329….esnext.js
(cdn-static.farfetch-contents.com)
70 ms
69 ms
0 ms
Unattributable
868 ms
204 ms
0 ms
Unattributable
499 ms
125 ms
0 ms
(program):2
369 ms
79 ms
0 ms
Forter
utility
272 ms
260 ms
10 ms
…0c0275c12bca/script.js
(0c0275c12bca.cdn4.forter.com)
272 ms
260 ms
10 ms
Riskified
utility
94 ms
89 ms
1 ms
/?shop=farfetch.com&sid=8331b891-b533-41a5-b553-8947ff76ef97
(beacon.riskified.com)
94 ms
89 ms
1 ms
Minimize main-thread work 6.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
5,442 ms
Other
483 ms
Garbage Collection
334 ms
Style & Layout
234 ms
Script Parsing & Compilation
119 ms
Parse HTML & CSS
54 ms
Rendering
45 ms
Reduce the impact of third-party code Third-party code blocked the main thread for 1,720 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
470 KiB
1,319 ms
/gtm.js?id=GTM-5VWCDN
(www.googletagmanager.com)
144 KiB
1,051 ms
/gtag/js?id=…
(www.googletagmanager.com)
134 KiB
167 ms
/gtag/destination?id=…
(www.googletagmanager.com)
101 KiB
66 ms
/gtag/destination?id=…
(www.googletagmanager.com)
88 KiB
35 ms
…5230/sw_iframe.html?origin=https%3A%2F%2Fwww.farfetch.com
(www.googletagmanager.com)
2 KiB
0 ms
/a?v=…
(www.googletagmanager.com)
1 KiB
0 ms
farfetch-contents.com
1,382 KiB
389 ms
…mobile/27762.client.8895680….esnext.js
(cdn-static.farfetch-contents.com)
1 KiB
209 ms
…sdks/coralogix-browser-sdk-1.4.6.js
(cdn-static.farfetch-contents.com)
139 KiB
89 ms
…mobile/58288.client.fdab203….esnext.js
(cdn-static.farfetch-contents.com)
26 KiB
57 ms
…mobile/32381.client.70e6329….esnext.js
(cdn-static.farfetch-contents.com)
1 KiB
20 ms
…mobile/83217.client.3c13aee….esnext.js
(cdn-static.farfetch-contents.com)
53 KiB
9 ms
…js/cpuMonitor.v3.js
(cdn-static.farfetch-contents.com)
3 KiB
1 ms
…mobile/45762.client.6a3ab20….esnext.js
(cdn-static.farfetch-contents.com)
212 KiB
1 ms
…vitorino/vitorino.min.js
(cdn-static.farfetch-contents.com)
5 KiB
1 ms
…mobile/77155.client.d086cd5….esnext.js
(cdn-static.farfetch-contents.com)
7 KiB
0 ms
…mobile/runtime.client.b458f69….esnext.js
(cdn-static.farfetch-contents.com)
12 KiB
0 ms
…mobile/61181.client.d6268ee….esnext.js
(cdn-static.farfetch-contents.com)
38 KiB
0 ms
…js/eventManager.min.js
(cdn-static.farfetch-contents.com)
1 KiB
0 ms
…mobile/803.client.6d5f2b2….esnext.js
(cdn-static.farfetch-contents.com)
29 KiB
0 ms
…mobile/6302.client.623d635….esnext.js
(cdn-static.farfetch-contents.com)
21 KiB
0 ms
…js/setRUMUse….v1.js
(cdn-static.farfetch-contents.com)
1 KiB
0 ms
…mobile/89706.client.837ad6d….esnext.js
(cdn-static.farfetch-contents.com)
17 KiB
0 ms
…mobile/71171.client.3c4f984….esnext.js
(cdn-static.farfetch-contents.com)
6 KiB
0 ms
…mobile/92879.client.ce4f36a….esnext.js
(cdn-static.farfetch-contents.com)
5 KiB
0 ms
…mobile/31131.client.636a5e8….esnext.js
(cdn-static.farfetch-contents.com)
5 KiB
0 ms
…mobile/97581.client.9aa1008….esnext.js
(cdn-static.farfetch-contents.com)
7 KiB
0 ms
…content/default.client.5e6f1e8….esnext.js
(cdn-static.farfetch-contents.com)
6 KiB
0 ms
…mobile/61349.client.1ebdccd….esnext.js
(cdn-static.farfetch-contents.com)
8 KiB
0 ms
…mobile/23479.client.e8b4f9f….esnext.js
(cdn-static.farfetch-contents.com)
4 KiB
0 ms
…mobile/68419.client.fef9532….esnext.js
(cdn-static.farfetch-contents.com)
5 KiB
0 ms
…mobile/63834.client.765803d….esnext.js
(cdn-static.farfetch-contents.com)
4 KiB
0 ms
…mobile/94515.client.c486f95….esnext.js
(cdn-static.farfetch-contents.com)
4 KiB
0 ms
…mobile/57864.client.31fed96….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/97750.client.2951143….esnext.js
(cdn-static.farfetch-contents.com)
3 KiB
0 ms
…480/welcome-page-image-ww.png
(cdn-static.farfetch-contents.com)
216 KiB
0 ms
…480/welcome-page-image-kw-1-.png
(cdn-static.farfetch-contents.com)
189 KiB
0 ms
…480/welcome-page-image-mw.png
(cdn-static.farfetch-contents.com)
137 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
…v2.00/NimbusSan….woff2
(cdn-static.farfetch-contents.com)
34 KiB
0 ms
…marketing-tracking-library/tracking-library-stable.min.js
(cdn-static.farfetch-contents.com)
25 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
…mobile/16613.client.da18368….esnext.js
(cdn-static.farfetch-contents.com)
7 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
…ios/fr-FR.svg
(cdn-static.farfetch-contents.com)
4 KiB
0 ms
…content/default.client.de5e4d9….css
(cdn-static.farfetch-contents.com)
3 KiB
0 ms
…android/fr-FR.svg
(cdn-static.farfetch-contents.com)
3 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
Forter
utility
175 KiB
9 ms
…0c0275c12bca/script.js
(0c0275c12bca.cdn4.forter.com)
173 KiB
9 ms
…fc503e2…/wpt.json
(cdn0.forter.com)
1 KiB
0 ms
…fc503e2…/prop.json?_=173…
(cdn0.forter.com)
0 KiB
0 ms
…fc503e2…/prop.json?_=173…
(cdn0.forter.com)
0 KiB
0 ms
…fc503e2…/prop.json?_=173…
(cdn0.forter.com)
0 KiB
0 ms
/prop.json
(fc503e2bf2304cbaa41d05c473b0c503-0c0275c12bca.cdn.forter.com)
0 KiB
0 ms
/events
(cdn3.forter.com)
0 KiB
0 ms
mPulse
analytics
50 KiB
0 ms
/boomerang/V8BTZ-CS5UD-BDWCH-VUP73-K8QTK
(s.go-mpulse.net)
50 KiB
0 ms
/api/config.json?key=…
(c.go-mpulse.net)
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
/?shop=farfetch.com&sid=8331b891-b533-41a5-b553-8947ff76ef97
(beacon.riskified.com)
15 KiB
0 ms
/v2/client_infos
(c.riskified.com)
1 KiB
0 ms
/img/image-l.gif?t=…
(img.riskified.com)
0 KiB
0 ms
/img/image-l.gif?t=…
(img.riskified.com)
0 KiB
0 ms
/img/image-l.gif?t=…
(img.riskified.com)
0 KiB
0 ms
/img/image-l.gif?t=…
(img.riskified.com)
0 KiB
0 ms
/img/image-l.gif?t=…
(img.riskified.com)
0 KiB
0 ms
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
…activity/src=5490350;type=pagev0;cat=farfe0;ord=….264%7CNot_A%2
(ade.googlesyndication.com)
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
Largest Contentful Paint element 8,200 ms
This is the largest contentful element painted within the viewport. Learn more about the Largest Contentful Paint elementLCP
Element
WEB_WELCOME PAGE_WW
<img alt="WEB_WELCOME PAGE_WW" src="https://cdn-static.farfetch-contents.com/cms-ccloud/caas/v1/media/123092/d…" loading="eager" data-component="Picture" class="emzgpi21 ltr-1i0wvsb">
Phase
% of LCP
Timing
TTFB
7%
600 ms
Load Delay
56%
4,600 ms
Load Time
14%
1,110 ms
Render Delay
23%
1,890 ms
Serve images in next-gen formats Potential savings of 512 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
539.5 KiB
512.4 KiB
WEB_WELCOME PAGE_WW
<img alt="WEB_WELCOME PAGE_WW" src="https://cdn-static.farfetch-contents.com/cms-ccloud/caas/v1/media/123092/d…" loading="eager" data-component="Picture" class="emzgpi21 ltr-1i0wvsb">
…480/welcome-page-image-ww.png
(cdn-static.farfetch-contents.com)
215.4 KiB
206.2 KiB
KW_LRG_COREMEDIA
<img alt="KW_LRG_COREMEDIA" src="https://cdn-static.farfetch-contents.com/cms-ccloud/caas/v1/media/123086/d…" loading="eager" data-component="Picture" class="emzgpi21 ltr-1i0wvsb">
…480/welcome-page-image-kw-1-.png
(cdn-static.farfetch-contents.com)
188.1 KiB
177.0 KiB
WEB_WELCOME PAGE_MW
<img alt="WEB_WELCOME PAGE_MW" src="https://cdn-static.farfetch-contents.com/cms-ccloud/caas/v1/media/123090/d…" loading="eager" data-component="Picture" class="emzgpi21 ltr-1i0wvsb">
…480/welcome-page-image-mw.png
(cdn-static.farfetch-contents.com)
136.0 KiB
129.3 KiB
Reduce unused JavaScript Potential savings of 493 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
farfetch-contents.com
438.8 KiB
209.8 KiB
…sdks/coralogix-browser-sdk-1.4.6.js
(cdn-static.farfetch-contents.com)
138.4 KiB
85.5 KiB
…mobile/45762.client.6a3ab20….esnext.js
(cdn-static.farfetch-contents.com)
211.3 KiB
70.5 KiB
…mobile/61181.client.d6268ee….esnext.js
(cdn-static.farfetch-contents.com)
36.9 KiB
29.6 KiB
…mobile/83217.client.3c13aee….esnext.js
(cdn-static.farfetch-contents.com)
52.2 KiB
24.3 KiB
Google Tag Manager
tag-manager
463.3 KiB
189.6 KiB
/gtag/js?id=…
(www.googletagmanager.com)
133.1 KiB
52.4 KiB
/gtag/destination?id=…
(www.googletagmanager.com)
100.3 KiB
49.2 KiB
/gtm.js?id=GTM-5VWCDN
(www.googletagmanager.com)
143.0 KiB
44.8 KiB
/gtag/destination?id=…
(www.googletagmanager.com)
86.9 KiB
43.3 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
/boomerang/V8BTZ-CS5UD-BDWCH-VUP73-K8QTK
(s.go-mpulse.net)
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
147.6 KiB
1,670 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/eventManager.min.js
(cdn-static.farfetch-contents.com)
0.8 KiB
150 ms
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,373 KiB
…vitorino/vitorino.min.js
(cdn-static.farfetch-contents.com)
5m
5 KiB
…marketing-tracking-library/tracking-library-stable.min.js
(cdn-static.farfetch-contents.com)
15m
25 KiB
…480/welcome-page-image-ww.png
(cdn-static.farfetch-contents.com)
30d
216 KiB
…mobile/45762.client.6a3ab20….esnext.js
(cdn-static.farfetch-contents.com)
30d
212 KiB
…480/welcome-page-image-kw-1-.png
(cdn-static.farfetch-contents.com)
30d
189 KiB
…sdks/coralogix-browser-sdk-1.4.6.js
(cdn-static.farfetch-contents.com)
30d
139 KiB
…480/welcome-page-image-mw.png
(cdn-static.farfetch-contents.com)
30d
137 KiB
…mobile/83217.client.3c13aee….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
…v2.00/NimbusSan….woff2
(cdn-static.farfetch-contents.com)
30d
34 KiB
…mobile/803.client.6d5f2b2….esnext.js
(cdn-static.farfetch-contents.com)
30d
29 KiB
…mobile/58288.client.fdab203….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.b458f69….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/16613.client.da18368….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/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
…ios/fr-FR.svg
(cdn-static.farfetch-contents.com)
30d
4 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
…android/fr-FR.svg
(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/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
farfetch.com
1st party
109 KiB
…OwlZC/30ZUWk
(www.farfetch.com)
6h
109 KiB
mPulse
analytics
50 KiB
/boomerang/V8BTZ-CS5UD-BDWCH-VUP73-K8QTK
(s.go-mpulse.net)
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
/?shop=farfetch.com&sid=8331b891-b533-41a5-b553-8947ff76ef97
(beacon.riskified.com)
10m
15 KiB
Google Tag Manager
tag-manager
1 KiB
/a?v=…
(www.googletagmanager.com)
None
1 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
…mobile/89706.client.837ad6d….esnext.js:286:3783
(cdn-static.farfetch-contents.com)
Array.isArray
…mobile/45762.client.6a3ab20….esnext.js
(cdn-static.farfetch-contents.com)
0.1 KiB
…mobile/45762.client.6a3ab20….esnext.js:184:341709
(cdn-static.farfetch-contents.com)
@babel/plugin-transform-classes
…mobile/83217.client.3c13aee….esnext.js
(cdn-static.farfetch-contents.com)
0.0 KiB
…mobile/83217.client.3c13aee….esnext.js:526:54220
(cdn-static.farfetch-contents.com)
@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
/fr/:92:1215
(www.farfetch.com)
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
1,721 ms
/gtm.js?id=GTM-5VWCDN
(www.googletagmanager.com)
8,656 ms
756 ms
/gtm.js?id=GTM-5VWCDN
(www.googletagmanager.com)
7,063 ms
275 ms
/gtag/js?id=…
(www.googletagmanager.com)
16,767 ms
217 ms
/gtm.js?id=GTM-5VWCDN
(www.googletagmanager.com)
14,095 ms
189 ms
/gtag/destination?id=…
(www.googletagmanager.com)
17,884 ms
116 ms
/gtag/destination?id=…
(www.googletagmanager.com)
18,634 ms
85 ms
/gtm.js?id=GTM-5VWCDN
(www.googletagmanager.com)
14,284 ms
83 ms
farfetch.com
1st party
1,145 ms
…OwlZC/30ZUWk
(www.farfetch.com)
3,863 ms
1,069 ms
…OwlZC/30ZUWk
(www.farfetch.com)
8,385 ms
76 ms
farfetch-contents.com
855 ms
…mobile/27762.client.8895680….esnext.js
(cdn-static.farfetch-contents.com)
13,396 ms
259 ms
…sdks/coralogix-browser-sdk-1.4.6.js
(cdn-static.farfetch-contents.com)
4,997 ms
189 ms
…sdks/coralogix-browser-sdk-1.4.6.js
(cdn-static.farfetch-contents.com)
3,634 ms
138 ms
…vitorino/vitorino.min.js
(cdn-static.farfetch-contents.com)
13,831 ms
108 ms
…js/cpuMonitor.v3.js
(cdn-static.farfetch-contents.com)
3,772 ms
91 ms
…mobile/32381.client.70e6329….esnext.js
(cdn-static.farfetch-contents.com)
13,939 ms
70 ms
Forter
utility
59 ms
…0c0275c12bca/script.js
(0c0275c12bca.cdn4.forter.com)
17,397 ms
59 ms
Initial server response time was short Root document took 480 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
480 ms
/fr/
(www.farfetch.com)
480 ms
User Timing marks and measures 119 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
GTM-siloed_AW-992356468:page_load:to:snippet_load
Measure
0.00 ms
1,769.20 ms
GTM-siloed_AW-992356468:227:snippet_load:to:ads_conversion_hit
Measure
1,769.20 ms
4,553.32 ms
TL Getting uv marker
Measure
3,196.97 ms
1,233.20 ms
TL Creating SDKs marker
Measure
4,430.30 ms
2.69 ms
TL Queues marker
Measure
4,433.34 ms
8.64 ms
TL Window obj marker
Measure
4,442.12 ms
6.95 ms
GTM-siloed_AW-992356468:container_setup_start:to:container_setup_end
Measure
6,248.11 ms
80.48 ms
GTM-siloed_AW-992356468:container_execute_start:to:container_blocking_end
Measure
6,260.23 ms
67.98 ms
GTM-siloed_AW-992356468:container_execute_start:to:container_execute_end
Measure
6,260.23 ms
122.51 ms
GTM-siloed_AW-992356468:1:event_setup_start:to:event_setup_end
Measure
6,261.58 ms
7.96 ms
GTM-siloed_AW-992356468:1:event_setup_start:to:event_execute_end
Measure
6,261.58 ms
140.56 ms
GTM-siloed_AW-992356468:1:event_evaluation_start:to:event_evaluation_end
Measure
6,263.03 ms
5.86 ms
GTM-siloed_AW-992356468:1:105:tag_execute_start:to:tag_execute_end
Measure
6,271.01 ms
2.41 ms
GTM-siloed_AW-992356468:1:105:tag_execute_start:to:tag_callback_success
Measure
6,271.01 ms
109.02 ms
GTM-siloed_AW-992356468:2:event_setup_start:to:event_setup_end
Measure
6,274.18 ms
1.99 ms
GTM-siloed_AW-992356468:2:event_setup_start:to:event_execute_end
Measure
6,274.18 ms
128.27 ms
GTM-siloed_AW-992356468:2:event_evaluation_start:to:event_evaluation_end
Measure
6,274.60 ms
1.13 ms
GTM-siloed_AW-992356468:2:112:tag_execute_start:to:tag_execute_end
Measure
6,277.27 ms
0.72 ms
GTM-siloed_AW-992356468:2:112:tag_execute_start:to:tag_callback_success
Measure
6,277.27 ms
103.15 ms
GTM-siloed_AW-992356468:2:109:tag_execute_start:to:tag_execute_end
Measure
6,278.37 ms
2.35 ms
GTM-siloed_AW-992356468:2:109:tag_execute_start:to:tag_callback_success
Measure
6,278.37 ms
102.25 ms
GTM-siloed_AW-992356468:3:event_setup_start:to:event_setup_end
Measure
6,281.77 ms
1.79 ms
GTM-siloed_AW-992356468:3:event_setup_start:to:event_execute_end
Measure
6,281.77 ms
120.85 ms
GTM-siloed_AW-992356468:3:event_evaluation_start:to:event_evaluation_end
Measure
6,282.07 ms
1.11 ms
GTM-siloed_AW-992356468:3:102:tag_execute_start:to:tag_execute_end
Measure
6,284.07 ms
1.66 ms
GTM-siloed_AW-992356468:3:102:tag_execute_start:to:tag_callback_success
Measure
6,284.07 ms
96.85 ms
GTM-siloed_AW-992356468:197:event_setup_start:to:event_setup_end
Measure
6,287.08 ms
4.52 ms
GTM-siloed_AW-992356468:197:event_setup_start:to:event_execute_end
Measure
6,287.08 ms
94.36 ms
GTM-siloed_AW-992356468:197:event_evaluation_start:to:event_evaluation_end
Measure
6,287.32 ms
3.76 ms
GTM-siloed_AW-992356468:200:event_setup_start:to:event_setup_end
Measure
6,292.32 ms
1.48 ms
GTM-siloed_AW-992356468:200:event_setup_start:to:event_execute_end
Measure
6,292.32 ms
89.97 ms
GTM-siloed_AW-992356468:200:event_evaluation_start:to:event_evaluation_end
Measure
6,292.57 ms
0.84 ms
GTM-siloed_AW-992356468:203:event_setup_start:to:event_setup_end
Measure
6,294.68 ms
3.35 ms
GTM-siloed_AW-992356468:203:event_setup_start:to:event_execute_end
Measure
6,294.68 ms
87.88 ms
GTM-siloed_AW-992356468:203:event_evaluation_start:to:event_evaluation_end
Measure
6,294.93 ms
2.76 ms
GTM-siloed_AW-992356468:210:event_setup_start:to:event_setup_end
Measure
6,298.56 ms
1.09 ms
GTM-siloed_AW-992356468:210:event_setup_start:to:event_execute_end
Measure
6,298.56 ms
89.40 ms
GTM-siloed_AW-992356468:210:event_evaluation_start:to:event_evaluation_end
Measure
6,298.81 ms
0.55 ms
GTM-siloed_AW-992356468:224:event_setup_start:to:event_setup_end
Measure
6,301.49 ms
2.88 ms
GTM-siloed_AW-992356468:224:event_setup_start:to:event_execute_end
Measure
6,301.49 ms
86.76 ms
GTM-siloed_AW-992356468:224:event_evaluation_start:to:event_evaluation_end
Measure
6,301.76 ms
2.26 ms
GTM-siloed_AW-992356468:227:event_setup_start:to:event_setup_end
Measure
6,304.79 ms
1.43 ms
GTM-siloed_AW-992356468:227:event_setup_start:to:event_execute_end
Measure
6,304.79 ms
83.72 ms
GTM-siloed_AW-992356468:227:event_evaluation_start:to:event_evaluation_end
Measure
6,305.08 ms
0.61 ms
GTM-siloed_AW-992356468:page_load
Mark
0.00 ms
GTM-siloed_AW-992356468:snippet_load
Mark
1,769.20 ms
TL - Start Bootstrap
Mark
3,196.04 ms
TL - Start getting uv
Mark
3,196.97 ms
TL - End getting uv
Mark
4,430.17 ms
TL - Start creating sdks
Mark
4,430.30 ms
TL - End creating sdks
Mark
4,432.98 ms
TL - End Bootstrap
Mark
4,433.19 ms
TL - Start creating queues
Mark
4,433.34 ms
TL - End creating queues
Mark
4,441.98 ms
TL - Start filling window obj
Mark
4,442.12 ms
TL - End filling window obj
Mark
4,449.07 ms
GTM-siloed_AW-992356468:container_setup_start
Mark
6,248.11 ms
GTM-siloed_AW-992356468:container_execute_start
Mark
6,260.23 ms
GTM-siloed_AW-992356468:1:event_setup_start
Mark
6,261.58 ms
GTM-siloed_AW-992356468:1:event_evaluation_start
Mark
6,263.03 ms
GTM-siloed_AW-992356468:1:event_evaluation_end
Mark
6,268.90 ms
GTM-siloed_AW-992356468:1:event_setup_end
Mark
6,269.54 ms
GTM-siloed_AW-992356468:1:105:tag_execute_start
Mark
6,271.01 ms
GTM-siloed_AW-992356468:1:105:tag_execute_end
Mark
6,273.42 ms
GTM-siloed_AW-992356468:2:event_setup_start
Mark
6,274.18 ms
GTM-siloed_AW-992356468:2:event_evaluation_start
Mark
6,274.60 ms
GTM-siloed_AW-992356468:2:event_evaluation_end
Mark
6,275.72 ms
GTM-siloed_AW-992356468:2:event_setup_end
Mark
6,276.18 ms
GTM-siloed_AW-992356468:2:112:tag_execute_start
Mark
6,277.27 ms
GTM-siloed_AW-992356468:2:112:tag_execute_end
Mark
6,277.99 ms
GTM-siloed_AW-992356468:2:109:tag_execute_start
Mark
6,278.37 ms
GTM-siloed_AW-992356468:2:109:tag_execute_end
Mark
6,280.72 ms
GTM-siloed_AW-992356468:3:event_setup_start
Mark
6,281.77 ms
GTM-siloed_AW-992356468:3:event_evaluation_start
Mark
6,282.07 ms
GTM-siloed_AW-992356468:3:event_evaluation_end
Mark
6,283.18 ms
GTM-siloed_AW-992356468:3:event_setup_end
Mark
6,283.56 ms
GTM-siloed_AW-992356468:3:102:tag_execute_start
Mark
6,284.07 ms
GTM-siloed_AW-992356468:3:102:tag_execute_end
Mark
6,285.73 ms
GTM-siloed_AW-992356468:197:event_setup_start
Mark
6,287.08 ms
GTM-siloed_AW-992356468:197:event_evaluation_start
Mark
6,287.32 ms
GTM-siloed_AW-992356468:197:event_evaluation_end
Mark
6,291.08 ms
GTM-siloed_AW-992356468:197:event_setup_end
Mark
6,291.60 ms
GTM-siloed_AW-992356468:200:event_setup_start
Mark
6,292.32 ms
GTM-siloed_AW-992356468:200:event_evaluation_start
Mark
6,292.57 ms
GTM-siloed_AW-992356468:200:event_evaluation_end
Mark
6,293.41 ms
GTM-siloed_AW-992356468:200:event_setup_end
Mark
6,293.79 ms
GTM-siloed_AW-992356468:203:event_setup_start
Mark
6,294.68 ms
GTM-siloed_AW-992356468:203:event_evaluation_start
Mark
6,294.93 ms
GTM-siloed_AW-992356468:203:event_evaluation_end
Mark
6,297.69 ms
GTM-siloed_AW-992356468:203:event_setup_end
Mark
6,298.03 ms
GTM-siloed_AW-992356468:210:event_setup_start
Mark
6,298.56 ms
GTM-siloed_AW-992356468:210:event_evaluation_start
Mark
6,298.81 ms
GTM-siloed_AW-992356468:210:event_evaluation_end
Mark
6,299.37 ms
GTM-siloed_AW-992356468:210:event_setup_end
Mark
6,299.65 ms
GTM-siloed_AW-992356468:224:event_setup_start
Mark
6,301.49 ms
GTM-siloed_AW-992356468:224:event_evaluation_start
Mark
6,301.76 ms
GTM-siloed_AW-992356468:224:event_evaluation_end
Mark
6,304.02 ms
GTM-siloed_AW-992356468:224:event_setup_end
Mark
6,304.37 ms
GTM-siloed_AW-992356468:227:event_setup_start
Mark
6,304.79 ms
GTM-siloed_AW-992356468:227:event_evaluation_start
Mark
6,305.08 ms
GTM-siloed_AW-992356468:227:event_evaluation_end
Mark
6,305.69 ms
GTM-siloed_AW-992356468:227:event_setup_end
Mark
6,306.21 ms
GTM-siloed_AW-992356468:227:ads_conversion_hit
Mark
6,322.52 ms
GTM-siloed_AW-992356468:container_blocking_end
Mark
6,328.21 ms
GTM-siloed_AW-992356468:container_setup_end
Mark
6,328.59 ms
GTM-siloed_AW-992356468:1:105:tag_callback_success
Mark
6,380.03 ms
GTM-siloed_AW-992356468:2:112:tag_callback_success
Mark
6,380.42 ms
GTM-siloed_AW-992356468:2:109:tag_callback_success
Mark
6,380.62 ms
GTM-siloed_AW-992356468:3:102:tag_callback_success
Mark
6,380.92 ms
GTM-siloed_AW-992356468:197:event_execute_end
Mark
6,381.44 ms
GTM-siloed_AW-992356468:200:event_execute_end
Mark
6,382.29 ms
GTM-siloed_AW-992356468:203:event_execute_end
Mark
6,382.56 ms
GTM-siloed_AW-992356468:container_execute_end
Mark
6,382.74 ms
GTM-siloed_AW-992356468:210:event_execute_end
Mark
6,387.95 ms
GTM-siloed_AW-992356468:224:event_execute_end
Mark
6,388.25 ms
GTM-siloed_AW-992356468:227:event_execute_end
Mark
6,388.50 ms
GTM-siloed_AW-992356468:1:event_execute_end
Mark
6,402.14 ms
GTM-siloed_AW-992356468:2:event_execute_end
Mark
6,402.46 ms
GTM-siloed_AW-992356468:3:event_execute_end
Mark
6,402.62 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: height
height
Unsupported CSS Property: visibility
visibility
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
Avoids enormous network payloads Total size was 2,389 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
892.2 KiB
…480/welcome-page-image-ww.png
(cdn-static.farfetch-contents.com)
215.9 KiB
…mobile/45762.client.6a3ab20….esnext.js
(cdn-static.farfetch-contents.com)
212.0 KiB
…480/welcome-page-image-kw-1-.png
(cdn-static.farfetch-contents.com)
188.6 KiB
…sdks/coralogix-browser-sdk-1.4.6.js
(cdn-static.farfetch-contents.com)
139.1 KiB
…480/welcome-page-image-mw.png
(cdn-static.farfetch-contents.com)
136.5 KiB
Google Tag Manager
tag-manager
379.6 KiB
/gtm.js?id=GTM-5VWCDN
(www.googletagmanager.com)
144.1 KiB
/gtag/js?id=…
(www.googletagmanager.com)
134.2 KiB
/gtag/destination?id=…
(www.googletagmanager.com)
101.3 KiB
Forter
utility
173.0 KiB
…0c0275c12bca/script.js
(0c0275c12bca.cdn4.forter.com)
173.0 KiB
farfetch.com
1st party
108.7 KiB
…OwlZC/30ZUWk
(www.farfetch.com)
108.7 KiB
Avoids an excessive DOM size 526 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
526
Maximum DOM Depth
label.ltr-3vrmm2 > div.ltr-1tyy8mh > svg.ltr-15kvush > use
<use xlink:href="#iconLoaded-checkboxEmpty">
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">
55
Avoid chaining critical requests 33 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,131.63 ms
Initial Navigation
/fr/
(www.farfetch.com)
…mobile/45762.client.6a3ab20….esnext.js
(cdn-static.farfetch-contents.com)
- 377.699 ms, 212.00 KiB
…mobile/61181.client.d6268ee….esnext.js
(cdn-static.farfetch-contents.com)
- 272.346 ms, 37.65 KiB
…mobile/68419.client.fef9532….esnext.js
(cdn-static.farfetch-contents.com)
- 180.156 ms, 4.89 KiB
…mobile/31131.client.636a5e8….esnext.js
(cdn-static.farfetch-contents.com)
- 150.307 ms, 5.38 KiB
…mobile/42512.client.69ba4cf….esnext.js
(cdn-static.farfetch-contents.com)
- 202.402 ms, 4.19 KiB
…mobile/89706.client.837ad6d….esnext.js
(cdn-static.farfetch-contents.com)
- 213.427 ms, 16.95 KiB
…mobile/83217.client.3c13aee….esnext.js
(cdn-static.farfetch-contents.com)
- 179.733 ms, 52.90 KiB
…mobile/61349.client.1ebdccd….esnext.js
(cdn-static.farfetch-contents.com)
- 181.421 ms, 8.30 KiB
…mobile/97581.client.9aa1008….esnext.js
(cdn-static.farfetch-contents.com)
- 181.644 ms, 6.54 KiB
…mobile/77155.client.d086cd5….esnext.js
(cdn-static.farfetch-contents.com)
- 80.261 ms, 7.47 KiB
…mobile/45762.client.9781f7a….css
(cdn-static.farfetch-contents.com)
- 105.588 ms, 4.62 KiB
…mobile/92879.client.ce4f36a….esnext.js
(cdn-static.farfetch-contents.com)
- 219.319 ms, 4.93 KiB
…mobile/94515.client.c486f95….esnext.js
(cdn-static.farfetch-contents.com)
- 137.977 ms, 4.03 KiB
…mobile/58288.client.fdab203….esnext.js
(cdn-static.farfetch-contents.com)
- 127.742 ms, 26.27 KiB
…mobile/23479.client.e8b4f9f….esnext.js
(cdn-static.farfetch-contents.com)
- 197.003 ms, 3.79 KiB
…mobile/6302.client.623d635….esnext.js
(cdn-static.farfetch-contents.com)
- 184.318 ms, 21.17 KiB
…mobile/97750.client.2951143….esnext.js
(cdn-static.farfetch-contents.com)
- 269.137 ms, 2.75 KiB
…mobile/63834.client.765803d….esnext.js
(cdn-static.farfetch-contents.com)
- 74.124 ms, 4.22 KiB
…mobile/57864.client.31fed96….esnext.js
(cdn-static.farfetch-contents.com)
- 109.011 ms, 3.70 KiB
…mobile/803.client.6d5f2b2….esnext.js
(cdn-static.farfetch-contents.com)
- 190.952 ms, 28.65 KiB
…mobile/71171.client.3c4f984….esnext.js
(cdn-static.farfetch-contents.com)
- 163.737 ms, 6.46 KiB
…content/default.client.de5e4d9….css
(cdn-static.farfetch-contents.com)
- 220.063 ms, 3.04 KiB
…content/default.client.5e6f1e8….esnext.js
(cdn-static.farfetch-contents.com)
- 145.933 ms, 6.24 KiB
…OwlZC/30ZUWk
(www.farfetch.com)
- 457.097 ms, 108.67 KiB
…mobile/56683.client.3b099b0….css
(cdn-static.farfetch-contents.com)
- 132.178 ms, 1.88 KiB
…sdks/coralogix-browser-sdk-1.4.6.js
(cdn-static.farfetch-contents.com)
- 340.459 ms, 139.14 KiB
…js/cpuMonitor.v3.js
(cdn-static.farfetch-contents.com)
- 179.944 ms, 2.76 KiB
…js/setRUMUse….v1.js
(cdn-static.farfetch-contents.com)
- 210.867 ms, 0.75 KiB
…v2.00/NimbusSan….woff2
(cdn-static.farfetch-contents.com)
- 47.119 ms, 33.59 KiB
…v2.00/FarfetchB….woff2
(cdn-static.farfetch-contents.com)
- 238.188 ms, 50.11 KiB
…v2.00/FarfetchBasis-Bold.woff2
(cdn-static.farfetch-contents.com)
- 281.052 ms, 48.97 KiB
…js/eventManager.min.js
(cdn-static.farfetch-contents.com)
- 179.734 ms, 0.83 KiB
…mobile/runtime.client.b458f69….esnext.js
(cdn-static.farfetch-contents.com)
- 237.275 ms, 12.26 KiB
More information about the performance of your application. These numbers don't directly affect the Performance score.
Passed audits (18)
Show Hide
Properly size images
Serve images that are appropriately-sized to save cellular data and improve load time. Learn how to size images.LCPFCP
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://cdn-images.farfetch-contents.com" 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://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.
100
Accessibility
These checks highlight opportunities to improve the accessibility of your web app. Automatic detection can only detect a subset of issues and does not guarantee the accessibility of your web app, so manual testing is also encouraged.
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.
Links are distinguishable without relying on color.
Low-contrast text is difficult or impossible for many users to read. Link text that is discernible improves the experience for users with low vision. Learn how to make links distinguishable.
Links have a discernible name
Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.
Lists contain only <li> elements and script supporting elements (<script> and <template>).
Screen readers have a specific way of announcing lists. Ensuring proper list structure aids screen reader output. Learn more about proper list structure.
List items (<li>) are contained within <ul>, <ol> or <menu> parent elements
Screen readers require list items (<li>) to be contained within a parent <ul>, <ol> or <menu> to be announced properly. Learn more about proper list structure.
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 (31)
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.
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.
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.
79
Best Practices
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
/boomerang/V8BTZ-CS5UD-BDWCH-VUP73-K8QTK:10:11504
(s.go-mpulse.net)
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
/fr/:1:0
(www.farfetch.com)
Refused to execute script from 'https://pagead2.googlesyndication.com/pagead/conversion/992356468/?random=1739383262509&cv=11&fst=1739383262509&bg=ffffff&guid=ON&async=1&gtm=45be5280v871604564z872394093za201zb887643346&gcs=G101&gcd=13q3r3q3q5l1&dma_cps=-&dma=0&tag_exp=101509156~101732279~101732281~102015666~102067808~102482432~102539968~102558064~102587591~102605417&u_w=412&u_h=823&url=https%3A%2F%2Fwww.farfetch.com%2Ffr%2F&label=hCbTCPPi3a8BEPTQmNkD&hn=www.googleadservices.com&frm=0&tiba=FARFETCH%20France%20%7C%20La%20r%C3%A9f%C3%A9rence%20mondiale%20du%20luxe%20contemporain&value=0&bttype=purchase&npa=1&pscdl=denied&uaa=&uab=64&uafvl=HeadlessChrome%3B131.0.6778.264%7CChromium%3B131.0.6778.264%7CNot_A%2520Brand%3B24.0.0.0&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
…marketing-tracking-library/tracking-library-stable.min.js
(cdn-static.farfetch-contents.com)
…marketing-tracking-library/tracking-library.min.js.map
(cdn-static.farfetch-contents.com)
SyntaxError: Unexpected token '/', "/*! For li"... is not valid JSON
Riskified
utility
/?shop=farfetch.com&sid=8331b891-b533-41a5-b553-8947ff76ef97
(beacon.riskified.com)
…ZmFyZmV0Y2guY29t/ODMzMWI4O…
(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/35010533336
Not applicable (1)
Show Hide
Redirects HTTP traffic to HTTPS
Make sure that you redirect all HTTP traffic to HTTPS in order to enable secure web features for all your users. Learn more.
100
SEO
These checks ensure that your page is following basic search engine optimization advice. There are many additional factors Lighthouse does not score here that may affect your search ranking, including performance on Core Web Vitals. Learn more about Google Search Essentials.
Additional items to manually check (1)
Show Hide
Structured data is valid
Run the Structured Data Testing Tool and the Structured Data Linter to validate structured data. Learn more about Structured Data.
Run these additional validators on your site to check additional SEO best practices.
Passed audits (10)
Show Hide
Page isn’t blocked from indexing
Search engines are unable to include your pages in search results if they don't have permission to crawl them. Learn more about crawler directives.
Document has a <title> element
The title gives screen reader users an overview of the page, and search engine users rely on it heavily to determine if a page is relevant to their search. Learn more about document titles.
Document has a meta description
Meta descriptions may be included in search results to concisely summarize page content. Learn more about the meta description.
Page has successful HTTP status code
Pages with unsuccessful HTTP status codes may not be indexed properly. Learn more about HTTP status codes.
Links have descriptive text
Descriptive link text helps search engines understand your content. Learn how to make links more accessible.
Links are crawlable
Search engines may use href attributes on links to crawl websites. Ensure that the href attribute of anchor elements links to an appropriate destination, so more pages of the site can be discovered. Learn how to make links crawlable
robots.txt is valid
If your robots.txt file is malformed, crawlers may not be able to understand how you want your website to be crawled or indexed. Learn more about robots.txt.
Image elements have [alt] attributes
Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the alt attribute.
Document has a valid hreflang
hreflang links tell search engines what version of a page they should list in search results for a given language or region. Learn more about hreflang.
Document has a valid rel=canonical
Canonical links suggest which URL to show in search results. Learn more about canonical links.
Discover what your real users are experiencing
Core Web Vitals Assessment: Passed
Largest Contentful Paint (LCP)
1.6 s
Page LoadsGood (≤ 2.5 s)91%Needs Improvement (2.5 s - 4 s)6%Poor (> 4 s)3%75th Percentile - 1.6 sCore Web Vital
Interaction to Next Paint (INP)
80 ms
Page LoadsGood (≤ 200 ms)91%Needs Improvement (200 ms - 500 ms)6%Poor (> 500 ms)3%75th Percentile - 80 msCore Web Vital
Cumulative Layout Shift (CLS)
0.04
Page LoadsGood (≤ 0.1)98%Needs Improvement (0.1 - 0.25)2%Poor (> 0.25)0%75th Percentile - 0.04Core Web Vital
Other Notable Metrics
First Contentful Paint (FCP)
1.5 s
Page LoadsGood (≤ 1.8 s)83%Needs Improvement (1.8 s - 3 s)12%Poor (> 3 s)5%75th Percentile - 1.5 s 
Time to First Byte (TTFB)
0.8 s
Page LoadsGood (≤ 0.8 s)72%Needs Improvement (0.8 s - 1.8 s)24%Poor (> 1.8 s)4%75th Percentile - 0.8 sExperimental
Latest 28-day collection period
Various desktop devicesMany samples (Chrome UX Report)Full visit durationsVarious network connectionsAll Chrome versions
Core Web Vitals Assessment: Passed
Largest Contentful Paint (LCP)
2.1 s
Page LoadsGood (≤ 2.5 s)82%Needs Improvement (2.5 s - 4 s)13%Poor (> 4 s)5%75th Percentile - 2.1 sCore Web Vital
Interaction to Next Paint (INP)
112 ms
Page LoadsGood (≤ 200 ms)89%Needs Improvement (200 ms - 500 ms)8%Poor (> 500 ms)3%75th Percentile - 112 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.6 s
Page LoadsGood (≤ 1.8 s)82%Needs Improvement (1.8 s - 3 s)15%Poor (> 3 s)3%75th Percentile - 1.6 s 
Time to First Byte (TTFB)
1.2 s
Page LoadsGood (≤ 0.8 s)42%Needs Improvement (0.8 s - 1.8 s)51%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
56
Performance
100
Accessibility
78
Best Practices
100
SEO
56
Performance
100
Accessibility
78
Best Practices
100
SEO
56 FCP+8LCP+18TBT+0CLS+24SI+6 Performance
Values are estimated and may vary. The performance score is calculated directly from these metrics.See calculator.
0–49 50–89 90–100
Final Screenshot
Metrics
First Contentful Paint
1.1 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more about the First Contentful Paint metric.
Largest Contentful Paint
1.7 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
2,140 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.063
Cumulative Layout Shift measures the movement of visible elements within the viewport. Learn more about the Cumulative Layout Shift metric.
Speed Index
2.1 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more about the Speed Index metric.
  • Captured at Feb 12, 2025, 6:00 PM UTC
  • Emulated Desktop with Lighthouse 12.2.3
    Unthrottled CPU/Memory Power: 334 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 131.0.6778.264 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 4.3 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to reduce Javascript execution time.TBT
URL
Total CPU Time
Script Evaluation
Script Parse
Google Tag Manager
tag-manager
1,787 ms
1,672 ms
34 ms
/gtm.js?id=GTM-5VWCDN
(www.googletagmanager.com)
1,491 ms
1,412 ms
13 ms
/gtag/js?id=…
(www.googletagmanager.com)
177 ms
154 ms
9 ms
/gtag/destination?id=…
(www.googletagmanager.com)
65 ms
57 ms
8 ms
/gtag/destination?id=…
(www.googletagmanager.com)
53 ms
49 ms
4 ms
farfetch.com
1st party
1,675 ms
1,434 ms
15 ms
…OwlZC/30ZUWk
(www.farfetch.com)
1,323 ms
1,316 ms
5 ms
/fr/
(www.farfetch.com)
278 ms
45 ms
9 ms
…UniversalVariable/GetUniversalVariableUserScript?pageType=…
(www.farfetch.com)
74 ms
74 ms
0 ms
farfetch-contents.com
782 ms
743 ms
13 ms
…desktop/74873.client.f45d56e….esnext.js
(cdn-static.farfetch-contents.com)
191 ms
191 ms
0 ms
…desktop/10210.client.5d745a4….esnext.js
(cdn-static.farfetch-contents.com)
164 ms
158 ms
2 ms
…sdks/coralogix-browser-sdk-1.4.6.js
(cdn-static.farfetch-contents.com)
144 ms
124 ms
11 ms
…desktop/27762.client.90582b5….esnext.js
(cdn-static.farfetch-contents.com)
122 ms
121 ms
0 ms
…desktop/57333.client.cf211d6….esnext.js
(cdn-static.farfetch-contents.com)
105 ms
105 ms
0 ms
…desktop/77053.client.faa76a7….esnext.js
(cdn-static.farfetch-contents.com)
55 ms
44 ms
0 ms
Unattributable
441 ms
161 ms
0 ms
Unattributable
297 ms
103 ms
0 ms
(program):2
144 ms
58 ms
0 ms
Forter
utility
177 ms
168 ms
7 ms
…0c0275c12bca/script.js
(0c0275c12bca.cdn4.forter.com)
177 ms
168 ms
7 ms
Riskified
utility
50 ms
47 ms
1 ms
/?shop=farfetch.com&sid=438b1ea8-12c0-43eb-8b3a-57200bb42a21
(beacon.riskified.com)
50 ms
47 ms
1 ms
Minimize main-thread work 5.1 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to minimize main-thread workTBT
Category
Time Spent
Script Evaluation
4,372 ms
Other
340 ms
Style & Layout
161 ms
Script Parsing & Compilation
93 ms
Garbage Collection
79 ms
Parse HTML & CSS
46 ms
Rendering
31 ms
Serve images in next-gen formats Potential savings of 512 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
539.5 KiB
512.4 KiB
WEB_WELCOME PAGE_WW
<img alt="WEB_WELCOME PAGE_WW" src="https://cdn-static.farfetch-contents.com/cms-ccloud/caas/v1/media/123092/d…" loading="eager" data-component="Picture" class="emzgpi21 ltr-1i0wvsb">
…480/welcome-page-image-ww.png
(cdn-static.farfetch-contents.com)
215.4 KiB
206.2 KiB
KW_LRG_COREMEDIA
<img alt="KW_LRG_COREMEDIA" src="https://cdn-static.farfetch-contents.com/cms-ccloud/caas/v1/media/123086/d…" loading="eager" data-component="Picture" class="emzgpi21 ltr-1i0wvsb">
…480/welcome-page-image-kw-1-.png
(cdn-static.farfetch-contents.com)
188.1 KiB
177.0 KiB
WEB_WELCOME PAGE_MW
<img alt="WEB_WELCOME PAGE_MW" src="https://cdn-static.farfetch-contents.com/cms-ccloud/caas/v1/media/123090/d…" loading="eager" data-component="Picture" class="emzgpi21 ltr-1i0wvsb">
…480/welcome-page-image-mw.png
(cdn-static.farfetch-contents.com)
136.0 KiB
129.3 KiB
Reduce initial server response time Root document took 800 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
800 ms
/fr/
(www.farfetch.com)
800 ms
Largest Contentful Paint element 1,720 ms
This is the largest contentful element painted within the viewport. Learn more about the Largest Contentful Paint elementLCP
Element
WEB_WELCOME PAGE_WW
<img alt="WEB_WELCOME PAGE_WW" src="https://cdn-static.farfetch-contents.com/cms-ccloud/caas/v1/media/123092/d…" loading="eager" data-component="Picture" class="emzgpi21 ltr-1i0wvsb">
Phase
% of LCP
Timing
TTFB
9%
160 ms
Load Delay
53%
920 ms
Load Time
21%
360 ms
Render Delay
17%
280 ms
Reduce unused JavaScript Potential savings of 566 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
farfetch-contents.com
464.1 KiB
219.3 KiB
…sdks/coralogix-browser-sdk-1.4.6.js
(cdn-static.farfetch-contents.com)
138.5 KiB
85.4 KiB
…desktop/10210.client.5d745a4….esnext.js
(cdn-static.farfetch-contents.com)
218.4 KiB
75.3 KiB
…desktop/83627.client.9d013c5….esnext.js
(cdn-static.farfetch-contents.com)
36.8 KiB
29.5 KiB
…desktop/55438.client.9834e23….esnext.js
(cdn-static.farfetch-contents.com)
70.4 KiB
29.1 KiB
Google Tag Manager
tag-manager
461.2 KiB
189.6 KiB
/gtag/js?id=…
(www.googletagmanager.com)
133.4 KiB
52.4 KiB
/gtag/destination?id=…
(www.googletagmanager.com)
97.7 KiB
49.0 KiB
/gtm.js?id=GTM-5VWCDN
(www.googletagmanager.com)
143.2 KiB
44.8 KiB
/gtag/destination?id=…
(www.googletagmanager.com)
86.9 KiB
43.3 KiB
Other Google APIs/SDKs
utility
85.1 KiB
63.4 KiB
/gsi/client
(accounts.google.com)
85.1 KiB
63.4 KiB
Forter
utility
172.3 KiB
61.6 KiB
…0c0275c12bca/script.js
(0c0275c12bca.cdn4.forter.com)
172.3 KiB
61.6 KiB
mPulse
analytics
49.1 KiB
31.9 KiB
/boomerang/V8BTZ-CS5UD-BDWCH-VUP73-K8QTK
(s.go-mpulse.net)
49.1 KiB
31.9 KiB
Properly size images Potential savings of 171 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
539.5 KiB
171.0 KiB
WEB_WELCOME PAGE_WW
<img alt="WEB_WELCOME PAGE_WW" src="https://cdn-static.farfetch-contents.com/cms-ccloud/caas/v1/media/123092/d…" loading="eager" data-component="Picture" class="emzgpi21 ltr-1i0wvsb">
…480/welcome-page-image-ww.png
(cdn-static.farfetch-contents.com)
215.4 KiB
68.3 KiB
KW_LRG_COREMEDIA
<img alt="KW_LRG_COREMEDIA" src="https://cdn-static.farfetch-contents.com/cms-ccloud/caas/v1/media/123086/d…" loading="eager" data-component="Picture" class="emzgpi21 ltr-1i0wvsb">
…480/welcome-page-image-kw-1-.png
(cdn-static.farfetch-contents.com)
188.1 KiB
59.6 KiB
WEB_WELCOME PAGE_MW
<img alt="WEB_WELCOME PAGE_MW" src="https://cdn-static.farfetch-contents.com/cms-ccloud/caas/v1/media/123090/d…" loading="eager" data-component="Picture" class="emzgpi21 ltr-1i0wvsb">
…480/welcome-page-image-mw.png
(cdn-static.farfetch-contents.com)
136.0 KiB
43.1 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.9 KiB
340 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.2 KiB
130 ms
Reduce the impact of third-party code Third-party code blocked the main thread for 1,090 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
468 KiB
779 ms
/gtm.js?id=GTM-5VWCDN
(www.googletagmanager.com)
144 KiB
641 ms
/gtag/js?id=…
(www.googletagmanager.com)
134 KiB
122 ms
/gtag/destination?id=…
(www.googletagmanager.com)
99 KiB
14 ms
/gtag/destination?id=…
(www.googletagmanager.com)
88 KiB
2 ms
…5230/sw_iframe.html?origin=https%3A%2F%2Fwww.farfetch.com
(www.googletagmanager.com)
2 KiB
0 ms
farfetch-contents.com
1,388 KiB
307 ms
…desktop/74873.client.f45d56e….esnext.js
(cdn-static.farfetch-contents.com)
29 KiB
128 ms
…desktop/27762.client.90582b5….esnext.js
(cdn-static.farfetch-contents.com)
1 KiB
72 ms
…sdks/coralogix-browser-sdk-1.4.6.js
(cdn-static.farfetch-contents.com)
139 KiB
66 ms
…desktop/57333.client.cf211d6….esnext.js
(cdn-static.farfetch-contents.com)
9 KiB
24 ms
…desktop/55438.client.9834e23….esnext.js
(cdn-static.farfetch-contents.com)
71 KiB
9 ms
…desktop/77053.client.faa76a7….esnext.js
(cdn-static.farfetch-contents.com)
1 KiB
5 ms
…desktop/10210.client.5d745a4….esnext.js
(cdn-static.farfetch-contents.com)
219 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
…desktop/runtime.client.7e20863….esnext.js
(cdn-static.farfetch-contents.com)
12 KiB
0 ms
…js/eventManager.min.js
(cdn-static.farfetch-contents.com)
1 KiB
0 ms
…desktop/803.client.8138d91….esnext.js
(cdn-static.farfetch-contents.com)
27 KiB
0 ms
…js/setRUMUse….v1.js
(cdn-static.farfetch-contents.com)
1 KiB
0 ms
…desktop/63309.client.432c8dd….esnext.js
(cdn-static.farfetch-contents.com)
15 KiB
0 ms
…desktop/89706.client.73bdaae….esnext.js
(cdn-static.farfetch-contents.com)
17 KiB
0 ms
…content/default.client.832b49e….esnext.js
(cdn-static.farfetch-contents.com)
10 KiB
0 ms
…desktop/64738.client.3a90818….esnext.js
(cdn-static.farfetch-contents.com)
5 KiB
0 ms
…desktop/97581.client.06aa5b6….esnext.js
(cdn-static.farfetch-contents.com)
6 KiB
0 ms
…desktop/78626.client.b9cbbc5….esnext.js
(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/2316.client.8b33843….esnext.js
(cdn-static.farfetch-contents.com)
5 KiB
0 ms
…desktop/44119.client.20f3f1b….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/49408.client.df2659a….esnext.js
(cdn-static.farfetch-contents.com)
3 KiB
0 ms
…desktop/66264.client.342f429….esnext.js
(cdn-static.farfetch-contents.com)
5 KiB
0 ms
…desktop/57864.client.b68907d….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
…480/welcome-page-image-ww.png
(cdn-static.farfetch-contents.com)
216 KiB
0 ms
…480/welcome-page-image-kw-1-.png
(cdn-static.farfetch-contents.com)
189 KiB
0 ms
…480/welcome-page-image-mw.png
(cdn-static.farfetch-contents.com)
137 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
…v2.00/NimbusSan….woff2
(cdn-static.farfetch-contents.com)
34 KiB
0 ms
…marketing-tracking-library/tracking-library-stable.min.js
(cdn-static.farfetch-contents.com)
25 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
…desktop/16613.client.c02ba02….esnext.js
(cdn-static.farfetch-contents.com)
7 KiB
0 ms
…desktop/10210.client.b15253c….css
(cdn-static.farfetch-contents.com)
5 KiB
0 ms
…desktop/GdprBanner.client.e13a52e….esnext.js
(cdn-static.farfetch-contents.com)
4 KiB
0 ms
…content/default.client.84f6fa3….css
(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/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
mPulse
analytics
50 KiB
0 ms
/boomerang/V8BTZ-CS5UD-BDWCH-VUP73-K8QTK
(s.go-mpulse.net)
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
…101b529…/wpt.json
(cdn0.forter.com)
1 KiB
0 ms
…101b529…/prop.json?_=173…
(cdn0.forter.com)
0 KiB
0 ms
…101b529…/prop.json?_=173…
(cdn0.forter.com)
0 KiB
0 ms
…101b529…/prop.json?_=173…
(cdn0.forter.com)
0 KiB
0 ms
/prop.json
(101b529461584c128c9a84332a6947a9-0c0275c12bca.cdn.forter.com)
0 KiB
0 ms
/events
(cdn3.forter.com)
0 KiB
0 ms
Other Google APIs/SDKs
utility
88 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
/?shop=farfetch.com&sid=438b1ea8-12c0-43eb-8b3a-57200bb42a21
(beacon.riskified.com)
15 KiB
0 ms
/v2/client_infos
(c.riskified.com)
1 KiB
0 ms
/img/image-l.gif?t=…
(img.riskified.com)
0 KiB
0 ms
/img/image-l.gif?t=…
(img.riskified.com)
0 KiB
0 ms
/img/image-l.gif?t=…
(img.riskified.com)
0 KiB
0 ms
/img/image-l.gif?t=…
(img.riskified.com)
0 KiB
0 ms
/img/image-l.gif?t=…
(img.riskified.com)
0 KiB
0 ms
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
…activity/src=5490350;type=pagev0;cat=farfe0;ord=1;n….264%7CNot_
(ade.googlesyndication.com)
1 KiB
0 ms
…activity/src=5490350;dc_pre=CIK5r8vbv…;type=pagev0;cat=fa….264%
(ade.googlesyndication.com)
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
Serve static assets with an efficient cache policy 53 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,379 KiB
…vitorino/vitorino.min.js
(cdn-static.farfetch-contents.com)
5m
5 KiB
…marketing-tracking-library/tracking-library-stable.min.js
(cdn-static.farfetch-contents.com)
15m
25 KiB
…desktop/10210.client.5d745a4….esnext.js
(cdn-static.farfetch-contents.com)
30d
219 KiB
…480/welcome-page-image-ww.png
(cdn-static.farfetch-contents.com)
30d
216 KiB
…480/welcome-page-image-kw-1-.png
(cdn-static.farfetch-contents.com)
30d
189 KiB
…sdks/coralogix-browser-sdk-1.4.6.js
(cdn-static.farfetch-contents.com)
30d
139 KiB
…480/welcome-page-image-mw.png
(cdn-static.farfetch-contents.com)
30d
137 KiB
…desktop/55438.client.9834e23….esnext.js
(cdn-static.farfetch-contents.com)
30d
71 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
…v2.00/NimbusSan….woff2
(cdn-static.farfetch-contents.com)
30d
34 KiB
…desktop/74873.client.f45d56e….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.7e20863….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/16613.client.c02ba02….esnext.js
(cdn-static.farfetch-contents.com)
30d
7 KiB
…desktop/97581.client.06aa5b6….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
…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
…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
…js/eventManager.min.js
(cdn-static.farfetch-contents.com)
30d
1 KiB
…desktop/27762.client.90582b5….esnext.js
(cdn-static.farfetch-contents.com)
30d
1 KiB
…js/setRUMUse….v1.js
(cdn-static.farfetch-contents.com)
30d
1 KiB
farfetch.com
1st party
115 KiB
…OwlZC/30ZUWk
(www.farfetch.com)
6h
115 KiB
mPulse
analytics
50 KiB
/boomerang/V8BTZ-CS5UD-BDWCH-VUP73-K8QTK
(s.go-mpulse.net)
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
/?shop=farfetch.com&sid=438b1ea8-12c0-43eb-8b3a-57200bb42a21
(beacon.riskified.com)
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.8 KiB
…desktop/89706.client.73bdaae….esnext.js:286:3783
(cdn-static.farfetch-contents.com)
Array.isArray
…desktop/10210.client.5d745a4….esnext.js
(cdn-static.farfetch-contents.com)
0.1 KiB
…desktop/10210.client.5d745a4….esnext.js:193:343280
(cdn-static.farfetch-contents.com)
@babel/plugin-transform-classes
…desktop/55438.client.9834e23….esnext.js
(cdn-static.farfetch-contents.com)
0.0 KiB
…desktop/55438.client.9834e23….esnext.js:1004:73608
(cdn-static.farfetch-contents.com)
@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
/fr/:92:1215
(www.farfetch.com)
Avoid an excessive DOM size 1,177 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,177
Maximum DOM Depth
label.ltr-3vrmm2 > div.ltr-1tyy8mh > svg.ltr-15kvush > use
<use xlink:href="#iconLoaded-checkboxEmpty">
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">
163
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
farfetch.com
1st party
1,311 ms
…OwlZC/30ZUWk
(www.farfetch.com)
1,000 ms
1,259 ms
…OwlZC/30ZUWk
(www.farfetch.com)
3,418 ms
52 ms
Google Tag Manager
tag-manager
1,174 ms
/gtm.js?id=GTM-5VWCDN
(www.googletagmanager.com)
2,453 ms
557 ms
/gtag/js?id=…
(www.googletagmanager.com)
4,423 ms
172 ms
/gtm.js?id=GTM-5VWCDN
(www.googletagmanager.com)
2,308 ms
145 ms
/gtm.js?id=GTM-5VWCDN
(www.googletagmanager.com)
3,759 ms
128 ms
/gtag/destination?id=…
(www.googletagmanager.com)
4,717 ms
64 ms
/gtm.js?id=GTM-5VWCDN
(www.googletagmanager.com)
3,887 ms
56 ms
/gtag/destination?id=…
(www.googletagmanager.com)
4,802 ms
52 ms
farfetch-contents.com
653 ms
…vitorino/vitorino.min.js
(cdn-static.farfetch-contents.com)
3,184 ms
179 ms
…desktop/27762.client.90582b5….esnext.js
(cdn-static.farfetch-contents.com)
3,062 ms
122 ms
…sdks/coralogix-browser-sdk-1.4.6.js
(cdn-static.farfetch-contents.com)
828 ms
116 ms
…desktop/57333.client.cf211d6….esnext.js
(cdn-static.farfetch-contents.com)
3,648 ms
74 ms
…js/cpuMonitor.v3.js
(cdn-static.farfetch-contents.com)
944 ms
56 ms
…desktop/77053.client.faa76a7….esnext.js
(cdn-static.farfetch-contents.com)
3,363 ms
55 ms
…desktop/10210.client.5d745a4….esnext.js
(cdn-static.farfetch-contents.com)
3,507 ms
51 ms
Avoid large layout shifts 3 layout shifts found
These are the largest layout shifts observed on the page. Each table item represents a single layout shift, and shows the element that shifted the most. Below each item are possible root causes that led to the layout shift. Some of these layout shifts may not be included in the CLS metric value due to windowing. Learn how to improve CLSCLS
Element
Layout shift score
NE PERDEZ PAS LE FIL Abonnez-vous pour recevoir des promotions, des sélections…
<div class="ltr-47c8sr e11lms100">
0.063
…OwlZC/30ZUWk
(www.farfetch.com)
A late network request adjusted the page layout
…desktop/69071.client.e964274….css
(cdn-static.farfetch-contents.com)
A late network request adjusted the page layout
…desktop/10210.client.b15253c….css
(cdn-static.farfetch-contents.com)
A late network request adjusted the page layout
…content/default.client.84f6fa3….css
(cdn-static.farfetch-contents.com)
A late network request adjusted the page layout
…sdks/coralogix-browser-sdk-1.4.6.js
(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/setRUMUse….v1.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
Désabonnez-vous à tout moment au bas de nos e-mails ou en répondant STOP à l'un…
<span>
0.010
MODE FEMME
<p class="_bdc4ef ltr-1ri59hw-Display" data-component="Display">
0.000
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,682.05 ms
1,272.38 ms
TL Creating SDKs marker
Measure
3,954.56 ms
2.47 ms
TL Queues marker
Measure
3,957.33 ms
7.13 ms
TL Window obj marker
Measure
3,964.56 ms
3.16 ms
TL - Start Bootstrap
Mark
2,681.45 ms
TL - Start getting uv
Mark
2,682.05 ms
TL - End getting uv
Mark
3,954.43 ms
TL - Start creating sdks
Mark
3,954.56 ms
TL - End creating sdks
Mark
3,957.03 ms
TL - End Bootstrap
Mark
3,957.20 ms
TL - Start creating queues
Mark
3,957.33 ms
TL - End creating queues
Mark
3,964.46 ms
TL - Start filling window obj
Mark
3,964.56 ms
TL - End filling window obj
Mark
3,967.72 ms
Avoids enormous network payloads Total size was 2,515 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
899.4 KiB
…desktop/10210.client.5d745a4….esnext.js
(cdn-static.farfetch-contents.com)
219.1 KiB
…480/welcome-page-image-ww.png
(cdn-static.farfetch-contents.com)
215.9 KiB
…480/welcome-page-image-kw-1-.png
(cdn-static.farfetch-contents.com)
188.6 KiB
…sdks/coralogix-browser-sdk-1.4.6.js
(cdn-static.farfetch-contents.com)
139.2 KiB
…480/welcome-page-image-mw.png
(cdn-static.farfetch-contents.com)
136.5 KiB
Google Tag Manager
tag-manager
278.6 KiB
/gtm.js?id=GTM-5VWCDN
(www.googletagmanager.com)
144.2 KiB
/gtag/js?id=…
(www.googletagmanager.com)
134.4 KiB
farfetch.com
1st party
222.7 KiB
…OwlZC/30ZUWk
(www.farfetch.com)
114.7 KiB
/fr/
(www.farfetch.com)
108.0 KiB
Forter
utility
173.1 KiB
…0c0275c12bca/script.js
(0c0275c12bca.cdn4.forter.com)
173.1 KiB
Avoid chaining critical requests 32 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,627.161 ms
Initial Navigation
/fr/
(www.farfetch.com)
…desktop/10210.client.5d745a4….esnext.js
(cdn-static.farfetch-contents.com)
- 154.101 ms, 219.13 KiB
…desktop/83627.client.9d013c5….esnext.js
(cdn-static.farfetch-contents.com)
- 335.57 ms, 37.50 KiB
…desktop/57333.client.cf211d6….esnext.js
(cdn-static.farfetch-contents.com)
- 158.694 ms, 8.78 KiB
…desktop/2316.client.8b33843….esnext.js
(cdn-static.farfetch-contents.com)
- 159.606 ms, 5.10 KiB
…desktop/64738.client.3a90818….esnext.js
(cdn-static.farfetch-contents.com)
- 53.635 ms, 5.33 KiB
…desktop/42512.client.eb0746b….esnext.js
(cdn-static.farfetch-contents.com)
- 158.299 ms, 4.19 KiB
…desktop/89706.client.73bdaae….esnext.js
(cdn-static.farfetch-contents.com)
- 95.233 ms, 16.93 KiB
…desktop/55438.client.9834e23….esnext.js
(cdn-static.farfetch-contents.com)
- 116.833 ms, 71.09 KiB
…desktop/78626.client.b9cbbc5….esnext.js
(cdn-static.farfetch-contents.com)
- 80.896 ms, 5.20 KiB
…desktop/97581.client.06aa5b6….esnext.js
(cdn-static.farfetch-contents.com)
- 156.316 ms, 6.43 KiB
…desktop/10210.client.b15253c….css
(cdn-static.farfetch-contents.com)
- 162.823 ms, 4.68 KiB
…desktop/44119.client.20f3f1b….esnext.js
(cdn-static.farfetch-contents.com)
- 94.931 ms, 4.08 KiB
…desktop/74873.client.f45d56e….esnext.js
(cdn-static.farfetch-contents.com)
- 86.355 ms, 28.51 KiB
…desktop/96451.client.6d7cba9….esnext.js
(cdn-static.farfetch-contents.com)
- 144.269 ms, 4.44 KiB
…desktop/63309.client.432c8dd….esnext.js
(cdn-static.farfetch-contents.com)
- 157.181 ms, 14.60 KiB
…desktop/49408.client.df2659a….esnext.js
(cdn-static.farfetch-contents.com)
- 84.649 ms, 2.82 KiB
…desktop/63834.client.555f284….esnext.js
(cdn-static.farfetch-contents.com)
- 95.687 ms, 4.18 KiB
…desktop/57864.client.b68907d….esnext.js
(cdn-static.farfetch-contents.com)
- 84.772 ms, 3.70 KiB
…desktop/66264.client.342f429….esnext.js
(cdn-static.farfetch-contents.com)
- 94.608 ms, 4.76 KiB
…desktop/803.client.8138d91….esnext.js
(cdn-static.farfetch-contents.com)
- 155.255 ms, 26.63 KiB
…content/default.client.832b49e….esnext.js
(cdn-static.farfetch-contents.com)
- 156.437 ms, 10.44 KiB
…content/default.client.84f6fa3….css
(cdn-static.farfetch-contents.com)
- 142.568 ms, 3.21 KiB
…OwlZC/30ZUWk
(www.farfetch.com)
- 43.746 ms, 114.73 KiB
…desktop/69071.client.e964274….css
(cdn-static.farfetch-contents.com)
- 163.907 ms, 2.20 KiB
…sdks/coralogix-browser-sdk-1.4.6.js
(cdn-static.farfetch-contents.com)
- 91.475 ms, 139.18 KiB
…js/cpuMonitor.v3.js
(cdn-static.farfetch-contents.com)
- 99.673 ms, 2.76 KiB
…v2.00/NimbusSan….woff2
(cdn-static.farfetch-contents.com)
- 138.081 ms, 33.59 KiB
…js/setRUMUse….v1.js
(cdn-static.farfetch-contents.com)
- 99.241 ms, 0.75 KiB
…v2.00/FarfetchB….woff2
(cdn-static.farfetch-contents.com)
- 28.635 ms, 50.11 KiB
…v2.00/FarfetchBasis-Bold.woff2
(cdn-static.farfetch-contents.com)
- 351.703 ms, 48.97 KiB
…js/eventManager.min.js
(cdn-static.farfetch-contents.com)
- 55.139 ms, 0.83 KiB
…desktop/runtime.client.7e20863….esnext.js
(cdn-static.farfetch-contents.com)
- 161.901 ms, 12.12 KiB
More information about the performance of your application. These numbers don't directly affect the Performance score.
Passed audits (18)
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://cdn-images.farfetch-contents.com" 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://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.
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.
100
Accessibility
These checks highlight opportunities to improve the accessibility of your web app. Automatic detection can only detect a subset of issues and does not guarantee the accessibility of your web app, so manual testing is also encouraged.
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.
Links are distinguishable without relying on color.
Low-contrast text is difficult or impossible for many users to read. Link text that is discernible improves the experience for users with low vision. Learn how to make links distinguishable.
Links have a discernible name
Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.
Lists contain only <li> elements and script supporting elements (<script> and <template>).
Screen readers have a specific way of announcing lists. Ensuring proper list structure aids screen reader output. Learn more about proper list structure.
List items (<li>) are contained within <ul>, <ol> or <menu> parent elements
Screen readers require list items (<li>) to be contained within a parent <ul>, <ol> or <menu> to be announced properly. Learn more about proper list structure.
No element has a [tabindex] value greater than 0
A value greater than 0 implies an explicit navigation ordering. Although technically valid, this often creates frustrating experiences for users who rely on assistive technologies. Learn more about the tabindex attribute.
Touch targets have sufficient size and spacing.
Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.
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.
78
Best Practices
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
/boomerang/V8BTZ-CS5UD-BDWCH-VUP73-K8QTK:10:11504
(s.go-mpulse.net)
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
/fr/:1:0
(www.farfetch.com)
Refused to execute script from 'https://pagead2.googlesyndication.com/pagead/conversion/992356468/?random=1739383261401&cv=11&fst=1739383261401&bg=ffffff&guid=ON&async=1&gtm=45be5280v871604564z872394093za201zb887643346&gcs=G101&gcd=13q3r3q3q5l1&dma_cps=-&dma=0&tag_exp=101732279~101732281~102067808~102482432~102539968~102558064~102587591~102605417&u_w=800&u_h=600&url=https%3A%2F%2Fwww.farfetch.com%2Ffr%2F&label=hCbTCPPi3a8BEPTQmNkD&hn=www.googleadservices.com&frm=0&tiba=FARFETCH%20France%20%7C%20La%20r%C3%A9f%C3%A9rence%20mondiale%20du%20luxe%20contemporain&value=0&bttype=purchase&npa=1&pscdl=denied&uaa=x86&uab=64&uafvl=HeadlessChrome%3B131.0.6778.264%7CChromium%3B131.0.6778.264%7CNot_A%2520Brand%3B24.0.0.0&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.
/fr/:1:0
(www.farfetch.com)
The fetch of the config file resulted in a network error: ERR_NAME_NOT_RESOLVED
/fr/: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
…marketing-tracking-library/tracking-library-stable.min.js
(cdn-static.farfetch-contents.com)
…marketing-tracking-library/tracking-library.min.js.map
(cdn-static.farfetch-contents.com)
SyntaxError: Unexpected token '/', "/*! For li"... is not valid JSON
Riskified
utility
/?shop=farfetch.com&sid=438b1ea8-12c0-43eb-8b3a-57200bb42a21
(beacon.riskified.com)
…ZmFyZmV0Y2guY29t/NDM4YjFlY…
(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/88039037019
Not applicable (2)
Show Hide
Redirects HTTP traffic to HTTPS
Make sure that you redirect all HTTP traffic to HTTPS in order to enable secure web features for all your users. Learn more.
Document uses legible font sizes
Font sizes less than 12px are too small to be legible and require mobile visitors to “pinch to zoom” in order to read. Strive to have >60% of page text ≥12px. Learn more about legible font sizes.
100
SEO
These checks ensure that your page is following basic search engine optimization advice. There are many additional factors Lighthouse does not score here that may affect your search ranking, including performance on Core Web Vitals. Learn more about Google Search Essentials.
Additional items to manually check (1)
Show Hide
Structured data is valid
Run the Structured Data Testing Tool and the Structured Data Linter to validate structured data. Learn more about Structured Data.
Run these additional validators on your site to check additional SEO best practices.
Passed audits (10)
Show Hide
Page isn’t blocked from indexing
Search engines are unable to include your pages in search results if they don't have permission to crawl them. Learn more about crawler directives.
Document has a <title> element
The title gives screen reader users an overview of the page, and search engine users rely on it heavily to determine if a page is relevant to their search. Learn more about document titles.
Document has a meta description
Meta descriptions may be included in search results to concisely summarize page content. Learn more about the meta description.
Page has successful HTTP status code
Pages with unsuccessful HTTP status codes may not be indexed properly. Learn more about HTTP status codes.
Links have descriptive text
Descriptive link text helps search engines understand your content. Learn how to make links more accessible.
Links are crawlable
Search engines may use href attributes on links to crawl websites. Ensure that the href attribute of anchor elements links to an appropriate destination, so more pages of the site can be discovered. Learn how to make links crawlable
robots.txt is valid
If your robots.txt file is malformed, crawlers may not be able to understand how you want your website to be crawled or indexed. Learn more about robots.txt.
Image elements have [alt] attributes
Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the alt attribute.
Document has a valid hreflang
hreflang links tell search engines what version of a page they should list in search results for a given language or region. Learn more about hreflang.
Document has a valid rel=canonical
Canonical links suggest which URL to show in search results. Learn more about canonical links.