Skip to content
https://www.amplitude.com

Lighthouse Desktop

· 0 checks — Desktop 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.

74

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.

RequestCache TTLTransfer Size
/engagement-browser/prod/split/df9b61a9061fbc33ed8e6b620d...60.0 s167.8 KiB
cdn.amplitude.com/script/e3e918f274fa30555c627abdb29840d5.experiment.js60.0 s134.3 KiB
/engagement-browser/prod/split/df9b61a9061fbc33ed8e6b620d...60.0 s64.8 KiB
cdn.amplitude.com/engagement-browser/prod/split/index.js60.0 s40.1 KiB
ob.roundprincemusic.com/i/8356b7ffc20afc0a5275c6176232dc10.js43200.0 s44.5 KiB
/engagement-browser/prod/split/df9b61a9061fbc33ed8e6b620d...60.0 s21.6 KiB
/engagement-browser/prod/split/df9b61a9061fbc33ed8e6b620d...60.0 s20.8 KiB
/engagement-browser/prod/split/df9b61a9061fbc33ed8e6b620d...60.0 s19.7 KiB
/engagement-browser/prod/split/df9b61a9061fbc33ed8e6b620d...60.0 s16.2 KiB
/engagement-browser/prod/split/df9b61a9061fbc33ed8e6b620d...60.0 s13.5 KiB
cc.cdn.civiccomputing.com/9/cookieControl-9.x.min.js604800.0 s123.2 KiB
snap.licdn.com/li.lms-analytics/insight.min.js86400.0 s18.7 KiB
/loader.js?orgId=9E80167060B7C1CB0A495E43%40AdobeOrg&inst...548.0 s6.0 KiB
/engagement-browser/prod/split/df9b61a9061fbc33ed8e6b620d...60.0 s3.4 KiB
/engagement-browser/prod/split/df9b61a9061fbc33ed8e6b620d...60.0 s2.4 KiB
/engagement-browser/prod/split/df9b61a9061fbc33ed8e6b620d...60.0 s1.9 KiB
/engagement-browser/prod/split/df9b61a9061fbc33ed8e6b620d...60.0 s1.0 KiB
/engagement-browser/prod/split/df9b61a9061fbc33ed8e6b620d...60.0 s1011 B
/engagement-browser/prod/split/df9b61a9061fbc33ed8e6b620d...60.0 s971 B
/engagement-browser/prod/split/df9b61a9061fbc33ed8e6b620d...60.0 s913 B
/collect?v=2&fmt=js&pid=38806&time=1775593491921&url=http...0.0 ms695 B
/engagement-browser/prod/split/df9b61a9061fbc33ed8e6b620d...60.0 s676 B

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:4.489 source:map[column:1959 line:11 type:source-location url:https://www.amplitude.com/_next/static/chunks/pages/_app-7eea1b37d0ebcc42.js?dpl=dpl_CNAx5ojJ92fNRGQzyqyxV2P745Sw 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:24.648 source:map[column:94285 line:0 type:source-location url:https://fast.wistia.net/assets/external/E-v1.js urlProvider:network]] map[reflowTime:1.822 source:map[column:84723 line:0 type:source-location url:https://fast.wistia.net/assets/external/popover.js@49b80af9d2806884c566f240cb7a5b25caa013f7 urlProvider:network]] map[reflowTime:1.889 source:map[column:93687 line:0 type:source-location url:https://fast.wistia.net/assets/external/E-v1.js urlProvider:network]] map[reflowTime:0.358 source:map[column:70169 line:0 type:source-location url:https://client-registry.mutinycdn.com/mutiny-client/223.5.6.3.js urlProvider:network]] map[reflowTime:19.402 source:map[type:text value:[unattributed]]]]

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.

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
div.flex > div.max-w-[540px] > div.absolute > img.object-contain div.flex > div.max-w-[540px] > div.absolute > img.object-contain
/_next/image?url=https%3A%2F%2Fcdn.sanity.io%2Fimages%2Fl...110.4 KiB94.8 KiB
div.flex > div.max-w-[540px] > div.absolute > img.object-contain div.flex > div.max-w-[540px] > div.absolute > img.object-contain
/_next/image?url=https%3A%2F%2Fcdn.sanity.io%2Fimages%2Fl...101.2 KiB87.0 KiB
div.flex > div.max-w-[540px] > div.absolute > img.object-contain div.flex > div.max-w-[540px] > div.absolute > img.object-contain
/_next/image?url=https%3A%2F%2Fcdn.sanity.io%2Fimages%2Fl...100.4 KiB86.3 KiB
div.flex > div.max-w-[540px] > div.absolute > img.object-contain div.flex > div.max-w-[540px] > div.absolute > img.object-contain
/_next/image?url=https%3A%2F%2Fcdn.sanity.io%2Fimages%2Fl...100.1 KiB86.0 KiB
div.flex > div.max-w-[540px] > div.absolute > img.object-contain div.flex > div.max-w-[540px] > div.absolute > img.object-contain
/_next/image?url=https%3A%2F%2Fcdn.sanity.io%2Fimages%2Fl...94.8 KiB81.5 KiB
div.flex > div.max-w-[540px] > div.absolute > img.object-contain div.flex > div.max-w-[540px] > div.absolute > img.object-contain
/_next/image?url=https%3A%2F%2Fcdn.sanity.io%2Fimages%2Fl...76.6 KiB65.8 KiB
div.flex > a.group > div.w-[294px] > img.bg-black div.flex > a.group > div.w-[294px] > img.bg-black
/_next/image?url=https%3A%2F%2Fcdn.sanity.io%2Fimages%2Fl...68.6 KiB61.9 KiB
div.flex > a.group > div.w-[294px] > img.bg-black div.flex > a.group > div.w-[294px] > img.bg-black
/_next/image?url=https%3A%2F%2Fcdn.sanity.io%2Fimages%2Fl...66.1 KiB59.4 KiB
div.flex > a.group > div.w-[294px] > img.bg-black div.flex > a.group > div.w-[294px] > img.bg-black
/_next/image?url=https%3A%2F%2Fcdn.sanity.io%2Fimages%2Fl...46.7 KiB39.9 KiB
div.flex > a.group > div.w-[294px] > img.bg-black div.flex > a.group > div.w-[294px] > img.bg-black
/_next/image?url=https%3A%2F%2Fcdn.sanity.io%2Fimages%2Fl...44.8 KiB38.0 KiB

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

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.

CategoryTime Spent
Script Evaluation2.8 s
Other795 ms
Style & Layout222 ms
Script Parsing & Compilation137 ms
Garbage Collection70 ms
Rendering60 ms
Parse HTML & CSS22 ms

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.

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.cursor-pointer > div.flex > div.w-[24px] > img div.cursor-pointer > div.flex > div.w-[24px] > img
/images/l5rq9j6r/production/7c7a672b13caa4f4bb0b4cf0fb049...
div.cursor-pointer > div.flex > div.w-[24px] > img div.cursor-pointer > div.flex > div.w-[24px] > img
/images/l5rq9j6r/production/9b74192d80688c514cee9b8cbe45a...
div.cursor-pointer > div.flex > div.w-[24px] > img div.cursor-pointer > div.flex > div.w-[24px] > img
/images/l5rq9j6r/production/209be063d9e977042afbe0a1a8840...
div.cursor-pointer > div.flex > div.w-[24px] > img div.cursor-pointer > div.flex > div.w-[24px] > img
/images/l5rq9j6r/production/8cead378a75edf83180014015008e...
div.cursor-pointer > div.flex > div.w-[24px] > img div.cursor-pointer > div.flex > div.w-[24px] > img
/images/l5rq9j6r/production/428b41e896c5a722033887725217e...
div.cursor-pointer > div.flex > div.w-[24px] > img div.cursor-pointer > div.flex > div.w-[24px] > img
/images/l5rq9j6r/production/819d8983ea4f71e8a83c75821e081...
div.cursor-pointer > div.flex > div.w-[24px] > img div.cursor-pointer > div.flex > div.w-[24px] > img
/images/l5rq9j6r/production/fefec1970062451aa118ce3d4e727...
div.cursor-pointer > div.flex > div.w-[24px] > img div.cursor-pointer > div.flex > div.w-[24px] > img
/images/l5rq9j6r/production/e4a46eb6cfe4e0fa596a4dcc3bd86...

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
Font display
LCP breakdown
Modern HTTP
Optimize viewport for mobile
Minify CSS
Minify JavaScript
User Timing marks and measures 7 user timings
Avoid long main-thread tasks 13 long tasks found
Avoid non-composited animations 3 animated elements found
Page didn't prevent back/forward cache restoration
Network Requests
Network Round Trip Times 100 ms
Server Backend Latencies 340 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 260 ms
Avoid large layout shifts 2 layout shifts found
INP breakdown
LCP request discovery
90

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.

Names and labels

When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.fixed > div.relative > div.h-[54px] > button.h-12.5 div.fixed > div.relative > div.h-[54px] > button.h-12.5
div.absolute > div.relative > div.MediaBlockView_video-container___sctQ > button.MediaBlockView_media-player__TxiV_ div.absolute > div.relative > div.MediaBlockView_video-container___sctQ > button.MediaBlockView_media-player__TxiV_
div.absolute > div.relative > div.MediaBlockView_video-container___sctQ > button.MediaBlockView_media-player__TxiV_ div.absolute > div.relative > div.MediaBlockView_video-container___sctQ > button.MediaBlockView_media-player__TxiV_
div.absolute > div.relative > div.MediaBlockView_video-container___sctQ > button.MediaBlockView_media-player__TxiV_ div.absolute > div.relative > div.MediaBlockView_video-container___sctQ > button.MediaBlockView_media-player__TxiV_

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
header.pt-[17px] > nav.relative > div.flex > a header.pt-[17px] > nav.relative > div.flex > a
div.fixed > div.relative > div.h-[54px] > a div.fixed > div.relative > div.h-[54px] > 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.

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
AI div.flex > div.flex-1 > div.flex > h4.px-3
AI Agents div.w-[294px] > div.flex > div.flex > h6.text-white
The Forrester Wave™: Digital Analytics Solutions, Q3 2025 a > div.flex > div.flex-1 > h4.font-gellix

These are opportunities to improve keyboard navigation in your application.

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
Case Study div.hidden > div > div.inline-block > a
Case Study div.hidden > div > div.inline-block > a
Case Study div.hidden > div > div.inline-block > a
Case Study div.hidden > div > div.inline-block > a
AI Agents Sense, analyze, and optimize your data-driven issues 24/7. Learn mo… div.relative > div.w-full > div.flex > a.group
MCP Prompt new Amplitude insights in Claude, Cursor, or any AI platform. Lear… div.relative > div.w-full > div.flex > a.group
AI Feedback Transform what your customers say anywhere into action. Learn more div.relative > div.w-full > div.flex > a.group
AI Visibility Reveal how LLMs talk about your brand so you can win AI search. … div.relative > div.w-full > div.flex > a.group
Report The Product Benchmark Report: How Top Teams Win and Grow Discover the s… div.max-w-[1140px] > div.hidden > div.w-full > a.group
Report The Forrester Wave™: Digital Analytics Solutions, Q3 2025 Forrester nam… div.hidden > div.w-full > div.flex > a
Guide AI Analytics Buyer’s Guide Learn what to look for in an analytics platfo… div.hidden > div.w-full > div.flex > a
Guide The Modern Guide to Data Democratization Discover five steps to safely m… div.hidden > div.w-full > div.flex > a
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.
`button`, `link`, and `menuitem` elements have accessible names
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.
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.
Document has a main landmark.
Deprecated ARIA roles were not used
`<video>` elements contain a `<track>` element with `[kind="captions"]`
Identical links have the same purpose.
`[accesskey]` values are unique
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
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
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.
77

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.

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
Failed to load resource: the server responded with a status of 404 ()
Failed to load resource: the server responded with a status of 429 ()

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.

URLMap URL
/_next/static/chunks/pages/_app-7eea1b37d0ebcc42.js?dpl=d...
cdn.amplitude.com/script/e3e918f274fa30555c627abdb29840d5.experiment.js
/engagement-browser/prod/split/df9b61a9061fbc33ed8e6b620d...
/assets/external/popover.js@49b80af9d2806884c566f240cb7a5...fast.wistia.net/assets/external/popover.js.map
/assets/external/playPauseLoadingControl.js@49b80af9d2806...fast.wistia.net/assets/external/playPauseLoadingControl.js.map
fast.wistia.net/assets/external/marketoForm.jsfast.wistia.net/assets/external/marketoForm.js.map
/assets/external/interFontFace.js@49b80af9d2806884c566f24...fast.wistia.net/assets/external/interFontFace.js.map
fast.wistia.net/assets/external/E-v1.jsfast.wistia.net/assets/external/E-v1.js.map
fast.wistia.net/assets/external/captions.jsfast.wistia.net/assets/external/captions.js.map
fast.wistia.net/assets/external/captions.jsfast.wistia.net/assets/external/captions.js.map
fast.wistia.net/assets/external/captions.jsfast.wistia.net/assets/external/captions.js.map
/assets/external/allIntegrations.js@49b80af9d2806884c566f...fast.wistia.net/assets/external/allIntegrations.js.map
/loader.js?orgId=9E80167060B7C1CB0A495E43%40AdobeOrg&inst...assets.adoberesources.net/loader.js.map
/builds/9f3ebe7d468ed39ab91c3bfd3f7de0214e72e953/dist/cor.../builds/9f3ebe7d468ed39ab91c3bfd3f7de0214e72e953/dist/cor...
/builds/9f3ebe7d468ed39ab91c3bfd3f7de0214e72e953/dist/cor.../builds/9f3ebe7d468ed39ab91c3bfd3f7de0214e72e953/dist/cor...
/assets/external/engines/hls_video.js@49b80af9d2806884c56...fast.wistia.net/assets/external/engines/hls_video.js.map
browser.sentry-cdn.com/9.6.1/bundle.min.jsbrowser.sentry-cdn.com/9.6.1/bundle.min.js.map
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 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
Redirects HTTP traffic to HTTPS
Mitigate clickjacking with XFO or CSP
85

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 destinationLink Text
amplitude.com/privacy#cookiesClick Here

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
Manage Settings p > div.ccc-description > div.ccc-actions > a.ccc-manage-settings-btn

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