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.

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.

More than 4 preconnect connections were found. These should be used sparingly and only to the most important origins.

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

value: No additional origins are good candidates for preconnecting

Requests are blocking the page's initial render, which may delay LCP. Deferring or inlining can move these network requests out of the critical path.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Transfer Size	Duration
www.dazn.com/static/boot-29.324.0-fba5a171a9c8268be362.js	213.1 KiB	1.2 s

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.

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: 756 ms

URL	Time Spent
dazn.com/	756 ms
www.dazn.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 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: 900 ms 144.8 KiB

URL	Transfer Size	Est Savings
www.dazn.com/static/boot-29.324.0-fba5a171a9c8268be362.js	212.3 KiB	144.8 KiB

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

●Use efficient cache lifetimes

●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

●Reduce unused CSS

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

●User Timing marks and measures 1 user timing

●JavaScript execution time 0.5 s

●Minimizes main-thread work 0.9 s

●Avoid long main-thread tasks 4 long tasks found

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

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 20 ms

●Server Backend Latencies 110 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

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

●Avoid large layout shifts 1 layout shift found

○INP breakdown

○LCP request discovery

○Avoid non-composited animations

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.

Internationalization and localization

If a page doesn't specify a `lang` attribute, a screen reader assumes that the page is in the default language that the user chose when setting up the screen reader. If the page isn't actually in the default language, then the screen reader might not announce the page's text correctly. Learn more about the `lang` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html `html`

These are opportunities to improve the interpretation of your content by users in different locales.

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

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

●Background and foreground colors have a sufficient contrast ratio

●Document has a `<title>` element

●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

○Buttons have an accessible name

○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

○Heading elements appear in a sequentially-descending order

○`<html>` element has a valid value for its `[lang]` attribute

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

○Form elements have associated labels

○Links are distinguishable without relying on color.

○Links have a discernible name

○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

○Touch targets have sufficient size and spacing.

