Skip to content
https://jamendo.com

Lighthouse Mobile

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

60

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
www.google-analytics.com/analytics.js7200.0 s20.9 KiB
appleid.cdn-apple.com/appleauth/static/jsapi/appleid/1/en_US/appleid.auth.js86400.0 s17.4 KiB
static.hotjar.com/c/hotjar-837371.js?sv=660.0 s6.2 KiB

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.

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.

URLEst Savings
www.jamendo.com/Client/assets/toolkit/fonts/futura-book.woff225 ms
www.jamendo.com/Client/assets/toolkit/fonts/futura-demi.woff225 ms
www.jamendo.com/Client/assets/toolkit/fonts/futura-bold.woff225 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-DIV
nodeLabel: div#skeleton-overlay > div.redirection-container > div.websites-redirect > div.identity-brand
path: 1,HTML,1,BODY,5,DIV,0,DIV,1,DIV,0,DIV
selector: div#skeleton-overlay > div.redirection-container > div.websites-redirect > div.identity-brand
snippet: <div class="identity-brand" jamendo-licensing="" margin="bottom-100">

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

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.

URLTransfer SizeDuration
appleid.cdn-apple.com/appleauth/static/jsapi/appleid/1/en_US/appleid.auth.js17.4 KiB935 ms
www.jamendo.com/Client/assets/toolkit/styles/toolkit.min.994137531.css72.4 KiB750 ms

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

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: 827 ms
URLTime Spent
jamendo.com/827 ms
www.jamendo.com/0.0 ms

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

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: 600 ms 66.4 KiB
URLTransfer SizeEst Savings
www.jamendo.com/Client/assets/toolkit/styles/toolkit.min.994137531.css72.0 KiB66.4 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: 2.2 s 408.8 KiB
URLTransfer SizeEst Savings
www.jamendo.com/Client/scripts/main-build.994137531.js430.5 KiB257.8 KiB
www.googletagmanager.com/gtag/js?id=G-6XE4DBPD2H&cx=c&_slc=1150.9 KiB62.5 KiB
www.googletagmanager.com/gtm.js?id=GTM-PW5RK8131.7 KiB50.9 KiB
script.hotjar.com/modules.6a0f3932cb1341a35c18.js56.1 KiB37.6 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.

URLTotal CPU TimeScript EvaluationScript Parse
www.jamendo.com/Client/scripts/main-build.994137531.js1.1 s822 ms166 ms
Unattributable263 ms58 ms0.0 ms
www.googletagmanager.com/gtm.js?id=GTM-PW5RK8235 ms198 ms35 ms
www.jamendo.com/205 ms7.8 ms2.2 ms
www.googletagmanager.com/gtag/js?id=G-6XE4DBPD2H&cx=c&_slc=1144 ms111 ms32 ms
script.hotjar.com/modules.6a0f3932cb1341a35c18.js127 ms103 ms18 ms
www.google-analytics.com/analytics.js61 ms51 ms5.4 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.

CategoryTime Spent
Script Evaluation1.4 s
Other355 ms
Script Parsing & Compilation267 ms
Style & Layout119 ms
Parse HTML & CSS37 ms
Garbage Collection21 ms
Rendering13 ms

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

●Layout shift culprits
●Optimize DOM size
●Forced reflow
●Improve image delivery
●LCP breakdown
●Modern HTTP
●Optimize viewport for mobile
●Minify CSS
●Minify JavaScript
●Avoids enormous network payloads Total size was 1,033 KiB
●User Timing marks and measures 5 user timings
●Avoid long main-thread tasks 7 long tasks found
●Image elements have explicit `width` and `height`
●Page didn't prevent back/forward cache restoration
●Network Requests
●Network Round Trip Times 30 ms
●Server Backend Latencies 30 ms
●Tasks
●Diagnostics
●Metrics
●Screenshot Thumbnails
●Final Screenshot
●Script Treemap Data
●Resources Summary
●Initial server response time was short Root document took 70 ms
●Avoid large layout shifts 1 layout shift found
○INP breakdown
○Avoid non-composited animations
69

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
body#app > nav#skeleton-navigation > nav.navigation > button.btn-icon body#app > nav#skeleton-navigation > nav.navigation > button.btn-icon
div.bar-container > ul.list-button > li > button.btn-icon div.bar-container > ul.list-button > li > button.btn-icon
div#skeleton-topbar-and-content > ul#skeleton-content-messages > li.messages_message > button.messages_message_dismiss div#skeleton-topbar-and-content > ul#skeleton-content-messages > li.messages_message > button.messages_message_dismiss

