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 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
portfolio.nabdz.com/_app/immutable/chunks/DMGLtoCd.js	0.0 ms	18.3 KiB
portfolio.nabdz.com/_app/immutable/nodes/2.bUxGQdOF.js	0.0 ms	13.6 KiB
portfolio.nabdz.com/_app/immutable/chunks/Bw9QDXRu.js	0.0 ms	9.7 KiB
portfolio.nabdz.com/_app/immutable/nodes/0.CvhTUhu0.js	0.0 ms	3.5 KiB
portfolio.nabdz.com/_app/immutable/chunks/B8IxreRs.js	0.0 ms	3.3 KiB
portfolio.nabdz.com/_app/immutable/entry/app.DsOUtHAi.js	0.0 ms	1.9 KiB
portfolio.nabdz.com/_app/immutable/chunks/B5EJ1eBi.js	0.0 ms	1.7 KiB
portfolio.nabdz.com/_app/immutable/chunks/CCKdEUft.js	0.0 ms	569 B
portfolio.nabdz.com/_app/immutable/nodes/1.XDt3OnCR.js	0.0 ms	285 B
portfolio.nabdz.com/_app/immutable/chunks/DvH31pTS.js	0.0 ms	179 B
portfolio.nabdz.com/_app/immutable/entry/start.sw-_dk5F.js	0.0 ms	147 B
portfolio.nabdz.com/_app/immutable/chunks/xihTtKlq.js	0.0 ms	123 B
portfolio.nabdz.com/_app/immutable/chunks/DQDQ37Av.js	0.0 ms	74 B

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.333859] map[node:map[boundingRect:map[bottom:1139 height:1275 left:-198 right:681 top:-136 width:879] lhId:page-7-DIV nodeLabel:div.app-layout > main#main-content > section#hero > div.diagonal-light-beam path:1,HTML,1,BODY,0,DIV,3,DIV,2,MAIN,2,SECTION,2,DIV selector:div.app-layout > main#main-content > section#hero > div.diagonal-light-beam snippet:<div class="diagonal-light-beam svelte-1q37ri0"> type:node] score:0.333859 subItems:map[items:[map[cause:Web font extra:map[type:url value:https://fonts.gstatic.com/s/plusjakartasans/v12/LDIoaomQNQcsA88c7O9yZ4KMCoOg4Ko20yygg_vb.woff2]]] type:subitems]]]

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:0.536 source:map[type:text value:[unattributed]]] map[reflowTime:231.013 source:map[column:25436 line:0 type:source-location url:https://portfolio.nabdz.com/_app/immutable/chunks/Bw9QDXRu.js urlProvider:network]] map[reflowTime:0.128 source:map[column:25489 line:0 type:source-location url:https://portfolio.nabdz.com/_app/immutable/chunks/Bw9QDXRu.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
Mial Zakaria - Creative Designer and Developer visual showcase `div.container > div.hero-right > div.visual-stage > img.hero-artwork-img`	portfolio.nabdz.com/images/mial-zakaria-hero.png	2.1 MiB	2.0 MiB
div.container > article.featured-project-card > div.card-visual-backdrop > img.backdrop-image `div.container > article.featured-project-card > div.card-visual-backdrop > img.backdrop-image`	portfolio.nabdz.com/images/projects/aquax-hero.png	492.5 KiB	463.0 KiB
Nabdz Web & Mobile App `article.featured-project-card > div.card-gallery-rail > button.gallery-thumb-btn > img.thumb-img`	portfolio.nabdz.com/images/projects/nabdz-web-mobile-app-hero-b6d591a5.jpg	225.4 KiB	222.8 KiB
Workspace desk setup with MZ laptop, coffee mug, and smartphone with neon glow `div.contact-grid > div.contact-left > div.desk-visual-container > img.desk-scene-img`	portfolio.nabdz.com/images/contact-desk-scene.png	227.8 KiB	202.7 KiB
Kenza Boulahlib Website `article.featured-project-card > div.card-gallery-rail > button.gallery-thumb-btn > img.thumb-img`	portfolio.nabdz.com/images/projects/kenza-boulahlib-website-hero-88b70d4a.jpg	165.0 KiB	162.4 KiB
div.container > article.featured-project-card > div.card-visual-backdrop > img.backdrop-image `div.container > article.featured-project-card > div.card-visual-backdrop > img.backdrop-image`	/images/projects/immocastle-real-estate-website-hero-5dcd...	206.8 KiB	136.7 KiB
Glowing green 3D paper plane tile `div.floating-cta-card > div.cta-card-content > div.cta-paper-plane-box > img.plane-tile-img`	portfolio.nabdz.com/images/cta-paper-plane.png	42.3 KiB	38.1 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
portfolio.nabdz.com/_app/immutable/assets/0.CggwavB0.css	2.5 KiB
/css2?family=JetBrains+Mono:wght@400;500;600&family=Outfi...	1.5 KiB	781 ms

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.

Element	Layout shift score
div.app-layout > main#main-content > section#hero > div.diagonal-light-beam `div.app-layout > main#main-content > section#hero > div.diagonal-light-beam`	0.334

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.

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

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
Style & Layout	1.2 s
Other	1.0 s
Script Evaluation	309 ms
Rendering	155 ms
Parse HTML & CSS	73 ms
Script Parsing & Compilation	5.5 ms

Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Transfer Size
portfolio.nabdz.com/images/mial-zakaria-hero.png	2.1 MiB
portfolio.nabdz.com/images/projects/aquax-hero.png	492.8 KiB
portfolio.nabdz.com/images/contact-desk-scene.png	228.0 KiB
portfolio.nabdz.com/images/projects/nabdz-web-mobile-app-hero-b6d591a5.jpg	225.6 KiB
/images/projects/immocastle-real-estate-website-hero-5dcd...	206.9 KiB
portfolio.nabdz.com/images/projects/kenza-boulahlib-website-hero-88b70d4a.jpg	165.2 KiB
portfolio.nabdz.com/images/cta-paper-plane.png	42.4 KiB
fonts.gstatic.com/s/outfit/v15/QGYvz_MVcBeNP4NJtEtqUYLknw.woff2	31.5 KiB
/s/jetbrainsmono/v24/tDbv2o-flEEny0FZhsfKu5WU4zr3E_BX0PnT...	30.6 KiB
/s/plusjakartasans/v12/LDIoaomQNQcsA88c7O9yZ4KMCoOg4Ko20y...	26.7 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
Workspace desk setup with MZ laptop, coffee mug, and smartphone with neon glow `div.contact-grid > div.contact-left > div.desk-visual-container > img.desk-scene-img`	portfolio.nabdz.com/images/contact-desk-scene.png

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

●Document request latency

●Optimize DOM size

●Font display

●LCP breakdown

●Modern HTTP

●Optimize viewport for mobile

●Minify CSS

●Minify JavaScript

●Reduce unused CSS

●Reduce unused JavaScript

●JavaScript execution time 0.3 s

●Avoid long main-thread tasks 6 long tasks found

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 160 ms

●Server Backend Latencies 230 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 160 ms

○INP breakdown

○LCP request discovery

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

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
OR REACH OUT DIRECTLY `div.contact-form-card > div.direct-reach-wrapper > div.direct-divider > span.svelte-wt4tt0`

These are opportunities to improve the legibility of your content.

○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

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

●Select elements have associated label elements.

●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

●Document has a main landmark.

●Deprecated ARIA roles were not used

●Elements with visible text labels have matching accessible names.

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

○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

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

○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

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