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

41

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
/sites/faa.gov/files/styles/faa_by_the_numbers_back/publi...2591.0 s581.1 KiB
www.faa.gov/themes/custom/faa/fonts/Lato/Lato-Semibold.woff21255.0 s180.1 KiB
www.faa.gov/sites/faa.gov/files/2023-02/aviation.jpg3373.0 s185.2 KiB
/sites/faa.gov/files/css/css_p9F6AjmDoFFSmS8e_l9d5QtoKLLn...1822.0 s45.5 KiB
/sites/faa.gov/files/js/js_-IDDgUY54vBFaZ-wnmt6hmsMMT0JH9...86.0 s39.2 KiB
/sites/faa.gov/files/js/js_t93kQP2c6wtHK4Vh5Hlrk6OAbWYyig...1473.0 s31.6 KiB
/sites/faa.gov/files/js/js_oQ1_vNDnKkOlwPYNL611aNqxALicHY...1851.0 s27.3 KiB
/sites/faa.gov/files/styles/faa_home_priorities_card/publ...3063.0 s23.5 KiB
/sites/faa.gov/files/styles/faa_home_priorities_card/publ...389.0 s19.7 KiB
/sites/faa.gov/files/js/js_DYXGbe7PgkjgAXERy9PsBpLbSvMEu5...2143.0 s20.6 KiB
www.google-analytics.com/analytics.js7200.0 s20.9 KiB
/sites/faa.gov/files/styles/faa_home_priorities_card/publ...1851.0 s17.7 KiB
/sites/faa.gov/files/css/css_NuAOq9yAl6SoIMrLcr1yQmoN5dr1...1425.0 s15.0 KiB
/sites/faa.gov/files/css/css_Cma74XMrE9FlgSoDro7nayfIjSWN...2614.0 s14.0 KiB
www.faa.gov/themes/custom/faa/images/logo-faa.svg1050.0 s12.2 KiB
/sites/faa.gov/files/styles/faa_home_news_image/public/20...1346.0 s11.8 KiB
dap.digitalgov.gov/Universal-Federated-Analytics-Min.js?agency=DOT0.0 ms9.5 KiB
www.faa.gov/akam/13/7dd5141d21600.0 s9.4 KiB
/sites/faa.gov/files/js/js_1DzfAiRK6xExZPPQyR3k7bfQREeAlK...2736.0 s5.6 KiB
dap.digitalgov.gov/web-vitals/dist/web-vitals.attribution.iife.js0.0 ms4.6 KiB
/sites/faa.gov/files/js/js_CvdUhVGZLyQvPV6aJ73oK2u18NkDsM...3250.0 s4.7 KiB
/sites/faa.gov/files/js/js_hApV7douVzMQ-1gpxBNyIR_SQYvukk...1821.0 s2.4 KiB
www.faa.gov/modules/contrib/collapsiblock/theme/dist/collapsiblock.js?tdk0161930.0 s1.7 KiB
www.faa.gov/themes/custom/dot_cms/js/custom.js?v=10.6.71705.0 s1.4 KiB
/sites/faa.gov/files/js/js_I6maBgOLeB-WpTpMaqZ3pnbo0qcPZZ...2591.0 s1.2 KiB
www.faa.gov/themes/custom/dot_cms/js/leftnav.js?v=10.6.71704.0 s841 B
www.faa.gov/themes/custom/faa/js/custom.js?v=10.6.72067.0 s735 B
www.faa.gov/themes/custom/dot_cms/images/assets/icon-dot-gov.svg2582.0 s674 B
www.faa.gov/themes/custom/dot_cms/images/assets/icon-https.svg1004.0 s622 B
www.faa.gov/core/misc/throbber-inactive.png1435.0 s629 B
www.faa.gov/themes/custom/dot_cms/images/assets/us_flag_small.svg917.0 s519 B
www.faa.gov/modules/contrib/purge_ajax_processor/js/trigger_purge.js?tdk0162127.0 s544 B
www.faa.gov/themes/custom/faa/js/global.js?v=10.6.7928.0 s445 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.

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-SECTION
nodeLabel: Providing the Safest, Most Efficient Aerospace System in the World.
path: 1,HTML,1,BODY,4,DIV,0,DIV,0,DIV,4,MAIN,1,DIV,0,DIV,0,DIV,0,SECTION
selector: div.hero-space > div.view-content > div > section.jumbotron
snippet: <section data-history-node-id="71" class="jumbotron jumbotron-fluid hero home-hero node node--type-homepage-image no…" style="background-image: url(/sites/faa.gov/files/2023-02/aviation.jpg)">

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

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
FAA By the Numbers 19,482 U.S. Airports 44,360 Average Daily Flights Handled by… div.container > div.row > div.col-12 > section.numbers
/sites/faa.gov/files/styles/faa_by_the_numbers_back/publi...580.5 KiB513.7 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: 2.1 s
URLTime Spent
faa.gov/1.1 s
www.faa.gov/1.1 s
www.faa.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

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

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.

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 Evaluation1.8 s
Other538 ms
Script Parsing & Compilation396 ms
Style & Layout357 ms
Parse HTML & CSS94 ms
Garbage Collection78 ms
Rendering71 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
Home div.row > div.col-10 > a.navbar-brand > img.img-fluid
www.faa.gov/themes/custom/faa/images/logo-faa.svg
Chicago O'Hare Airport div.col-12 > div.views-field > span.field-content > img.image-style-faa-home-news-image
/sites/faa.gov/files/styles/faa_home_news_image/public/20...
U.S. flag div.collapsed > div.usa-banner-guidance-gov > div.usa-media_block-icon > img.usa-banner-flag
www.faa.gov/themes/custom/dot_cms/images/assets/us_flag_small.svg
Controller at night div.card > div.card__featured_img > div.featured__gradient > img.image-style-faa-home-topics-main

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
●Minify JavaScript
●User Timing marks and measures 29 user timings
●Avoid long main-thread tasks 16 long tasks found
●Network Requests
●Network Round Trip Times 90 ms
●Server Backend Latencies 330 ms
●Tasks
●Diagnostics
●Metrics
●Screenshot Thumbnails
●Final Screenshot
●Script Treemap Data
●Resources Summary
●Initial server response time was short Root document took 210 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.

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
form > div.row > div.home__form > input.btn form > div.row > div.home__form > input.btn
div.quick_search-delays > form#faa-airport-status-lookup-form > div.col-4 > input#airport-code-status-search-submit div.quick_search-delays > form#faa-airport-status-lookup-form > div.col-4 > input#airport-code-status-search-submit

These are opportunities to improve the legibility of your content.

Navigation

A value greater than 0 implies an explicit navigation ordering. Although technically valid, this often creates frustrating experiences for users who rely on assistive technologies. Learn more about the `tabindex` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
form > div.row > div.col-12 > span.tool form > div.row > div.col-12 > span.tool

These are opportunities to improve keyboard navigation in your application.

○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
●Input buttons have discernible text.
●Form elements have associated labels
●`[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
●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
●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
○`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
○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 type="image">` elements have `[alt]` text
○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.
○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.
81

Best Practices

Trust and Safety

All sites should be protected with HTTPS, even ones that don't handle sensitive data. This includes avoiding mixed content, where some resources are loaded over HTTP despite the initial request being served over HTTPS. HTTPS prevents intruders from tampering with or passively listening in on the communications between your app and your users, and is a prerequisite for HTTP/2 and many new web platform APIs. Learn more about HTTPS.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Insecure URLRequest Resolution
www.faa.gov/Allowed
●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 browser errors logged to the console
●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
●Page has valid source maps
○Redirects HTTP traffic to HTTPS
○Mitigate clickjacking with XFO or CSP
100

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.

○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 have descriptive text
●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