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.

Consider setting font-display to swap or optional to ensure text is consistently visible. swap can be further optimized to mitigate layout shifts with font metric overrides.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Est Savings
immocastlepromotion.dz/icons/font-awesome/webfonts/fa-brands-400.woff2	80 ms
immocastlepromotion.dz/icons/font-awesome/webfonts/fa-regular-400.woff2	75 ms
immocastlepromotion.dz/icons/font-awesome/webfonts/fa-solid-900.woff2	70 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
ImmoCastle Residence Architecture `div.v2-about-grid > div.v2-about-images > div.v2-about-img-wrapper > img`	/cdn/gallery/d191f8b5c57974d5fe8028997dea74bd951edda1aefc...	405.1 KiB	369.7 KiB
NUVOLA `div.swiper > div#swiper-wrapper-b8cca0e5b610467bf > div.swiper-slide > img.pv2-hero-bg`	immocastlepromotion.dz/cdn/thumbnails/6a2ec1d260efd.webp	304.9 KiB	112.6 KiB
CASTELLUM 1 `div.swiper > div#swiper-wrapper-b8cca0e5b610467bf > div.swiper-slide > img.pv2-hero-bg`	immocastlepromotion.dz/cdn/thumbnails/6a2ec1c518d12.webp	203.9 KiB	59.6 KiB
Nouvelle Vallée 2 `div.swiper > div#swiper-wrapper-b8cca0e5b610467bf > div.swiper-slide > img.pv2-hero-bg`	immocastlepromotion.dz/cdn/thumbnails/6a7d88d57443b.webp	242.0 KiB	57.4 KiB
Immocastle Promotion `div.v2-footer-grid > div.v2-footer-brand > a.v2-footer-logo-link > img.v2-footer-logo`	immocastlepromotion.dz/assets/images/logo%20immocastle%20white.webp	19.2 KiB	18.8 KiB
Nouvelle Vallée `div.swiper > div#swiper-wrapper-b8cca0e5b610467bf > div.swiper-slide > img.pv2-hero-bg`	immocastlepromotion.dz/cdn/thumbnails/6a33f553ed194.webp	126.6 KiB	9.1 KiB
CASTELLUM 2 `div.swiper > div#swiper-wrapper-b8cca0e5b610467bf > div.swiper-slide > img.pv2-hero-bg`	immocastlepromotion.dz/cdn/thumbnails/6a2ec1b116af1.webp	199.5 KiB	7.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.

More than 4 preconnect connections were found. These should be used sparingly and only to the most important origins.

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
immocastlepromotion.dz/js/theme-init.js	323 B
immocastlepromotion.dz/vendor/rangeslider/rangeslider.css	2.8 KiB
immocastlepromotion.dz/css/index.css?v=2.1.0	5.2 KiB
immocastlepromotion.dz/vendor/bootstrap-select/css/bootstrap-select.min.css	2.1 KiB
immocastlepromotion.dz/icons/line-awesome/css/line-awesome.min.css	14.8 KiB	409 ms
immocastlepromotion.dz/vendor/magnific-popup/magnific-popup.min.css	1.5 KiB
immocastlepromotion.dz/vendor/lightgallery/css/lightgallery.min.css	3.5 KiB
immocastlepromotion.dz/icons/font-awesome/css/all.min.css	12.1 KiB	204 ms
cdnjs.cloudflare.com/ajax/libs/font-awesome/6.5.2/css/all.min.css	19.2 KiB	982 ms
/css2?family=Montserrat:wght@400;600;700&family=Oswald:wg...	1.2 KiB	819 ms

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: 450 ms 127.4 KiB

URL	Transfer Size	Est Savings
immocastlepromotion.dz/css/skin/main.css?v=2.1.0	83.3 KiB	82.4 KiB
cdnjs.cloudflare.com/ajax/libs/font-awesome/6.5.2/css/all.min.css	18.5 KiB	18.3 KiB
immocastlepromotion.dz/icons/line-awesome/css/line-awesome.min.css	14.8 KiB	14.8 KiB
immocastlepromotion.dz/icons/font-awesome/css/all.min.css	12.1 KiB	11.9 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: 500 ms 73.1 KiB

URL	Transfer Size	Est Savings
www.googletagmanager.com/gtag/js?id=G-LT6M5ZW4Q2	172.3 KiB	73.1 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.7 s
Style & Layout	750 ms
Script Evaluation	557 ms
Rendering	316 ms
Script Parsing & Compilation	121 ms
Parse HTML & CSS	110 ms
Garbage Collection	70 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
Pages with cache-control:no-store header cannot enter back/forward cache.	Actionable
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

Minifying CSS files can reduce network payload sizes. Learn how to minify CSS.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 0.0 ms 17.5 KiB

URL	Transfer Size	Est Savings
immocastlepromotion.dz/css/skin/main.css?v=2.1.0	83.4 KiB	17.5 KiB

Minifying JavaScript files can reduce payload sizes and script parse time. Learn how to minify JavaScript.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 0.0 ms 3.8 KiB

URL	Transfer Size	Est Savings
immocastlepromotion.dz/vendor/rangeslider/rangeslider.js	11.8 KiB	3.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
ImmoCastle Residence Architecture `div.v2-about-grid > div.v2-about-images > div.v2-about-img-wrapper > img`	/cdn/gallery/d191f8b5c57974d5fe8028997dea74bd951edda1aefc...
Immocastle Promotion `div.nav-container > div.logo > a > img#navLogo`	immocastlepromotion.dz/assets/images/logo%20immocastle%20white.webp
Immocastle Promotion `div.v2-footer-grid > div.v2-footer-brand > a.v2-footer-logo-link > img.v2-footer-logo`	immocastlepromotion.dz/assets/images/logo%20immocastle%20white.webp

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

●Forced reflow

●LCP breakdown

●Modern HTTP

●Optimize viewport for mobile

●Avoids enormous network payloads Total size was 2,262 KiB

●JavaScript execution time 0.6 s

●Avoid long main-thread tasks 7 long tasks found

●Avoid non-composited animations 47 animated elements found

●Network Requests

●Network Round Trip Times 50 ms

●Server Backend Latencies 50 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 80 ms

●Avoid large layout shifts 3 layout shifts found

○INP breakdown

○LCP request discovery

○User Timing marks and measures

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
© 2026 Immocastle Promotion. Tous droits réservés. `div.v2-footer-bottom > div.container > div.v2-footer-bottom-inner > span.v2-footer-copyright`
Immocastle Promotion `div.container > div.v2-footer-bottom-inner > span.v2-footer-copyright > a`
Politique de confidentialité `div.container > div.v2-footer-bottom-inner > span.v2-footer-legal > a`
Sitemap `div.container > div.v2-footer-bottom-inner > span.v2-footer-legal > a`

These are opportunities to improve the legibility of your content.

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
Zones Résidentielles `div.v2-about-features > div.v2-about-feature-item > div.feature-info > h4.v2-about-feature-title`
NOS PROJETS `div.container > div.v2-footer-grid > div.v2-footer-col > h5.v2-footer-col-title`

These are opportunities to improve keyboard navigation in your application.

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

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

●ARIA attributes are used as specified for the element's role

●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 are distinguishable without relying on color.

●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

●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

●Identical links have the same purpose.

○`[accesskey]` values are unique

○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

○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

○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

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

○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

●Ensure proper origin isolation with COOP

●Mitigate DOM-based XSS with Trusted Types

●Detected JavaScript libraries

●Page has valid source maps

○Redirects HTTP traffic to HTTPS

○Use a strong HSTS policy

○Mitigate clickjacking with XFO or CSP

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`