Skip to content
https://federalreserve.gov

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.

27

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
www.federalreserve.gov/images/GettyImages-1465565182.jpg0.0 ms714.4 KiB
www.federalreserve.gov/images/GettyImages-1945538926.jpg0.0 ms315.5 KiB
www.federalreserve.gov/assets/main.js0.0 ms299.3 KiB
players.brightcove.net/66043936001/default_default/index.min.js300.0 s291.8 KiB
www.federalreserve.gov/assets/main.css0.0 ms151.2 KiB
www.federalreserve.gov/css/icons.data.svg.css0.0 ms140.7 KiB
www.federalreserve.gov/images/filmstrip-fintech-chart-cellphone.jpg0.0 ms69.3 KiB
www.federalreserve.gov/images/pubs-filmstrip-img2.jpg0.0 ms66.4 KiB
www.federalreserve.gov/images/instagram.png0.0 ms63.5 KiB
www.federalreserve.gov/js/angular.min.js0.0 ms60.5 KiB
www.federalreserve.gov/css/bluesteel-theme.css0.0 ms47.1 KiB
www.federalreserve.gov/images/OpenGov%402x.png0.0 ms37.9 KiB
www.federalreserve.gov/js/jquery.min.js0.0 ms29.7 KiB
www.federalreserve.gov/images/us-currency-education-program.png0.0 ms22.9 KiB
www.federalreserve.gov/images/fr-consumer-help.png0.0 ms18.1 KiB
www.federalreserve.gov/images/fed-listens-img.jpg0.0 ms17.3 KiB
www.federalreserve.gov/assets/league-spartan-latin-400-normal.woff0.0 ms16.7 KiB
www.federalreserve.gov/css/bootstrap.css0.0 ms16.4 KiB
www.federalreserve.gov/js/modernizr-latest.js0.0 ms15.3 KiB
www.federalreserve.gov/images/fomc-calendar.svg0.0 ms13.8 KiB
www.federalreserve.gov/js/bootstrap.min.js0.0 ms10.7 KiB
/cdn-cgi/challenge-platform/h/b/scripts/jsd/0b8fb825cb67/...14400.0 s13.3 KiB
www.federalreserve.gov/js/slides/ekko-lightbox.min.js0.0 ms4.6 KiB
/cdn-cgi/zaraz/s.js?z=JTdCJTIyZXhlY3V0ZWQlMjIlM0ElNUIlNUQ...0.0 ms3.9 KiB
www.federalreserve.gov/js/scripts.js0.0 ms3.2 KiB
www.federalreserve.gov/images/cep-logo.svg0.0 ms3.1 KiB
www.federalreserve.gov/images/USAGov%402x.png0.0 ms2.8 KiB
www.federalreserve.gov/images/fed-exp-hompage.svg0.0 ms2.7 KiB
www.federalreserve.gov/images/icon-calendar.png0.0 ms2.2 KiB
www.federalreserve.gov/images/icon-teal-files.png0.0 ms2.2 KiB
www.federalreserve.gov/images/icon-bell.png0.0 ms1.7 KiB
www.federalreserve.gov/js/sticky-tables.js0.0 ms1.7 KiB
www.federalreserve.gov/assets/Banner.js0.0 ms1.1 KiB
designsystem.digital.gov/assets/img/icon-https.svg60.0 s992 B
designsystem.digital.gov/assets/img/icon-dot-gov.svg60.0 s967 B
www.federalreserve.gov/images/icon-us-flag.svg0.0 ms894 B
www.federalreserve.gov/js/t4-nav-controller.js0.0 ms799 B
www.federalreserve.gov/images/icon-bldg-ren-icon.svg0.0 ms743 B
www.federalreserve.gov/images/icon--transparent-more-info.png0.0 ms440 B
www.federalreserve.gov/images/caret-icon.svg0.0 ms366 B
www.federalreserve.gov/images/expand_more.svg0.0 ms237 B
www.federalreserve.gov/js/app.js0.0 ms177 B
www.federalreserve.gov/js/modal.js0.0 ms64 B

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.

A forced reflow occurs when JavaScript queries geometric properties (such as offsetWidth) after styles have been invalidated by a change to the DOM state. This can result in poor performance. Learn more about forced reflows and possible mitigations.

Why this matters

