Skip to content
https://oanda.com

Lighthouse Desktop

· 0 checks — Desktop Lighthouse audit -- Performance, Accessibility, Best Practices, and SEO category breakdown.
SCORE
0
GRADE
FIX
0
REVIEW
0
PASS
0
INFO
0

Detailed Report

Audit breakdown by category with detailed findings.

90

Performance

Insights

Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Polyfills and transforms enable older browsers to use new JavaScript features. However, many aren't necessary for modern browsers. Consider modifying your JavaScript build process to not transpile Baseline features, unless you know you must support older browsers. Learn why most sites can deploy ES6+ code without transpiling

Why this matters

Performance issues directly impact user engagement and conversion rates.

3rd party code can significantly impact load performance. Reduce and defer loading of 3rd party code to prioritize your page's content.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Your first network request is the most important. Reduce its latency by avoiding redirects, ensuring a fast server response, and enabling text compression.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Consider setting font-display to swap or optional to ensure text is consistently visible. swap can be further optimized to mitigate layout shifts with font metric overrides.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URLEst Savings
fonts.gstatic.com/s/roboto/v51/KFO7CnqEu92Fr1ME7kSn66aGLdTylUAMa3yUBHMdazQ.woff250 ms
/s/opensans/v44/memvYaGs126MiZpBA-UvWbX2vVnXBbObj2OVTS-mu...45 ms
/s/opensans/v44/memvYaGs126MiZpBA-UvWbX2vVnXBbObj2OVTSGmu...25 ms

Reducing the download time of images can improve the perceived load time of the page and LCP. Learn more about optimizing image size

Why this matters

Performance issues directly impact user engagement and conversion rates.

URLResource SizeEst Savings
div.flex-column > div.paragraph__header__description > div.d-none > img div.flex-column > div.paragraph__header__description > div.d-none > img
www.oanda.com/eu-en/sites/default/files/media/image/2026-01/header-en_0.jpg125.8 KiB73.3 KiB
div.section-elements > div.paragraph > div.element-image--desktop > img.image-style-_90-auto div.section-elements > div.paragraph > div.element-image--desktop > img.image-style-_90-auto
/eu-en/sites/default/files/styles/690_auto/public/media/i...21.5 KiB13.2 KiB
div.section-elements > div.paragraph > div.element-image--desktop > img.image-style-_90-auto div.section-elements > div.paragraph > div.element-image--desktop > img.image-style-_90-auto
/eu-en/sites/default/files/styles/690_auto/public/media/i...11.8 KiB7.3 KiB

Optimize LCP by making the LCP image discoverable from the HTML immediately, and avoiding lazy-loading

Why this matters

Performance issues directly impact user engagement and conversion rates.

lhId: page-0-IMG
nodeLabel: div.flex-column > div.paragraph__header__description > div.d-none > img
path: 1,HTML,1,BODY,6,MAIN,1,DIV,0,DIV,0,ARTICLE,0,DIV,0,SECTION,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,IMG
selector: div.flex-column > div.paragraph__header__description > div.d-none > img
snippet: <img loading="lazy" src="/eu-en/sites/default/files/media/image/2026-01/header-en_0.jpg" width="1920" height="857" alt="">

Avoid chaining critical requests by reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.

Why this matters

Performance issues directly impact user engagement and conversion rates.

