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.

A forced reflow occurs when JavaScript queries geometric properties (such as offsetWidth) after styles have been invalidated by a change to the DOM state. This can result in poor performance. Learn more about forced reflows and possible mitigations.

Why this matters

Performance issues directly impact user engagement and conversion rates.

headings: [map[key:source label:Top function call valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]

items: [map[reflowTime:54.392 source:map[column:1403 line:1 type:source-location url:https://cricauctionhub.vercel.app/assets/vendor-react-BN9WHClH.js urlProvider:network]]]

headings: [map[key:source label:Source valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]

items: [map[reflowTime:47.372 source:map[column:4826 line:0 type:source-location url:https://cricauctionhub.vercel.app/assets/LandingPage-ic8zZm21.js urlProvider:network]] map[reflowTime:0.342 source:map[column:4873 line:0 type:source-location url:https://cricauctionhub.vercel.app/assets/LandingPage-ic8zZm21.js urlProvider:network]] map[reflowTime:0.318 source:map[column:5026 line:0 type:source-location url:https://cricauctionhub.vercel.app/assets/LandingPage-ic8zZm21.js urlProvider:network]] map[reflowTime:3.932 source:map[column:83897 line:8 type:source-location url:https://cricauctionhub.vercel.app/assets/vendor-animation-BiNnr-ly.js urlProvider:network]] map[reflowTime:2.428 source:map[column:101593 line:8 type:source-location url:https://cricauctionhub.vercel.app/assets/vendor-animation-BiNnr-ly.js urlProvider:network]]]

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

	URL	Resource Size	Est Savings
APL logo `div.auction-card-wrapper > article.auction-card > div.card-image > img.card-logo-img`	/n7trd1nz/image/upload/v1785519858/cricauction/tournament...	576.0 KiB	575.3 KiB
CricAuctionHub logo `div.auction-card-wrapper > article.auction-card > div.card-image > img.card-logo-img`	/n7trd1nz/image/upload/v1786603983/cricauction/tournament...	371.4 KiB	370.2 KiB
Cric Auction Hub Live Coin Back `div.coin-visual-stage > div.rotating-coin-container > div.coin-face > img.cric-auction-coin-img`	cricauctionhub.vercel.app/assets/newgoldlogo-11SZGJA8.png	315.3 KiB	299.2 KiB
msd logo `div.auction-card-wrapper > article.auction-card > div.card-image > img.card-logo-img`	/n7trd1nz/image/upload/v1785753119/cricauction/tournament...	210.8 KiB	210.0 KiB
Kesari cricketrs logo `div.auction-card-wrapper > article.auction-card > div.card-image > img.card-logo-img`	/n7trd1nz/image/upload/v1785825999/cricauction/tournament...	148.9 KiB	148.2 KiB
KPL logo `div.auction-card-wrapper > article.auction-card > div.card-image > img.card-logo-img`	/n7trd1nz/image/upload/v1786022500/cricauction/tournament...	148.9 KiB	148.2 KiB
Barish Trophy logo `div.auction-card-wrapper > article.auction-card > div.card-image > img.card-logo-img`	/n7trd1nz/image/upload/v1787294995/cricauction/tournament...	102.3 KiB	101.6 KiB
CPL logo `div.auction-card-wrapper > article.auction-card > div.card-image > img.card-logo-img`	/n7trd1nz/image/upload/v1787297499/cricauction/tournament...	55.8 KiB	54.6 KiB
CricAuctionHub `header.navbar > div.navbar-container > a.navbar-logo > img.logo-img`	cricauctionhub.vercel.app/assets/cricauctionlogo1-CiJJxOHU.webp	22.5 KiB	22.2 KiB
main > section.hero-section > div.hero-bg-image-wrapper > img.hero-bg-image `main > section.hero-section > div.hero-bg-image-wrapper > img.hero-bg-image`	cricauctionhub.vercel.app/assets/hero-auction-bg.webp	77.4 KiB	16.2 KiB

Each subpart has specific improvement strategies. Ideally, most of the LCP time should be spent on loading the resources, not within delays.

Why this matters

Performance issues directly impact user engagement and conversion rates.

headings: [map[key:label label:Subpart valueType:text] map[key:duration label:Duration valueType:ms]]

items: [map[duration:58.96 label:Time to first byte subpart:timeToFirstByte] map[duration:2505.369 label:Element render delay subpart:elementRenderDelay]]

lhId: page-10-P

nodeLabel: Experience the thrill of live cricket auctions. Build your dream team, manage t…

path: 1,HTML,1,BODY,0,DIV,0,DIV,1,MAIN,0,SECTION,4,DIV,0,DIV,0,DIV,2,P

selector: div.hero-content > div.hero-split-grid > div.hero-text-col > p.hero-subheadline

snippet: <p class="hero-subheadline" style="opacity: 1; transform: none;">

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.

URL	Transfer Size	Duration
cricauctionhub.vercel.app/assets/index-D8wLJQGa.css	4.1 KiB
fonts.googleapis.com/css2?family=Inter:wght@400;500;600;700;800&display=swap	1.2 KiB	814 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
sdk.cashfree.com/js/v3/cashfree.js	0.0 ms	17.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: 750 ms 103.3 KiB

URL	Transfer Size	Est Savings
cricauctionhub.vercel.app/assets/vendor-animation-BiNnr-ly.js	89.3 KiB	46.2 KiB
cricauctionhub.vercel.app/assets/vendor-react-BN9WHClH.js	82.8 KiB	35.3 KiB
cricauctionhub.vercel.app/assets/index-CAgWzavq.js	34.7 KiB	21.8 KiB

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
Other	8.7 s
Script Evaluation	945 ms
Style & Layout	722 ms
Rendering	295 ms
Script Parsing & Compilation	8.6 ms
Parse HTML & CSS	6.2 ms
Garbage Collection	5.2 ms

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

●Modern HTTP

●Optimize viewport for mobile

●Minify CSS

●Minify JavaScript

●Reduce unused CSS

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

●JavaScript execution time 0.9 s

●Avoid long main-thread tasks 20 long tasks found

●Avoid non-composited animations 6 animated elements 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 440 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 20 ms

○INP breakdown

○LCP request discovery

○User Timing marks and measures

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

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
Selected Match `div.pricing-container > div.pricing-grid > div.simple-pricing-card > div.selected-badge`

These are opportunities to improve the legibility of your content.

Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
CricAuctionHub `div.landing-page-wrapper > header.navbar > div.navbar-container > a.navbar-logo`

○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

●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

●`[aria-*]` attributes have valid values

●`[aria-*]` attributes are valid and not misspelled

●Buttons have an accessible name

●Image elements have `[alt]` attributes

●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.

●ARIA attributes are used as specified for the element's role

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

●Elements use only permitted ARIA attributes

●Document has a `<title>` element

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

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

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

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

●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

●Uses ARIA roles only on compatible elements

●Image elements do not have `[alt]` attributes that are redundant text.

○`[accesskey]` values are unique

○`button`, `link`, and `menuitem` elements have accessible names

○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 with the `role=text` attribute do not have focusable descendents.

○ARIA toggle fields have accessible names

○ARIA `tooltip` elements have accessible names

○ARIA `treeitem` elements have accessible names

○The page contains a heading, skip link, or landmark region

○`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.

○Definition list items are wrapped in `<dl>` elements

○ARIA IDs are unique

○No form fields have multiple labels

○`<frame>` or `<iframe>` elements have a title

○`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.

○Input buttons have discernible text.

○`<input type="image">` elements have `[alt]` text

○Form elements have associated labels

○Links are distinguishable without relying on color.

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

○Identical links have the same purpose.

○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
cric-auction-server.onrender.com/api/auth/profile	`Failed to load resource: the server responded with a status of 401 ()`

●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

●Page has valid source maps

○Redirects HTTP traffic to HTTPS

○Use a strong HSTS policy

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