Skip to content
https://fadr.com/remix/6a7d59b94d98eba9a4f6f59f

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.

53

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.

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:1.0073039799492165] map[node:map[boundingRect:map[bottom:2083 height:1938 left:68 right:1268 top:146 width:1200] lhId:page-6-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,2,DIV selector:div#__next > div#file-drag > div#layout > div.page snippet:<div class="page _remix"> type:node] score:0.9080260047281324 subItems:map[items:[map[cause:Unsized image element extra:map[boundingRect:map[bottom:2327 height:43 left:100 right:257 top:2283 width:157] lhId:page-14-IMG nodeLabel:Fadr Logo path:1,HTML,1,BODY,0,DIV,0,DIV,0,DIV,3,FOOTER,0,DIV,1,DIV,0,DIV,0,DIV,0,A,0,IMG selector:div > div.flex > a > img snippet:<img alt="Fadr Logo" loading="lazy" width="157" height="44" decoding="async" data-nimg="1" style="color:transparent" src="/assets/images/logo/logo.svg"> type:node]]] type:subitems]] map[node:map[boundingRect:map[bottom:2494 height:410 left:0 right:1335 top:2083 width:1335] lhId:page-1-FOOTER nodeLabel:HOME Fadr Fadr Plus CREATE Stems Remix DJ PLUGINS Stems Plugin Siren Plugin Dru… path:1,HTML,1,BODY,0,DIV,0,DIV,0,DIV,3,FOOTER selector:div#__next > div#file-drag > div#layout > footer#footer snippet:<footer id="footer"> type:node] score:0.09275357937133351] map[node:map[boundingRect:map[bottom:2083 height:1938 left:68 right:1268 top:146 width:1200] lhId:page-6-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,2,DIV selector:div#__next > div#file-drag > div#layout > div.page snippet:<div class="page _remix"> type:node] score:0.002361308116627266 subItems:map[items:[map[cause:Unsized image element extra:map[boundingRect:map[bottom:2327 height:43 left:100 right:257 top:2283 width:157] lhId:page-14-IMG nodeLabel:Fadr Logo path:1,HTML,1,BODY,0,DIV,0,DIV,0,DIV,3,FOOTER,0,DIV,1,DIV,0,DIV,0,DIV,0,A,0,IMG selector:div > div.flex > a > img snippet:<img alt="Fadr Logo" loading="lazy" width="157" height="44" decoding="async" data-nimg="1" style="color:transparent" src="/assets/images/logo/logo.svg"> type:node]]] type:subitems]] map[node:map[boundingRect:map[bottom:2083 height:1938 left:68 right:1268 top:146 width:1200] lhId:page-6-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,2,DIV selector:div#__next > div#file-drag > div#layout > div.page snippet:<div class="page _remix"> type:node] score:0.002170212765957447 subItems:map[items:[map[cause:Unsized image element extra:map[boundingRect:map[bottom:2327 height:43 left:100 right:257 top:2283 width:157] lhId:page-14-IMG nodeLabel:Fadr Logo path:1,HTML,1,BODY,0,DIV,0,DIV,0,DIV,3,FOOTER,0,DIV,1,DIV,0,DIV,0,DIV,0,A,0,IMG selector:div > div.flex > a > img snippet:<img alt="Fadr Logo" loading="lazy" width="157" height="44" decoding="async" data-nimg="1" style="color:transparent" src="/assets/images/logo/logo.svg"> type:node]]] type:subitems]] map[node:map[boundingRect:map[bottom:2083 height:1938 left:68 right:1268 top:146 width:1200] lhId:page-6-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,2,DIV selector:div#__next > div#file-drag > div#layout > div.page snippet:<div class="page _remix"> type:node] score:0.001992874967165747 subItems:map[items:[map[cause:Unsized image element extra:map[boundingRect:map[bottom:2327 height:43 left:100 right:257 top:2283 width:157] lhId:page-14-IMG nodeLabel:Fadr Logo path:1,HTML,1,BODY,0,DIV,0,DIV,0,DIV,3,FOOTER,0,DIV,1,DIV,0,DIV,0,DIV,0,A,0,IMG selector:div > div.flex > a > img snippet:<img alt="Fadr Logo" loading="lazy" width="157" height="44" decoding="async" data-nimg="1" style="color:transparent" src="/assets/images/logo/logo.svg"> type:node]]] type:subitems]]]

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.

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: "Emo Rock Anthems" pack artwork - Fadr
path: 1,HTML,1,BODY,0,DIV,0,DIV,0,DIV,2,DIV,2,DIV,2,DIV,4,BUTTON,0,IMG
selector: div.library-browser > div.flex > button.pack-preview > img.song-preview-image
snippet: <img alt="&quot;Emo Rock Anthems&quot; 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="https://fadr.com/_next/image?url=https%3A%2F%2Fsongtostems-songs.s3.us-eas…" 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.

URLResource SizeEst Savings
"Festival Tech 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...19.6 KiB10.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.

ElementLayout 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.908
HOME Fadr Fadr Plus CREATE Stems Remix DJ PLUGINS Stems Plugin Siren Plugin Dru… div#__next > div#file-drag > div#layout > footer#footer
0.093
Remix Help Collab Something went wrong. Library Choose a pack and find tracks … div#__next > div#file-drag > div#layout > div.page
0.002
Remix Help Collab Something went wrong. Library Choose a pack and find tracks … div#__next > div#file-drag > div#layout > div.page
0.002
Remix Help Collab Something went wrong. Library Choose a pack and find tracks … div#__next > div#file-drag > div#layout > div.page
0.002

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

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.

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

●Max Potential First Input Delay 70 ms
●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
●JavaScript execution time 0.7 s
●Minimizes main-thread work 1.4 s
●Avoid long main-thread tasks 4 long tasks found
●Avoid non-composited animations 1 animated element found
●Image elements have explicit `width` and `height`
●Network Requests
●Network Round Trip Times 130 ms
●Server Backend Latencies 130 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 30 ms
○INP breakdown
81

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.header-popout > div.header-content > nav.header-options > button div.header-popout > div.header-content > nav.header-options > button
div.page-bounds > div.logo-column > div.flex > button.flex div.page-bounds > div.logo-column > div.flex > button.flex

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
div.logo-column > div.flex > div.social-links > a div.logo-column > div.flex > div.social-links > a
div.logo-column > div.flex > div.social-links > a div.logo-column > div.flex > div.social-links > a
div.logo-column > div.flex > div.social-links > a div.logo-column > div.flex > div.social-links > a
div.logo-column > div.flex > div.social-links > a div.logo-column > div.flex > div.social-links > 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.

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
HOME div.page-bounds > div.flex > div.nav-link-group > h6.nav-link-header
CREATE div.flex > div.nav-link-group > a > h6.nav-link-header
PLUGINS div.flex > div.nav-link-group > a > h6.nav-link-header
LEARN div.page-bounds > div.flex > div.nav-link-group > h6.nav-link-header
USER div.page-bounds > div.flex > div.nav-link-group > h6.nav-link-header
INFO div.page-bounds > div.flex > div.nav-link-group > h6.nav-link-header

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
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
●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
●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.
●Touch targets have sufficient size and spacing.
●Deprecated ARIA roles were not used
●Identical links have the same purpose.
○`[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.
○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.
96

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.

SourceDescription
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
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
●Image elements have `[alt]` attributes
●Document has a valid `hreflang`
○robots.txt is valid
○Document has a valid `rel=canonical`

Send Feedback