C — https://www.deezer.com | BeaverCheck Audit

Site Health

Score: 73 / 100 Same as last audit

Based on 8 categories, 0 sections

How is this calculated?

The overall score is a weighted average of individual category scores. Categories with more impact on user experience and security carry more weight.

Performance 25%Security 25%Accessibility 15%SEO 10%Infrastructure 10%Compliance 8%Content 5%Sustainability 2%

Weights reflect general web best practices. Individual needs may differ.

Top Priorities (5)

Content-Security-Policy header is missing

Security › Security Headers

Cookie 'bm_sz' is missing the Secure flag

Security › Cookie Security

No Content-Security-Policy header found

Security › Content Security Policy

1 control(s) without accessible label

Accessibility › Form Accessibility

2 button(s) with no accessible text

Accessibility › Link & Button Quality

Embed this badge

Markdown

[![BeaverCheck](https://beavercheck.com/badge?url=https%3A%2F%2Fwww.deezer.com)](https://beavercheck.com/results/8415e1cc-21ac-6b6c-c83b-756b78e1bf22)

HTML

<a href="https://beavercheck.com/results/8415e1cc-21ac-6b6c-c83b-756b78e1bf22"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fwww.deezer.com" alt="BeaverCheck Score"></a>

Image URL

https://beavercheck.com/badge?url=https%3A%2F%2Fwww.deezer.com

This badge auto-updates with your latest scan result.

Was this report useful?

Thanks for your feedback!

Recent Trends

Performance stable →

TTFB stable →

100ms

FCP stable →

6.7s

LCP stable →

11.2s

Press ? for shortcuts

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse.

53 +5

Performance

Accessibility

Best Practices

SEO

Core Web Vitals

Key metrics that affect user experience.

First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.

6.68 s

Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.

11.17 s

Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.

286 ms

Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.

0.000

Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.

6.79 s

Time to Interactive Time to Interactive — how long until the page is fully interactive and responds to user input. Under 3.8s is good.

11.20 s

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.

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

3rd party code can significantly impact load performance. Reduce and defer loading of 3rd party code to prioritize your page's content.

A long cache lifetime can speed up repeat visits to your page. Learn more about caching.

Request	Cache TTL	Transfer Size
/CF6YEld6/91qK8Zv/WnnBwoW/9n/E9kazL3Gwiu9Dp3Vb3/ChhnPnsWA...	21600.0 s	176.7 KiB
qb3mmcu0z3.kameleoon.io/engine.js	14400.0 s	43.1 KiB
www.deezer.com/CF6YEld6/91qK8Zv/WnnBwoW/9n/VrkaOm/A3xPPnsWAg/ShoucH4O/Tl8p	86400.0 s	28.5 KiB
survey.survicate.com/workspaces/e69a030efff76782eb8bdad0a7d95357/web_surveys.js	10.0 s	9.9 KiB
cdn.segment.com/next-integrations/actions/3962/1faa179dfb20d0a3f5a0.js	0.0 ms	9.2 KiB
/next-integrations/actions/braze-cloud-plugins/c3dbe2dde9...	0.0 ms	2.5 KiB
cdn-assets.dzcdn.net/common/css/deezer-brand.css	300.0 s	1.1 KiB
cdn-assets.dzcdn.net/common/css/inter.css	300.0 s	870 B
www.deezer.com/CF6YEld6/91qK8Zv/WnnBwoW/9n/VrkaOm/A3xPPnsWAg/VyMAeAhl/cDJZ	86400.0 s	1007 B

Your first network request is the most important. Reduce its latency by avoiding redirects, ensuring a fast server response, and enabling text compression.

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.

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.

URL	Transfer Size	Duration
cdn-assets.dzcdn.net/common/css/deezer-brand.css	1.1 KiB	762 ms
cdn-assets.dzcdn.net/common/css/inter.css	870 B	151 ms
/cache/css/sass_c/app-backstage-plain-html.bbde1571c0047b...	8.7 KiB	150 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.

Estimated savings: 809 ms

URL	Time Spent
www.deezer.com/	809 ms
www.deezer.com/us/	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.

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.

Diagnostics

Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.

Estimated savings: 1.1 s 252.3 KiB

URL	Transfer Size	Est Savings
surveys-static-prd.survicate-cdn.com/widget_core-28.22.7.js	159.1 KiB	75.6 KiB
www.googletagmanager.com/gtm.js?id=GTM-PPQNZ6	181.7 KiB	70.1 KiB
cdn-files.dzcdn.net/cache/js/app-backstage-plain-html.1de236d206f16f2e8525.js	112.3 KiB	68.0 KiB
/CF6YEld6/91qK8Zv/WnnBwoW/9n/E9kazL3Gwiu9Dp3Vb3/ChhnPnsWA...	175.8 KiB	38.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.

URL	Total CPU Time	Script Evaluation	Script Parse
/CF6YEld6/91qK8Zv/WnnBwoW/9n/E9kazL3Gwiu9Dp3Vb3/ChhnPnsWA...	657 ms	527 ms	40 ms
surveys-static-prd.survicate-cdn.com/widget_core-28.22.7.js	333 ms	209 ms	65 ms
Unattributable	326 ms	55 ms	0.0 ms
www.googletagmanager.com/gtm.js?id=GTM-PPQNZ6	256 ms	205 ms	49 ms
qb3mmcu0z3.kameleoon.io/engine.js	243 ms	191 ms	14 ms
cdn-assets.dzcdn.net/common/js/gdpr-appliance.js	137 ms	96 ms	40 ms
cdn-files.dzcdn.net/cache/js/app-backstage-plain-html.1de236d206f16f2e8525.js	98 ms	64 ms	29 ms
www.deezer.com/us/	85 ms	10 ms	2.3 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

Category	Time Spent
Script Evaluation	1.5 s
Other	333 ms
Script Parsing & Compilation	274 ms
Style & Layout	169 ms
Parse HTML & CSS	38 ms
Garbage Collection	29 ms
Rendering	11 ms

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

Failure reason	Failure type
Pages with cache-control:no-store header cannot enter back/forward cache.	Actionable
Pages whose main resource has cache-control:no-store cannot enter back/forward cache.	Not actionable
Back/forward cache is disabled because some JavaScript network request received resource with Cache-Control: no-store header.	Not actionable

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.

Estimated savings: 0.0 ms 40.7 KiB

URL	Transfer Size	Est Savings
.sr-only{border:0;clip:rect(0,0,0,0);height:1px;margin:-1px;overflow:hidden;padding:0; … } …	28.0 KiB	27.9 KiB
cdn-files.dzcdn.net/cache/css/sass_c/bootstrap-tempo.d4454b37f0bbdda229df.css	16.3 KiB	12.8 KiB

Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensions

	URL
Get it on Google Play `footer.footer > div.cell > a > img#footer-play-store-button`	cdn-assets.dzcdn.net/common/images/play-store-badge/en-us.svg
Download on the App Store `footer.footer > div.cell > a > img#footer-app-store-button`	cdn-assets.dzcdn.net/common/images/apple-store-badge/en-us.svg

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

●Layout shift culprits

●Optimize DOM size

●Font display

●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,544 KiB

●Avoid long main-thread tasks 9 long tasks found

●Network Requests

●Network Round Trip Times 30 ms

●Server Backend Latencies 60 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

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

○INP breakdown

○LCP request discovery

○User Timing marks and measures

○Avoid non-composited animations

○Avoid large layout shifts

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.

Failing Elements
section.gap-2xl-vertical > div.stack-m-vertical > div.carousel-controls > button.tempo-icon-btn `section.gap-2xl-vertical > div.stack-m-vertical > div.carousel-controls > button.tempo-icon-btn`
section.gap-2xl-vertical > div.stack-m-vertical > div.carousel-controls > button.tempo-icon-btn `section.gap-2xl-vertical > div.stack-m-vertical > div.carousel-controls > button.tempo-icon-btn`

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Failing Elements
div.carousel-item > div.border-s > picture.tempo-picture > img `div.carousel-item > div.border-s > picture.tempo-picture > img`
div.carousel-item > div.border-s > picture.tempo-picture > img `div.carousel-item > div.border-s > picture.tempo-picture > img`
div.carousel-item > div.border-s > picture.tempo-picture > img `div.carousel-item > div.border-s > picture.tempo-picture > img`
div.carousel-item > div.border-s > picture.tempo-picture > img `div.carousel-item > div.border-s > picture.tempo-picture > img`
section.bg-primary > div.w-full > picture.tempo-picture > img `section.bg-primary > div.w-full > picture.tempo-picture > img`

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

Failing Elements
Čeština Dansk Deutsch English English (us) Español Español (latam) Français Hrv… `div.legal > div.legal-list > div.index-navbar-lang > select#language_select`

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.

Failing Elements
body#unlogged-body > nav.tempo-topbar > a#topbar-deezer-logo `body#unlogged-body > nav.tempo-topbar > a#topbar-deezer-logo`
div > footer.footer > div.cell > a.logo-container `div > footer.footer > div.cell > a.logo-container`
div.cell > ul.social-list > li.social-list-item > a#footer-social-link-facebook `div.cell > ul.social-list > li.social-list-item > a#footer-social-link-facebook`
div.cell > ul.social-list > li.social-list-item > a#footer-social-link-instagram `div.cell > ul.social-list > li.social-list-item > a#footer-social-link-instagram`
div.cell > ul.social-list > li.social-list-item > a#footer-social-link-twitter `div.cell > ul.social-list > li.social-list-item > a#footer-social-link-twitter`
div.cell > ul.social-list > li.social-list-item > a#footer-social-link-youtube `div.cell > ul.social-list > li.social-list-item > a#footer-social-link-youtube`

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.

Failing Elements
partners `div.gdpr-modalScrollableContent > div.gdpr-wrapperCookieContent > p.gdpr-text > a#gdpr-partners-link`
Accept `div.gdpr-modalContainer > div.gdpr-modalCtas > div.gdpr-ctaContainer > button#gdpr-btn-accept-all`

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.

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

●`[aria-hidden="true"]` elements do not contain focusable descendents

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

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

○Deprecated ARIA roles were not used

○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 use only permitted ARIA attributes

○`[role]`s have all required `[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

○`[role]` values are valid

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

○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

○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

Source	Description
www.deezer.com/us/	`The Content Security Policy directive 'upgrade-insecure-requests' is ignored when delivered in a report-only policy.`
cdn-assets.dzcdn.net/common/js/gdpr-appliance.js line 2, col 48550	`The Content Security Policy directive 'upgrade-insecure-requests' is ignored when delivered in a report-only policy.`
cdn-assets.dzcdn.net/common/js/gdpr-appliance.js line 2, col 48550	`The Content Security Policy directive 'upgrade-insecure-requests' is ignored when delivered in a report-only policy.`
/CF6YEld6/91qK8Zv/WnnBwoW/9n/E9kazL3Gwiu9Dp3Vb3/ChhnPnsWA...	`The Content Security Policy directive 'upgrade-insecure-requests' is ignored when delivered in a report-only policy.`
/CF6YEld6/91qK8Zv/WnnBwoW/9n/E9kazL3Gwiu9Dp3Vb3/ChhnPnsWA...	`The Content Security Policy directive 'upgrade-insecure-requests' is ignored when delivered in a report-only 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.

URL	Map URL
/CF6YEld6/91qK8Zv/WnnBwoW/9n/E9kazL3Gwiu9Dp3Vb3/ChhnPnsWA...
cdn-assets.dzcdn.net/common/js/gdpr-appliance.js	/common/js/index.js.8c52057c757b2c0ca48fe1c70ad2278f295f7...
/next-integrations/integrations/vendor/commons.59560acdd6...	/next-integrations/integrations/vendor/commons.59560acdd6...
/next-integrations/integrations/survicate/1.0.3/survicate...	cdn.segment.com/next-integrations/integrations/survicate/1.0.3/survicate.js.map
/next-integrations/actions/braze-cloud-plugins/c3dbe2dde9...	/next-integrations/actions/braze-cloud-plugins/c3dbe2dde9...
cdn.segment.com/next-integrations/actions/3962/1faa179dfb20d0a3f5a0.js	cdn.segment.com/next-integrations/actions/3962/1faa179dfb20d0a3f5a0.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

●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

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.

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

Uncrawlable Link
partners `div.gdpr-modalScrollableContent > div.gdpr-wrapperCookieContent > p.gdpr-text > a#gdpr-partners-link`

To appear in search results, crawlers need access to your app.

Content Best Practices

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Failing Elements
div.carousel-item > div.border-s > picture.tempo-picture > img `div.carousel-item > div.border-s > picture.tempo-picture > img`
div.carousel-item > div.border-s > picture.tempo-picture > img `div.carousel-item > div.border-s > picture.tempo-picture > img`
div.carousel-item > div.border-s > picture.tempo-picture > img `div.carousel-item > div.border-s > picture.tempo-picture > img`
div.carousel-item > div.border-s > picture.tempo-picture > img `div.carousel-item > div.border-s > picture.tempo-picture > img`
section.bg-primary > div.w-full > picture.tempo-picture > img `section.bg-primary > div.w-full > picture.tempo-picture > img`

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 have descriptive text

●robots.txt is valid

●Document has a valid `hreflang`

●Document has a valid `rel=canonical`

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse. — Desktop

Performance

Accessibility

Best Practices

SEO

Core Web Vitals

Key metrics that affect user experience. — Desktop

First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.

595 ms

Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.

1.45 s

Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.

2 ms

Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.

0.000

Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.

706 ms

Time to Interactive Time to Interactive — how long until the page is fully interactive and responds to user input. Under 3.8s is good.

2.31 s

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.

3rd party code can significantly impact load performance. Reduce and defer loading of 3rd party code to prioritize your page's content.

A long cache lifetime can speed up repeat visits to your page. Learn more about caching.

Request	Cache TTL	Transfer Size
/CF6YEld6/91qK8Zv/WnnBwoW/9n/E9kazL3Gwiu9Dp3Vb3/ChhnPnsWA...	21600.0 s	176.7 KiB
qb3mmcu0z3.kameleoon.io/engine.js	14400.0 s	43.1 KiB
www.deezer.com/CF6YEld6/91qK8Zv/WnnBwoW/9n/VrkaOm/A3xPPnsWAg/ShoucH4O/Tl8p	86400.0 s	28.5 KiB
survey.survicate.com/workspaces/e69a030efff76782eb8bdad0a7d95357/web_surveys.js	10.0 s	9.9 KiB
cdn.segment.com/next-integrations/actions/3962/1faa179dfb20d0a3f5a0.js	0.0 ms	9.2 KiB
/next-integrations/actions/braze-cloud-plugins/c3dbe2dde9...	0.0 ms	2.5 KiB
cdn-assets.dzcdn.net/common/css/deezer-brand.css	300.0 s	1.1 KiB
cdn-assets.dzcdn.net/common/css/inter.css	300.0 s	870 B
www.deezer.com/CF6YEld6/91qK8Zv/WnnBwoW/9n/VrkaOm/A3xPPnsWAg/VyMAeAhl/cDJZ	86400.0 s	1007 B

Your first network request is the most important. Reduce its latency by avoiding redirects, ensuring a fast server response, and enabling text compression.

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.

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

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.

URL	Transfer Size	Duration
/cache/css/sass_c/app-backstage-plain-html.bbde1571c0047b...	8.9 KiB
cdn-assets.dzcdn.net/common/css/deezer-brand.css	1.1 KiB	207 ms
cdn-assets.dzcdn.net/common/css/inter.css	870 B

Reducing the download time of images can improve the perceived load time of the page and LCP. Learn more about optimizing image size

	URL	Resource Size	Est Savings
div.carousel-item > div.border-s > picture.tempo-picture > img `div.carousel-item > div.border-s > picture.tempo-picture > img`	/images/misc/e09238f5979af9b6154d7a2e2b82ef90/0x1024-0000...	30.4 KiB	28.6 KiB
div.carousel-item > div.border-s > picture.tempo-picture > img `div.carousel-item > div.border-s > picture.tempo-picture > img`	/images/misc/7ceb561b396814c22bd280dcaff9db5e/0x1024-0000...	28.2 KiB	26.6 KiB
div.carousel-item > div.border-s > picture.tempo-picture > img `div.carousel-item > div.border-s > picture.tempo-picture > img`	/images/misc/8b67c242cb79b3cf3b93b098a49b7a3f/0x1024-0000...	27.3 KiB	25.8 KiB
div.carousel-item > div.border-s > picture.tempo-picture > img `div.carousel-item > div.border-s > picture.tempo-picture > img`	/images/misc/aad78231b5786bcd6d246746638a67c9/0x1024-0000...	24.4 KiB	23.0 KiB

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

Diagnostics

Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.

Estimated savings: 160 ms 251.7 KiB

URL	Transfer Size	Est Savings
surveys-static-prd.survicate-cdn.com/widget_core-28.22.7.js	159.3 KiB	75.5 KiB
www.googletagmanager.com/gtm.js?id=GTM-PPQNZ6	181.7 KiB	69.6 KiB
cdn-files.dzcdn.net/cache/js/app-backstage-plain-html.1de236d206f16f2e8525.js	112.3 KiB	68.1 KiB
/CF6YEld6/91qK8Zv/WnnBwoW/9n/E9kazL3Gwiu9Dp3Vb3/ChhnPnsWA...	175.8 KiB	38.6 KiB

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

Failure reason	Failure type
Pages with cache-control:no-store header cannot enter back/forward cache.	Actionable
Pages whose main resource has cache-control:no-store cannot enter back/forward cache.	Not actionable
Back/forward cache is disabled because some JavaScript network request received resource with Cache-Control: no-store header.	Not actionable

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.

Estimated savings: 0.0 ms 40.6 KiB

URL	Transfer Size	Est Savings
.sr-only{border:0;clip:rect(0,0,0,0);height:1px;margin:-1px;overflow:hidden;padding:0; … } …	28.0 KiB	28.0 KiB
cdn-files.dzcdn.net/cache/css/sass_c/bootstrap-tempo.d4454b37f0bbdda229df.css	16.3 KiB	12.6 KiB

Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensions

	URL
Get it on Google Play `footer.footer > div.cell > a > img#footer-play-store-button`	cdn-assets.dzcdn.net/common/images/play-store-badge/en-us.svg
Download on the App Store `footer.footer > div.cell > a > img#footer-app-store-button`	cdn-assets.dzcdn.net/common/images/apple-store-badge/en-us.svg

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

Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.

Estimated savings: 268 ms

URL	Time Spent
www.deezer.com/	268 ms
www.deezer.com/us/	0.0 ms

●Time to Interactive 2.3 s

●Layout shift culprits

●Optimize DOM size

●Font display

●Forced reflow

●LCP breakdown

●Modern HTTP

●Optimize viewport for mobile

●Max Potential First Input Delay 60 ms

●Minify CSS

●Minify JavaScript

●Avoids enormous network payloads Total size was 1,549 KiB

●JavaScript execution time 0.4 s

●Minimizes main-thread work 0.7 s

●Avoid long main-thread tasks 2 long tasks found

●Network Requests

●Network Round Trip Times 30 ms

●Server Backend Latencies 70 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

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

○INP breakdown

○LCP request discovery

○User Timing marks and measures

○Avoid non-composited animations

○Avoid large layout shifts

Accessibility

Contrast

Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.

Failing Elements
partners `div.gdpr-modalScrollableContent > div.gdpr-wrapperCookieContent > p.gdpr-text > a#gdpr-partners-link`
Accept `div.gdpr-modalContainer > div.gdpr-modalCtas > div.gdpr-ctaContainer > button#gdpr-btn-accept-all`

These are opportunities to improve the legibility of your content.

Names and labels

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Failing Elements
div.carousel-item > div.border-s > picture.tempo-picture > img `div.carousel-item > div.border-s > picture.tempo-picture > img`
div.carousel-item > div.border-s > picture.tempo-picture > img `div.carousel-item > div.border-s > picture.tempo-picture > img`
div.carousel-item > div.border-s > picture.tempo-picture > img `div.carousel-item > div.border-s > picture.tempo-picture > img`
div.carousel-item > div.border-s > picture.tempo-picture > img `div.carousel-item > div.border-s > picture.tempo-picture > img`
section.bg-primary > div.w-full > picture.tempo-picture > img `section.bg-primary > div.w-full > picture.tempo-picture > img`

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

Failing Elements
Čeština Dansk Deutsch English English (us) Español Español (latam) Français Hrv… `div.legal > div.legal-list > div.index-navbar-lang > select#language_select`

Failing Elements
body#unlogged-body > nav.tempo-topbar > a#topbar-deezer-logo `body#unlogged-body > nav.tempo-topbar > a#topbar-deezer-logo`
div > footer.footer > div.cell > a.logo-container `div > footer.footer > div.cell > a.logo-container`
div.cell > ul.social-list > li.social-list-item > a#footer-social-link-facebook `div.cell > ul.social-list > li.social-list-item > a#footer-social-link-facebook`
div.cell > ul.social-list > li.social-list-item > a#footer-social-link-instagram `div.cell > ul.social-list > li.social-list-item > a#footer-social-link-instagram`
div.cell > ul.social-list > li.social-list-item > a#footer-social-link-twitter `div.cell > ul.social-list > li.social-list-item > a#footer-social-link-twitter`
div.cell > ul.social-list > li.social-list-item > a#footer-social-link-youtube `div.cell > ul.social-list > li.social-list-item > a#footer-social-link-youtube`

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.

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

●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-hidden="true"]` elements do not contain focusable descendents

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

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

○Deprecated ARIA roles were not used

○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 use only permitted ARIA attributes

○`[role]`s have all required `[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

○`[role]` values are valid

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

○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

○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

Source	Description
www.deezer.com/us/	`The Content Security Policy directive 'upgrade-insecure-requests' is ignored when delivered in a report-only policy.`
cdn-assets.dzcdn.net/common/js/gdpr-appliance.js line 2, col 48550	`The Content Security Policy directive 'upgrade-insecure-requests' is ignored when delivered in a report-only policy.`
cdn-assets.dzcdn.net/common/js/gdpr-appliance.js line 2, col 48550	`The Content Security Policy directive 'upgrade-insecure-requests' is ignored when delivered in a report-only policy.`
/CF6YEld6/91qK8Zv/WnnBwoW/9n/E9kazL3Gwiu9Dp3Vb3/ChhnPnsWA...	`The Content Security Policy directive 'upgrade-insecure-requests' is ignored when delivered in a report-only policy.`
/CF6YEld6/91qK8Zv/WnnBwoW/9n/E9kazL3Gwiu9Dp3Vb3/ChhnPnsWA...	`The Content Security Policy directive 'upgrade-insecure-requests' is ignored when delivered in a report-only policy.`

URL	Map URL
/CF6YEld6/91qK8Zv/WnnBwoW/9n/E9kazL3Gwiu9Dp3Vb3/ChhnPnsWA...
cdn-assets.dzcdn.net/common/js/gdpr-appliance.js	/common/js/index.js.8c52057c757b2c0ca48fe1c70ad2278f295f7...
/next-integrations/integrations/vendor/commons.59560acdd6...	/next-integrations/integrations/vendor/commons.59560acdd6...
/next-integrations/integrations/survicate/1.0.3/survicate...	cdn.segment.com/next-integrations/integrations/survicate/1.0.3/survicate.js.map
/next-integrations/actions/braze-cloud-plugins/c3dbe2dde9...	/next-integrations/actions/braze-cloud-plugins/c3dbe2dde9...
cdn.segment.com/next-integrations/actions/3962/1faa179dfb20d0a3f5a0.js	cdn.segment.com/next-integrations/actions/3962/1faa179dfb20d0a3f5a0.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

●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

SEO

Crawling and Indexing

Uncrawlable Link
partners `div.gdpr-modalScrollableContent > div.gdpr-wrapperCookieContent > p.gdpr-text > a#gdpr-partners-link`

To appear in search results, crawlers need access to your app.

Content Best Practices

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Failing Elements
div.carousel-item > div.border-s > picture.tempo-picture > img `div.carousel-item > div.border-s > picture.tempo-picture > img`
div.carousel-item > div.border-s > picture.tempo-picture > img `div.carousel-item > div.border-s > picture.tempo-picture > img`
div.carousel-item > div.border-s > picture.tempo-picture > img `div.carousel-item > div.border-s > picture.tempo-picture > img`
div.carousel-item > div.border-s > picture.tempo-picture > img `div.carousel-item > div.border-s > picture.tempo-picture > img`
section.bg-primary > div.w-full > picture.tempo-picture > img `section.bg-primary > div.w-full > picture.tempo-picture > img`

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 have descriptive text

●robots.txt is valid

●Document has a valid `hreflang`

●Document has a valid `rel=canonical`

Browse & Analyze

Learn

Results for https://www.deezer.com

Site Health

Top Priorities (5)

Lighthouse Scores

Core Web Vitals

Detailed Report

Performance

Insights

Diagnostics

Accessibility

Names and labels

Contrast

Best practices

Best Practices

General

SEO

Crawling and Indexing

Content Best Practices

Lighthouse Scores

Core Web Vitals

Detailed Report

Performance

Insights

Diagnostics

Accessibility

Contrast

Names and labels

Best Practices

General

SEO

Crawling and Indexing

Content Best Practices

Keyboard Shortcuts