Skip to content
https://finra.org

Lighthouse Mobile

· 0 checks — Mobile 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.

29

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.

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
How FINRA Serves Investors and Members As a not-for-profit, self-regulatory or… div.paragraph > div.field > div.field__item > div.paragraph--three-sections-items
www.finra.org/sites/default/files/2024-05/Mask%20Group%2038.png1.9 MiB1.7 MiB
div.field > div > div.field > img div.field > div > div.field > img
www.finra.org/sites/default/files/2024-05/Mask%20Group%2039_0.png1.6 MiB1.5 MiB

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-2-DIV
nodeLabel: A vibrant market is at its best when it works for everyone. Scroll
path: 1,HTML,1,BODY,7,DIV,0,DIV,0,DIV,1,DIV,0,DIV,0,DIV,0,MAIN,0,SECTION,2,DIV,0,DIV,0,ARTICLE,0,DIV,0,DIV,0,DIV,0,DIV
selector: div.node__content > div.field > div.field__item > div#page_title
snippet: <div class="paragraph paragraph--type--hero-paragraph paragraph--view-mode--featured-s…" id="page_title" data-once="scrollArrow">

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

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

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

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: 803 ms
URLTime Spent
finra.org/803 ms
www.finra.org/0.0 ms

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.

Diagnostics

Minifying JavaScript files can reduce payload sizes and script parse time. Learn how to minify JavaScript.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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: 1.4 s 164.9 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.

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.

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.

CategoryTime Spent
Script Evaluation3.4 s
Other1.5 s
Script Parsing & Compilation1.3 s
Style & Layout598 ms
Parse HTML & CSS270 ms
Garbage Collection138 ms
Rendering97 ms

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

●Layout shift culprits
●Optimize DOM size
●Forced reflow
●LCP breakdown
●Modern HTTP
●Optimize viewport for mobile
●Minify CSS
●User Timing marks and measures 16 user timings
●Avoid long main-thread tasks 20 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 290 ms
●Tasks
●Diagnostics
●Metrics
●Screenshot Thumbnails
●Final Screenshot
●Script Treemap Data
●Resources Summary
●Initial server response time was short Root document took 20 ms
●Avoid large layout shifts 2 layout shifts found
○INP breakdown
○Avoid non-composited animations
93

Accessibility

These checks highlight opportunities to improve the accessibility of your web app. Automatic detection can only detect a subset of issues and does not guarantee the accessibility of your web app, so manual testing is also encouraged.

ARIA

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div#block-finra-bootstrap-sass-loginoverlaynewhomepage-2 > div.content > div.clearfix > div#login-icon div#block-finra-bootstrap-sass-loginoverlaynewhomepage-2 > div.content > div.clearfix > div#login-icon

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

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
Report / Study div > div.node__content > div.field--name-field-core-content-type-tax > div#content-type-375506
Read More div > div.read-more > a > span.anchor-link
Report / Study div > div.node__content > div.field--name-field-core-content-type-tax > div#content-type-376296
Read More div > div.read-more > a > span.anchor-link
About FINRA div > div.node__content > div.field--name-field-core-content-type-tax > div#content-type-374256
Read More div > div.read-more > a > span.anchor-link
See What's New div.field__item > div.paragraph > div.featured-section-whats-new > a
READ NOW ABOUT HOW FINRA SERVES INVESTORS AND MEMBERS div.three-sections-item__wrapper > div.content > div.field > a
READ NOW ABOUT EXPOSING INSIDER RISK div.three-sections-item__wrapper > div.content > div.field > a
LEARN MORE ABOUT FINRA’S CRYPTO HUB div.three-sections-item__wrapper > div.content > div.field > a
Media Center div.announcement-wrapper > div.node > div.content > div#content-type-375916
Read More div.content > div.read-more > a > span.anchor-link
Read More div.content > div.read-more > a > span.anchor-link
Investor Insights div.field__item > div.announcement-wrapper > div.node > div#content-type-204291
Read More div.node > div.read-more > a > span.anchor-link
Media Center div.field__item > div.announcement-wrapper > div.node > div#content-type-379551
Read More div.node > div.read-more > a > span.anchor-link
Notice div.field__item > div.announcement-wrapper > div.node > div#content-type-379456
Read More div.node > div.read-more > a > span.anchor-link

These are opportunities to improve the legibility of your content.

Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Register div#column_para > div.paragraph > div.field > a.hero-card-link
Contact Us div#column_para > div.paragraph > div.field > a.hero-card-link
Search Cases div#column_para > div.paragraph > div.field > a.hero-card-link
Search Brokercheck div#column_para > div.paragraph > div.field > a.hero-card-link
Read More div.announcement-wrapper > div > div.read-more > a
Read More div.announcement-wrapper > div > div.read-more > a
Read More div.announcement-wrapper > div > div.read-more > a
Read More div.announcement-wrapper > div.node > div.read-more > a
Read More div.announcement-wrapper > div.node > div.read-more > a
Read More div.announcement-wrapper > div.node > div.read-more > a
○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 have a discernible name
●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.
●Heading elements appear in a sequentially-descending order
●Document has a main landmark.
●Deprecated ARIA roles were not used
●ARIA IDs are unique
○`[accesskey]` values are unique
○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
○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
○Links are distinguishable without relying on color.
○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.
○`[lang]` attributes have a valid value
○`<video>` elements contain a `<track>` element with `[kind="captions"]`
○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.
○Identical links have the same purpose.
○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.
73

Best Practices

User Experience