description: [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints help the browser establish a connection earlier in the page load, saving time when the first request for that origin is made. The following are the origins that the page preconnected to.
title: Preconnected origins
description: Add [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints to your most important origins, but try to use no more than 4.
title: Preconnect candidates

Requests are blocking the page's initial render, which may delay LCP. Deferring or inlining can move these network requests out of the critical path.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URLTransfer SizeDuration
proxy.tms.pl/g4/g4.js?43.7 KiB302 ms
/css?family=Open+Sans:300,400,400i,600,700|Roboto:400,400...2.5 KiB61 ms
fonts.googleapis.com/icon?family=Material+Icons817 B269 ms
/eu-en/sites/default/files/css/css_M-DU-yKnTOFN__nflzIoDd...4.2 KiB
/eu-en/sites/default/files/css/css_OKyVQ-uh_EFJW3RFWX9Ju1...575 B
/eu-en/sites/default/files/css/css_3UpPdXfq_yy2PDElOj--gP...80.3 KiB247 ms
/eu-en/sites/default/files/css/css_hJcseH0tKhY80-LWR5xt1V...2.6 KiB
use.typekit.net/ubr8mcz.css1.2 KiB205 ms
/p.css?s=1&k=ubr8mcz&ht=tk&f=24553.24554.24558.24559.2453...172 B236 ms

A long cache lifetime can speed up repeat visits to your page. Learn more about caching.

Why this matters

Performance issues directly impact user engagement and conversion rates.

RequestCache TTLTransfer Size
cdn.optimizely.com/js/23275990004.js120.0 s96.3 KiB
connect.facebook.net/en_US/fbevents.js1200.0 s96.6 KiB
sm.tms.pl/static/sm.js7200.0 s46.0 KiB
/signals/config/632505510231268?v=2.9.303&r=stable&domain...1200.0 s36.4 KiB
www.google-analytics.com/analytics.js7200.0 s20.9 KiB
www.tradingview-widget.com/widget/broker-rating.js?locale=en&broker=oanda14400.0 s16.4 KiB
tdn.r42tag.com/lib/1423-v1.js14400.0 s13.6 KiB
www.oanda.com/cdn-cgi/challenge-platform/h/b/scripts/jsd/0b8fb825cb67/main.js?14400.0 s11.7 KiB
sm.tms.pl/static/chunk/sm_war.20de86dae41ade6a0ba1.js7200.0 s2.4 KiB
/dynamic/0l7rn25gall1lmg9/custom.js?uri=%2Feu-en&location...7200.0 s1.1 KiB
/api/r.gif?uri=%2Feu-en&location=www.oanda.com&uuid=19db2...0.0 ms442 B
tdn.r42tag.com/stats?siteId=1423&counterId=1&cb=17768195286320.0 ms395 B
/p.css?s=1&k=ubr8mcz&ht=tk&f=24553.24554.24558.24559.2453...604800.0 s172 B
/a?v=3&t=l&pid=2066271668&rv=64h1&tag_exp=0~115938466~115...0.0 ms11 B

These insights are also available in the Chrome DevTools Performance Panel - record a trace to view more detailed information.

Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 534 ms
URLTime Spent
oanda.com/251 ms
www.oanda.com/242 ms
www.oanda.com/eu-en/41 ms
www.oanda.com/eu-en0.0 ms

Time to Interactive is the amount of time it takes for the page to become fully interactive. Learn more about the Time to Interactive metric.

Why this matters

Performance issues directly impact user engagement and conversion rates.

TTI

Diagnostics

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 160 ms 71.1 KiB
URLTransfer SizeEst Savings
/eu-en/sites/default/files/css/css_3UpPdXfq_yy2PDElOj--gP...80.0 KiB71.1 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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 80 ms 651.7 KiB
URLTransfer SizeEst Savings
/eu-en/sites/default/files/js/js_WEIMI6IiOL2a0Z8TMFTkbivv...131.9 KiB88.3 KiB
www.googletagmanager.com/gtag/destination?id=AW-11107549976&cx=c&gtm=4e64h1143.7 KiB70.7 KiB
www.googletagmanager.com/gtag/destination?id=AW-940337901&cx=c&gtm=4e64h1144.1 KiB70.2 KiB
www.googletagmanager.com/gtag/js?id=G-6PG6QGNWP6&cx=c&gtm=4e64h1177.0 KiB69.2 KiB
www.googletagmanager.com/gtag/js?id=G-Q2HXMSGECM&cx=c&gtm=4e64h1173.9 KiB65.8 KiB
www.googletagmanager.com/gtag/destination?id=DC-12816379&cx=c&gtm=4e64h1130.0 KiB64.9 KiB
www.googletagmanager.com/gtag/js?id=G-40RVRRL679&cx=c&gtm=4e64h1161.2 KiB61.3 KiB
www.googletagmanager.com/gtm.js?id=GTM-TLC257H184.6 KiB59.4 KiB
connect.facebook.net/en_US/fbevents.js96.5 KiB43.3 KiB
cdn.optimizely.com/js/23275990004.js95.7 KiB36.5 KiB
sm.tms.pl/static/sm.js45.5 KiB22.1 KiB

Many navigations are performed by going back to a previous page, or forwards again. The back/forward cache (bfcache) can speed up these return navigations. Learn more about the bfcache

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failure reasonFailure type
Pages with WebSocket cannot enter back/forward cache.Pending browser support

Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensions

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL
Logo div.brand-logo > a.brand-link > div.logo-wrapper > img
www.oanda.com/eu-en/themes/custom/pattern_theme/assets/logo.svg
Logo div.brand-logo > a.brand-link > div.logo-wrapper > img
www.oanda.com/eu-en/themes/custom/pattern_theme/assets/logo.svg

More information about the performance of your application. These numbers don't directly affect the Performance score.

●Max Potential First Input Delay 70 ms
●Layout shift culprits
●Optimize DOM size
●Forced reflow
●LCP breakdown
●Modern HTTP
●Optimize viewport for mobile
●Minify CSS
●Minify JavaScript
●Avoids enormous network payloads Total size was 2,216 KiB
●User Timing marks and measures 235 user timings
●JavaScript execution time 0.5 s
●Minimizes main-thread work 1.4 s
●Avoid long main-thread tasks 5 long tasks found
●Avoid non-composited animations 11 animated elements found
●Network Requests
●Network Round Trip Times 50 ms
●Server Backend Latencies 180 ms
●Tasks
●Diagnostics
●Metrics
●Screenshot Thumbnails
●Final Screenshot
●Script Treemap Data
●Resources Summary
●Initial server response time was short Root document took 120 ms
●Avoid large layout shifts 1 layout shift found
○INP breakdown
94

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.

Contrast

Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Find out more div.paragraph > div > div.element-link > a.link
Find out more div.paragraph > div > div.element-link > a.link
Find out more div.paragraph > div > div.element-link > a.link
Find out more div.paragraph > div > div.element-link > a.link
Find out more div.paragraph > div > div.element-link > a.link
Find out more div.paragraph > div > div.element-link > a.link
1.174 tr.border-0 > td.py-2 > a.fc-primary-1 > span.instrument-sell
1.175 tr.border-0 > td.p-2 > a.fc-primary-1 > span.instrument-buy
1.351 tr.border-0 > td.py-2 > a.fc-primary-1 > span.instrument-sell
1.351 tr.border-0 > td.p-2 > a.fc-primary-1 > span.instrument-buy
-0.07 % tr.border-0 > td.change-column > a.fc-primary-1 > span.instrument-change
-0.09 % tr.border-0 > td.change-column > a.fc-primary-1 > span.instrument-change
0.780 tr.border-0 > td.py-2 > a.fc-primary-1 > span.instrument-sell
0.781 tr.border-0 > td.p-2 > a.fc-primary-1 > span.instrument-buy
0.716 tr.border-0 > td.py-2 > a.fc-primary-1 > span.instrument-sell
0.716 tr.border-0 > td.p-2 > a.fc-primary-1 > span.instrument-buy
0.590 tr.border-0 > td.py-2 > a.fc-primary-1 > span.instrument-sell
0.591 tr.border-0 > td.p-2 > a.fc-primary-1 > span.instrument-buy
-1.13 % tr.border-0 > td.change-column > a.fc-primary-1 > span.instrument-change
-0.84 % tr.border-0 > td.change-column > a.fc-primary-1 > span.instrument-change
76284.000 tr.border-0 > td.py-2 > a.fc-primary-1 > span.instrument-sell
76345.000 tr.border-0 > td.p-2 > a.fc-primary-1 > span.instrument-buy
2322.300 tr.border-0 > td.py-2 > a.fc-primary-1 > span.instrument-sell
2327.850 tr.border-0 > td.p-2 > a.fc-primary-1 > span.instrument-buy
55.420 tr.border-0 > td.py-2 > a.fc-primary-1 > span.instrument-sell
55.950 tr.border-0 > td.p-2 > a.fc-primary-1 > span.instrument-buy
-1.90 % tr.border-0 > td.change-column > a.fc-primary-1 > span.instrument-change
-0.97 % tr.border-0 > td.change-column > a.fc-primary-1 > span.instrument-change

These are opportunities to improve the legibility of your content.

Names and labels

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.node__content > div.paragraph > div.paragraph > a.d-block div.node__content > div.paragraph > div.paragraph > a.d-block
div.node__content > div.paragraph > div.paragraph > a.d-block div.node__content > div.paragraph > div.paragraph > a.d-block
div.node__content > div.paragraph > div.paragraph > a.d-block div.node__content > div.paragraph > div.paragraph > a.d-block

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

Screen readers have features to make navigating tables easier. Ensuring that `<td>` elements in a large table (3 or more cells in width and height) have an associated table header may improve the experience for screen reader users. Learn more about table headers.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Name of instrument Change (%) Sell Buy Spread US500 0.16 % 7137.100 7137.800 … div.row > div#myTabContent > div#popular-155401741 > table.quotes-table
○Interactive controls are keyboard focusable
○Interactive elements indicate their purpose and state
○The page has a logical tab order
○Visual order on the page follows DOM order
○User focus is not accidentally trapped in a region
○The user's focus is directed to new content added to the page
○HTML5 landmark elements are used to improve navigation
○Offscreen content is hidden from assistive technology
○Custom controls have associated labels
○Custom controls have ARIA roles
●`[aria-*]` attributes match their roles
●`[aria-hidden="true"]` is not present on the document `<body>`
●`[role]`s have all required `[aria-*]` attributes
●Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
●`[role]`s are contained by their required parent element
●`[role]` values are valid
●`[aria-*]` attributes have valid values
●`[aria-*]` attributes are valid and not misspelled
●Buttons have an accessible name
●Image elements have `[alt]` attributes
●Form elements have associated labels
●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
●ARIA attributes are used as specified for the element's role
●`[aria-hidden="true"]` elements do not contain focusable descendents
●Elements use only permitted ARIA attributes
●Document has a `<title>` element
●`<html>` element has a `[lang]` attribute
●`<html>` element has a valid value for its `[lang]` attribute
●Links are distinguishable without relying on color.
●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
●No element has a `[tabindex]` value greater than 0
●Touch targets have sufficient size and spacing.
●Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
●`[lang]` attributes have a valid value
●Heading elements appear in a sequentially-descending order
●Document has a main landmark.
●Deprecated ARIA roles were not used
●ARIA IDs are unique
●All heading elements contain content.
●Identical links have the same purpose.
●Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements have accessible names
○Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
○ARIA input fields have accessible names
○ARIA `meter` elements have accessible names
○ARIA `progressbar` elements have accessible names
○Elements with the `role=text` attribute do not have focusable descendents.
○ARIA toggle fields have accessible names
○ARIA `tooltip` elements have accessible names
○ARIA `treeitem` elements have accessible names
○The page contains a heading, skip link, or landmark region
○`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
○Definition list items are wrapped in `<dl>` elements
○No form fields have multiple labels
○`<frame>` or `<iframe>` elements have a title
○`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.
○Input buttons have discernible text.
○`<input type="image">` elements have `[alt]` text
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○Select elements have associated label elements.
○Skip links are focusable.
○`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
○`<video>` elements contain a `<track>` element with `[kind="captions"]`
○Tables have different content in the summary attribute and `<caption>`.
○Uses ARIA roles only on compatible elements
○Image elements do not have `[alt]` attributes that are redundant text.
○Elements with visible text labels have matching accessible names.
73

Best Practices

General

Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Deprecation / WarningSource
SharedStorage
www.oanda.com/cdn-cgi/challenge-platform/scripts/jsd/main.js
StorageType.persistent is deprecated. Please use standardized navigator.storage instead.
www.oanda.com/cdn-cgi/challenge-platform/scripts/jsd/main.js
Fledge
www.oanda.com/cdn-cgi/challenge-platform/scripts/jsd/main.js

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

SourceDescription
www.googletagmanager.com/gtag/js?id=G-40RVRRL679&cx=c&gtm=4e64h1 line 662, col 244
Connecting to 'https://sst.oanda.com/g/collect?v=2&tid=G-40RVRRL679&gtm=45je64h1v9218050320z8899019973za20gzb899019973zd899019973&_p=1776819528333&gcs=G101&gcd=13p3t3p2p5l1&npa=1&dma_cps=-&dma=1&ecid=1275286211&_eu=AAAAAGA&_fplc=0&are=1&cid=1769388209.1776819530&frm=0&pscdl=denied&rcb=15&sr=800x600&uaa=x86&uab=64&uafvl=Chromium%3B147.0.7727.101%7CNot.A%252FBrand%3B8.0.0.0&uam=&uamb=0&uap=macOS&uapv=10.15.7&uaw=0&ul=en-us&ur=ES-MD&sst.rnd=274612671.1776819530&sst.etld=google.es&sst.gcsub=region1&sst.tft=1776819528333&sst.lpc=247984537&sst.navt=n&sst.ude=0&sst.sw_exp=1&gaf=2&_s=1&tag_exp=0~115938466~115938469~117266400~117512543&sid=1776819528&sct=1&seg=0&dl=https%3A%2F%2Fwww.oanda.com%2Feu-en&dt=Online%20Forex%2C%20Shares%20%26%20Crypto%20CFD%20Trading%20Broker%20%7C%20OANDA&_tu=LA&en=page_view&_fv=1&_ss=1&ep.gtm_id=GTM-TLC257H&epn.timestamp=1776819528592&tfd=3028&richsstsse' violates the following Content Security Policy directive: "connect-src 'self' vc-service.saleago.com sm.tms.pl logx.optimizely.com wss://master-tmspl.test.tms.pl cdn.cookielaw.org www.google-analytics.com *.google-analytics.com geolocation.onetrust.com *.googlesyndication.com *.tms.pl privacyportal-eu.onetrust.com bat.bing.net oanda.com wss://tms.pl region1.analytics.google.com bat.bing.com www.google.com google.com connect.facebook.net static.hotjar.com *.hotjar.com conntect.facebook.net vc.hotjar.io green-panda-h7erwbabgq-lm.a.run.app blue-panda-446190479072.europe-central2.run.app https://premium.tmskantor.pl event-hub-01.oanda.com https://ipapi.co". The action has been blocked.
www.oanda.com/eu-en/report-uri/enforce
Failed to load resource: net::ERR_FAILED
/syncResponse?ca_site=1423&ca_partner=7&ca_cookie=e709922...
Failed to load resource: the server responded with a status of 400 ()
www.googletagmanager.com/gtag/js?id=G-40RVRRL679&cx=c&gtm=4e64h1 line 662, col 244
Fetch API cannot load https://sst.oanda.com/g/collect?v=2&tid=G-40RVRRL679&gtm=45je64h1v9218050320z8899019973za20gzb899019973zd899019973&_p=1776819528333&gcs=G101&gcd=13p3t3p2p5l1&npa=1&dma_cps=-&dma=1&ecid=1275286211&_eu=AAAAAGA&_fplc=0&are=1&cid=1769388209.1776819530&frm=0&pscdl=denied&rcb=15&sr=800x600&uaa=x86&uab=64&uafvl=Chromium%3B147.0.7727.101%7CNot.A%252FBrand%3B8.0.0.0&uam=&uamb=0&uap=macOS&uapv=10.15.7&uaw=0&ul=en-us&ur=ES-MD&sst.rnd=274612671.1776819530&sst.etld=google.es&sst.gcsub=region1&sst.tft=1776819528333&sst.lpc=247984537&sst.navt=n&sst.ude=0&sst.sw_exp=1&gaf=2&_s=1&tag_exp=0~115938466~115938469~117266400~117512543&sid=1776819528&sct=1&seg=0&dl=https%3A%2F%2Fwww.oanda.com%2Feu-en&dt=Online%20Forex%2C%20Shares%20%26%20Crypto%20CFD%20Trading%20Broker%20%7C%20OANDA&_tu=LA&en=page_view&_fv=1&_ss=1&ep.gtm_id=GTM-TLC257H&epn.timestamp=1776819528592&tfd=3028&richsstsse. Refused to connect because it violates the document's Content Security Policy.
www.googletagmanager.com/gtm.js?id=GTM-TLC257H line 265, col 503
Uncaught [object Object]
www.googletagmanager.com/gtm.js?id=GTM-TLC257H line 265, col 503
Uncaught [object Object]

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Issue type
Content security policy
●Uses HTTPS
●Avoids third-party cookies
●Allows users to paste into input fields
●Avoids requesting the geolocation permission on page load
●Avoids requesting the notification permission on page load
●Displays images with correct aspect ratio
●Serves images with appropriate resolution
●Page has the HTML doctype
●Properly defines charset
●Ensure CSP is effective against XSS attacks
●Use a strong HSTS policy
●Ensure proper origin isolation with COOP
●Mitigate DOM-based XSS with Trusted Types
●Detected JavaScript libraries
●Page has valid source maps
○Redirects HTTP traffic to HTTPS
○Mitigate clickjacking with XFO or CSP
92

SEO

These checks ensure that your page is following basic search engine optimization advice. There are many additional factors Lighthouse does not score here that may affect your search ranking, including performance on Core Web Vitals. Learn more about Google Search Essentials.

Crawling and Indexing

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Uncrawlable Link
DEMO div.header-main-navigation__top-bar__controls > div.header-main-navigation__top-bar__controls__open-account > div.header-main-navigation__top-bar__controls__open-account > a.custom-btn--primary
Language switcher popup div.header-section__main__container__row > div.header-main-navigation__top-bar__controls > div.language-switcher > a.custom-btn
Demo Open demo account div.hamburger-menu__mobile > div.hamburger-menu__mobile__open-account > div.header-main-navigation__top-bar__controls__open-account > a.custom-btn--primary

To appear in search results, crawlers need access to your app.

○Structured data is valid
●Page isn’t blocked from indexing
●Document has a `<title>` element
●Document has a meta description
●Page has successful HTTP status code
●Links have descriptive text
●robots.txt is valid
●Image elements have `[alt]` attributes
●Document has a valid `hreflang`
●Document has a valid `rel=canonical`

Send Feedback