Form elements without effective labels can create frustrating experiences for screen reader users. Learn more about the `select` element.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
English Français Deutsch Español Italiano Polskie Português Pусский div.wrap > div > div.language > select.js-navigation-lang

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
nav.navigation > div.wrap > div > a nav.navigation > div.wrap > div > a
div > ul.social > li > a.btn-pill div > ul.social > li > a.btn-pill
div > ul.social > li > a.btn-pill div > ul.social > li > a.btn-pill
div > ul.social > li > a.btn-pill div > ul.social > li > a.btn-pill

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
BACKGROUND MUSIC FOR ANY VENUE li > a.button-cart > div.button-cart-text-container > h3

These are opportunities to improve the legibility of your content.

Best practices

Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a web page. Learn more about the viewport meta tag.

Why this matters

Informational: a Permissions-Policy directive showing feature -> allowed origins.

Source: MDN Permissions-Policy

Failing Elements
head > meta head > meta

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-hidden="true"]` is not present on the document `<body>`
●`[role]`s have all required `[aria-*]` attributes
●`[role]` values are valid
●Form elements have associated labels
●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
●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
○`[aria-*]` attributes match their roles
○`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
○ARIA input fields have accessible names
○ARIA `meter` elements have accessible names
○ARIA `progressbar` elements have accessible names
○Elements use only permitted ARIA attributes
○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
○`[aria-*]` attributes have valid values
○`[aria-*]` attributes are valid and not misspelled
○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
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○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.
92

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
www.googletagmanager.com/gtag/js?id=G-6XE4DBPD2H&cx=c&_slc=1 line 217, col 390
Connecting to 'https://region1.analytics.google.com/g/collect?v=2&tid=G-6XE4DBPD2H&gtm=45je64k1h1v9126490146za20g&_p=1776901018072&_gaz=1&gcd=13l3l3l2l3l1&npa=1&dma_cps=a&dma=1&_eu=EBAIAGA&are=1&cid=1921909834.1776901019&frm=0&ir=1&pscdl=noapi&rcb=14&sr=412x823&uaa=&uab=64&uafvl=Chromium%3B147.0.7727.101%7CNot.A%252FBrand%3B8.0.0.0&uam=moto%20g%20power%20(2022)&uamb=1&uap=Android&uapv=11.0&uaw=0&ul=en-us&gaf=2&_s=1&tag_exp=0~115616986~115938466~115938469~117266400~117384405~117512542&dl=https%3A%2F%2Fwww.jamendo.com%2F&dt=Jamendo%20Music%20%7C%20Free%20music%20downloads&sid=1776901018&sct=1&seg=0&_tu=wAQ&en=page_view&_fv=1&_ss=1&_ee=1&gap.uat=0~115616986~115938466~115938468~117266400~118463262&tfd=764' violates the following Content Security Policy directive: "connect-src 'self' *.jamendo.com https://tagmanager.google.com https://insights.hotjar.com https://in.hotjar.com https://vc.hotjar.io https://www.google-analytics.com https://stats.g.doubleclick.net". The action has been blocked.
www.googletagmanager.com/gtag/js?id=G-6XE4DBPD2H&cx=c&_slc=1 line 217, col 390
Fetch API cannot load https://region1.analytics.google.com/g/collect?v=2&tid=G-6XE4DBPD2H&gtm=45je64k1h1v9126490146za20g&_p=1776901018072&_gaz=1&gcd=13l3l3l2l3l1&npa=1&dma_cps=a&dma=1&_eu=EBAIAGA&are=1&cid=1921909834.1776901019&frm=0&ir=1&pscdl=noapi&rcb=14&sr=412x823&uaa=&uab=64&uafvl=Chromium%3B147.0.7727.101%7CNot.A%252FBrand%3B8.0.0.0&uam=moto%20g%20power%20(2022)&uamb=1&uap=Android&uapv=11.0&uaw=0&ul=en-us&gaf=2&_s=1&tag_exp=0~115616986~115938466~115938469~117266400~117384405~117512542&dl=https%3A%2F%2Fwww.jamendo.com%2F&dt=Jamendo%20Music%20%7C%20Free%20music%20downloads&sid=1776901018&sct=1&seg=0&_tu=wAQ&en=page_view&_fv=1&_ss=1&_ee=1&gap.uat=0~115616986~115938466~115938468~117266400~118463262&tfd=764. Refused to connect because it violates the document's Content Security Policy.

Issues logged to the `Issues` panel in Chrome Devtools indicate unresolved problems. They can come from network request failures, insufficient security controls, and other browser concerns. Open up the Issues panel in Chrome DevTools for more details on each issue.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Issue type
Content security policy

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
www.jamendo.com/Client/scripts/main-build.994137531.js
www.jamendo.com/Client/cordova.994137531.jswww.jamendo.com/Client/cordova.js.map
●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
●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
○Redirects HTTP traffic to HTTPS
92

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
www.jamendo.com/cookiesLearn more
www.jamendo.com/startSTART

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

Send Feedback