Image display dimensions should match natural aspect ratio. Learn more about image aspect ratio.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URLAspect Ratio (Displayed)Aspect Ratio (Actual)
FINRA: 85 years of protecting investors - Home div.page-header > section.region > a.navbar-brand > img.img-fluid
www.finra.org/sites/default/files/FINRA_Logo_Desktop.png64 x 20 (3.20)240 x 62 (3.87)

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
StorageType.persistent is deprecated. Please use standardized navigator.storage instead.
Fledge
AttributionReporting

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
Uncaught TypeError: Promise.allSettled is not a function
Uncaught TypeError: Promise.allSettled is not a function

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.

URLMap URL
/themes/custom/finra_bootstrap_sass/node_modules/@fortawe...
www.finra.org/themes/custom/finra_bootstrap_sass/js/popper.min.js?tbansewww.finra.org/themes/custom/finra_bootstrap_sass/js/popper.min.js.map
www.finra.org/themes/custom/finra_bootstrap_sass/js/bootstrap.min.js?tbansewww.finra.org/themes/custom/finra_bootstrap_sass/js/bootstrap.min.js.map
www.finra.org/core/assets/vendor/tabbable/index.umd.min.js?v=6.2.0www.finra.org/core/assets/vendor/tabbable/index.umd.min.js.map
www.finra.org/core/assets/vendor/once/once.min.js?v=1.0.1www.finra.org/core/assets/vendor/once/once.min.js.map
www.finra.org/core/assets/vendor/jquery.ui/ui/widgets/resizable-min.js?v=10.5.8www.finra.org/core/assets/vendor/jquery.ui/ui/widgets/resizable-min.js.map
www.finra.org/core/assets/vendor/jquery.ui/ui/widgets/mouse-min.js?v=10.5.8www.finra.org/core/assets/vendor/jquery.ui/ui/widgets/mouse-min.js.map
www.finra.org/core/assets/vendor/jquery.ui/ui/widgets/draggable-min.js?v=10.5.8www.finra.org/core/assets/vendor/jquery.ui/ui/widgets/draggable-min.js.map
www.finra.org/core/assets/vendor/jquery.ui/ui/widgets/dialog-min.js?v=10.5.8www.finra.org/core/assets/vendor/jquery.ui/ui/widgets/dialog-min.js.map
/core/assets/vendor/jquery.ui/ui/widgets/controlgroup-min...www.finra.org/core/assets/vendor/jquery.ui/ui/widgets/controlgroup-min.js.map
/core/assets/vendor/jquery.ui/ui/widgets/checkboxradio-mi...www.finra.org/core/assets/vendor/jquery.ui/ui/widgets/checkboxradio-min.js.map
www.finra.org/core/assets/vendor/jquery.ui/ui/widgets/button-min.js?v=10.5.8www.finra.org/core/assets/vendor/jquery.ui/ui/widgets/button-min.js.map
www.finra.org/core/assets/vendor/jquery.ui/ui/widget-min.js?v=10.5.8www.finra.org/core/assets/vendor/jquery.ui/ui/widget-min.js.map
www.finra.org/core/assets/vendor/jquery.ui/ui/version-min.js?v=10.5.8www.finra.org/core/assets/vendor/jquery.ui/ui/version-min.js.map
www.finra.org/core/assets/vendor/jquery.ui/ui/unique-id-min.js?v=10.5.8www.finra.org/core/assets/vendor/jquery.ui/ui/unique-id-min.js.map
www.finra.org/core/assets/vendor/jquery.ui/ui/scroll-parent-min.js?v=10.5.8www.finra.org/core/assets/vendor/jquery.ui/ui/scroll-parent-min.js.map
www.finra.org/core/assets/vendor/jquery.ui/ui/plugin-min.js?v=10.5.8www.finra.org/core/assets/vendor/jquery.ui/ui/plugin-min.js.map
www.finra.org/core/assets/vendor/jquery.ui/ui/labels-min.js?v=10.5.8www.finra.org/core/assets/vendor/jquery.ui/ui/labels-min.js.map
www.finra.org/core/assets/vendor/jquery.ui/ui/keycode-min.js?v=10.5.8www.finra.org/core/assets/vendor/jquery.ui/ui/keycode-min.js.map
www.finra.org/core/assets/vendor/jquery.ui/ui/jquery-patch-min.js?v=10.5.8www.finra.org/core/assets/vendor/jquery.ui/ui/jquery-patch-min.js.map
www.finra.org/core/assets/vendor/jquery.ui/ui/form-reset-mixin-min.js?v=10.5.8www.finra.org/core/assets/vendor/jquery.ui/ui/form-reset-mixin-min.js.map
www.finra.org/core/assets/vendor/jquery.ui/ui/focusable-min.js?v=10.5.8www.finra.org/core/assets/vendor/jquery.ui/ui/focusable-min.js.map
www.finra.org/core/assets/vendor/jquery.ui/ui/disable-selection-min.js?v=10.5.8www.finra.org/core/assets/vendor/jquery.ui/ui/disable-selection-min.js.map
www.finra.org/core/assets/vendor/jquery.ui/ui/data-min.js?v=10.5.8www.finra.org/core/assets/vendor/jquery.ui/ui/data-min.js.map
●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
●Serves images with appropriate resolution
●Page has the HTML doctype
●Properly defines charset
●No issues in the `Issues` panel in Chrome Devtools
●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
92

SEO

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

Content Best Practices

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 are crawlable
●Image elements have `[alt]` attributes
●Document has a valid `hreflang`
●Document has a valid `rel=canonical`
○robots.txt is valid

Send Feedback