Skip to content
https://sahra-mr.ai.studio

Lighthouse Mobile

· 0 checks — Mobile Lighthouse audit -- Performance, Accessibility, Best Practices, and SEO category breakdown.
SCORE
0
GRADE
FIX
0
REVIEW
0
PASS
0
INFO
0

Detailed Report

Audit breakdown by category with detailed findings.

55

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.20442983731916603] map[node:map[boundingRect:map[bottom:818 height:384 left:-31 right:353 top:434 width:384] lhId:page-1-DIV nodeLabel:main#main-content > div.space-y-10 > section.relative > div.absolute path:1,HTML,1,BODY,0,DIV,0,DIV,2,MAIN,0,DIV,0,SECTION,1,DIV selector:main#main-content > div.space-y-10 > section.relative > div.absolute snippet:<div class="absolute bottom-0 left-0 -mb-12 -ml-12 w-96 h-96 bg-emerald-500/10 rounded…"> type:node] score:0.1168235605398458 subItems:map[items:[map[cause:Web font extra:map[type:url value:https://fonts.gstatic.com/s/cairo/v31/SLXVc1nY6HkvangtZmpQdkhzfH5lkSscQyyS8p4_RHH1.woff2]] map[cause:Web font extra:map[type:url value:https://fonts.gstatic.com/s/tajawal/v12/Iurf6YBj_oCad4k1l5anHrRpiZtK6GwN9w.woff2]]] type:subitems]] map[node:map[boundingRect:map[bottom:818 height:384 left:-31 right:353 top:434 width:384] lhId:page-1-DIV nodeLabel:main#main-content > div.space-y-10 > section.relative > div.absolute path:1,HTML,1,BODY,0,DIV,0,DIV,2,MAIN,0,DIV,0,SECTION,1,DIV selector:main#main-content > div.space-y-10 > section.relative > div.absolute snippet:<div class="absolute bottom-0 left-0 -mb-12 -ml-12 w-96 h-96 bg-emerald-500/10 rounded…"> type:node] score:0.0767599609241824 subItems:map[items:[map[cause:Web font extra:map[type:url value:https://fonts.gstatic.com/s/tajawal/v12/Iurf6YBj_oCad4k1l5anHrFpiZtK6Gw.woff2]]] type:subitems]] map[node:map[boundingRect:map[bottom:818 height:384 left:-31 right:353 top:434 width:384] lhId:page-1-DIV nodeLabel:main#main-content > div.space-y-10 > section.relative > div.absolute path:1,HTML,1,BODY,0,DIV,0,DIV,2,MAIN,0,DIV,0,SECTION,1,DIV selector:main#main-content > div.space-y-10 > section.relative > div.absolute snippet:<div class="absolute bottom-0 left-0 -mb-12 -ml-12 w-96 h-96 bg-emerald-500/10 rounded…"> type:node] score:0.01084631585513784 subItems:map[items:[map[cause:Web font extra:map[type:url value:https://fonts.gstatic.com/s/cairo/v31/SLXVc1nY6HkvangtZmpQdkhzfH5lkSscRiyS8p4_RA.woff2]]] type:subitems]]]

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.

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.

URLResource SizeEst Savings
SAHRA ALERT div.flex > button.cursor-pointer > div.relative > img.w-full
sahra-mr.ai.studio/assets/aistudio/sahra-icon_5d5c3ad4.png207.0 KiB206.9 KiB

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

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.

ElementLayout shift score
main#main-content > div.space-y-10 > section.relative > div.absolute main#main-content > div.space-y-10 > section.relative > div.absolute
0.117
main#main-content > div.space-y-10 > section.relative > div.absolute main#main-content > div.space-y-10 > section.relative > div.absolute
0.077
main#main-content > div.space-y-10 > section.relative > div.absolute main#main-content > div.space-y-10 > section.relative > div.absolute
0.011

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

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: 1.9 s 394.0 KiB
URLTransfer SizeEst Savings
sahra-mr.ai.studio/assets/index-uR0U1icO.js646.5 KiB394.0 KiB

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

●Use efficient cache lifetimes
●Document request latency
●Optimize DOM size
●Font display
●Forced reflow
●LCP breakdown
●Modern HTTP
●Optimize viewport for mobile
●Max Potential First Input Delay 50 ms
●Minify CSS
●Minify JavaScript
●Reduce unused CSS
●Avoids enormous network payloads Total size was 1,073 KiB
●JavaScript execution time 0.1 s
●Minimizes main-thread work 1.0 s
●Avoid long main-thread tasks 5 long tasks 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 60 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 40 ms
○INP breakdown
○LCP request discovery
○User Timing marks and measures
○Avoid non-composited animations
98

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.

Navigation

Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
ميثاق الشفافية وحدود المشروع التجريبي وحماية المصدر section.bg-amber-50/90 > div.flex > div > h3.text-sm

These are opportunities to improve keyboard navigation in your application.

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
SAHRA ALERT header.sticky > div.max-w-7xl > div.flex > button.cursor-pointer
○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
●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
●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
●No element has a `[tabindex]` value greater than 0
●Touch targets have sufficient size and spacing.
●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.
○`[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.
○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
○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.
100

Best Practices

General

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.

●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 clickjacking with XFO or CSP
●Mitigate DOM-based XSS with Trusted Types
○Redirects HTTP traffic to HTTPS
○Detected JavaScript libraries
92

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.

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 #ContentError
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 <meta name="viewport" content="width=device-width, initial-scale=1.0" />Syntax not understood
6 <title>SAHRA ALERT – مساعد معلومات المناخ الموريتاني</title>Syntax not understood
7 <link rel="icon" type="image/png" href="/assets/aistudio/sahra-icon_5d5c3ad4.png" />Syntax not understood
8 <meta name="description" content="منصة SAHRA ALERT — مبادرة فردية مستقلة من تطوير المشارك الموريتاني زين الدين محمد ربيع (نواذيبو، موريتانيا) لمسابقة P.A.S Challenge 2026 (فئة اللغات الإفريقية)، لشرح النشرات المناخية باللهجة الحسانية الموريتانية والفرنسية." />Syntax not understood
9 <meta property="og:title" content="SAHRA ALERT – Mauritanian Climate Information Assistant" />Unknown directive
10 <meta property="og:description" content="SAHRA ALERT — Initiative individuelle de Zeindine Mohamed Rabie (Nouadhibou, Mauritanie) pour le P.A.S Challenge 2026 (Catégorie Langues africaines), vulgarisant les bulletins climatiques en hassaniya et en français." />Unknown directive
11 <meta property="og:image" content="/assets/aistudio/sahra-logo_2f6141dc.png" />Unknown directive
12 <meta property="og:type" content="website" />Unknown directive
13 <meta name="twitter:card" content="summary_large_image" />Unknown directive
14 <link rel="preconnect" href="https://fonts.googleapis.com">Unknown directive
15 <link rel="preconnect" href="https://fonts.gstatic.com" crossorigin>Unknown directive
16 <link href="https://fonts.googleapis.com/css2?family=Cairo:wght@300;400;500;600;700;800;900&family=Tajawal:wght@400;500;700;800&display=swap" rel="stylesheet">Unknown directive
17 <script type="module" crossorigin src="/assets/index-uR0U1icO.js"></script>Syntax not understood
18 <link rel="stylesheet" crossorigin href="/assets/index-CqnmJmdK.css">Syntax not understood
19 </head>Syntax not understood
20 <body class="bg-amber-50/40 text-stone-900 font-['Cairo',sans-serif] antialiased selection:bg-amber-200 selection:text-amber-900">Unknown directive
21 <div id="root"></div>Syntax not understood
22 </body>Syntax not understood
23</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
●Document has a meta description
●Page has successful HTTP status code
●Links have descriptive text
●Links are crawlable
●Image elements have `[alt]` attributes
●Document has a valid `hreflang`
○Document has a valid `rel=canonical`

Send Feedback