Skip to content
https://american.edu

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.

56

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.

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
Portion of the AU campus map div.flexrow > div.area > div.beyond-photo > img.lazyload
american.edu/images/map-mobile.png326.8 KiB315.4 KiB
home div#washSpotlight > div#slides > picture > img
american.edu/customcf/assets/2021-images/home_m.jpg156.5 KiB133.2 KiB
Clawed the eagle and students dancing on a basketball court div.flexrow > div.area > div.beyond-photo > img.lazyload
american.edu/images/clawed-mobile.jpg109.5 KiB98.1 KiB
classroom div#washSpotlight > div#slides > picture > img
american.edu/customcf/assets/2021-images/classroom_m.jpg105.5 KiB82.2 KiB
playground div#washSpotlight > div#slides > picture > img
american.edu/customcf/assets/2021-images/playground_m.jpg104.3 KiB81.0 KiB
lab div#washSpotlight > div#slides > picture > img
american.edu/customcf/assets/2021-images/lab_m.jpg75.9 KiB52.6 KiB
community div#washSpotlight > div#slides > picture > img
american.edu/customcf/assets/2021-images/community_m.jpg64.0 KiB42.4 KiB
Photo by Jeff Watts. div#gridCol_1_1_1_1_5727554 > div#cs_control_5727557 > article > img
american.edu/news/images/D26_298_020-3_2_5589884_600x315.JPG52.4 KiB39.9 KiB
AU WordMark div.col-xs-12 > div.video-background-content > div.content > img
american.edu/images/your-purpose-wordmark.png43.4 KiB39.4 KiB
2026 commencement speakers div#gridCol_1_1_1_1_5727552 > div#cs_control_5727555 > article > img
/news/images/26-116_Cment_Speakers_Spr_2026_1200x630_5589...41.3 KiB28.8 KiB
You Belong at AU wordmark div.belong-container > div.flexrow > div.area > img.lazyload
american.edu/images/YouBelongAtAU_lockup.png29.5 KiB17.3 KiB
The Artemis II rocket captured with the moon. Photo courtesy of NASA. div#gridCol_1_1_1_1_5727553 > div#cs_control_5727556 > article > img
/news/images/Artemis-II-at-the-pad-Full-Snow-Moon-0201202...14.4 KiB8.6 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-12-IMG
nodeLabel: mobile hero watching over monument
path: 1,HTML,1,BODY,5,DIV,2,MAIN,2,SECTION,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,2,DIV,0,DIV,0,DIV,1,IMG
selector: div.bv-wrap > div.row > div.col-xs-12 > img.visible-xs
snippet: <img class="visible-xs" src="/images/mobile-hero.jpg" alt="mobile hero watching over monument">

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

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

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.

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.

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.

Estimated savings: 460 ms 83.8 KiB

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
Other1.3 s
Script Evaluation1.2 s
Style & Layout438 ms
Script Parsing & Compilation113 ms
Rendering108 ms
Parse HTML & CSS98 ms

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
div.panel > div#heading-left-E3B0C44298FC1C149AFBF4C8996FB92427AE41E4649B934CA495991B7852B855 > div.panel-title > img.is-decorative div.panel > div#heading-left-E3B0C44298FC1C149AFBF4C8996FB92427AE41E4649B934CA495991B7852B855 > div.panel-title > img.is-decorative
american.edu/about/images/clawed5-2.jpg
You Belong at AU wordmark div.belong-container > div.flexrow > div.area > img.lazyload
american.edu/images/YouBelongAtAU_lockup.png
mobile hero watching over monument div.bv-wrap > div.row > div.col-xs-12 > img.visible-xs
american.edu/images/mobile-hero.jpg
2026 commencement speakers div#gridCol_1_1_1_1_5727552 > div#cs_control_5727555 > article > img
/news/images/26-116_Cment_Speakers_Spr_2026_1200x630_5589...
The Artemis II rocket captured with the moon. Photo courtesy of NASA. div#gridCol_1_1_1_1_5727553 > div#cs_control_5727556 > article > img
/news/images/Artemis-II-at-the-pad-Full-Snow-Moon-0201202...
Photo by Jeff Watts. div#gridCol_1_1_1_1_5727554 > div#cs_control_5727557 > article > img
american.edu/news/images/D26_298_020-3_2_5589884_600x315.JPG
AU WordMark div.col-xs-12 > div.video-background-content > div.content > img
american.edu/images/your-purpose-wordmark.png
Portion of the AU campus map div.flexrow > div.area > div.beyond-photo > img.lazyload
american.edu/images/map-mobile.png
Clawed the eagle and students dancing on a basketball court div.flexrow > div.area > div.beyond-photo > img.lazyload
american.edu/images/clawed-mobile.jpg
Welcome New Eagles! Deposit Deadline for undergraduate students is May 1. div.row-center > a > picture > img
american.edu/about/images/DepositReminderMobile_2025.png
American University Homepage span > span > a.crest > img#logo-full
american.edu/customcf/assets/crest-logotype.svg
American University in Washington, DC div#ftr-flex-context > div#ftr-logo-home > a > img
american.edu/customcf/2016-redesign/images/logos/crest-logotype-blue.svg

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

