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.

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.

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.

URL	Transfer Size	Duration
www.google.com/recaptcha/enterprise.js	1.0 KiB	891 ms

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
/homepage-refresh-how-it-works-video-still-d-7-23.jpg	0.0 ms	481.1 KiB
d25oniaj7o2jcw.cloudfront.net/smartcoach.jpg	0.0 ms	131.1 KiB
transcend-cdn.com/cm/8aaeb48f-a8e6-4725-820c-b18c4f7cd6cc/ui.js	60.0 s	93.3 KiB
cdn.optimizely.com/js/23507871404.js	120.0 s	94.0 KiB
connect.facebook.net/en_US/bundle/sdk.js/	1200.0 s	77.8 KiB
transcend-cdn.com/cm/8aaeb48f-a8e6-4725-820c-b18c4f7cd6cc/airgap.js	60.0 s	57.0 KiB
d25oniaj7o2jcw.cloudfront.net/hawaii.jpg	0.0 ms	24.6 KiB
d25oniaj7o2jcw.cloudfront.net/gfmgivingfunds.jpg	0.0 ms	19.7 KiB
d25oniaj7o2jcw.cloudfront.net/lupita.jpg	0.0 ms	16.5 KiB
static.chartbeat.com/js/chartbeat.js	86400.0 s	15.9 KiB
connect.facebook.net/en_US/sdk.js	1200.0 s	6.9 KiB
transcend-cdn.com/cm/8aaeb48f-a8e6-4725-820c-b18c4f7cd6cc/cm.css	60.0 s	4.2 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.

	URL	Resource Size	Est Savings
div.hrt-container > div.video_videoPreviewContainer__waGpY > picture > img.video_image__NT0b7 `div.hrt-container > div.video_videoPreviewContainer__waGpY > picture > img.video_image__NT0b7`	/homepage-refresh-how-it-works-video-still-d-7-23.jpg	480.2 KiB	448.3 KiB
Wireframe mobile UI for sharing a fundraiser link to social networks `div.how-it-works-steps_content__gC9HX > div.how-it-works-steps_columns__SU7vs > div.how-it-works-steps_imageContainer__y0dWy > img.home-how-it-works-image`	www.gofundme.com/nextassets/home/howitworks/step-2.en.png	102.4 KiB	72.5 KiB
Wireframe mobile UI for creating a fundraiser and setting a monetary goal `div.how-it-works-steps_content__gC9HX > div.how-it-works-steps_columns__SU7vs > div.how-it-works-steps_imageContainer__y0dWy > img.home-how-it-works-image`	www.gofundme.com/nextassets/home/howitworks/step-1.en-us.png	41.5 KiB	29.4 KiB
Wireframe mobile UI for bank transfer settings `div.how-it-works-steps_content__gC9HX > div.how-it-works-steps_columns__SU7vs > div.how-it-works-steps_imageContainer__y0dWy > img.home-how-it-works-image`	www.gofundme.com/nextassets/home/howitworks/step-3.en-us.png	39.0 KiB	27.7 KiB
New `li.merch-card_merch-unit__936GP > a.merch-card_merch-unit-link__U4Zki > div.merch-card_merch-unit-link__U4Zki > div.merch-card_merch-unit-image__S5lyz`	d25oniaj7o2jcw.cloudfront.net/smartcoach.jpg	130.6 KiB	19.8 KiB
Medical Support for Dharma Teja Kanulla `a.card_link__KbsfM > div.card_container__TjAss > div.card_imageContainer__2RJ99 > img.card-image_image___GL8n`	/EGLtI12uxYklWDVE46eF7bnd-cA=/720x405/https://d2g8igdw686...	30.8 KiB	19.6 KiB
A Race Against Time to save our 3-year-old son Gurmoh `a.card_link__KbsfM > div.card_container__TjAss > div.card_imageContainer__2RJ99 > img.card-image_image___GL8n`	/wxAwjyRtHr9M4hwYwUo40G7g-Sg=/720x405/https://i.ytimg.com...	26.9 KiB	15.8 KiB
Operación para fractura de cuello `a.card_link__KbsfM > div.card_container__TjAss > div.card_imageContainer__2RJ99 > img.card-image_image___GL8n`	/3yH6tJVgMgwG6-ZQJABQ7bjkZkM=/720x405/https://d2g8igdw686...	15.2 KiB	8.8 KiB

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

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

URL	Time Spent
gofund.me/	1.1 s
www.gofundme.com/	0.0 ms

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: 450 ms 67.5 KiB

