https://astonishing-marigold-c4563e.netlify.app

Lighthouse Desktop

· 0 checks — Desktop 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
js.stripe.com/v3	120.0 s	265.3 KiB
/engagement-browser/prod/split/27af780ed9b7852e0f27a662ae...	60.0 s	169.8 KiB
/engagement-browser/prod/split/27af780ed9b7852e0f27a662ae...	60.0 s	77.0 KiB
js.hs-analytics.net/analytics/1790946000000/7477936.js	300.0 s	43.5 KiB
cdn.amplitude.com/engagement-browser/prod/split/index.js	60.0 s	40.4 KiB
/analytics.js/v1/bHbADSxnRvrpFMYP6pMNP38JC4J7Av75/analyti...	120.0 s	30.4 KiB
/engagement-browser/prod/split/27af780ed9b7852e0f27a662ae...	60.0 s	29.7 KiB
js.hubspot.com/web-interactives-embed.js	600.0 s	28.3 KiB
js.hs-banner.com/v2/7477936/banner.js	300.0 s	24.3 KiB
/engagement-browser/prod/split/27af780ed9b7852e0f27a662ae...	60.0 s	23.1 KiB
/engagement-browser/prod/split/27af780ed9b7852e0f27a662ae...	60.0 s	21.7 KiB
/engagement-browser/prod/split/27af780ed9b7852e0f27a662ae...	60.0 s	14.8 KiB
/engagement-browser/prod/split/27af780ed9b7852e0f27a662ae...	60.0 s	13.9 KiB
m.stripe.network/out-4.5.45.js	300.0 s	14.0 KiB
cdn.segment.com/next-integrations/actions/3962/1faa179dfb20d0a3f5a0.js	0.0 ms	9.1 KiB
/engagement-browser/prod/split/27af780ed9b7852e0f27a662ae...	60.0 s	8.1 KiB
cdn.sift.com/s.js	86400.0 s	19.7 KiB
js.hsadspixel.net/pixels.js	600.0 s	5.3 KiB
/engagement-browser/prod/split/27af780ed9b7852e0f27a662ae...	60.0 s	3.1 KiB
/engagement-browser/prod/split/27af780ed9b7852e0f27a662ae...	60.0 s	3.0 KiB
/next-integrations/actions/amplitude-plugins/f12a4347e108...	0.0 ms	2.7 KiB
join.netlify.com/pr/js	14400.0 s	3.4 KiB
/engagement-browser/prod/split/27af780ed9b7852e0f27a662ae...	60.0 s	1.9 KiB
js-na1.hs-scripts.com/7477936.js	0.0 ms	1.3 KiB
/engagement-browser/prod/split/27af780ed9b7852e0f27a662ae...	60.0 s	1.0 KiB
/engagement-browser/prod/split/27af780ed9b7852e0f27a662ae...	60.0 s	987 B
/engagement-browser/prod/split/27af780ed9b7852e0f27a662ae...	60.0 s	945 B
/engagement-browser/prod/split/27af780ed9b7852e0f27a662ae...	60.0 s	913 B
www.gstatic.com/recaptcha/api2/logo_48.png	604800.0 s	2.3 KiB

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:0.581 source:map[column:1713 line:162 type:source-location url:https://app.netlify.com/assets/js/monitoring.vendor.c012580a8f2afda594c8.js 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:5.065 source:map[column:446 line:170 type:source-location url:https://www.gstatic.com/recaptcha/releases/kemdRjWFxNjgsGdhRslyEPwU/recaptcha__en.js urlProvider:network]] map[reflowTime:1.165 source:map[column:47 line:709 type:source-location url:https://www.gstatic.com/recaptcha/releases/kemdRjWFxNjgsGdhRslyEPwU/recaptcha__en.js urlProvider:network]] map[reflowTime:14.922 source:map[type:text value:[unattributed]]] map[reflowTime:1.389 source:map[column:7059 line:55 type:source-location url:https://cdn.sift.com/s.js urlProvider:network]] map[reflowTime:3.07 source:map[column:405 line:406 type:source-location url:https://www.gstatic.com/recaptcha/releases/kemdRjWFxNjgsGdhRslyEPwU/recaptcha__en.js urlProvider:network]] map[reflowTime:0.581 source:map[column:34873 line:171 type:source-location url:https://app.netlify.com/assets/js/monitoring.vendor.c012580a8f2afda594c8.js urlProvider:network]] map[reflowTime:1.006 source:map[column:86507 line:44 type:source-location url:https://js.hs-analytics.net/analytics/1790946000000/7477936.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

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
app.netlify.com/assets/js/app.a0f7af8e90e0c6ecd1cb.js	777.7 KiB	637 ms
app.netlify.com/assets/js/containers.b069c124dea8d438c76a.js	21.1 KiB
app.netlify.com/assets/js/runtime.0785fc80e6ed1c7e1393.js	18.4 KiB
app.netlify.com/assets/js/74899.c1fcfbc3efc89c6d34ce.js	336.4 KiB	290 ms
app.netlify.com/assets/js/monitoring.vendor.c012580a8f2afda594c8.js	244.4 KiB	232 ms
app.netlify.com/assets/js/actions.e07ac5b97410a8651f73.js	47.8 KiB	58 ms
app.netlify.com/assets/js/buildInfo.vendor.a766dc0d55ce38ae0f56.js	46.3 KiB	58 ms
app.netlify.com/assets/js/react.vendor.40cf545a9b4675eb6968.js	107.2 KiB	116 ms
app.netlify.com/assets/js/highcharts.vendor.062d44badf31a5e6140f.js	172.1 KiB	116 ms
app.netlify.com/assets/js/reactUiUtilities.vendor.9d4da4e73d390b9bdd1c.js	26.1 KiB	58 ms
app.netlify.com/assets/js/iso-3166.vendor.8f5322372851ddbd9305.js	54.1 KiB	58 ms
app.netlify.com/assets/js/graphiql.vendor.5504280cfbb32a6faef6.js	6.9 KiB
app.netlify.com/assets/js/graphql.vendor.5f6fef2f88e8d4c2c9ef.js	15.3 KiB
app.netlify.com/assets/js/relayRouterRedux.vendor.4fcd5c9d861a84e7d6b8.js	23.9 KiB
app.netlify.com/assets/js/ui.09e619ede87cb4781bb3.js	79.1 KiB	116 ms
app.netlify.com/assets/js/markdown.vendor.24df7c60576704bc90db.js	18.7 KiB
app.netlify.com/assets/js/lib.179500b1ad7adfc9dee2.js	62.7 KiB
app.netlify.com/assets/js/helpers.76dad575de075d21db44.js	36.9 KiB	58 ms
app.netlify.com/assets/js/lodash.vendor.3318fdd9dc27e5f1aab4.js	13.2 KiB	58 ms
app.netlify.com/assets/css/app.b24329d4cba9943eb913.css	78.6 KiB	174 ms
app.netlify.com/assets/css/74899.06a001937f5fb8e51e43.css	3.3 KiB

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
fonts.gstatic.com/s/roboto/v48/KFO7CnqEu92Fr1ME7kSn66aGLdTylUAMa3yUBHMdazQ.woff2	10 ms

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

Lists the toplevel main thread tasks that executed during page load.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Collection of useful page vitals.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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: 249 ms

URL	Time Spent
astonishing-marigold-c4563e.netlify.app/	249 ms
/edge-access?domain=astonishing-marigold-c4563e.netlify.a...	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.

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

Diagnostics

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.

Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay. Learn how to avoid long main-thread tasks

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.

Estimated savings: 170 ms 75.9 KiB

URL	Transfer Size	Est Savings
app.netlify.com/assets/css/app.b24329d4cba9943eb913.css	78.3 KiB	75.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: 1.8 s 2.3 MiB

URL	Transfer Size	Est Savings
app.netlify.com/assets/js/app.a0f7af8e90e0c6ecd1cb.js	777.1 KiB	644.0 KiB
app.netlify.com/assets/js/74899.c1fcfbc3efc89c6d34ce.js	336.2 KiB	252.3 KiB
js.stripe.com/v3	265.0 KiB	195.6 KiB
www.gstatic.com/recaptcha/releases/kemdRjWFxNjgsGdhRslyEPwU/recaptcha__en.js	346.3 KiB	181.8 KiB
app.netlify.com/assets/js/monitoring.vendor.c012580a8f2afda594c8.js	243.7 KiB	162.4 KiB
app.netlify.com/assets/js/highcharts.vendor.062d44badf31a5e6140f.js	171.9 KiB	161.4 KiB
www.googletagmanager.com/gtag/js?id=AW-957669464&cx=c&gtm=4e69u2	164.5 KiB	115.4 KiB
/engagement-browser/prod/split/27af780ed9b7852e0f27a662ae...	169.2 KiB	85.3 KiB
www.googletagmanager.com/gtm.js?id=GTM-WZQ32TR&l=dataLayer	159.5 KiB	71.6 KiB
app.netlify.com/assets/js/react.vendor.40cf545a9b4675eb6968.js	107.0 KiB	67.8 KiB
www.googletagmanager.com/gtag/js?id=AW-957669464	164.5 KiB	64.4 KiB
app.netlify.com/assets/js/ui.09e619ede87cb4781bb3.js	78.6 KiB	58.5 KiB
/engagement-browser/prod/split/27af780ed9b7852e0f27a662ae...	76.4 KiB	58.0 KiB
app.netlify.com/assets/js/lib.179500b1ad7adfc9dee2.js	62.5 KiB	50.4 KiB
app.netlify.com/assets/js/buildInfo.vendor.a766dc0d55ce38ae0f56.js	46.0 KiB	39.2 KiB
app.netlify.com/assets/js/actions.e07ac5b97410a8651f73.js	47.5 KiB	35.4 KiB
astonishing-marigold-c4563e.netlify.app/	54.6 KiB	30.9 KiB
app.netlify.com/assets/js/helpers.76dad575de075d21db44.js	36.7 KiB	23.3 KiB
/engagement-browser/prod/split/27af780ed9b7852e0f27a662ae...	22.6 KiB	21.0 KiB
cdn.amplitude.com/engagement-browser/prod/split/index.js	39.8 KiB	20.1 KiB

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
app.netlify.com/assets/js/app.a0f7af8e90e0c6ecd1cb.js	777.7 KiB
www.gstatic.com/recaptcha/releases/kemdRjWFxNjgsGdhRslyEPwU/recaptcha__en.js	346.9 KiB
www.gstatic.com/recaptcha/releases/kemdRjWFxNjgsGdhRslyEPwU/recaptcha__en.js	346.4 KiB
app.netlify.com/assets/js/74899.c1fcfbc3efc89c6d34ce.js	336.4 KiB
js.stripe.com/v3	265.3 KiB
app.netlify.com/assets/js/monitoring.vendor.c012580a8f2afda594c8.js	244.4 KiB
app.netlify.com/assets/js/highcharts.vendor.062d44badf31a5e6140f.js	172.1 KiB
/engagement-browser/prod/split/27af780ed9b7852e0f27a662ae...	169.8 KiB
www.googletagmanager.com/gtag/js?id=AW-957669464&cx=c&gtm=4e69u2	164.6 KiB
www.googletagmanager.com/gtag/js?id=AW-957669464	164.6 KiB

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

●Improve image delivery

●LCP breakdown

●Modern HTTP

●Optimize viewport for mobile

●Minify CSS

●Minify JavaScript

●User Timing marks and measures 7 user timings

●Image elements have explicit `width` and `height`

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 70 ms

●Server Backend Latencies 70 ms

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

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

○INP breakdown

○LCP request discovery

○Avoid non-composited animations

○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

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

●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

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

○Image elements have `[alt]` attributes

○Input buttons have discernible text.

○`<input type="image">` elements have `[alt]` text

○Form elements have associated labels

○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

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

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
astonishing-marigold-c4563e.netlify.app/	`Failed to load resource: the server responded with a status of 401 ()`

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 DOM-based XSS with Trusted Types

●Detected JavaScript libraries

○Redirects HTTP traffic to HTTPS

○Use a strong HSTS policy

○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

●robots.txt is valid

●Document has a valid `hreflang`

●Document has a valid `rel=canonical`

○Image elements have `[alt]` attributes