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.

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Transfer Size	Duration
daaz.com/_next/static/css/051b1e26bba2c1b6.css	7.1 KiB	352 ms

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Request	Cache TTL	Transfer Size
daaz.com/cdn-cgi/challenge-platform/h/b/scripts/jsd/0b8fb825cb67/main.js?	14400.0 s	12.4 KiB
/beacon.min.js/v8c78df7c7c0f484497ecbca7046644da177152312...	86400.0 s	10.7 KiB

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

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: 4.1 s 637.2 KiB

URL	Transfer Size	Est Savings
daaz.com/_next/static/chunks/chunk-mui-core-2f5f818422d15edc.js	244.9 KiB	191.4 KiB
daaz.com/_next/static/chunks/chunk-common-2a92d6e684783dd3.js	207.3 KiB	179.4 KiB
daaz.com/_next/static/chunks/chunk-react-25455d355ec1c5c3.js	110.6 KiB	107.9 KiB
www.googletagmanager.com/gtag/js?id=G-ZV711NY6HM	145.3 KiB	71.3 KiB
daaz.com/_next/static/chunks/9993-75c39c505550b836.js	130.7 KiB	43.9 KiB
daaz.com/_next/static/chunks/chunk-utils-953b2b2a9cd47d93.js	53.1 KiB	43.2 KiB

Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to reduce Javascript execution time.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Total CPU Time	Script Evaluation	Script Parse
daaz.com/_next/static/chunks/9993-75c39c505550b836.js	3.4 s	2.7 s	59 ms
daaz.com/	2.9 s	80 ms	8.0 ms
Unattributable	456 ms	26 ms	0.0 ms
daaz.com/cdn-cgi/challenge-platform/scripts/jsd/main.js	320 ms	305 ms	3.7 ms
www.googletagmanager.com/gtag/js?id=G-ZV711NY6HM	263 ms	202 ms	60 ms
daaz.com/_next/static/chunks/chunk-mui-core-2f5f818422d15edc.js	220 ms	116 ms	103 ms
daaz.com/_next/static/chunks/chunk-sentry-6a4cdcce39236637.js	216 ms	213 ms	1.5 ms
daaz.com/_next/static/chunks/7399.d3950a40c292a507.js	117 ms	59 ms	33 ms
daaz.com/_next/static/chunks/chunk-common-2a92d6e684783dd3.js	85 ms	4.6 ms	80 ms
/beacon.min.js/v8c78df7c7c0f484497ecbca7046644da177152312...	58 ms	37 ms	5.6 ms
daaz.com/_next/static/chunks/chunk-forms-c91deb3d5ad87c6e.js	58 ms	50 ms	7.6 ms

Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to minimize main-thread work

Why this matters

Performance issues directly impact user engagement and conversion rates.

Category	Time Spent
Script Evaluation	3.9 s
Other	2.2 s
Style & Layout	863 ms
Rendering	840 ms
Script Parsing & Compilation	491 ms
Garbage Collection	81 ms
Parse HTML & CSS	20 ms

Minifying CSS files can reduce network payload sizes. Learn how to minify CSS.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 0.0 ms 2.1 KiB

URL	Transfer Size	Est Savings
.css-px2o3f { display: flex; flex-direction: column; width: 100%; box-sizing: border-box; … } …	18.8 KiB	2.1 KiB

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: 0.0 ms 14.7 KiB

URL	Transfer Size	Est Savings
.css-px2o3f { display: flex; flex-direction: column; width: 100%; box-sizing: border-box; … } …	18.8 KiB	14.7 KiB

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

	URL
Daaz Logo `div.header_inner > div.MuiToolbar-root > a > img.mainlogo`	daaz.com/assets/images/logo.svg
Daaz Logo `div.MuiGrid-root > div.MuiGrid-root > div.MuiGrid-root > img.footer_logo`	daaz.com/assets/images/logo.svg

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

●Layout shift culprits

●Document request latency

●Optimize DOM size

●Font display

●Forced reflow

●Improve image delivery

●LCP breakdown

●Modern HTTP

●Optimize viewport for mobile

●Minify JavaScript

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

●Avoid long main-thread tasks 20 long tasks found

●Avoid non-composited animations 4 animated elements found

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 10 ms

●Server Backend Latencies 390 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 180 ms

●Avoid large layout shifts 15 layout shifts found

○INP breakdown

○LCP request discovery