URL	Transfer Size	Est Savings
www.gofundme.com/ssr/_next/static/css/9ff8b4810ddcab7b.css	71.5 KiB	67.5 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: 1.8 s 1.6 MiB

URL	Transfer Size	Est Savings
www.gstatic.com/recaptcha/releases/gTpTIWhbKpxADzTzkcabhXN4/recaptcha__en.js	361.8 KiB	241.7 KiB
www.gofundme.com/ssr/_next/static/chunks/pages/_app-c97a9f77ff07650f.js	402.7 KiB	153.6 KiB
www.gofundme.com/ssr/_next/static/chunks/41659-d73388a4319f0f8b.js	157.5 KiB	133.7 KiB
www.googletagmanager.com/gtag/js?id=G-WF86BFEZ5L&cx=c&gtm=4e64h1h1	174.0 KiB	111.0 KiB
www.gofundme.com/ssr/_next/static/chunks/ac262c97-05d574404bcbdf98.js	125.1 KiB	93.4 KiB
www.gofundme.com/ssr/_next/static/chunks/1b25d643-c3cc5c2633675ebb.js	81.7 KiB	72.1 KiB
accounts.google.com/gsi/client	95.6 KiB	72.0 KiB
www.gofundme.com/ssr/_next/static/chunks/pages/s-ae68de969a16dd64.js	103.4 KiB	68.8 KiB
www.googletagmanager.com/gtag/js?id=G-D71Z0789ZK&cx=c&gtm=4e64h1	156.3 KiB	66.2 KiB
www.googletagmanager.com/gtag/js?id=G-DE4PB0SD88&cx=c&gtm=4e64h1	156.9 KiB	66.0 KiB
www.googletagmanager.com/gtag/js?id=AW-945652478&cx=c&gtm=4e64h1	144.5 KiB	65.0 KiB
www.googletagmanager.com/gtag/js?id=G-WF86BFEZ5L	174.1 KiB	64.7 KiB
www.googletagmanager.com/gtag/js?id=AW-955875456&cx=c&gtm=4e64h1	147.0 KiB	63.7 KiB
www.googletagmanager.com/gtm.js?id=GTM-PW9SXF3N&l=dataLayer	181.7 KiB	63.6 KiB
www.googletagmanager.com/gtm.js?id=GTM-TDTFTZ	115.0 KiB	62.4 KiB
www.googletagmanager.com/gtag/js?id=DC-13981538&cx=c&gtm=4e64h1	131.5 KiB	59.2 KiB
cdn.optimizely.com/js/23507871404.js	93.4 KiB	55.3 KiB
connect.facebook.net/en_US/bundle/sdk.js/	77.6 KiB	53.7 KiB
transcend-cdn.com/cm/8aaeb48f-a8e6-4725-820c-b18c4f7cd6cc/ui.js	92.9 KiB	37.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.

