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

79

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.ic3.gov/img/fbi_seal_new.webp120.0 s115.9 KiB
www.ic3.gov/assets/css/uswds.min.css120.0 s47.5 KiB
www.ic3.gov/img/ic3_logo.webp120.0 s36.9 KiB
www.ic3.gov/img/losses.webp120.0 s24.6 KiB
www.ic3.gov/assets/js/uswds.min.js120.0 s23.5 KiB
www.ic3.gov/assets/fonts/merriweather/Latin-Merriweather-Regular.woff2120.0 s21.6 KiB
www.ic3.gov/assets/fonts/source-sans-pro/sourcesanspro-regular-webfont.woff2120.0 s20.5 KiB
www.ic3.gov/assets/fonts/source-sans-pro/sourcesanspro-light-webfont.woff2120.0 s20.3 KiB
www.ic3.gov/assets/fonts/source-sans-pro/sourcesanspro-bold-webfont.woff2120.0 s20.2 KiB
dap.digitalgov.gov/Universal-Federated-Analytics-Min.js?agency=DOJ0.0 ms9.4 KiB
www.ic3.gov/css/site.css120.0 s2.6 KiB
www.ic3.gov/assets/img/icon-https.svg120.0 s1.0 KiB
www.ic3.gov/assets/img/icon-dot-gov.svg120.0 s973 B
www.ic3.gov/assets/img/usa-icons-bg/search--white.svg120.0 s692 B
www.ic3.gov/assets/js/uswds-init.min.js120.0 s665 B
www.ic3.gov/assets/img/material-icons/rss_feed.svg120.0 s614 B
www.ic3.gov/assets/img/us_flag_small.png120.0 s580 B
www.ic3.gov/assets/img/usa-icons/error.svg120.0 s571 B
www.ic3.gov/assets/img/usa-icons/warning.svg120.0 s536 B
www.ic3.gov/assets/img/usa-icons/expand_more.svg120.0 s530 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.

Consider setting font-display to swap or optional to ensure text is consistently visible. swap can be further optimized to mitigate layout shifts with font metric overrides.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URLEst Savings
www.ic3.gov/assets/fonts/source-sans-pro/sourcesanspro-light-webfont.woff2195 ms
www.ic3.gov/assets/fonts/merriweather/Latin-Merriweather-Regular.woff2180 ms
www.ic3.gov/assets/fonts/source-sans-pro/sourcesanspro-bold-webfont.woff2165 ms
www.ic3.gov/assets/fonts/source-sans-pro/sourcesanspro-regular-webfont.woff2160 ms

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

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.ic3.gov/assets/css/uswds.min.css47.5 KiB549 ms
www.ic3.gov/assets/js/uswds-init.min.js665 B
www.ic3.gov/css/site.css2.6 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.

URLResource SizeEst Savings
FBI Seal div#foot > div.grid-col-auto > picture > img.usa-footer__logo-img
www.ic3.gov/img/fbi_seal_new.webp115.4 KiB114.2 KiB
IC3 Logo div.usa-logo > a > picture > img.usa-footer__logo-img
www.ic3.gov/img/ic3_logo.webp36.5 KiB33.3 KiB
Column chart showing complaint-reported losses over a five-year period: $4.2 bi… div > figure > picture > img
www.ic3.gov/img/losses.webp24.2 KiB15.9 KiB

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: 1.2 s
URLTime Spent
ic3.gov/1.2 s
www.ic3.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

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: 270 ms 45.6 KiB
URLTransfer SizeEst Savings
www.ic3.gov/assets/css/uswds.min.css47.2 KiB45.6 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
Column chart showing complaint-reported losses over a five-year period: $4.2 bi… div > figure > picture > img
www.ic3.gov/img/losses.webp
IC3 Logo div.usa-logo > a > picture > img.usa-footer__logo-img
www.ic3.gov/img/ic3_logo.webp
header.usa-banner__header > div.usa-banner__inner > div.grid-col-auto > img.usa-banner__header-flag header.usa-banner__header > div.usa-banner__inner > div.grid-col-auto > img.usa-banner__header-flag
www.ic3.gov/assets/img/us_flag_small.png
FBI Seal div#foot > div.grid-col-auto > picture > img.usa-footer__logo-img
www.ic3.gov/img/fbi_seal_new.webp
RSS Symbol section > header > a > img
www.ic3.gov/assets/img/material-icons/rss_feed.svg
RSS Symbol section.tablet:margin-0 > header > a > img
www.ic3.gov/assets/img/material-icons/rss_feed.svg

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
●Max Potential First Input Delay 30 ms
●Minify CSS
●Minify JavaScript
●Reduce unused JavaScript
●Avoids enormous network payloads Total size was 368 KiB
●JavaScript execution time 0.0 s
●Minimizes main-thread work 0.6 s
●Avoid long main-thread tasks 1 long task found
●Page didn't prevent back/forward cache restoration
●Network Requests
●Network Round Trip Times 150 ms
●Server Backend Latencies 50 ms
●Tasks
●Diagnostics
●Metrics
●Screenshot Thumbnails
●Final Screenshot
●Script Treemap Data
●Resources Summary
●Initial server response time was short Root document took 170 ms
●Avoid large layout shifts 3 layout shifts found
○INP breakdown
○LCP request discovery
○User Timing marks and measures
○Avoid non-composited animations
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.

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
FEDERAL BUREAU OF INVESTIGATION div#foot > div.grid-col-auto > div.agency > h3

These are opportunities to improve keyboard navigation in your application.

Best practices

Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Annual Report div > div.display-flex > div > a

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 are distinguishable without relying on color.
●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
●Skip links are focusable.
●Document has a main landmark.
●Deprecated ARIA roles were not used
●Identical links have the same purpose.
○`[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
○`<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.
○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.
○Uses ARIA roles only on compatible elements
○Image elements do not have `[alt]` attributes that are redundant text.
○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

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
dap.digitalgov.gov/Universal-Federated-Analytics-Min.js?agency=DOJ line 35, col 233
This document requires 'TrustedScriptURL' assignment and the 'default' policy failed to execute. The action has been blocked.
www.ic3.gov/ line 12, col 374
TrustedScriptURL Violation: https://dap.digitalgov.gov/web-vitals/dist/web-vitals.attribution.iife.js
dap.digitalgov.gov/Universal-Federated-Analytics-Min.js?agency=DOJ line 35, col 233
Uncaught TypeError: Failed to set the 'src' property on 'HTMLScriptElement': This document requires 'TrustedScriptURL' assignment and the 'default' policy failed to execute.

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
●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
●Ensure CSP is effective against XSS attacks
●Ensure proper origin isolation with COOP
●Page has valid source maps
○Redirects HTTP traffic to HTTPS
○Use a strong HSTS policy
○Mitigate clickjacking with XFO or CSP
○Mitigate DOM-based XSS with Trusted Types
○Detected JavaScript libraries
83

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

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.

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
●Page has successful HTTP status code
●Links have descriptive text
●Links are crawlable
●Image elements have `[alt]` attributes
●Document has a valid `hreflang`
○Document has a valid `rel=canonical`

Send Feedback