Skip to content
https://fidelity.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.

83

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.

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
dmt.fidelity.com/prod/meas/1.0 s266.6 KiB
cdnssl.clicktale.net/www43/ptc/e802b0fb-4da3-4648-a335-e31c353417bf.js900.0 s137.4 KiB
/OMgr3/Z/EN/Igz4/ZZWIz_H_/EtafmDSbOrbGVc/fA4ZTQ50AwI/fCpP...21600.0 s171.6 KiB
cdn.cookielaw.org/scripttemplates/202407.1.0/otBannerSdk.js86400.0 s109.8 KiB
/analytics.js/v1/YhIHGbwsOzNaANEek8UTzMdnEz7lKUIl/analyti...120.0 s28.9 KiB
www.fidelity.com/akam/13/7c338aec21600.0 s9.1 KiB
/WRSiteInterceptEngine/?Q_ZID=ZN_cvGJH8lmjxbKyln&Q_LOC=&Q...3600.0 s4.6 KiB
cdn.cookielaw.org/scripttemplates/otSDKStub.js86400.0 s9.1 KiB
/dxjsmodule/12.1a2b7192fd54e87d3971.chunk.js?Q_CLIENTVERS...604800.0 s35.9 KiB
/logos/0eed0401-3fa0-4eac-af40-ebc20bde018d/5a69002b-db62...86400.0 s8.3 KiB
/dxjsmodule/CoreModule.js?Q_CLIENTVERSION=2.46.0&Q_CLIENT...604800.0 s30.9 KiB
pdx1.qualtrics.com/WRQualtricsSiteIntercept/Graphic.php?IM=IM_3sG1rQoYXJ0DWjc36.0 s2.1 KiB
/dxjsmodule/FeedbackButtonModule.js?Q_CLIENTVERSION=2.46....604800.0 s19.4 KiB
/dxjsmodule/37.7ea1ffe71ad8c0799cc1.chunk.js?Q_CLIENTVERS...604800.0 s18.6 KiB
cdn.cookielaw.org/logos/static/powered_by_logo.svg86400.0 s2.6 KiB
/dxjsmodule/1.bc67e778235741631577.chunk.js?Q_CLIENTVERSI...604800.0 s7.1 KiB
/dxjsmodule/PopOverModule.js?Q_CLIENTVERSION=2.46.0&Q_CLI...604800.0 s3.4 KiB
/dxjsmodule/EmbeddedTargetModule.js?Q_CLIENTVERSION=2.46....604800.0 s2.9 KiB
/dxjsmodule/PopUpModule.js?Q_CLIENTVERSION=2.46.0&Q_CLIEN...604800.0 s1.9 KiB
/dxjsmodule/7.f7df015b06d8a90ce822.chunk.js?Q_CLIENTVERSI...604800.0 s1.4 KiB

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

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
dmt.fidelity.com/prod/meas/266.6 KiB525 ms
www.fidelity.com/intlacct/js/jquery-3.7.1.min.js29.8 KiB81 ms
www.fidelity.com/intlacct/js/cookie-redirect.js862 B
www.fidelity.com/intlacct/css/footer.css853 B
www.fidelity.com/intlacct/css/inter-accounts.css5.3 KiB

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

Diagnostics

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: 120 ms 609.7 KiB
URLTransfer SizeEst Savings
dmt.fidelity.com/prod/meas/265.6 KiB131.1 KiB
cdnssl.clicktale.net/www43/ptc/e802b0fb-4da3-4648-a335-e31c353417bf.js136.9 KiB101.0 KiB
/fidelity/prod/code/74b258192231769794d6664eacb44661.js?c...114.6 KiB70.7 KiB
www.googletagmanager.com/gtag/js?id=G-GL9JN8SMCE177.0 KiB65.9 KiB
cdn.cookielaw.org/scripttemplates/202407.1.0/otBannerSdk.js109.6 KiB64.1 KiB
www.googletagmanager.com/gtag/js?id=DC-2579983&cx=c&gtm=4e64k0h2130.7 KiB60.8 KiB
www.googletagmanager.com/gtag/js?id=DC-3824016&cx=c&gtm=4e64k0h2129.3 KiB60.3 KiB
/OMgr3/Z/EN/Igz4/ZZWIz_H_/EtafmDSbOrbGVc/fA4ZTQ50AwI/fCpP...170.7 KiB34.9 KiB
/dxjsmodule/12.1a2b7192fd54e87d3971.chunk.js?Q_CLIENTVERS...35.7 KiB20.8 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 cache-control:no-store header cannot enter back/forward cache.Actionable
Pages whose main resource has cache-control:no-store cannot enter back/forward cache.Not actionable
Back/forward cache is disabled because some JavaScript network request received resource with Cache-Control: no-store header.Not actionable

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.

