Lighthouse Mobile

· 0 checks — Mobile Lighthouse audit -- Performance, Accessibility, Best Practices, and SEO category breakdown.

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Detailed Report

Audit breakdown by category with detailed findings.

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.

Request	Cache TTL	Transfer Size
lib.thehotline.us/font/gotham/gotham-800.woff2	0.0 ms	59.8 KiB
lib.thehotline.us/font/gotham/gotham-400.woff2	0.0 ms	58.8 KiB
lib.thehotline.us/font/gotham/gotham-300.woff2	0.0 ms	58.3 KiB
/cdn-cgi/challenge-platform/h/b/scripts/jsd/0b8fb825cb67/...	14400.0 s	13.1 KiB
chat.thehotline.us/p/v3/thl-chat-widget.js?k=02699376-4775-49f4-73f0-328e315075e	0.0 ms	7.2 KiB
/beacon.min.js/v8c78df7c7c0f484497ecbca7046644da177152312...	86400.0 s	10.7 KiB

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:2.266 source:map[column:2196 line:67 type:source-location url:https://www.thehotline.org/wp-content/themes/hotline-main/assets/scripts/libs.js?ver=1762318808 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:38.317 source:map[column:60 line:1782 type:source-location url:https://www.thehotline.org/ urlProvider:network]] map[reflowTime:0.83 source:map[column:50 line:54 type:source-location url:https://www.thehotline.org/wp-content/themes/hotline-main/assets/scripts/libs.js?ver=1762318808 urlProvider:network]] map[reflowTime:3.966 source:map[column:3742 line:66 type:source-location url:https://www.thehotline.org/wp-content/themes/hotline-main/assets/scripts/libs.js?ver=1762318808 urlProvider:network]] map[reflowTime:3.324 source:map[column:24 line:162 type:source-location url:https://www.thehotline.org/wp-content/themes/hotline-main/assets/scripts/app.js?ver=1762318808 urlProvider:network]] map[reflowTime:41.057 source:map[type:text value:[unattributed]]] map[reflowTime:0.703 source:map[column:8666 line:0 type:source-location url:https://www.thehotline.org/cdn-cgi/challenge-platform/scripts/jsd/main.js urlProvider:network]]]

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.

URL	Transfer Size	Duration
www.thehotline.org/wp-includes/js/jquery/jquery.min.js?ver=3.7.1	31.2 KiB	787 ms
/wp-content/themes/hotline-main/assets/styles/app.css?ver...	32.8 KiB	316 ms
www.thehotline.org/wp-includes/js/jquery/jquery-migrate.min.js?ver=3.4.1	5.4 KiB	473 ms

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.

URL	Est Savings
/wp-content/themes/hotline-main/assets/fonts/icomoon/font...	10 ms

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.

	URL	Resource Size	Est Savings
div.socials1 > div.footer1-badges > a > img.alignnone `div.socials1 > div.footer1-badges > a > img.alignnone`	/wp-content/uploads/media/2025/07/Charity-Navigator_4-Sta...	11.1 KiB	9.9 KiB
div.socials1 > div.footer1-badges > a > img.alignnone `div.socials1 > div.footer1-badges > a > img.alignnone`	www.thehotline.org/wp-content/uploads/media/2025/07/2026-Platinum-Seal.png	8.0 KiB	6.3 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: 780 ms

URL	Time Spent
thehotline.org/	780 ms
www.thehotline.org/	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

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.

Estimated savings: 150 ms 6.0 KiB

URL	Transfer Size	Est Savings
/wp-content/themes/hotline-main/assets/styles/app.css?ver...	32.8 KiB	6.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: 300 ms 25.9 KiB

URL	Transfer Size	Est Savings
/wp-content/themes/hotline-main/assets/styles/app.css?ver...	32.3 KiB	25.9 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: 600 ms 181.5 KiB

URL	Transfer Size	Est Savings
www.googletagmanager.com/gtag/js?id=G-X0XC77RC6Q&cx=c&gtm=4e64m0h2	156.6 KiB	66.0 KiB
www.googletagmanager.com/gtm.js?id=GTM-NR3HV5VV	120.5 KiB	64.4 KiB
/wp-content/themes/hotline-main/assets/scripts/libs.js?ve...	41.3 KiB	30.5 KiB
www.thehotline.org/wp-includes/js/jquery/jquery.min.js?ver=3.7.1	30.7 KiB	20.5 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.

Category	Time Spent
Script Evaluation	1.1 s
Style & Layout	716 ms
Other	578 ms
Script Parsing & Compilation	157 ms
Rendering	129 ms
Parse HTML & CSS	76 ms
Garbage Collection	6.8 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.

Estimated savings: 0.0 ms 5.1 KiB

URL	Transfer Size	Est Savings
/wp-content/themes/hotline-main/assets/scripts/app.js?ver...	8.7 KiB	3.1 KiB
chat.thehotline.us/p/v3/thl-chat-widget.js?k=02699376-4775-49f4-73f0-328e315075e	6.8 KiB	2.0 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
The Hotline `div.top2-wrap > h1.logo1 > a > img`	www.thehotline.org/wp-content/themes/hotline-main/assets/images/logo-ndvh.svg
The Hotline `div.sidenav1-header > h1.logo1 > a > img`	www.thehotline.org/wp-content/themes/hotline-main/assets/images/logo-ndvh.svg
div.contact1-header > figure > span.img1 > img.lazyautosizes `div.contact1-header > figure > span.img1 > img.lazyautosizes`	/wp-content/uploads/media/2025/07/the-hotline-connect-ico...
div.contact1-header > figure > span.img1 > img.lazyautosizes `div.contact1-header > figure > span.img1 > img.lazyautosizes`	/wp-content/uploads/media/2025/07/the-hotline-connect-ico...
div.contact1-header > figure > span.img1 > img.lazyload `div.contact1-header > figure > span.img1 > img.lazyload`
div.contact1-header > figure > span.img1 > img.lazyload `div.contact1-header > figure > span.img1 > img.lazyload`

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

●Layout shift culprits

●Optimize DOM size

●LCP breakdown

●Modern HTTP

●Optimize viewport for mobile

●Avoids enormous network payloads Total size was 932 KiB

●User Timing marks and measures 5 user timings

●JavaScript execution time 1.2 s

●Avoid long main-thread tasks 11 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 10 ms

●Server Backend Latencies 80 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

●Initial server response time was short Root document took 400 ms

●Avoid large layout shifts 1 layout shift found

○INP breakdown

○LCP request discovery

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
exit `div.exit1 > p.exit1-wrap > a > span`

These are opportunities to improve the legibility of your content.

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
We are here to serve all those affected by relationship abuse 24/7 confidential… `div.hero3-main > h1.title1 > span > h3`

These are opportunities to improve keyboard navigation in your application.

Names and labels

Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
address > div.socials1 > div.footer1-badges > a `address > div.socials1 > div.footer1-badges > a`
address > div.socials1 > div.footer1-badges > a `address > div.socials1 > div.footer1-badges > a`

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

○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

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

●`[accesskey]` values are unique

●ARIA attributes are used as specified for the element's role

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

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

●Document has a main landmark.

●Deprecated ARIA roles were not used

●Uses ARIA roles only on compatible elements

○`button`, `link`, and `menuitem` elements have accessible names

○Elements with `role="dialog"` or `role="alertdialog"` have accessible names.

○`[aria-hidden="true"]` elements do not contain focusable descendents

○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

○Buttons have an accessible name

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

○Skip links are focusable.

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

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

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 / Warning	Source
SharedStorage	www.thehotline.org/cdn-cgi/challenge-platform/scripts/jsd/main.js
StorageType.persistent is deprecated. Please use standardized navigator.storage instead.	www.thehotline.org/cdn-cgi/challenge-platform/scripts/jsd/main.js
Fledge	www.thehotline.org/cdn-cgi/challenge-platform/scripts/jsd/main.js

●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 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 clickjacking with XFO or CSP

●Mitigate DOM-based XSS with Trusted Types

●Detected JavaScript libraries

●Page has valid source maps

○Redirects HTTP traffic to HTTPS

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

●robots.txt is valid

●Image elements have `[alt]` attributes

●Document has a valid `hreflang`

●Document has a valid `rel=canonical`