●Layout shift culprits
●Document request latency
●Optimize DOM size
●Forced reflow
●LCP breakdown
●Modern HTTP
●Optimize viewport for mobile
●JavaScript execution time 1.1 s
●Avoid long main-thread tasks 6 long tasks found
●Avoid non-composited animations 1 animated element found
●Page didn't prevent back/forward cache restoration
●Network Requests
●Network Round Trip Times 20 ms
●Server Backend Latencies 150 ms
●Tasks
●Diagnostics
●Metrics
●Screenshot Thumbnails
●Final Screenshot
●Script Treemap Data
●Resources Summary
●Avoid multiple page redirects
●Initial server response time was short Root document took 160 ms
●Avoid large layout shifts 9 layout shifts found
○INP breakdown
○User Timing marks and measures
100

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.

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
Privacy Notice div#onetrust-group-container > div#onetrust-policy > div#onetrust-policy-text > a.ot-cookie-policy-link
○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
●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
●Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
●`[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
●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.
●Deprecated ARIA roles were not used
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements 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
○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.
○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.
69

Best Practices

User Experience

Image display dimensions should match natural aspect ratio. Learn more about image aspect ratio.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URLAspect Ratio (Displayed)Aspect Ratio (Actual)
playground div#washSpotlight > div#slides > picture > img
american.edu/customcf/assets/2021-images/playground_m.jpg412 x 347 (1.19)766 x 554 (1.38)
lab div#washSpotlight > div#slides > picture > img
american.edu/customcf/assets/2021-images/lab_m.jpg412 x 347 (1.19)766 x 554 (1.38)
classroom div#washSpotlight > div#slides > picture > img
american.edu/customcf/assets/2021-images/classroom_m.jpg412 x 347 (1.19)766 x 554 (1.38)
home div#washSpotlight > div#slides > picture > img
american.edu/customcf/assets/2021-images/home_m.jpg412 x 347 (1.19)766 x 554 (1.38)
community div#washSpotlight > div#slides > picture > img
american.edu/customcf/assets/2021-images/community_m.jpg412 x 347 (1.19)766 x 554 (1.38)

Image natural dimensions should be proportional to the display size and the pixel ratio to maximize image clarity. Learn how to provide responsive images.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URLDisplayed sizeActual sizeExpected size
mobile hero watching over monument div.bv-wrap > div.row > div.col-xs-12 > img.visible-xs
american.edu/images/mobile-hero.jpg412 x 581426 x 601618 x 872

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
StorageType.persistent is deprecated. Please use standardized navigator.storage instead.
Fledge

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
Access to font at 'https://cloudfront.american.edu/assets/fonts/GT-Walsheim-Bold-Oblique.woff' from origin 'https://american.edu' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.
Access to font at 'https://cloudfront.american.edu/assets/fonts/GT-Walsheim-Bold.woff' from origin 'https://american.edu' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.
Access to font at 'https://cloudfront.american.edu/assets/fonts/GT-Walsheim-Regular-Oblique.woff' from origin 'https://american.edu' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.
Access to font at 'https://cloudfront.american.edu/assets/fonts/GT-Walsheim-Regular.woff' from origin 'https://american.edu' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.
Failed to load resource: net::ERR_FAILED
Failed to load resource: net::ERR_FAILED
Failed to load resource: net::ERR_FAILED
Failed to load resource: net::ERR_FAILED
●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
●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
●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
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

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

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
Cookie Preferences div#ftr-address-policies > ul.clearfix > li > a

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
●robots.txt is valid
●Image elements have `[alt]` attributes
●Document has a valid `hreflang`
○Document has a valid `rel=canonical`

Send Feedback