Estimated savings: 0.0 ms 4.3 KiB
URLTransfer SizeEst Savings
www.fidelity.com/intlacct/js/inter-accounts.js13.0 KiB4.3 KiB

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 20.5 KiB
URLTransfer SizeEst Savings
20.8 KiB20.5 KiB

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
Fidelity Investments div.layout-footer-region > div.primary-footer > a > img.fid-logo
www.fidelity.com/intlacct/images/Footer_Logo.png
Fidelity.com body.inter-agreement > div.layout-header-region > div.navless-header > img
www.fidelity.com/intlacct/images/fidelity_com_logo.gif
Give Feedback body.inter-agreement > div.QSIFeedbackButton > button#QSIFeedbackButton-btn > img
pdx1.qualtrics.com/WRQualtricsSiteIntercept/Graphic.php?IM=IM_3sG1rQoYXJ0DWjc

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

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: 302 ms
URLTime Spent
fidelity.com/302 ms
www.fidelity.com/0.0 ms
●Time to Interactive 2.2 s
●Max Potential First Input Delay 70 ms
●Layout shift culprits
●Optimize DOM size
●Font display
●Forced reflow
●Improve image delivery
●LCP breakdown
●Modern HTTP
●Optimize viewport for mobile
●Minify CSS
●Avoids enormous network payloads Total size was 1,678 KiB
●User Timing marks and measures 7 user timings
●JavaScript execution time 0.8 s
●Minimizes main-thread work 1.2 s
●Avoid long main-thread tasks 3 long tasks found
●Network Requests
●Network Round Trip Times 100 ms
●Server Backend Latencies 230 ms
●Tasks
●Diagnostics
●Metrics
●Screenshot Thumbnails
●Final Screenshot
●Script Treemap Data
●Resources Summary
●Initial server response time was short Root document took 170 ms
○INP breakdown
○LCP request discovery
○Avoid non-composited animations
○Avoid large layout shifts
98

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.

Best practices

One main landmark helps screen reader users navigate a web page. Learn more about landmarks.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html html

These items highlight common accessibility best practices.

○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
●`[aria-hidden="true"]` elements do not contain focusable descendents
●Elements use only permitted ARIA attributes
●Background and foreground colors have a sufficient contrast ratio
●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
●Touch targets have sufficient size and spacing.
●Heading elements appear in a sequentially-descending order
●`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.
●Deprecated ARIA roles were not used
●Uses ARIA roles only on compatible elements
○`[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 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
○Input buttons have discernible text.
○`<input type="image">` elements have `[alt]` text
○Form elements have associated labels
○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
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○Select elements have associated label elements.
○Skip links are focusable.
○No element has a `[tabindex]` value greater than 0
○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.
○Image elements do not have `[alt]` attributes that are redundant text.
○Identical links have the same purpose.
○Elements with visible text labels have matching accessible names.
○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.
92

Best Practices

Browser Compatibility

Specifying a doctype prevents the browser from switching to quirks-mode. Learn more about the doctype declaration.

Why this matters

Performance issues directly impact user engagement and conversion rates.

General

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
/internal/id-event/?vendor=trackIdentity&sv_domain=fideli...
Failed to load resource: the server responded with a status of 403 ()

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
/OMgr3/Z/EN/Igz4/ZZWIz_H_/EtafmDSbOrbGVc/fA4ZTQ50AwI/fCpP...
dmt.fidelity.com/prod/meas/
www.glancecdn.net/cobrowse/js/GlancePresenceVisitor_6.26.0M.jswww.glancecdn.net/cobrowse/js/map.js.map
www.glancecdn.net/cobrowse/CobrowseJS.ashx?group=19772&site=productionwww.glancecdn.net/cobrowse/map.js.map
/analytics.js/v1/YhIHGbwsOzNaANEek8UTzMdnEz7lKUIl/analyti.../analytics.js/v1/YhIHGbwsOzNaANEek8UTzMdnEz7lKUIl/standal...
/analytics-next/bundles/schemaFilter.bundle.1b218d13fed02.../analytics-next/bundles/schemaFilter.bundle.1b218d13fed02...
/analytics-next/bundles/ajs-destination.bundle.8e6b895db7.../analytics-next/bundles/ajs-destination.bundle.8e6b895db7...
●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
●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
42

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 are unable to include your pages in search results if they don't have permission to crawl them. Learn more about crawler directives.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Blocking Directive Source
head.at-element-marker > meta

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
I Accept div.page-jump-option > div.accept-btn-box > h2 > a.accept-link

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

Content Best Practices

Meta descriptions may be included in search results to concisely summarize page content. Learn more about the meta description.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

○Structured data is valid
●Document has a `<title>` element
●Page has successful HTTP status code
●Links have descriptive text
●Image elements have `[alt]` attributes
●Document has a valid `hreflang`
○Document has a valid `rel=canonical`

Send Feedback