https://office-project-beat-box-front-end.vercel.app

Lighthouse Desktop

· 0 checks — Desktop 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 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
checkout.razorpay.com/v1/checkout.js	120.0 s	57.4 KiB
cdn.razorpay.com/static/cx/razorpay-risk-detection/bundle.js	0.0 ms	1.8 KiB

Layout shifts occur when elements move absent any user interaction. Investigate the causes of layout shifts, such as elements being added, removed, or their fonts changing as the page loads.

Why this matters

Performance issues directly impact user engagement and conversion rates.

headings: [map[key:node label:Element subItemsHeading:map[key:extra] valueType:node] map[granularity:0.001 key:score label:Layout shift score subItemsHeading:map[key:cause valueType:text] valueType:numeric]]

items: [map[node:map[type:text value:Total] score:0.6582] map[node:map[boundingRect:map[bottom:940 height:788 left:0 right:1350 top:152 width:1350] lhId:page-1-FOOTER nodeLabel:1 Year Warranty 100% Genuine product warranty support. 7 Days Replacement No… path:1,HTML,1,BODY,0,DIV,1,DIV,2,FOOTER selector:body > div#root > div.d-flex > footer.position-relative snippet:<footer class="position-relative overflow-hidden" style="background: var(--bb-surface-2); border-top: 1px solid var(--bb-border);"> type:node] score:0.3291] map[node:map[boundingRect:map[bottom:940 height:788 left:0 right:1350 top:152 width:1350] lhId:page-1-FOOTER nodeLabel:1 Year Warranty 100% Genuine product warranty support. 7 Days Replacement No… path:1,HTML,1,BODY,0,DIV,1,DIV,2,FOOTER selector:body > div#root > div.d-flex > footer.position-relative snippet:<footer class="position-relative overflow-hidden" style="background: var(--bb-surface-2); border-top: 1px solid var(--bb-border);"> type:node] score:0.3291]]

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
office-project-beat-box-front-end.vercel.app/assets/index-B87KetCZ.css	43.7 KiB	81 ms
checkout.razorpay.com/v1/checkout.js	57.4 KiB	286 ms

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
BeatBox Logo `div.container-fluid > div.d-flex > a.navbar-brand > img.rounded-3`	office-project-beat-box-front-end.vercel.app/assets/beatbox_logo-ByRE-M8x.png	548.7 KiB	548.5 KiB

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

Diagnostics

Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity. Learn how to reduce unused CSS.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 50 ms 40.1 KiB

URL	Transfer Size	Est Savings
office-project-beat-box-front-end.vercel.app/assets/index-B87KetCZ.css	43.6 KiB	40.1 KiB

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 90 ms 121.9 KiB

URL	Transfer Size	Est Savings
office-project-beat-box-front-end.vercel.app/assets/index-C0J4MEJ3.js	257.5 KiB	97.0 KiB
checkout.razorpay.com/v1/checkout.js	56.9 KiB	24.9 KiB

Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Transfer Size
office-project-beat-box-front-end.vercel.app/assets/beatbox_logo-ByRE-M8x.png	549.2 KiB
office-project-beat-box-front-end.vercel.app/favicon.png?v=2	549.2 KiB
office-project-beat-box-front-end.vercel.app/assets/index-C0J4MEJ3.js	258.0 KiB
checkout-static-next.razorpay.com/build/chunks/v2-entry-app-4b998a56.modern.js	173.3 KiB
/build/chunks/v2-entry-v2-asset-common-103f00e4.modern.js	112.4 KiB
/build/chunks/v2-entry-lottie-player-04228f89.modern.js	76.7 KiB
checkout.razorpay.com/v1/checkout.js	57.4 KiB
office-project-beat-box-front-end.vercel.app/assets/index-B87KetCZ.css	43.7 KiB
/build/247362bd02f22583cc45188a3db717dc06393787/v2-entry....	39.9 KiB
/build/chunks/v2-entry-lang-hi-ts-be4e4f6b.modern.js	32.3 KiB

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

These are the largest layout shifts observed on the page. Each table item represents a single layout shift, and shows the element that shifted the most. Below each item are possible root causes that led to the layout shift. Some of these layout shifts may not be included in the CLS metric value due to windowing. Learn how to improve CLS

Why this matters

Performance issues directly impact user engagement and conversion rates.

Element	Layout shift score
1 Year Warranty 100% Genuine product warranty support. 7 Days Replacement No… `body > div#root > div.d-flex > footer.position-relative`	0.329
1 Year Warranty 100% Genuine product warranty support. 7 Days Replacement No… `body > div#root > div.d-flex > footer.position-relative`	0.329

●Document request latency

●Optimize DOM size

●Font display

●Forced reflow

●LCP breakdown

●Modern HTTP

●Optimize viewport for mobile

●Time to Interactive 1.0 s

●Max Potential First Input Delay 50 ms

●Minify CSS

●Minify JavaScript

●JavaScript execution time 0.5 s

●Minimizes main-thread work 1.8 s

●Avoid non-composited animations 1 animated element found

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

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 240 ms

●Server Backend Latencies 30 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 10 ms

○INP breakdown

○LCP request discovery

○User Timing marks and measures

○Avoid long main-thread tasks

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
div#navbarNav > div.d-flex > form.position-relative > button.btn `div#navbarNav > div.d-flex > form.position-relative > button.btn`

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.row > div.col-12 > div.d-flex > a.btn `div.row > div.col-12 > div.d-flex > a.btn`
div.row > div.col-12 > div.d-flex > a.btn `div.row > div.col-12 > div.d-flex > a.btn`
div.row > div.col-12 > div.d-flex > a.btn `div.row > div.col-12 > div.d-flex > a.btn`
div.row > div.col-12 > div.d-flex > a.btn `div.row > div.col-12 > div.d-flex > a.btn`

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-*]` attributes match their roles

●`[aria-hidden="true"]` is not present on the document `<body>`

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

●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

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

○`[accesskey]` values are unique

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

○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

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

○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

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

○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
office-project-beat-box-front-end.vercel.app/	`Access to XMLHttpRequest at 'https://beatbox-api.runasp.net/api/category' from origin 'https://office-project-beat-box-front-end.vercel.app' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.`
office-project-beat-box-front-end.vercel.app/	`Access to XMLHttpRequest at 'https://beatbox-api.runasp.net/api/category' from origin 'https://office-project-beat-box-front-end.vercel.app' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.`
office-project-beat-box-front-end.vercel.app/	`Access to XMLHttpRequest at 'https://beatbox-api.runasp.net/api/product' from origin 'https://office-project-beat-box-front-end.vercel.app' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.`
office-project-beat-box-front-end.vercel.app/	`Access to XMLHttpRequest at 'https://beatbox-api.runasp.net/api/product' from origin 'https://office-project-beat-box-front-end.vercel.app' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.`
office-project-beat-box-front-end.vercel.app/assets/index-C0J4MEJ3.js line 825, col 85594	`Error fetching categories: AxiosError: Network Error at h.onerror (https://office-project-beat-box-front-end.vercel.app/assets/index-C0J4MEJ3.js:12:15522) at jo.request (https://office-project-beat-box-front-end.vercel.app/assets/index-C0J4MEJ3.js:14:2128) at async Object.getCategories (https://office-project-beat-box-front-end.vercel.app/assets/index-C0J4MEJ3.js:215:65466) at async https://office-project-beat-box-front-end.vercel.app/assets/index-C0J4MEJ3.js:215:68969`
office-project-beat-box-front-end.vercel.app/assets/index-C0J4MEJ3.js line 825, col 85594	`Error loading categories in header: AxiosError: Network Error at h.onerror (https://office-project-beat-box-front-end.vercel.app/assets/index-C0J4MEJ3.js:12:15522) at jo.request (https://office-project-beat-box-front-end.vercel.app/assets/index-C0J4MEJ3.js:14:2128) at async Object.getCategories (https://office-project-beat-box-front-end.vercel.app/assets/index-C0J4MEJ3.js:215:65466) at async https://office-project-beat-box-front-end.vercel.app/assets/index-C0J4MEJ3.js:215:68969`
office-project-beat-box-front-end.vercel.app/assets/index-C0J4MEJ3.js line 825, col 85594	`Failed to load categories: AxiosError: Network Error at h.onerror (https://office-project-beat-box-front-end.vercel.app/assets/index-C0J4MEJ3.js:12:15522) at jo.request (https://office-project-beat-box-front-end.vercel.app/assets/index-C0J4MEJ3.js:14:2128) at async Object.fetchCategories (https://office-project-beat-box-front-end.vercel.app/assets/index-C0J4MEJ3.js:194:221482) at async e (https://office-project-beat-box-front-end.vercel.app/assets/Home-BTVDOQ_2.js:48:1954)`
beatbox-api.runasp.net/api/category	`Failed to load resource: net::ERR_FAILED`
beatbox-api.runasp.net/api/product	`Failed to load resource: net::ERR_FAILED`
beatbox-api.runasp.net/api/category	`Failed to load resource: net::ERR_FAILED`
beatbox-api.runasp.net/api/product	`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
office-project-beat-box-front-end.vercel.app/assets/index-C0J4MEJ3.js

●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

○Redirects HTTP traffic to HTTPS

○Use a strong HSTS policy

○Detected JavaScript libraries

SEO

These checks ensure that your page is following basic search engine optimization advice. There are many additional factors Lighthouse does not score here that may affect your search ranking, including performance on Core Web Vitals. Learn more about Google Search Essentials.

Content Best Practices

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

●Page isn’t blocked from indexing

●Document has a `<title>` element

●Page has successful HTTP status code

●Links have descriptive text

●Links are crawlable

●Image elements have `[alt]` attributes

●Document has a valid `hreflang`

○robots.txt is valid

○Document has a valid `rel=canonical`