○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
www.dazn.com/static/boot-29.324.0-fba5a171a9c8268be362.js line 1, col 890907	`[Bootstrap] handleInitError`
www.dazn.com/static/boot-29.324.0-fba5a171a9c8268be362.js line 1, col 876385	`[Bootstrap] setupPublicAPI (v2)`
www.dazn.com/static/boot-29.324.0-fba5a171a9c8268be362.js line 1, col 891069	`[Bootstrap] setupPublicAPI has failed`
www.dazn.com/static/boot-29.324.0-fba5a171a9c8268be362.js line 1, col 684344	`[Bootstrap] window.dazn is undefined while End of the World`
www.dazn.com/	`Access to fetch at 'https://startup.core.indazn.com/v1/main/web?Platform=web&LandingPageKey=generic&Brand=dazn' from origin 'https://www.dazn.com' has been blocked by CORS policy: Response to preflight request doesn't pass access control check: It does not have HTTP ok status.`
www.dazn.com/static/boot-29.324.0-fba5a171a9c8268be362.js line 1, col 820706	Error fetching startup response: TypeError: Failed to fetch at e.<computed> (https://www.dazn.com/:2:18834) at https://www.dazn.com/static/boot-29.324.0-fba5a171a9c8268be362.js:2:819933 at l (https://www.dazn.com/static/boot-29.324.0-fba5a171a9c8268be362.js:2:810368) at Generator.<anonymous> (https://www.dazn.com/static/boot-29.324.0-fba5a171a9c8268be362.js:2:811724) at Generator.next (https://www.dazn.com/static/boot-29.324.0-fba5a171a9c8268be362.js:2:810731) at Da (https://www.dazn.com/static/boot-29.324.0-fba5a171a9c8268be362.js:2:816375) at a (https://www.dazn.com/static/boot-29.324.0-fba5a171a9c8268be362.js:2:816579) at https://www.dazn.com/static/boot-29.324.0-fba5a171a9c8268be362.js:2:816640 at f (https://www.dazn.com/:2:25101) at new Promise (<anonymous>)
www.dazn.com/static/boot-29.324.0-fba5a171a9c8268be362.js line 1, col 876434	Error: [Bootstrap] API init error @ "l10n" [Bootstrap] Startup data is not available: getStartupDataCountry() at new t (https://www.dazn.com/static/boot-29.324.0-fba5a171a9c8268be362.js:2:362852) at e.createEraroError (https://www.dazn.com/static/boot-29.324.0-fba5a171a9c8268be362.js:2:368097) at s (https://www.dazn.com/static/boot-29.324.0-fba5a171a9c8268be362.js:2:821612) at Object.getStartupDataCountry (https://www.dazn.com/static/boot-29.324.0-fba5a171a9c8268be362.js:2:822180) at g (https://www.dazn.com/static/boot-29.324.0-fba5a171a9c8268be362.js:2:751248) at v (https://www.dazn.com/static/boot-29.324.0-fba5a171a9c8268be362.js:2:751482) at Object.b [as getUILanguage] (https://www.dazn.com/static/boot-29.324.0-fba5a171a9c8268be362.js:2:752713) at https://www.dazn.com/static/boot-29.324.0-fba5a171a9c8268be362.js:2:356890 at f (https://www.dazn.com/:2:25101)
www.dazn.com/static/boot-29.324.0-fba5a171a9c8268be362.js line 1, col 891124	Error: [Bootstrap] Startup data is not available: getStartupData() at new t (https://www.dazn.com/static/boot-29.324.0-fba5a171a9c8268be362.js:2:362852) at e.createEraroError (https://www.dazn.com/static/boot-29.324.0-fba5a171a9c8268be362.js:2:368097) at s (https://www.dazn.com/static/boot-29.324.0-fba5a171a9c8268be362.js:2:821612) at Object.getStartupData (https://www.dazn.com/static/boot-29.324.0-fba5a171a9c8268be362.js:2:821999) at getBrowser (https://www.dazn.com/static/boot-29.324.0-fba5a171a9c8268be362.js:2:856103) at P (https://www.dazn.com/static/boot-29.324.0-fba5a171a9c8268be362.js:2:708110) at B (https://www.dazn.com/static/boot-29.324.0-fba5a171a9c8268be362.js:2:709209) at H (https://www.dazn.com/static/boot-29.324.0-fba5a171a9c8268be362.js:2:709810) at Object.getVariableStringAnonymous (https://www.dazn.com/static/boot-29.324.0-fba5a171a9c8268be362.js:2:711112) at https://www.dazn.com/static/boot-29.324.0-fba5a171a9c8268be362.js:2:877351
www.dazn.com/static/boot-29.324.0-fba5a171a9c8268be362.js line 1, col 890952	Error: Failed to get startup data. TypeError: Failed to fetch \| createNewRelicTracer(boot.launch).wrapAsyncFn(startup) at new t (https://www.dazn.com/static/boot-29.324.0-fba5a171a9c8268be362.js:2:362852) at e.createEraroError (https://www.dazn.com/static/boot-29.324.0-fba5a171a9c8268be362.js:2:368097) at https://www.dazn.com/static/boot-29.324.0-fba5a171a9c8268be362.js:2:821150 at l (https://www.dazn.com/static/boot-29.324.0-fba5a171a9c8268be362.js:2:810368) at Generator.<anonymous> (https://www.dazn.com/static/boot-29.324.0-fba5a171a9c8268be362.js:2:811724) at Generator.throw (https://www.dazn.com/static/boot-29.324.0-fba5a171a9c8268be362.js:2:810731) at Da (https://www.dazn.com/static/boot-29.324.0-fba5a171a9c8268be362.js:2:816375) at s (https://www.dazn.com/static/boot-29.324.0-fba5a171a9c8268be362.js:2:816616) at f (https://www.dazn.com/:2:25101)
www.dazn.com/static/boot-29.324.0-fba5a171a9c8268be362.js line 1, col 683227	Error: Failed to get startup data. TypeError: Failed to fetch \| createNewRelicTracer(boot.launch).wrapAsyncFn(startup) \| from initMainModules at new t (https://www.dazn.com/static/boot-29.324.0-fba5a171a9c8268be362.js:2:362852) at e.createEraroError (https://www.dazn.com/static/boot-29.324.0-fba5a171a9c8268be362.js:2:368097) at https://www.dazn.com/static/boot-29.324.0-fba5a171a9c8268be362.js:2:821150 at l (https://www.dazn.com/static/boot-29.324.0-fba5a171a9c8268be362.js:2:810368) at Generator.<anonymous> (https://www.dazn.com/static/boot-29.324.0-fba5a171a9c8268be362.js:2:811724) at Generator.throw (https://www.dazn.com/static/boot-29.324.0-fba5a171a9c8268be362.js:2:810731) at Da (https://www.dazn.com/static/boot-29.324.0-fba5a171a9c8268be362.js:2:816375) at s (https://www.dazn.com/static/boot-29.324.0-fba5a171a9c8268be362.js:2:816616) at f (https://www.dazn.com/:2:25101)
www.dazn.com/static/boot-29.324.0-fba5a171a9c8268be362.js line 1, col 362851	Error: Unhandled Promise Rejection: [Bootstrap] Startup data is not available: getStartupData() \| createNewRelicTracer(boot.launch).wrapAsyncFn(analytics) at new t (https://www.dazn.com/static/boot-29.324.0-fba5a171a9c8268be362.js:2:362852) at e.createEraroError (https://www.dazn.com/static/boot-29.324.0-fba5a171a9c8268be362.js:2:368097) at s (https://www.dazn.com/static/boot-29.324.0-fba5a171a9c8268be362.js:2:821612) at Object.getStartupData (https://www.dazn.com/static/boot-29.324.0-fba5a171a9c8268be362.js:2:821999) at getBrowser (https://www.dazn.com/static/boot-29.324.0-fba5a171a9c8268be362.js:2:856103) at P (https://www.dazn.com/static/boot-29.324.0-fba5a171a9c8268be362.js:2:708110) at B (https://www.dazn.com/static/boot-29.324.0-fba5a171a9c8268be362.js:2:709209) at H (https://www.dazn.com/static/boot-29.324.0-fba5a171a9c8268be362.js:2:709810) at Object.getVariableBooleanAnonymous (https://www.dazn.com/static/boot-29.324.0-fba5a171a9c8268be362.js:2:710776) at https://www.dazn.com/static/boot-29.324.0-fba5a171a9c8268be362.js:2:886285
/v1/main/web?Platform=web&LandingPageKey=generic&Brand=dazn	`Failed to load resource: net::ERR_FAILED`

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.

URL	Map URL
www.dazn.com/static/boot-29.324.0-fba5a171a9c8268be362.js	www.dazn.com/static/boot-29.324.0-fba5a171a9c8268be362.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

●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

○Use a strong HSTS policy

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 are unable to include your pages in search results if they don't have permission to crawl them. Learn more about crawler directives.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Blocking Directive Source
`head > meta.protected`

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

Content Best Practices

Meta descriptions may be included in search results to concisely summarize page content. Learn more about the meta description.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Format your HTML in a way that enables crawlers to better understand your app’s content.

○Structured data is valid

●Document has a `<title>` element

●Page has successful HTTP status code

●Links have descriptive text

●Links are crawlable

●robots.txt is valid

●Document has a valid `hreflang`

○Image elements have `[alt]` attributes

○Document has a valid `rel=canonical`