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
daralsharka.online/assets/audio/ambient.mp3	14400.0 s	794.8 KiB
daralsharka.online/assets/images/logo-icon.png	604800.0 s	227.0 KiB
daralsharka.online/assets/uploads/cat_1790182071.png	604800.0 s	161.0 KiB
daralsharka.online/assets/uploads/cat_1790182048.png	604800.0 s	113.4 KiB
daralsharka.online/assets/uploads/home-20260924-1df8add7.jpg	604800.0 s	84.7 KiB
daralsharka.online/assets/uploads/prod-20260923-660ff08d.jpg	604800.0 s	72.9 KiB
daralsharka.online/assets/uploads/prod-20260923-48ee450c.webp	604800.0 s	68.8 KiB
/beacon.min.js/v31edd6df95cf4e85bb4c19e7a9bdbcba178836298...	86400.0 s	10.1 KiB
daralsharka.online/assets/css/style.css	604800.0 s	2.4 KiB

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
دار الشارقة للعبايات `div.container > div.header-center > a.logo > img.logo-img`	daralsharka.online/assets/images/logo-icon.png	226.1 KiB	225.5 KiB
Tast `div.cat-circles > a.cat-circle > div.cat-circle-img > img`	daralsharka.online/assets/uploads/cat_1790182071.png	160.1 KiB	157.4 KiB
حرير `div.cat-circles > a.cat-circle > div.cat-circle-img > img`	daralsharka.online/assets/uploads/cat_1790182048.png	112.4 KiB	107.2 KiB
بشت الاوان `div.product-grid > article.pcard > a.pcard-img > img`	daralsharka.online/assets/uploads/prod-20260923-660ff08d.jpg	71.9 KiB	5.3 KiB

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

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
fonts.googleapis.com/css2?family=Tajawal:wght@400;500;700;800&display=swap	1.1 KiB	231 ms
daralsharka.online/assets/css/style.css	2.4 KiB	68 ms

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

Diagnostics

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failure reason	Failure type
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

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
دار الشارقة للعبايات `div.container > div.header-center > a.logo > img.logo-img`	daralsharka.online/assets/images/logo-icon.png
دار الشارقة للعبايات `div.container > div.footer-brand-section > a.footer-logo-link > img.footer-logo`	daralsharka.online/assets/images/logo-icon.png

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

●Time to Interactive 1.8 s

●Layout shift culprits

●Document request latency

●Optimize DOM size

●Font display

●Forced reflow

●LCP breakdown

●LCP request discovery

●Modern HTTP

●Optimize viewport for mobile

●Max Potential First Input Delay 20 ms

●Minify CSS

●Minify JavaScript

●Reduce unused CSS

●Reduce unused JavaScript

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

●JavaScript execution time 0.0 s

●Minimizes main-thread work 0.3 s

●Avoid long main-thread tasks 1 long task found

●Network Requests

●Network Round Trip Times 10 ms

●Server Backend Latencies 20 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 590 ms

●Avoid large layout shifts 1 layout shift found

○INP breakdown

○User Timing marks and measures

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

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
body > main#main-content > div#musicPlayer > button.music-btn `body > main#main-content > div#musicPlayer > button.music-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.

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
DAR AL SHARKA `div.header-center > a.logo > span.logo-text > span.logo-text-en`
عرض الكل `section.section > div.container > div.sec-head-row > a.sec-link`
30,000 د.ع `article.pcard > div.pcard-info > div.pcard-price > span.pcard-new`
25,000 د.ع `article.pcard > div.pcard-info > div.pcard-price > span.pcard-new`
38,000 د.ع `article.pcard > div.pcard-info > div.pcard-price > span.pcard-old`
25,000 د.ع `article.pcard > div.pcard-info > div.pcard-price > span.pcard-new`
40,000 د.ع `article.pcard > div.pcard-info > div.pcard-price > span.pcard-old`
الأكثر طلباً `div.container > div.sec-head-row > div > span.section-eyebrow`
عرض الكل `section.section > div.container > div.sec-head-row > a.sec-link`
48,000 د.ع `article.pcard > div.pcard-info > div.pcard-price > span.pcard-new`
50,000 د.ع `article.pcard > div.pcard-info > div.pcard-price > span.pcard-old`
30,000 د.ع `article.pcard > div.pcard-info > div.pcard-price > span.pcard-new`
25,000 د.ع `article.pcard > div.pcard-info > div.pcard-price > span.pcard-new`
38,000 د.ع `article.pcard > div.pcard-info > div.pcard-price > span.pcard-old`
25,000 د.ع `article.pcard > div.pcard-info > div.pcard-price > span.pcard-new`
40,000 د.ع `article.pcard > div.pcard-info > div.pcard-price > span.pcard-old`
لماذا نحن؟ `section.why-section > div.container > div.section-head > span.section-eyebrow`
آراء عميلاتنا `section.testimonials-section > div.container > div.section-head > span.section-eyebrow`
تصميم وتطوير Mohammed Khaleel 🇮🇶 `footer.site-footer > div.container > div.footer-bottom > p.footer-credit`

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
دار الشارقة للعبايات DAR AL SHARKA `header.site-header > div.container > div.header-center > a.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

●`[role]` values are valid

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

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

●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

●Touch targets have sufficient size and spacing.

●Heading elements appear in a sequentially-descending order

●Skip links are focusable.

●Document has a main landmark.

●Deprecated ARIA roles were not used

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

●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 input fields 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

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

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

○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

○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
daralsharka.online/manifest.json	`Failed to load resource: the server responded with a status of 403 ()`
daralsharka.online/manifest.json	`Failed to load resource: the server responded with a status of 403 ()`
daralsharka.online/	`Manifest fetch from https://daralsharka.online/manifest.json failed, code 403`
daralsharka.online/	`Manifest fetch from https://daralsharka.online/manifest.json failed, code 403`

●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 DOM-based XSS with Trusted Types

●Page has valid source maps

○Redirects HTTP traffic to HTTPS

○Use a strong HSTS policy

○Mitigate clickjacking with XFO or CSP

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