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

55

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.

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:2253.004 label:Time to first byte subpart:timeToFirstByte] map[duration:19.514 label:Resource load delay subpart:resourceLoadDelay] map[duration:106.747 label:Resource load duration subpart:resourceLoadDuration] map[duration:213.147 label:Element render delay subpart:elementRenderDelay]]
lhId: page-0-IMG
nodeLabel: Home Page Hero Image
path: 5,HTML,1,BODY,11,DIV,4,DIV,0,DIV,3,DIV,1,DIV,0,DIV,0,MAIN,0,SECTION,9,DIV,0,DIV,7,DIV,4,DIV,0,DIV,4,DIV,0,SECTION,0,DIV,0,DIV,0,DIV,1,DIV,0,DIV,0,IMG
selector: div.c-home-page-hero__left-wrapper > div.c-home-page-hero__left-content > div.c-home-page-hero__left-image > img
snippet: <img width="851" height="663" fetchpriority="high" src="/sites/default/files/2026-01/PLAIN%20HERO%20light%20blue.png" alt="Home Page Hero Image">

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
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.

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
connect.facebook.net/en_US/fbevents.js1200.0 s96.6 KiB
my.hellobar.com/modules-v2.js14400.0 s118.6 KiB
adaa.informz.net/web_trk/sp.js0.0 ms22.0 KiB
www.redditstatic.com/ads/pixel.js60.0 s19.0 KiB
assets.adobedtm.com/175f7caa2b90/6f3e0a100776/launch-c8ef5da8c000.min.js3600.0 s18.8 KiB
nexus.ensighten.com/choozle/16118/Bootstrap.js300.0 s9.3 KiB
adaa.org/cdn-cgi/challenge-platform/h/b/scripts/jsd/0b8fb825cb67/main.js?14400.0 s12.5 KiB
tags.crwdcntrl.net/lt/c/12671/lt.min.js86400.0 s20.0 KiB
static.hotjar.com/c/hotjar-5354568.js?sv=760.0 s6.2 KiB
/signals/config/1547202075599663?v=2.9.303&r=c2&domain=ad...1200.0 s4.9 KiB
adaa.org/cdn-cgi/scripts/7d0fa10a/cloudflare-static/rocket-loader.min.js2865.0 s4.0 KiB
static.adzerk.net/ados.js604800.0 s9.1 KiB
static.addtoany.com/menu/page.js86400.0 s2.2 KiB
/rp.gif?ts=1776897377261&id=a2_hnb5orov56py&event=gtm.loa...0.0 ms666 B
adaa.org/cdn-cgi/scripts/5c5dd728/cloudflare-static/email-decode.min.js2865.0 s730 B
twin-iq.kickfire.com/twin.js?169610.0 ms602 B
/twin.php?TWIQ=16961&kftwiqpg=https%3A%2F%2Fadaa.org%2F&H...0.0 ms250 B
insight.adsrvr.org/track/pxl/?adv=t4d9dkq&ct=0:ghjhvor&fmt=30.0 ms148 B
/identity/?key=c6c69b399c1b14ee35ff52d6b570ad258654dedae4...0.0 ms105 B
static.addtoany.com/menu/svg/icons/x.js864000.0 s782 B
/rp.gif?ts=1776897377256&id=a2_hnb5orov56py&event=gtm.ini...0.0 ms76 B
/rp.gif?ts=1776897377258&id=a2_hnb5orov56py&event=gtm.ini...0.0 ms76 B
/rp.gif?ts=1776897377259&id=a2_hnb5orov56py&event=gtm.js&...0.0 ms76 B
/rp.gif?ts=1776897377260&id=a2_hnb5orov56py&event=gtm.dom...0.0 ms76 B
/usersync/114/store?ext1=addc3960-3e9b-11f1-9524-115b2d9a...0.0 ms16 B

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
Post Image div#c-professional-bottom-link__module > div.field__item > a.c-professional-bottom-link__post-image > img.image-style-img350x200
/sites/default/files/styles/img350x200/public/thumbnails-...124.2 KiB113.9 KiB
Post Image div > div.c-find-help__column > a > img.image-style-img350x200
/sites/default/files/styles/img350x200/public/2021-02/fin...22.8 KiB11.4 KiB

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

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: 2.1 s
URLTime Spent
adaa.org/2.2 s

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.

Estimated savings: 1.2 s 158.2 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.8 s
Other892 ms
Script Parsing & Compilation458 ms
Style & Layout319 ms
Parse HTML & CSS101 ms
Rendering91 ms
Garbage Collection65 ms

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 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.

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 request discovery
●Modern HTTP
●Optimize viewport for mobile
●Minify CSS
●Avoids enormous network payloads Total size was 2,007 KiB
●User Timing marks and measures 5 user timings
●Avoid long main-thread tasks 18 long tasks found
●Image elements have explicit `width` and `height`
●Page didn't prevent back/forward cache restoration
●Network Requests
●Network Round Trip Times 100 ms
●Server Backend Latencies 260 ms
●Tasks
●Diagnostics
●Metrics
●Screenshot Thumbnails
●Final Screenshot
●Script Treemap Data
●Resources Summary
●Avoid multiple page redirects
●Avoid large layout shifts 2 layout shifts found
○INP breakdown
○Avoid non-composited animations
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
DONATE TODAY div.d-flex-padding-div > div.c-nav-bar__other-buttons > div.c-nav-bar__action-links > a.c-nav-bar__donate-link
FIND YOUR THERAPIST div.d-flex-padding-div > div.c-nav-bar__other-buttons > div.c-nav-bar__action-links > a.c-nav-bar__find-therapist-link
SEARCH div.d-flex-padding-div > div.c-nav-bar__other-buttons > div.c-nav-bar__action-links > a.c-nav-bar__donate-link
MENU div.c-nav-bar__unexpanded-menu > div.d-flex-padding-div > div.c-nav-bar__other-buttons > a#c-nav-bar__expand-menu-mobile
Listen Now! div.c-home-page-hero__content > div.c-home-page-hero__right > div.c-home-page-hero__right-post > a.c-home-page-hero__right-link
Read the Blog div.c-home-page-hero__content > div.c-home-page-hero__right > div.c-home-page-hero__right-post > a.c-home-page-hero__right-link
Subscribe div#c-public-bottom-link__module > div.c-public-bottom-link__post > div.c-public-bottom-link__post-content > a.c-public-bottom-link__post-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.
●Select elements have associated label elements.
●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 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
●Identical links have the same purpose.
○`[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
○Links are distinguishable without relying on color.
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○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.
73

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)
Home Page Hero Image div.c-home-page-hero__left-wrapper > div.c-home-page-hero__left-content > div.c-home-page-hero__left-image > img
adaa.org/sites/default/files/2026-01/PLAIN%20HERO%20light%20blue.png352 x 510 (0.69)700 x 500 (1.40)

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
Home Page Hero Image div.c-home-page-hero__left-wrapper > div.c-home-page-hero__left-content > div.c-home-page-hero__left-image > img
adaa.org/sites/default/files/2026-01/PLAIN%20HERO%20light%20blue.png352 x 510700 x 500528 x 765

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
●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 browser errors logged to the console
●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
●Page has valid source maps
○Redirects HTTP traffic to HTTPS
○Use a strong HSTS policy
○Mitigate clickjacking with XFO or CSP
92

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

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

Send Feedback