Lighthouse Mobile

· 0 checks — Mobile Lighthouse audit -- Performance, Accessibility, Best Practices, and SEO category breakdown.

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Detailed Report

Audit breakdown by category with detailed findings.

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.

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

value: no origins were preconnected

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

value: No additional origins are good candidates for preconnecting

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.

Request	Cache TTL	Transfer Size
app.usercentrics.eu/session/1px.png?settingsId=P5B3ZD8GUH62fz	1800.0 s	1.0 KiB

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.

	URL	Resource Size	Est Savings
Perpetual Futures `div#EUInvestDuplex > div.css-197qm98 > picture > img.css-jkroxf`	/ilblxxee70tt/Rg0YNcbKE33nUCBg3e0mJ/b0e0438381e2f29ee265a...	313.3 KiB	265.2 KiB
Robinhood Crypto `div.css-fsstbj > div.backgroundSection > picture > img.css-9s6vxj`	/ilblxxee70tt/6JTT2Lf1qlja5mkueKmAxp/1536258be91df383a7fa...	175.9 KiB	127.6 KiB

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

The maximum potential First Input Delay that your users could experience is the duration of the longest task. Learn more about the Maximum Potential First Input Delay metric.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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: 2.4 s

URL	Time Spent
www.robinhood.com/	1.1 s
robinhood.com/	1.1 s
robinhood.com/us/en/	168 ms
robinhood.com/eu/fr/	0.0 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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 532 ms

URL	Time Spent
robinhood.com/eu/fr/	632 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

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Total CPU Time	Script Evaluation	Script Parse
/assets/generated_assets/brand/_next/static/chunks/pages/...	1.8 s	1.5 s	190 ms
Unattributable	942 ms	180 ms	0.0 ms
/assets/generated_assets/webapp/vendor/user_centrics/3.33...	632 ms	497 ms	60 ms
robinhood.com/eu/fr/	495 ms	4.3 ms	0.9 ms
/assets/generated_assets/brand/_next/static/chunks/ab5b22...	302 ms	2.0 ms	299 ms
/assets/generated_assets/brand/_next/static/chunks/main-7...	259 ms	197 ms	50 ms
/assets/generated_assets/brand/_next/static/chunks/23740-...	171 ms	79 ms	91 ms
/assets/generated_assets/brand/_next/static/chunks/6030-a...	98 ms	36 ms	2.6 ms
/assets/generated_assets/brand/_next/static/chunks/93794-...	94 ms	1.6 ms	92 ms
/assets/generated_assets/brand/_next/static/chunks/6389-e...	71 ms	0.9 ms	28 ms
/assets/generated_assets/brand/_next/static/chunks/46006....	64 ms	50 ms	4.8 ms

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 work

Why this matters

Performance issues directly impact user engagement and conversion rates.

Category	Time Spent
Script Evaluation	2.7 s
Other	955 ms
Script Parsing & Compilation	859 ms
Style & Layout	326 ms
Garbage Collection	91 ms
Rendering	89 ms
Parse HTML & CSS	77 ms

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: 0.0 ms 10.4 KiB

URL	Transfer Size	Est Savings
.css-evezer { box-sizing: border-box; margin: 0px auto; max-width: 1440px; min-width: 1049px; … } …	14.1 KiB	10.4 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: 0.0 ms 964.4 KiB

URL	Transfer Size	Est Savings
/assets/generated_assets/brand/_next/static/chunks/ab5b22...	597.8 KiB	435.4 KiB
/assets/generated_assets/brand/_next/static/chunks/pages/...	524.4 KiB	339.3 KiB
/assets/generated_assets/brand/_next/static/chunks/93794-...	150.1 KiB	119.1 KiB
/assets/generated_assets/webapp/vendor/user_centrics/3.33...	142.0 KiB	70.6 KiB

Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Transfer Size
/ilblxxee70tt/1muiYk5dsnWO50wS5uCWuZ/2ad4d5b171d33c360b59...	2.2 MiB
/ilblxxee70tt/TfyKsPXEjAEiKIDQ10baG/8e6014037aecfe4f7fe43...	861.4 KiB
/assets/generated_assets/brand/_next/static/chunks/ab5b22...	598.6 KiB
/assets/generated_assets/brand/_next/static/chunks/pages/...	525.2 KiB
/ilblxxee70tt/Rg0YNcbKE33nUCBg3e0mJ/b0e0438381e2f29ee265a...	314.0 KiB
/ilblxxee70tt/7CNzj0pFTdllv25t9537N4/e9ee1203c269519f664c...	229.0 KiB
/ilblxxee70tt/6JTT2Lf1qlja5mkueKmAxp/1536258be91df383a7fa...	176.5 KiB
/assets/generated_assets/brand/_next/static/chunks/93794-...	150.9 KiB
/assets/generated_assets/webapp/vendor/user_centrics/3.33...	142.9 KiB
/ilblxxee70tt/6DXGzd2boLMbeX1uooWWrf/693b35c0bd1e49baaf60...	124.0 KiB

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