○User Timing marks and measures

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
header#header_transparent > div.header_inner > div.MuiToolbar-root > button.MuiButtonBase-root `header#header_transparent > div.header_inner > div.MuiToolbar-root > button.MuiButtonBase-root`
div.MuiFormControl-root > div.MuiInputBase-root > div.MuiInputAdornment-root > button.MuiButtonBase-root `div.MuiFormControl-root > div.MuiInputBase-root > div.MuiInputAdornment-root > button.MuiButtonBase-root`

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.MuiToolbar-root > div.main_menu > div.MuiStack-root > a.MuiButtonBase-root `div.MuiToolbar-root > div.main_menu > div.MuiStack-root > a.MuiButtonBase-root`
div.MuiToolbar-root > div.main_menu > div.MuiStack-root > a.MuiButtonBase-root `div.MuiToolbar-root > div.main_menu > div.MuiStack-root > a.MuiButtonBase-root`

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.

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
div.MuiGrid-root > div.MuiGrid-root > div#legal > h3.MuiTypography-root `div.MuiGrid-root > div.MuiGrid-root > div#legal > h3.MuiTypography-root`

These are opportunities to improve keyboard navigation in your application.

Best practices

Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Facebook `div.MuiGrid-root > div.MuiGrid-root > div.social_icons > button.MuiButtonBase-root`
Facebook `div.MuiGrid-root > div.social_icons > button.MuiButtonBase-root > a`
X `div.MuiGrid-root > div.MuiGrid-root > div.social_icons > button.MuiButtonBase-root`
X `div.MuiGrid-root > div.social_icons > button.MuiButtonBase-root > a`
Linkedin `div.MuiGrid-root > div.MuiGrid-root > div.social_icons > button.MuiButtonBase-root`
Linkedin `div.MuiGrid-root > div.social_icons > button.MuiButtonBase-root > a`
instagram `div.MuiGrid-root > div.MuiGrid-root > div.social_icons > button.MuiButtonBase-root`
instagram `div.MuiGrid-root > div.social_icons > button.MuiButtonBase-root > a`
youtube `div.MuiGrid-root > div.MuiGrid-root > div.social_icons > button.MuiButtonBase-root`
youtube `div.MuiGrid-root > div.social_icons > button.MuiButtonBase-root > a`
tumblr `div.MuiGrid-root > div.MuiGrid-root > div.social_icons > button.MuiButtonBase-root`
tumblr `div.MuiGrid-root > div.social_icons > button.MuiButtonBase-root > a`
reddit `div.MuiGrid-root > div.MuiGrid-root > div.social_icons > button.MuiButtonBase-root`
reddit `div.MuiGrid-root > div.social_icons > button.MuiButtonBase-root > a`
blog `div.MuiGrid-root > div.MuiGrid-root > div.social_icons > button.MuiButtonBase-root`
blog `div.MuiGrid-root > div.social_icons > button.MuiButtonBase-root > a`

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

●Form elements have associated labels

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

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

●ARIA input fields have accessible names

●Elements use only permitted ARIA attributes

●Background and foreground colors have a sufficient contrast ratio

●Document has a `<title>` element

●`<html>` element has a `[lang]` attribute

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

●Links are distinguishable without relying on color.

●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).

●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements

●No element has a `[tabindex]` value greater than 0

●Document has a main landmark.

●Deprecated ARIA roles were not used

●ARIA IDs are unique

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

○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

○The document does not use `<meta http-equiv="refresh">`

○`<object>` elements have alternate text

○Select elements have associated label elements.

○Skip links are focusable.

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

Best Practices

General

Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Deprecation / Warning	Source
SharedStorage	daaz.com/cdn-cgi/challenge-platform/scripts/jsd/main.js
StorageType.persistent is deprecated. Please use standardized navigator.storage instead.	daaz.com/cdn-cgi/challenge-platform/scripts/jsd/main.js
Fledge	daaz.com/cdn-cgi/challenge-platform/scripts/jsd/main.js

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
daaz.com/favicon.svg	`Failed to load resource: the server responded with a status of 404 ()`

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
daaz.com/_next/static/chunks/chunk-mui-core-2f5f818422d15edc.js
daaz.com/_next/static/chunks/chunk-common-2a92d6e684783dd3.js

●Uses HTTPS

●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

○Redirects HTTP traffic to HTTPS

○Detected JavaScript libraries

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

●robots.txt is valid

●Image elements have `[alt]` attributes

●Document has a valid `hreflang`

●Document has a valid `rel=canonical`