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

40

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
div.row > div.col-12x > div.marquee-panel-pic > img.flex-image-3-2 div.row > div.col-12x > div.marquee-panel-pic > img.flex-image-3-2
/-/media/project/frbstl/stlouisfed/annual-report/2025/ar2...73.4 KiB24.9 KiB
Shoppers wander through the Marché d’Aligre outdoor market in Paris. div.box-shadow > a.outline-fix > div.card-image > img.flex-image-3-2
/-/media/project/frbstl/stlouisfed/blog/2026/ote/apr/blog...46.1 KiB16.2 KiB
A St. Louis Fed team member collaborates with two others during a workshop. div.row > div.col-12 > div.info-panel-pic > img.flex-image-3-2
/-/media/project/frbstl/stlouisfed/images/homepage/what-w...55.0 KiB15.9 KiB
Group of employees converse as they stand together. div.col-lg-4x > a.a-link-no-hover > div.who-we-are-image > img.flex-image-3-2
/-/media/project/frbstl/stlouisfed/images/homepage/ourcul...49.9 KiB10.8 KiB
The Eighth District Beige Book and Map of the Eighth District div.box-shadow > a.outline-fix > div.card-image > img.flex-image-3-2
/-/media/project/frbstl/stlouisfed/images/publications/th...32.0 KiB7.5 KiB
Alberto G. Musalem div.box-shadow > a.outline-fix > div.card-image > img.flex-image-3-2
/-/media/project/frbstl/stlouisfed/images/musalem/preside...27.4 KiB6.4 KiB
Two men in suits converse as they shake hands. div.col-lg-4x > a.a-link-no-hover > div.who-we-are-image > img.flex-image-3-2
/-/media/project/frbstl/stlouisfed/images/homepage/whowea...43.9 KiB4.8 KiB
Man writes on a whiteboard as two colleagues observe. div.row > div.col-12 > div.info-panel-pic > img.flex-image-3-2
/-/media/project/frbstl/stlouisfed/images/homepage/provid...43.1 KiB4.1 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.row > div.col-12x > div.marquee-panel-pic > img.flex-image-3-2
path: 5,HTML,2,BODY,4,DIV,4,MAIN,0,DIV,0,DIV,1,DIV,0,DIV,1,DIV,0,DIV,1,DIV,0,DIV,0,DIV,0,DIV,0,IMG
selector: div.row > div.col-12x > div.marquee-panel-pic > img.flex-image-3-2
snippet: <img class="flex-image-3-2" src="/-/media/project/frbstl/stlouisfed/annual-report/2025/ar25-full-image.jpg" 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
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

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.

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: 885 ms
URLTime Spent
stlouisfed.org/885 ms
www.stlouisfed.org/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: 608 ms
URLTime Spent
www.stlouisfed.org/708 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

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 CSS files can reduce network payload sizes. Learn how to minify CSS.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 150 ms 5.7 KiB

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: 1.0 s 193.3 KiB
URLTransfer SizeEst Savings
www.stlouisfed.org/-/media/base-themes/core-libraries/scripts/fullcalendar.js173.9 KiB78.6 KiB
www.stlouisfed.org/-/media/base-themes/core-libraries/scripts/xaquery.js137.7 KiB19.8 KiB
www.stlouisfed.org/-/media/base-themes/core-libraries/scripts/moment.js41.3 KiB14.9 KiB
/-/media/base-themes/core-libraries/scripts/mediaelement-...72.8 KiB14.1 KiB
www.stlouisfed.org/-/media/base-themes/core-libraries/scripts/typeahead.js27.7 KiB12.1 KiB
/-/media/base-themes/components-theme/scripts/component-c...15.1 KiB9.3 KiB
/-/media/base-themes/searchtheme/scripts/component-search...6.3 KiB3.6 KiB
/-/media/base-themes/searchtheme/scripts/component-frbstl...6.3 KiB3.5 KiB
/-/media/themes/frbstl/stlouisfed/stlouisfed/scripts/comp...5.3 KiB3.1 KiB
/-/media/base-themes/searchtheme/scripts/component-search...5.0 KiB2.9 KiB
/-/media/base-themes/searchtheme/scripts/component-search...4.6 KiB2.7 KiB
/-/media/base-themes/components-theme/scripts/component-o...4.9 KiB2.7 KiB
www.stlouisfed.org/-/media/base-themes/core-libraries/scripts/flash-polyfill.js3.7 KiB2.6 KiB
/-/media/base-themes/searchtheme/scripts/component-search...4.3 KiB2.6 KiB
/-/media/base-themes/searchtheme/scripts/component-search...4.2 KiB2.6 KiB
/-/media/base-themes/searchtheme/scripts/component-frbstl...4.4 KiB2.5 KiB
/-/media/base-themes/searchtheme/scripts/component-search...4.0 KiB2.4 KiB
/-/media/base-themes/searchtheme/scripts/component-search...4.0 KiB2.4 KiB
/-/media/themes/frbstl/stlouisfed/stlouisfed/scripts/mega...6.0 KiB2.3 KiB
www.stlouisfed.org/-/media/base-themes/maps/scripts/component-map.js5.3 KiB2.2 KiB
/-/media/base-themes/searchtheme/scripts/component-search...3.3 KiB2.2 KiB
/-/media/base-themes/searchtheme/scripts/component-search...3.7 KiB2.1 KiB
/-/media/base-themes/components-theme/scripts/component-f...3.5 KiB2.1 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: 130 ms 104.6 KiB

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 Evaluation2.0 s
Other913 ms
Script Parsing & Compilation399 ms
Style & Layout282 ms
Parse HTML & CSS172 ms
Garbage Collection82 ms
Rendering55 ms

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

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
Federal Reserve Bank of St. Louis mobile eagle logo div.row > div.col-8 > a.outline-fix > img.mobile-header-image
/-/media/project/frbstl/stlouisfed/images/common/mobilelo...

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
●Optimize viewport for mobile
●User Timing marks and measures 5 user timings
●Avoid long main-thread tasks 20 long tasks found
●Network Requests
●Network Round Trip Times 50 ms
●Server Backend Latencies 360 ms
●Tasks
●Diagnostics
●Metrics
●Screenshot Thumbnails
●Final Screenshot
●Script Treemap Data
●Resources Summary
○INP breakdown
○Avoid non-composited animations
○Avoid large layout shifts
95

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.

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.row > div.col-12 > div > a.fred-info-link-button div.row > div.col-12 > div > a.fred-info-link-button
div.stay-in-touch-container > div.row > div.col-6x > a.outline-fix div.stay-in-touch-container > div.row > div.col-6x > a.outline-fix

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.

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
From Our President & CEO Pres. Musalem's Remarks and Community Engagement div.cardsHomepage > div.card-content > div.box-shadow > a.outline-fix
Beige Book Eighth District Economic Activity Remains Unchanged div.cardsHomepage > div.card-content > div.box-shadow > a.outline-fix
Economic Analysis Why Does AI Adoption Differ So Much across Countries? div.cardsHomepage > div.card-content > div.box-shadow > a.outline-fix
○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>`
●`[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
●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.
●Identical links have the same purpose.
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements have accessible names
○Deprecated ARIA roles were not used
○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
○`[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
○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
○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.
○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.
○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.
96

Best Practices

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
Permissions policy violation: accelerometer is not allowed in this document.
Permissions policy violation: accelerometer is not allowed in this document.

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.

●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 issues in the `Issues` panel in Chrome Devtools
●Ensure CSP is effective against XSS attacks
●Use a strong HSTS policy
●Mitigate DOM-based XSS with Trusted Types
●Detected JavaScript libraries
○Redirects HTTP traffic to HTTPS
○Ensure proper origin isolation with COOP
○Mitigate clickjacking with XFO or CSP
85

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

Descriptive link text helps search engines understand your content. Learn how to make links more accessible.

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.

Crawling and Indexing

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.

○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`

Send Feedback