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.

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.02178397339512321] map[node:map[boundingRect:map[bottom:2529 height:26 left:0 right:412 top:2504 width:412] lhId:page-1-P nodeLabel:المزين | دورك محجوز path:1,HTML,1,BODY,3,FOOTER,1,P selector:body > footer > p snippet:<p> type:node] score:0.01162858079308578 subItems:map[items:[map[cause:Unsized image element extra:map[boundingRect:map[bottom:2494 height:151 left:151 right:261 top:2342 width:110] lhId:page-12-IMG nodeLabel:المزين path:1,HTML,1,BODY,3,FOOTER,0,IMG selector:body > footer > img snippet:<img src="assets/logo.png" alt="المزين"> type:node]]] type:subitems]] map[node:map[boundingRect:map[bottom:0 height:0 left:0 right:0 top:0 width:0] lhId:page-3-DIV nodeLabel: المزين دورك محجوز … path:0,DIV selector:div#mz-splash > div.mz-splash-content snippet:<div class="mz-splash-content"> type:node] score:0.008682485682336507 subItems:map[items:[map[cause:Web font extra:map[type:url value:https://fonts.gstatic.com/s/tajawal/v12/Iurf6YBj_oCad4k1l5anHrRpiZtK6GwN9w.woff2]] map[cause:Web font extra:map[type:url value:https://fonts.gstatic.com/s/tajawal/v12/Iurf6YBj_oCad4k1l8KiHrRpiZtK6GwN9w.woff2]] map[cause:Web font extra:map[type:url value:https://fonts.gstatic.com/s/tajawal/v12/Iurf6YBj_oCad4k1l4qkHrFpiZtK6Gw.woff2]]] type:subitems]] map[node:map[boundingRect:map[bottom:2529 height:26 left:0 right:412 top:2504 width:412] lhId:page-1-P nodeLabel:المزين | دورك محجوز path:1,HTML,1,BODY,3,FOOTER,1,P selector:body > footer > p snippet:<p> type:node] score:0.001472906919700925 subItems:map[items:[map[cause:Unsized image element extra:map[boundingRect:map[bottom:2494 height:151 left:151 right:261 top:2342 width:110] lhId:page-12-IMG nodeLabel:المزين path:1,HTML,1,BODY,3,FOOTER,0,IMG selector:body > footer > img snippet:<img src="assets/logo.png" alt="المزين"> type:node]] map[cause:Web font extra:map[type:url value:https://fonts.gstatic.com/s/tajawal/v12/Iura6YBj_oCad4k1nzSBC5xLhLFw4Q.woff2]] map[cause:Web font extra:map[type:url value:https://fonts.gstatic.com/s/tajawal/v12/Iura6YBj_oCad4k1nzGBC5xLhLE.woff2]] map[cause:Web font extra:map[type:url value:https://fonts.gstatic.com/s/tajawal/v12/Iurf6YBj_oCad4k1l8KiHrFpiZtK6Gw.woff2]]] type:subitems]]]

items: [map[node:map[type:text value:Total] score:0.3062420103970067] map[node:map[boundingRect:map[bottom:2559 height:247 left:0 right:412 top:2312 width:412] lhId:page-8-FOOTER nodeLabel:المزين | دورك محجوز path:1,HTML,1,BODY,3,FOOTER selector:body > footer snippet:<footer> type:node] score:0.3018143425072845 subItems:map[items:[map[cause:Unsized image element extra:map[boundingRect:map[bottom:773 height:358 left:76 right:336 top:415 width:260] lhId:page-0-IMG nodeLabel:لوجو المزين path:1,HTML,1,BODY,1,MAIN,0,SECTION,0,DIV,1,IMG selector:main#app > section.hero > div.w > img snippet:<img src="assets/logo.png" alt="لوجو المزين"> type:node]]] type:subitems]] map[node:map[boundingRect:map[bottom:173 height:64 left:48 right:396 top:109 width:348] lhId:page-10-EM nodeLabel:دي تجربة تليق بيك path:1,HTML,1,BODY,1,MAIN,0,SECTION,0,DIV,0,DIV,0,H1,1,EM selector:div.w > div > h1 > em snippet:<em> type:node] score:0.004427667889722232 subItems:map[items:[map[cause:Unsized image element extra:map[boundingRect:map[bottom:2494 height:151 left:151 right:261 top:2342 width:110] lhId:page-12-IMG nodeLabel:المزين path:1,HTML,1,BODY,3,FOOTER,0,IMG selector:body > footer > img snippet:<img src="assets/logo.png" alt="المزين"> type:node]] map[cause:Web font extra:map[type:url value:https://fonts.gstatic.com/s/tajawal/v12/Iurf6YBj_oCad4k1l5anHrFpiZtK6Gw.woff2]] map[cause:Web font extra:map[type:url value:https://fonts.gstatic.com/s/tajawal/v12/Iurf6YBj_oCad4k1l4qkHrRpiZtK6GwN9w.woff2]]] type:subitems]]]

Optimize LCP by making the LCP image discoverable from the HTML immediately, and avoiding lazy-loading

Why this matters

Performance issues directly impact user engagement and conversion rates.

lhId: page-0-IMG

nodeLabel: لوجو المزين

path: 1,HTML,1,BODY,1,MAIN,0,SECTION,0,DIV,1,IMG

selector: main#app > section.hero > div.w > img

snippet: <img src="assets/logo.png" alt="لوجو المزين">

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
fonts.googleapis.com/css2?family=Tajawal:wght@400;500;700;800&display=swap	1.1 KiB	838 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
1-mezayn.ethiodeploy.app/app.js?v=15	14400.0 s	33.3 KiB
1-mezayn.ethiodeploy.app/assets/logo.png	14400.0 s	26.8 KiB
1-mezayn.ethiodeploy.app/vendor/capacitor.js	14400.0 s	3.8 KiB
1-mezayn.ethiodeploy.app/qrcard.js?v=1	14400.0 s	2.4 KiB
1-mezayn.ethiodeploy.app/vendor/push-notifications.js	14400.0 s	549 B

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

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

URL	Transfer Size	Est Savings
1-mezayn.ethiodeploy.app/app.js?v=15	28.9 KiB	20.8 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
لوجو المزين `main#app > section.hero > div.w > img`	1-mezayn.ethiodeploy.app/assets/logo.png
المزين `body > footer > img`	1-mezayn.ethiodeploy.app/assets/logo.png

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
المزين \| دورك محجوز `body > footer`	0.302
المزين \| دورك محجوز `body > footer > p`	0.012
المزين دورك محجوز … `div#mz-splash > div.mz-splash-content`	0.009
دي تجربة تليق بيك `div.w > div > h1 > em`	0.004
المزين \| دورك محجوز `body > footer > p`	0.001

●Time to Interactive 2.7 s

●Document request latency

●Optimize DOM size

●Font display

●Forced reflow

●Improve image delivery

●LCP breakdown

●Modern HTTP

●Optimize viewport for mobile

●Max Potential First Input Delay 20 ms

●Minify CSS

●Minify JavaScript

●Reduce unused CSS

●Avoids enormous network payloads Total size was 152 KiB

●JavaScript execution time 0.1 s

●Minimizes main-thread work 0.6 s

●Avoid long main-thread tasks 3 long tasks found

●Avoid non-composited animations 1 animated element found

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 30 ms

●Server Backend Latencies 140 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 70 ms

○INP breakdown

○User Timing marks and measures

100

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.

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
English `header > div.w > nav > button#lang`
✂ ⭐ Top Rated 🔥 الأكثر حجزاً `div.w > div#fs > article.card > a.phw`
✂ ✔ موثّق 🆕 جديد `div.w > div#fs > article.card > a.phw`

○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

●Buttons have an accessible name

●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

●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 have a discernible name

●Touch targets have sufficient size and spacing.

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

●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

○Deprecated ARIA roles were not used

○Elements with `role="dialog"` or `role="alertdialog"` have accessible names.

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

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

○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

○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
1-mezayn.ethiodeploy.app/favicon.ico	`Failed to load resource: the server responded with a status of 404 ()`

●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

●Use a strong HSTS policy

●Mitigate DOM-based XSS with Trusted Types

●Page has valid source maps

○Redirects HTTP traffic to HTTPS

○Ensure CSP is effective against XSS attacks

○Ensure proper origin isolation with COOP

○Mitigate clickjacking with XFO or CSP

○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

●robots.txt is valid

●Image elements have `[alt]` attributes

●Document has a valid `hreflang`

○Document has a valid `rel=canonical`