https://fadr.com/remix/6a7d59b94d98eba9a4f6f59f

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
connect.facebook.net/en_US/fbevents.js	1200.0 s	104.9 KiB
/public/client_js/capiParamBuilder/clientParamBuilder.bun...	0.0 ms	63.2 KiB
/signals/config/565325038898474?v=2.9.377&r=stable&domain...	1200.0 s	63.6 KiB
us-assets.i.posthog.com/static/surveys.js?v=1.410.1	14400.0 s	33.3 KiB
/array/phc_c83c64EFmv6EpiRVATmjjv9ci7endf2M1FQLAtYg9RN/co...	300.0 s	786 B
hatscripts.github.io/circle-flags/flags/us.svg	600.0 s	738 B
www.gstatic.com/recaptcha/api2/logo_48.png	604800.0 s	2.2 KiB

Layout shifts occur when elements move absent any user interaction. Investigate the causes of layout shifts, such as elements being added, removed, or their fonts changing as the page loads.

Why this matters

Performance issues directly impact user engagement and conversion rates.

headings: [map[key:node label:Element subItemsHeading:map[key:extra] valueType:node] map[granularity:0.001 key:score label:Layout shift score subItemsHeading:map[key:cause valueType:text] valueType:numeric]]

items: [map[node:map[type:text value:Total] score:0.1655429589977692] map[node:map[boundingRect:map[bottom:4454 height:4401 left:0 right:412 top:53 width:412] lhId:page-1-DIV nodeLabel:Remix Help Collab Something went wrong. Library Choose a pack and find tracks … path:1,HTML,1,BODY,0,DIV,0,DIV,0,DIV,1,DIV selector:div#__next > div#file-drag > div#layout > div.page snippet:<div class="page _remix"> type:node] score:0.1318347509113001 subItems:map[items:[map[cause:Web font extra:map[type:url value:https://fonts.gstatic.com/s/roboto/v48/KFO7CnqEu92Fr1ME7kSn66aGLdTylUAMa3yUBHMdazQ.woff2]]] type:subitems]] map[node:map[boundingRect:map[bottom:4454 height:4401 left:0 right:412 top:53 width:412] lhId:page-1-DIV nodeLabel:Remix Help Collab Something went wrong. Library Choose a pack and find tracks … path:1,HTML,1,BODY,0,DIV,0,DIV,0,DIV,1,DIV selector:div#__next > div#file-drag > div#layout > div.page snippet:<div class="page _remix"> type:node] score:0.004784394843569373] map[node:map[boundingRect:map[bottom:4454 height:4401 left:0 right:412 top:53 width:412] lhId:page-1-DIV nodeLabel:Remix Help Collab Something went wrong. Library Choose a pack and find tracks … path:1,HTML,1,BODY,0,DIV,0,DIV,0,DIV,1,DIV selector:div#__next > div#file-drag > div#layout > div.page snippet:<div class="page _remix"> type:node] score:0.004695857736786702] map[node:map[boundingRect:map[bottom:4454 height:4401 left:0 right:412 top:53 width:412] lhId:page-1-DIV nodeLabel:Remix Help Collab Something went wrong. Library Choose a pack and find tracks … path:1,HTML,1,BODY,0,DIV,0,DIV,0,DIV,1,DIV selector:div#__next > div#file-drag > div#layout > div.page snippet:<div class="page _remix"> type:node] score:0.004556915841489143] map[node:map[boundingRect:map[bottom:4454 height:4401 left:0 right:412 top:53 width:412] lhId:page-1-DIV nodeLabel:Remix Help Collab Something went wrong. Library Choose a pack and find tracks … path:1,HTML,1,BODY,0,DIV,0,DIV,0,DIV,1,DIV selector:div#__next > div#file-drag > div#layout > div.page snippet:<div class="page _remix"> type:node] score:0.004305399407082821]]

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	55 ms

Optimize LCP by making the LCP image discoverable from the HTML immediately, and avoiding lazy-loading

Why this matters

Performance issues directly impact user engagement and conversion rates.

lhId: page-0-IMG

nodeLabel: "Modern Trap" pack artwork - Fadr

path: 1,HTML,1,BODY,0,DIV,0,DIV,0,DIV,1,DIV,2,DIV,2,DIV,1,BUTTON,0,IMG

selector: div.library-browser > div.flex > button.pack-preview > img.song-preview-image

snippet: <img alt=""Modern Trap" pack artwork - Fadr" loading="lazy" width="368" height="135" decoding="async" data-nimg="1" class="song-preview-image" srcset="/_next/image?url=https%3A%2F%2Fsongtostems-songs.s3.us-east-1.amazonaws.co…" src="/_next/image?url=https%3A%2F%2Fsongtostems-songs.s3.us-east-1.amazonaws.co…" style="color: transparent;">

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
"Pop Rock" pack artwork - Fadr `div.library-browser > div.flex > button.pack-preview > img.song-preview-image`	/_next/image?url=https%3A%2F%2Fsongtostems-songs.s3.us-ea...	41.8 KiB	29.4 KiB
"Nu Disco House" pack artwork - Fadr `div.library-browser > div.flex > button.pack-preview > img.song-preview-image`	/_next/image?url=https%3A%2F%2Fsongtostems-songs.s3.us-ea...	31.4 KiB	17.8 KiB

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

These are the largest layout shifts observed on the page. Each table item represents a single layout shift, and shows the element that shifted the most. Below each item are possible root causes that led to the layout shift. Some of these layout shifts may not be included in the CLS metric value due to windowing. Learn how to improve CLS

Why this matters

Performance issues directly impact user engagement and conversion rates.

Element	Layout shift score
Remix Help Collab Something went wrong. Library Choose a pack and find tracks … `div#__next > div#file-drag > div#layout > div.page`	0.132
Remix Help Collab Something went wrong. Library Choose a pack and find tracks … `div#__next > div#file-drag > div#layout > div.page`	0.005
Remix Help Collab Something went wrong. Library Choose a pack and find tracks … `div#__next > div#file-drag > div#layout > div.page`	0.005
Remix Help Collab Something went wrong. Library Choose a pack and find tracks … `div#__next > div#file-drag > div#layout > div.page`	0.005
Remix Help Collab Something went wrong. Library Choose a pack and find tracks … `div#__next > div#file-drag > div#layout > div.page`	0.004
Remix Help Collab Something went wrong. Library Choose a pack and find tracks … `div#__next > div#file-drag > div#layout > div.page`	0.004
Remix Help Collab Something went wrong. Library Choose a pack and find tracks … `div#__next > div#file-drag > div#layout > div.page`	0.004
Remix Help Collab Something went wrong. Library Choose a pack and find tracks … `div#__next > div#file-drag > div#layout > div.page`	0.004
Remix Help Collab Something went wrong. Library Choose a pack and find tracks … `div#__next > div#file-drag > div#layout > div.page`	0.004

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

Many navigations are performed by going back to a previous page, or forwards again. The back/forward cache (bfcache) can speed up these return navigations. Learn more about the bfcache

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.

Estimated savings: 4.4 s 649.6 KiB

URL	Transfer Size	Est Savings
www.gstatic.com/recaptcha/releases/XOqlk8PL_yVx6IdpLbpXdiLy/recaptcha__en.js	335.8 KiB	180.8 KiB
www.googletagmanager.com/gtag/js?id=G-60EFHN20ZK&cx=c&gtm=4e68c0h2	183.9 KiB	71.5 KiB
www.googletagmanager.com/gtm.js?id=GTM-KW5FTPV	158.7 KiB	65.8 KiB
www.googletagmanager.com/gtag/js?id=AW-339071403&cx=c&gtm=4e68c0h2	154.8 KiB	58.4 KiB
fadr.com/_next/static/chunks/pages/_app-3ee1ae18aa524866.js	91.6 KiB	54.1 KiB
/public/client_js/capiParamBuilder/clientParamBuilder.bun...	62.8 KiB	40.8 KiB
app.posthog.com/static/array.js	70.1 KiB	40.6 KiB
connect.facebook.net/en_US/fbevents.js	104.8 KiB	37.0 KiB
fadr.com/_next/static/chunks/7055-4a5e6154e1049117.js	33.3 KiB	31.2 KiB
us-assets.i.posthog.com/static/surveys.js?v=1.410.1	32.8 KiB	26.7 KiB
fadr.com/_next/static/chunks/pages/plus/%5B%5B...plus%5D%5D-d4727c164b3fbaac.js	24.3 KiB	21.9 KiB
/signals/config/565325038898474?v=2.9.377&r=stable&domain...	63.5 KiB	20.8 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
fadr.com/_next/static/chunks/framework-19baaf6675f9027b.js	1.1 s	771 ms	14 ms
www.gstatic.com/recaptcha/releases/XOqlk8PL_yVx6IdpLbpXdiLy/recaptcha__en.js	788 ms	593 ms	64 ms
Unattributable	696 ms	45 ms	0.0 ms
fadr.com/remix/6a7d59b94d98eba9a4f6f59f	615 ms	17 ms	0.6 ms
www.googletagmanager.com/gtag/js?id=G-60EFHN20ZK&cx=c&gtm=4e68c0h2	301 ms	257 ms	41 ms
connect.facebook.net/en_US/fbevents.js	244 ms	217 ms	25 ms
www.googletagmanager.com/gtm.js?id=GTM-KW5FTPV	243 ms	197 ms	41 ms
www.googletagmanager.com/gtag/js?id=AW-339071403&cx=c&gtm=4e68c0h2	219 ms	187 ms	30 ms
app.posthog.com/static/array.js	139 ms	112 ms	23 ms
/signals/config/565325038898474?v=2.9.377&r=stable&domain...	131 ms	110 ms	20 ms
fadr.com/_next/static/chunks/pages/_app-3ee1ae18aa524866.js	131 ms	79 ms	22 ms
fadr.com/_next/static/chunks/main-d896c0f1e7e19d3c.js	106 ms	93 ms	8.2 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	2.9 s
Other	1.2 s
Script Parsing & Compilation	328 ms
Rendering	232 ms
Style & Layout	211 ms
Garbage Collection	89 ms
Parse HTML & CSS	20 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
api.fadr.com/public	516.7 KiB
www.gstatic.com/recaptcha/releases/XOqlk8PL_yVx6IdpLbpXdiLy/recaptcha__en.js	336.4 KiB
www.gstatic.com/recaptcha/releases/XOqlk8PL_yVx6IdpLbpXdiLy/recaptcha__en.js	335.7 KiB
www.googletagmanager.com/gtag/js?id=G-60EFHN20ZK&cx=c&gtm=4e68c0h2	184.0 KiB
www.googletagmanager.com/gtm.js?id=GTM-KW5FTPV	159.0 KiB
www.googletagmanager.com/gtag/js?id=AW-339071403&cx=c&gtm=4e68c0h2	154.8 KiB
connect.facebook.net/en_US/fbevents.js	104.9 KiB
fadr.com/_next/static/chunks/pages/_app-3ee1ae18aa524866.js	92.0 KiB
app.posthog.com/static/array.js	70.7 KiB
/signals/config/565325038898474?v=2.9.377&r=stable&domain...	63.6 KiB

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

●Document request latency

●Optimize DOM size

●Forced reflow

●LCP breakdown

●Modern HTTP

●Network dependency tree

●Render blocking requests

●Optimize viewport for mobile

●Minify CSS

●Minify JavaScript

●Reduce unused CSS

●User Timing marks and measures 4 user timings

●Avoid long main-thread tasks 18 long tasks found

●Avoid non-composited animations 1 animated element found

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

●Network Requests

●Network Round Trip Times 110 ms

●Server Backend Latencies 290 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 110 ms

○INP breakdown

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.

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
Demo Songs `button.pack-preview > div.vertical-flex > div.pack-preview-title > h4`
[6] `button.pack-preview > div.vertical-flex > div.pack-preview-title > h6`
[20] `button.pack-preview > div.vertical-flex > div.pack-preview-title > h6`
[5] `button.pack-preview > div.vertical-flex > div.pack-preview-title > h6`
[5] `button.pack-preview > div.vertical-flex > div.pack-preview-title > h6`
[10] `button.pack-preview > div.vertical-flex > div.pack-preview-title > h6`
[5] `button.pack-preview > div.vertical-flex > div.pack-preview-title > h6`
[5] `button.pack-preview > div.vertical-flex > div.pack-preview-title > h6`
[5] `button.pack-preview > div.vertical-flex > div.pack-preview-title > h6`
[5] `button.pack-preview > div.vertical-flex > div.pack-preview-title > h6`
[5] `button.pack-preview > div.vertical-flex > div.pack-preview-title > h6`
[5] `button.pack-preview > div.vertical-flex > div.pack-preview-title > h6`
[5] `button.pack-preview > div.vertical-flex > div.pack-preview-title > h6`
[5] `button.pack-preview > div.vertical-flex > div.pack-preview-title > h6`
[5] `button.pack-preview > div.vertical-flex > div.pack-preview-title > h6`
[5] `button.pack-preview > div.vertical-flex > div.pack-preview-title > h6`
[5] `button.pack-preview > div.vertical-flex > div.pack-preview-title > h6`
[5] `button.pack-preview > div.vertical-flex > div.pack-preview-title > h6`
[5] `button.pack-preview > div.vertical-flex > div.pack-preview-title > h6`
[5] `button.pack-preview > div.vertical-flex > div.pack-preview-title > h6`
[5] `button.pack-preview > div.vertical-flex > div.pack-preview-title > h6`
[5] `button.pack-preview > div.vertical-flex > div.pack-preview-title > h6`
[5] `button.pack-preview > div.vertical-flex > div.pack-preview-title > h6`
[5] `button.pack-preview > div.vertical-flex > div.pack-preview-title > h6`
[5] `button.pack-preview > div.vertical-flex > div.pack-preview-title > h6`
[5] `button.pack-preview > div.vertical-flex > div.pack-preview-title > h6`

These are opportunities to improve keyboard navigation in your application.

Best practices

One main landmark helps screen reader users navigate a web page. Learn more about landmarks.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html `html`

These items highlight common accessibility best practices.

○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

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

●Links have a discernible name

●Touch targets have sufficient size and spacing.

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

○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

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

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

○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
api.fadr.com/remixes/6a7d59b94d98eba9a4f6f59f	`Failed to load resource: the server responded with a status of 500 ()`

●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

●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

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
fadr.com/menu	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

●Image elements have `[alt]` attributes

●Document has a valid `hreflang`

○robots.txt is valid

○Document has a valid `rel=canonical`