●Layout shift culprits

●Optimize DOM size

●Font display

●Forced reflow

●LCP breakdown

●Modern HTTP

●Render blocking requests

●Optimize viewport for mobile

●Minify CSS

●Minify JavaScript

●User Timing marks and measures 7 user timings

●Avoid long main-thread tasks 13 long tasks found

●Image elements have explicit `width` and `height`

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 30 ms

●Server Backend Latencies 330 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

●Avoid large layout shifts 4 layout shifts found

○INP breakdown

○LCP request discovery

○Avoid non-composited animations

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
Investir `div.text-column > div.text-content > div.label > h3.css-10drz4f`
Perpétuels `div.text-column > div.text-content > div.label > h3.css-10drz4f`

These are opportunities to improve the legibility of your content.

Navigation

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Investir `div.text-column > div.text-content > div.label > h3.css-10drz4f`
Perpétuels `div.text-column > div.text-content > div.label > h3.css-10drz4f`

These are opportunities to improve keyboard navigation in your application.

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.css-9uj12p > ul.css-98zc54 > li.css-nvozuq > a.css-1unrqcp `div.css-9uj12p > ul.css-98zc54 > li.css-nvozuq > a.css-1unrqcp`
div.css-9uj12p > ul.css-98zc54 > li.css-nvozuq > a.css-1unrqcp `div.css-9uj12p > ul.css-98zc54 > li.css-nvozuq > a.css-1unrqcp`
div.css-9uj12p > ul.css-98zc54 > li.css-nvozuq > a.css-1unrqcp `div.css-9uj12p > ul.css-98zc54 > li.css-nvozuq > a.css-1unrqcp`
div.css-9uj12p > ul.css-98zc54 > li.css-nvozuq > a.css-1unrqcp `div.css-9uj12p > ul.css-98zc54 > li.css-nvozuq > a.css-1unrqcp`

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.

○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

●`[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

●`[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

●Elements with `role="dialog"` or `role="alertdialog"` have accessible names.

●`[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.

●`[lang]` attributes have a valid value

●Document has a main landmark.

●Deprecated ARIA roles were not used

●`<video>` elements contain a `<track>` element with `[kind="captions"]`

●Identical links have the same purpose.

●Elements with visible text labels have matching accessible names.

○`[accesskey]` values are unique

○`button`, `link`, and `menuitem` elements have accessible names

○ARIA input fields have accessible names

○ARIA `meter` elements have accessible names

○ARIA `progressbar` elements have accessible names

○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

○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

○ARIA IDs are unique

○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

○Form elements have associated labels

○The document does not use `<meta http-equiv="refresh">`

○`<object>` elements have alternate text

○Select elements have associated label elements.

○Skip links are focusable.

○Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.

○`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.

○Tables have different content in the summary attribute and `<caption>`.

○All heading elements contain content.

○Uses ARIA roles only on compatible elements

○Image elements do not have `[alt]` attributes that are redundant text.

○Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.

○`<td>` elements in a large `<table>` have one or more table headers.

Best Practices

General

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

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL
/assets/generated_assets/webapp/vendor/user_centrics/3.33...
/assets/generated_assets/brand/_next/static/chunks/pages/...
/assets/generated_assets/brand/_next/static/chunks/ab5b22...
/assets/generated_assets/brand/_next/static/chunks/93794-...

●Uses HTTPS

●Avoids deprecated APIs

●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

●No browser errors logged to the console

●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

○Redirects HTTP traffic to HTTPS

○Mitigate clickjacking with XFO or CSP

SEO

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

Content Best Practices

Canonical links suggest which URL to show in search results. Learn more about canonical links.

Why this matters

Informational: a Permissions-Policy directive showing feature -> allowed origins.

Source: MDN Permissions-Policy

Format your HTML in a way that enables crawlers to better understand your app’s content.

○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

●Links are crawlable

●robots.txt is valid

●Image elements have `[alt]` attributes

●Document has a valid `hreflang`