URL	Total CPU Time	Script Evaluation	Script Parse
www.gofundme.com/ssr/_next/static/chunks/framework-c41ad6c83d422ded.js	1.8 s	1.6 s	18 ms
www.gofundme.com/	1.3 s	8.8 ms	2.1 ms
Unattributable	832 ms	43 ms	0.0 ms
www.gofundme.com/ssr/_next/static/chunks/pages/_app-c97a9f77ff07650f.js	645 ms	474 ms	147 ms
www.gofundme.com/ssr/_next/static/chunks/8a2eb0bf.0c06a0d09a071bc1.js	419 ms	307 ms	11 ms
www.googletagmanager.com/gtm.js?id=GTM-PW9SXF3N&l=dataLayer	393 ms	317 ms	70 ms
www.googletagmanager.com/gtag/js?id=G-DE4PB0SD88&cx=c&gtm=4e64h1	346 ms	241 ms	33 ms
www.googletagmanager.com/gtag/js?id=G-D71Z0789ZK&cx=c&gtm=4e64h1	249 ms	213 ms	32 ms
transcend-cdn.com/cm/8aaeb48f-a8e6-4725-820c-b18c4f7cd6cc/ui.js	234 ms	186 ms	28 ms
www.googletagmanager.com/gtag/js?id=AW-955875456&cx=c&gtm=4e64h1	216 ms	181 ms	33 ms
www.googletagmanager.com/gtag/js?id=DC-13981538&cx=c&gtm=4e64h1	213 ms	176 ms	26 ms
www.googletagmanager.com/gtag/js?id=AW-945652478&cx=c&gtm=4e64h1	183 ms	149 ms	33 ms
www.gstatic.com/recaptcha/releases/gTpTIWhbKpxADzTzkcabhXN4/recaptcha__en.js	162 ms	84 ms	78 ms
cdn.optimizely.com/js/23507871404.js	156 ms	118 ms	37 ms
www.googletagmanager.com/gtm.js?id=GTM-TDTFTZ	137 ms	102 ms	30 ms
www.gofundme.com/ssr/_next/static/chunks/main-515fe902c792b8d3.js	124 ms	101 ms	20 ms
www.googletagmanager.com/gtag/js?id=G-WF86BFEZ5L	117 ms	71 ms	46 ms
transcend-cdn.com/cm/8aaeb48f-a8e6-4725-820c-b18c4f7cd6cc/airgap.js	104 ms	88 ms	12 ms
static.chartbeat.com/js/chartbeat.js	84 ms	76 ms	5.5 ms
www.gofundme.com/ssr/_next/static/chunks/pages/index-6f61545b19049be4.js	83 ms	71 ms	6.6 ms
accounts.google.com/gsi/client	80 ms	63 ms	16 ms
connect.facebook.net/en_US/bundle/sdk.js/	75 ms	56 ms	18 ms
www.gofundme.com/ssr/_next/static/chunks/ac262c97-05d574404bcbdf98.js	72 ms	63 ms	8.5 ms
www.gofundme.com/ssr/_next/static/chunks/1b25d643-c3cc5c2633675ebb.js	65 ms	36 ms	29 ms
www.googletagmanager.com/gtag/js?id=G-WF86BFEZ5L&cx=c&gtm=4e64h1h1	64 ms	24 ms	40 ms

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	5.0 s
Other	1.4 s
Script Parsing & Compilation	890 ms
Style & Layout	491 ms
Rendering	247 ms
Garbage Collection	243 ms
Parse HTML & CSS	135 ms

Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Transfer Size
/homepage-refresh-how-it-works-video-still-d-7-23.jpg	481.1 KiB
www.gofundme.com/ssr/_next/static/chunks/pages/_app-c97a9f77ff07650f.js	403.2 KiB
www.gstatic.com/recaptcha/releases/gTpTIWhbKpxADzTzkcabhXN4/recaptcha__en.js	362.4 KiB
www.gofundme.com/	207.5 KiB
www.googletagmanager.com/gtm.js?id=GTM-PW9SXF3N&l=dataLayer	181.7 KiB
www.googletagmanager.com/gtag/js?id=G-WF86BFEZ5L	174.2 KiB
www.googletagmanager.com/gtag/js?id=G-WF86BFEZ5L&cx=c&gtm=4e64h1h1	174.1 KiB
www.gofundme.com/nextassets/home/hero-education-3.png	160.4 KiB
www.googletagmanager.com/gtag/js?id=G-DE4PB0SD88&cx=c&gtm=4e64h1	156.9 KiB
www.googletagmanager.com/gtag/js?id=G-D71Z0789ZK&cx=c&gtm=4e64h1	156.4 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
div.hrt-container > div.video_videoPreviewContainer__waGpY > picture > img.video_image__NT0b7 `div.hrt-container > div.video_videoPreviewContainer__waGpY > picture > img.video_image__NT0b7`	/homepage-refresh-how-it-works-video-still-d-7-23.jpg

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 breakdown

●Modern HTTP

●Optimize viewport for mobile

●Minify CSS

●Minify JavaScript

●User Timing marks and measures 20 user timings

●Avoid long main-thread tasks 20 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 100 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 110 ms

○INP breakdown

○LCP request discovery

○Avoid large layout shifts

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.

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

●Elements with visible text labels have matching accessible names.

○`[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

○Links are distinguishable without relying on color.

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

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

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.

Source	Description
auth.gofundme.com/v1/auth/refresh?dcs=f&dcr=f	`Failed to load resource: the server responded with a status of 400 ()`
api.gofundme.com/person/v2/account	`Failed to load resource: the server responded with a status of 401 ()`
www.gofundme.com/	`Not signed in with the identity provider.`

Source maps translate minified code to the original source code. This helps developers debug in production. In addition, Lighthouse is able to provide further insights. Consider deploying source maps to take advantage of these benefits. Learn more about source maps.

Why this matters

Performance issues directly impact user engagement and conversion rates.

●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

●No issues in the `Issues` panel in Chrome Devtools

●Ensure CSP is effective against XSS attacks

●Ensure proper origin isolation with COOP

●Mitigate clickjacking with XFO or CSP

●Mitigate DOM-based XSS with Trusted Types

●Detected JavaScript libraries

○Redirects HTTP traffic to HTTPS

○Use a strong HSTS policy

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.

Link destination	Link Text
www.gofundme.com/c/how-it-works	Learn more
www.gofundme.com/c/how-it-works	Learn more

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`