Performance issues directly impact user engagement and conversion rates.

headings: [map[key:source label:Top function call valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]
items: [map[reflowTime:29.785 source:map[column:10742 line:5 type:source-location url:https://www.federalreserve.gov/assets/main.js urlProvider:network]]]
headings: [map[key:source label:Source valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]
items: [map[reflowTime:59.784 source:map[type:text value:[unattributed]]] map[reflowTime:1.577 source:map[column:132923 line:28 type:source-location url:https://players.brightcove.net/66043936001/default_default/index.min.js urlProvider:network]] map[reflowTime:21.828 source:map[column:78771 line:0 type:source-location url:https://players.brightcove.net/66043936001/default_default/index.min.js urlProvider:network]] map[reflowTime:4.6 source:map[column:3933 line:1 type:source-location url:https://www.federalreserve.gov/assets/main.js urlProvider:network]] map[reflowTime:0.185 source:map[column:4196 line:1 type:source-location url:https://www.federalreserve.gov/assets/main.js urlProvider:network]] map[reflowTime:0.156 source:map[column:4240 line:1 type:source-location url:https://www.federalreserve.gov/assets/main.js urlProvider:network]] map[reflowTime:8.841 source:map[column:4988 line:1 type:source-location url:https://www.federalreserve.gov/assets/main.js urlProvider:network]] map[reflowTime:0.083 source:map[column:5047 line:1 type:source-location url:https://www.federalreserve.gov/assets/main.js urlProvider:network]] map[reflowTime:0.069 source:map[column:8293 line:1 type:source-location url:https://www.federalreserve.gov/assets/main.js urlProvider:network]] map[reflowTime:0.048 source:map[column:788 line:42 type:source-location url:https://www.federalreserve.gov/ urlProvider:network]] map[reflowTime:1.364 source:map[column:209844 line:13 type:source-location url:https://www.federalreserve.gov/assets/main.js urlProvider:network]] map[reflowTime:1.815 source:map[column:5547 line:13 type:source-location url:https://www.federalreserve.gov/assets/main.js urlProvider:network]] map[reflowTime:17.89 source:map[column:41205 line:13 type:source-location url:https://www.federalreserve.gov/assets/main.js urlProvider:network]] map[reflowTime:7.335 source:map[column:39974 line:13 type:source-location url:https://www.federalreserve.gov/assets/main.js urlProvider:network]] map[reflowTime:2.427 source:map[column:7042 line:13 type:source-location url:https://www.federalreserve.gov/assets/main.js urlProvider:network]]]

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
Protect yourself from Fraud and Scams div.media-card__content > div.media-card__image-container > a > img.media-card__image
www.federalreserve.gov/images/GettyImages-1465565182.jpg713.5 KiB702.1 KiB
Proposals for Comment div.media-card__content > div.media-card__image-container > a > img.media-card__image
www.federalreserve.gov/images/GettyImages-1945538926.jpg315.0 KiB304.5 KiB
More Information on Financial Innovation article.media-card-horizontal > div.media-card__image-container > a > img.media-card-horizontal__image
www.federalreserve.gov/images/filmstrip-fintech-chart-cellphone.jpg69.1 KiB59.3 KiB
More Information on Funding, Credit, Liquidity, and Loan Facilities and Reporti… article.media-card-horizontal > div.media-card__image-container > a > img.media-card-horizontal__image
www.federalreserve.gov/images/pubs-filmstrip-img2.jpg66.2 KiB56.1 KiB
Federal Reserve Instagram Page div.row > div.col-xs-12 > div.footer__social > a.icon__md
www.federalreserve.gov/images/instagram.png63.3 KiB50.4 KiB
Link to Open.gov div.row > div.col-xs-12 > a > img.footer__image
www.federalreserve.gov/images/OpenGov%402x.png37.8 KiB37.2 KiB
div.panel-body > div.embed-responsive > div#frb-video > video#frb-video_html5_api div.panel-body > div.embed-responsive > div#frb-video > video#frb-video_html5_api
/v1/jit/66043936001/a29dbc45-c50b-4c5b-be9d-6a37d9b8c030/...35.7 KiB26.2 KiB
Fed Listens div.media-card__content > div.media-card__image-container > a > img.media-card__image
www.federalreserve.gov/images/fed-listens-img.jpg17.1 KiB13.9 KiB
U.S. Currency Education Program USCURRENCY.GOV MORE INFO div#content > section.bpw-flex-container > div.overlay-card__border > article.overlay-card
www.federalreserve.gov/images/us-currency-education-program.png22.8 KiB10.5 KiB
Federal Reserve Consumer Help Icon Files LEARN MORE MORE INFO div#content > section.bpw-flex-container > div.overlay-card__border > article.overlay-card
www.federalreserve.gov/images/fr-consumer-help.png18.0 KiB5.9 KiB

Each subpart has specific improvement strategies. Ideally, most of the LCP time should be spent on loading the resources, not within delays.

Why this matters

Performance issues directly impact user engagement and conversion rates.

headings: [map[key:label label:Subpart valueType:text] map[key:duration label:Duration valueType:ms]]
items: [map[duration:222.37899975585938 label:Time to first byte subpart:timeToFirstByte] map[duration:2568.1440002441404 label:Element render delay subpart:elementRenderDelay]]
lhId: page-10-P
nodeLabel: Speech by Governor Barr on rural economic development at “Strengthening America…
path: 1,HTML,1,BODY,9,DIV,1,DIV,1,DIV,0,DIV,0,DIV,0,DIV,0,UL,4,LI,0,P
selector: div.fed-tabs__panel-content > ul.list-unstyled > li > p
snippet: <p>

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
www.federalreserve.gov/css/icons.data.svg.css140.7 KiB1.5 s
www.federalreserve.gov/assets/main.css151.2 KiB1.5 s
www.federalreserve.gov/css/bluesteel-theme.css47.1 KiB452 ms
www.federalreserve.gov/js/angular.min.js60.5 KiB452 ms
www.federalreserve.gov/js/modernizr-latest.js15.3 KiB
www.federalreserve.gov/css/bootstrap.css16.4 KiB
www.federalreserve.gov/js/app.js177 B

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: 782 ms
URLTime Spent
federalreserve.gov/782 ms
www.federalreserve.gov/0.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

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: 150 ms 10.0 KiB
URLTransfer SizeEst Savings
www.federalreserve.gov/js/modernizr-latest.js15.2 KiB10.0 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: 1.2 s 275.3 KiB
URLTransfer SizeEst Savings
www.federalreserve.gov/assets/main.css151.1 KiB122.4 KiB
www.federalreserve.gov/css/icons.data.svg.css140.7 KiB118.0 KiB
www.federalreserve.gov/css/bluesteel-theme.css47.0 KiB19.6 KiB
www.federalreserve.gov/css/bootstrap.css16.3 KiB15.3 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: 1.7 s 320.2 KiB
URLTransfer SizeEst Savings
www.federalreserve.gov/assets/main.js299.3 KiB150.3 KiB
players.brightcove.net/66043936001/default_default/index.min.js291.3 KiB129.0 KiB
www.federalreserve.gov/js/angular.min.js60.4 KiB40.9 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.

URLTotal CPU TimeScript EvaluationScript Parse
www.federalreserve.gov/assets/main.js6.3 s3.5 s5.1 ms
players.brightcove.net/66043936001/default_default/index.min.js1.4 s971 ms138 ms
Unattributable1.0 s9.4 ms0.0 ms
www.federalreserve.gov/909 ms49 ms5.0 ms
www.federalreserve.gov/cdn-cgi/challenge-platform/scripts/jsd/main.js338 ms295 ms4.0 ms
www.federalreserve.gov/js/angular.min.js201 ms179 ms21 ms
www.federalreserve.gov/js/modernizr-latest.js112 ms52 ms7.0 ms
www.federalreserve.gov/js/jquery.min.js77 ms61 ms12 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.

CategoryTime Spent
Script Evaluation5.2 s
Parse HTML & CSS1.9 s
Other1.4 s
Style & Layout1.3 s
Rendering297 ms
Script Parsing & Compilation211 ms
Garbage Collection110 ms

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.

URLTransfer Size
/media/v1/hls/v4/clear/66043936001/a29dbc45-c50b-4c5b-be9...870.6 KiB
www.federalreserve.gov/images/GettyImages-1465565182.jpg714.4 KiB
www.federalreserve.gov/images/GettyImages-1945538926.jpg315.5 KiB
www.federalreserve.gov/assets/main.js299.3 KiB
players.brightcove.net/66043936001/default_default/index.min.js291.8 KiB
/manifest/v1/hls/v4/clear/66043936001/a29dbc45-c50b-4c5b-...151.6 KiB
www.federalreserve.gov/assets/main.css151.2 KiB
/manifest/v1/hls/v4/clear/66043936001/a29dbc45-c50b-4c5b-...150.9 KiB
/media/v1/hls/v4/clear/66043936001/a29dbc45-c50b-4c5b-be9...150.9 KiB
www.federalreserve.gov/css/icons.data.svg.css140.7 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
More Information on Financial Innovation article.media-card-horizontal > div.media-card__image-container > a > img.media-card-horizontal__image
www.federalreserve.gov/images/filmstrip-fintech-chart-cellphone.jpg
More Information on Funding, Credit, Liquidity, and Loan Facilities and Reporti… article.media-card-horizontal > div.media-card__image-container > a > img.media-card-horizontal__image
www.federalreserve.gov/images/pubs-filmstrip-img2.jpg
The Federal Reserve Explained div.fed-tabs__featured > figure.fed-tabs__media > a > img.img-responsive
www.federalreserve.gov/images/fed-exp-hompage.svg
Link to Open.gov div.row > div.col-xs-12 > a > img.footer__image
www.federalreserve.gov/images/OpenGov%402x.png
Link to USA.gov div.row > div.col-xs-12 > a > img.footer__image
www.federalreserve.gov/images/USAGov%402x.png
Expand More div.custom-banner > div.custom-banner__header > button.custom-banner__button > img#banner-caret-_R_0_
www.federalreserve.gov/images/expand_more.svg

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
●Modern HTTP
●Optimize viewport for mobile
●Minify CSS
●User Timing marks and measures 6 user timings
●Avoid long main-thread tasks 20 long tasks found
●Avoid non-composited animations 2 animated elements found
●Page didn't prevent back/forward cache restoration
●Network Requests
●Network Round Trip Times 110 ms
●Server Backend Latencies 150 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 large layout shifts
99

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.

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
TUE 4/21 div.calendar-module > div.calendar > div.calendar__day > h4.calendar__header
BOARD OF GOVERNORS of the FEDERAL RESERVE SYSTEM footer.container > div.row > div.col-xs-12 > h6.footer__heading

These are opportunities to improve keyboard navigation in your application.

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
View More div.card > div.card-body > div.more > a
View More div._column_owt5y_1 > div.homepageBox > div.homepageContent > a
View More div._column_owt5y_1 > div.homepageBox > div.homepageContent > a
View More div._column_owt5y_1 > div.homepageBox > div.homepageContent > 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
●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
●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
●`button`, `link`, and `menuitem` elements have accessible names
●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
●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
●Skip links are focusable.
●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.
○`[accesskey]` values are unique
○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
○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.
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○Select elements have associated label elements.
○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.
77

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.federalreserve.gov/cdn-cgi/challenge-platform/scripts/jsd/main.js
StorageType.persistent is deprecated. Please use standardized navigator.storage instead.
www.federalreserve.gov/cdn-cgi/challenge-platform/scripts/jsd/main.js
Fledge
www.federalreserve.gov/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.federalreserve.gov/assets/league-spartan-latin-400-normal.woff2
Failed to load resource: the server responded with a status of 404 ()

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
www.federalreserve.gov/assets/main.js
www.federalreserve.gov/js/angular.min.jswww.federalreserve.gov/js/angular.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
●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
●Ensure proper origin isolation with COOP
●Mitigate DOM-based XSS with Trusted Types
●Detected JavaScript libraries
○Redirects HTTP traffic to HTTPS
○Use a strong HSTS policy
○Mitigate clickjacking with XFO or CSP
91

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.

Link destinationLink Text
www.federalreserve.gov/faqs/building-project-faqs.htmLearn More
/monetarypolicy/review-of-monetary-policy-strategy-tools-...Learn More
/supervisionreg/disaster-preparedness-and-recovery-resour...Learn More
/faqs/what-should-i-do-if-i-have-damaged-or-mutilated-cur...Learn More
www.federalreserve.gov/paymentsystems/fednow_faq.htmLearn More

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`
○robots.txt is valid
○Document has a valid `rel=canonical`

Send Feedback