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:Source valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]

items: [map[reflowTime:1.001 source:map[column:6313 line:28 type:source-location url:https://masar.slidd.app/assets/useScrollMotion-Cw_qHNSZ.js urlProvider:network]] map[reflowTime:0.136 source:map[column:5256 line:28 type:source-location url:https://masar.slidd.app/assets/useScrollMotion-Cw_qHNSZ.js urlProvider:network]] map[reflowTime:0.13 source:map[column:2388 line:28 type:source-location url:https://masar.slidd.app/assets/useScrollMotion-Cw_qHNSZ.js urlProvider:network]] map[reflowTime:0.054 source:map[column:4368 line:36 type:source-location url:https://masar.slidd.app/assets/useScrollMotion-Cw_qHNSZ.js urlProvider:network]] map[reflowTime:16.151 source:map[column:2710 line:14 type:source-location url:https://masar.slidd.app/assets/useScrollMotion-Cw_qHNSZ.js urlProvider:network]] map[reflowTime:33.576 source:map[column:2132 line:34 type:source-location url:https://masar.slidd.app/assets/useScrollMotion-Cw_qHNSZ.js urlProvider:network]] map[reflowTime:2.24 source:map[column:1433 line:43 type:source-location url:https://masar.slidd.app/assets/useScrollMotion-Cw_qHNSZ.js urlProvider:network]] map[reflowTime:2.126 source:map[column:2100 line:43 type:source-location url:https://masar.slidd.app/assets/useScrollMotion-Cw_qHNSZ.js urlProvider:network]] map[reflowTime:2.693 source:map[column:1317 line:21 type:source-location url:https://masar.slidd.app/assets/useScrollMotion-Cw_qHNSZ.js urlProvider:network]] map[reflowTime:0.175 source:map[column:1121 line:21 type:source-location url:https://masar.slidd.app/assets/useScrollMotion-Cw_qHNSZ.js urlProvider:network]] map[reflowTime:0.699 source:map[column:8016 line:14 type:source-location url:https://masar.slidd.app/assets/useScrollMotion-Cw_qHNSZ.js urlProvider:network]] map[reflowTime:5.421 source:map[column:1252 line:28 type:source-location url:https://masar.slidd.app/assets/useScrollMotion-Cw_qHNSZ.js urlProvider:network]] map[reflowTime:34.056 source:map[column:15305 line:14 type:source-location url:https://masar.slidd.app/assets/useScrollMotion-Cw_qHNSZ.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
main.flex-1 > div > section.us-hero-wrap > div.us-hero-bg `main.flex-1 > div > section.us-hero-wrap > div.us-hero-bg`	masar.slidd.app/assets/ucas-cover-CIoaZgco.jpg	706.7 KiB	573.3 KiB

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-DIV

nodeLabel: main.flex-1 > div > section.us-hero-wrap > div.us-hero-bg

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

selector: main.flex-1 > div > section.us-hero-wrap > div.us-hero-bg

snippet: <div class="us-hero-bg" aria-hidden="true" style="background-image: url("/assets/ucas-cover-CIoaZgco.jpg");">

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
/css2?family=Cairo:wght@400;500;600;700;800;900&family=Ta...	1.4 KiB	857 ms
masar.slidd.app/assets/index-Dwzi8tfc.css	86.8 KiB	1.1 s

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 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: 600 ms 81.5 KiB

URL	Transfer Size	Est Savings
masar.slidd.app/assets/index-Dwzi8tfc.css	86.5 KiB	81.5 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: 300 ms 33.0 KiB

URL	Transfer Size	Est Savings
masar.slidd.app/assets/index-DGdx5kQJ.js	91.1 KiB	33.0 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	1.4 s
Rendering	1.0 s
Style & Layout	801 ms
Script Evaluation	650 ms
Parse HTML & CSS	25 ms
Script Parsing & Compilation	2.9 ms

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
Internal error.	Not actionable

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

●Use efficient cache lifetimes

●Layout shift culprits

●Document request latency

●Optimize DOM size

●Font display

●LCP breakdown

●Modern HTTP

●Optimize viewport for mobile

●Minify CSS

●Minify JavaScript

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

●JavaScript execution time 0.6 s

●Avoid long main-thread tasks 6 long tasks found

●Avoid non-composited animations 4 animated elements found

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

●Network Requests

●Network Round Trip Times 30 ms

●Server Backend Latencies 340 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 220 ms

○INP breakdown

○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
مسار `div.us-wrap > a.router-link-active > span > small`

These are opportunities to improve the legibility of your content.

Names and labels

Form elements without effective labels can create frustrating experiences for screen reader users. Learn more about the `select` element.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
كل التخصصات برمجيات وقواعد بيانات تصميم وتطوير مواقع الويب تكنولوجيا الوسائط ال… `div.us-wrap > div.us-filterbar > label.us-field > select.us-select`
دبلوم وبكالوريوس دبلوم بكالوريوس `div.us-wrap > div.us-filterbar > label.us-field > select.us-select`

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

●`[role]`s have all required `[aria-*]` attributes

●`[role]` values are valid

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

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

●Buttons have an accessible name

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

●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

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

○Image elements have `[alt]` attributes

○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

○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

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

100

Best Practices

●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 browser errors logged to the console

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

●Page has valid source maps

○Redirects HTTP traffic to HTTPS

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

Crawling and Indexing

If your robots.txt file is malformed, crawlers may not be able to understand how you want your website to be crawled or indexed. Learn more about robots.txt.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Line #	Content	Error
1	`<!DOCTYPE html>`	`Syntax not understood`
2	`<html lang="ar" dir="rtl">`	`Syntax not understood`
3	`<head>`	`Syntax not understood`
4	`<meta charset="UTF-8" />`	`Syntax not understood`
5	`<link rel="icon" href="/favicon.ico" />`	`Syntax not understood`
6	`<meta name="viewport" content="width=device-width, initial-scale=1.0" />`	`Syntax not understood`
7	`<title>مسار</title>`	`Syntax not understood`
8	`<link rel="preconnect" href="https://fonts.googleapis.com" />`	`Unknown directive`
9	`<link rel="preconnect" href="https://fonts.gstatic.com" crossorigin />`	`Unknown directive`
10	`<link`	`Syntax not understood`
11	`href="https://fonts.googleapis.com/css2?family=Cairo:wght@400;500;600;700;800;900&family=Tajawal:wght@400;500;700;800&display=swap"`	`Unknown directive`
12	`rel="stylesheet"`	`Syntax not understood`
13	`/>`	`Syntax not understood`
14	`<script type="module" crossorigin src="/assets/index-DGdx5kQJ.js"></script>`	`Syntax not understood`
15	`<link rel="stylesheet" crossorigin href="/assets/index-Dwzi8tfc.css">`	`Syntax not understood`
16	`</head>`	`Syntax not understood`
17	`<body>`	`Syntax not understood`
18	`<div id="app"></div>`	`Syntax not understood`
19	`</body>`	`Syntax not understood`
20	`</html>`	`Syntax not understood`

To appear in search results, crawlers need access to your app.

○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

●Document has a valid `hreflang`

○Image elements have `[alt]` attributes

○Document has a valid `rel=canonical`