https://website-bug-fixes-an-as87.bolt.host

Lighthouse Desktop

· 0 checks — Desktop 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.13682665265738553] map[node:map[boundingRect:map[bottom:1055 height:56 left:67 right:368 top:999 width:301] lhId:page-1-DIV nodeLabel:Featured products A handpicked artisan selection of high quality path:1,HTML,1,BODY,0,DIV,0,DIV,1,MAIN,0,DIV,3,SECTION,0,DIV,0,DIV selector:div > section.mx-auto > div.flex > div snippet:<div> type:node] score:0.08948892974929225] map[node:map[boundingRect:map[bottom:1987 height:988 left:35 right:1315 top:999 width:1280] lhId:page-5-SECTION nodeLabel:Featured products A handpicked artisan selection of high quality Shop → Featu… path:1,HTML,1,BODY,0,DIV,0,DIV,1,MAIN,0,DIV,3,SECTION selector:div.flex > main.flex-1 > div > section.mx-auto snippet:<section class="mx-auto max-w-7xl px-4 pb-16 sm:px-6 lg:px-8"> type:node] score:0.03760912938154861] map[node:map[boundingRect:map[bottom:1987 height:988 left:35 right:1315 top:999 width:1280] lhId:page-5-SECTION nodeLabel:Featured products A handpicked artisan selection of high quality Shop → Featu… path:1,HTML,1,BODY,0,DIV,0,DIV,1,MAIN,0,DIV,3,SECTION selector:div.flex > main.flex-1 > div > section.mx-auto snippet:<section class="mx-auto max-w-7xl px-4 pb-16 sm:px-6 lg:px-8"> type:node] score:0.00972859352654467 subItems:map[items:[map[cause:Web font extra:map[type:url value:https://fonts.gstatic.com/s/inter/v20/UcC73FwrK3iLTeHuS_nVMrMxCp50SjIa1ZL7W0Q5nw.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: Souk marocain

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

selector: main.flex-1 > div > section.relative > img.absolute

snippet: <img src="https://images.pexels.com/photos/35513343/pexels-photo-35513343.jpeg?auto=…" alt="Souk marocain" class="absolute inset-0 h-full w-full object-cover opacity-40">

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
website-bug-fixes-an-as87.bolt.host/assets/index-NL90mH8n.css	5.5 KiB
/css2?family=Cairo:wght@400;600;700&family=Inter:wght@400...	1.6 KiB	323 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
Beni Ouarain Rug `div.group > a.block > div.relative > img.h-full`	/photos/34113608/pexels-photo-34113608.jpeg?auto=compress...	98.5 KiB	84.8 KiB
Fès Leather Babouche `div.group > a.block > div.relative > img.h-full`	/photos/27967570/pexels-photo-27967570.jpeg?auto=compress...	93.4 KiB	79.7 KiB
Organic Argan Oil 100 ml `div.group > a.block > div.relative > img.h-full`	/photos/13812743/pexels-photo-13812743.jpeg?auto=compress...	65.5 KiB	52.5 KiB
Souk marocain `main.flex-1 > div > section.relative > img.absolute`	/photos/35513343/pexels-photo-35513343.jpeg?auto=compress...	92.9 KiB	35.5 KiB
Clay Tagine 30 cm `div.group > a.block > div.relative > img.h-full`	/photos/35473885/pexels-photo-35473885.jpeg?auto=compress...	39.2 KiB	31.4 KiB
Engraved Brass Lantern `div.group > a.block > div.relative > img.h-full`	/photos/774378/pexels-photo-774378.jpeg?auto=compress&cs=...	33.5 KiB	26.9 KiB
Moroccan Glass Teapot `div.group > a.block > div.relative > img.h-full`	/photos/10900909/pexels-photo-10900909.jpeg?auto=compress...	24.7 KiB	19.8 KiB
Kelaat M'Gouna Rose Water 200 ml `div.group > a.block > div.relative > img.h-full`	/photos/39281916/pexels-photo-39281916.jpeg?auto=compress...	23.6 KiB	18.9 KiB

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: 220 ms 76.3 KiB

URL	Transfer Size	Est Savings
website-bug-fixes-an-as87.bolt.host/assets/index-C9QJKPma.js	128.6 KiB	76.3 KiB

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
Featured products A handpicked artisan selection of high quality `div > section.mx-auto > div.flex > div`	0.089
Featured products A handpicked artisan selection of high quality Shop → Featu… `div.flex > main.flex-1 > div > section.mx-auto`	0.038
Featured products A handpicked artisan selection of high quality Shop → Featu… `div.flex > main.flex-1 > div > section.mx-auto`	0.010

●Time to Interactive 1.4 s

●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 20 ms

●Minify CSS

●Minify JavaScript

●Reduce unused CSS

●Avoids enormous network payloads Total size was 732 KiB

●JavaScript execution time 0.0 s

●Minimizes main-thread work 0.2 s

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

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 30 ms

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

○INP breakdown

○User Timing marks and measures

○Avoid long main-thread tasks

○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
Home `header.sticky > div.mx-auto > nav.hidden > a.text-sm`
A handpicked artisan selection of high quality `section.mx-auto > div.flex > div > p.mt-1`
Shop → `div > section.mx-auto > div.flex > a.text-sm`
Featured `div.group > a.block > div.relative > span.absolute`
Featured `div.group > a.block > div.relative > span.absolute`
Featured `div.group > a.block > div.relative > span.absolute`
Featured `div.group > a.block > div.relative > span.absolute`
Featured `div.group > a.block > div.relative > span.absolute`
Featured `div.group > a.block > div.relative > span.absolute`
Featured `div.group > a.block > div.relative > span.absolute`
© 2026 Hirfa — All rights reserved `footer.mt-16 > div.border-t > div.mx-auto > span`
Made with love in Morocco `footer.mt-16 > div.border-t > div.mx-auto > span`

These are opportunities to improve the legibility of your content.

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 `div.mx-auto > div.flex > div.relative > button.btn-ghost`

○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

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

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

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

○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

○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

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

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
website-bug-fixes-an-as87.bolt.host/	`Loading the script 'https://bolt.new/badge.js?s=f5ffad85-4029-419f-ab67-8cf25eacd7f1' violates the following Content Security Policy directive: "script-src 'self' 'unsafe-inline'". Note that 'script-src-elem' was not explicitly set, so 'script-src' is used as a fallback. The action has been blocked.`
website-bug-fixes-an-as87.bolt.host/	`Loading the script 'https://bolt.new/deployed-preview-script.js?origin=https%3A%2F%2Fbolt.new' violates the following Content Security Policy directive: "script-src 'self' 'unsafe-inline'". Note that 'script-src-elem' was not explicitly set, so 'script-src' is used as a fallback. The action has been blocked.`
website-bug-fixes-an-as87.bolt.host/ line 16, col 0	`The Content Security Policy directive 'frame-ancestors' is ignored when delivered via a <meta> element.`
website-bug-fixes-an-as87.bolt.host/ line 12, col 0	`X-Frame-Options may only be set via an HTTP header sent along with a document. It may not be set inside <meta>.`

Issues logged to the `Issues` panel in Chrome Devtools indicate unresolved problems. They can come from network request failures, insufficient security controls, and other browser concerns. Open up the Issues panel in Chrome DevTools for more details on each issue.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Issue type
Content security policy

●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

●Ensure CSP is effective against XSS attacks

●Ensure proper origin isolation with COOP

●Mitigate clickjacking with XFO or CSP

●Mitigate DOM-based XSS with Trusted Types

●Page has valid source maps

○Redirects HTTP traffic to HTTPS

○Use a strong HSTS policy

○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

Descriptive link text helps search engines understand your content. Learn how to make links more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Link destination	Link Text
website-bug-fixes-an-as87.bolt.host/about	Learn more

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
131	`<!doctype html>`	`Syntax not understood`
132	`<html lang="ar" dir="rtl">`	`Syntax not understood`
133	`<head>`	`Syntax not understood`
134	`<meta charset="UTF-8" />`	`Syntax not understood`
135	`<meta name="viewport" content="width=device-width, initial-scale=1.0" />`	`Syntax not understood`
136	`<meta name="theme-color" content="#db7022" />`	`Syntax not understood`
137	`<meta`	`Syntax not understood`
138	`name="description"`	`Syntax not understood`
139	`content="حِرفة (Hirfa) — متجر إلكتروني للحرف المغربية الأصيلة: زيت أركان، جلد فاس، طاجين، زرابي بني ورين، وغيرها. توصيل لكل المغرب والطلب عبر واتساب."`	`Unknown directive`
140	`/>`	`Syntax not understood`
141	`<meta name="referrer" content="strict-origin-when-cross-origin" />`	`Syntax not understood`
142	`<meta http-equiv="X-Content-Type-Options" content="nosniff" />`	`Syntax not understood`
143	`<meta http-equiv="X-Frame-Options" content="SAMEORIGIN" />`	`Syntax not understood`
144	`<meta`	`Syntax not understood`
145	`http-equiv="Content-Security-Policy"`	`Syntax not understood`
146	`content="default-src 'self'; img-src 'self' https://images.pexels.com data:; script-src 'self' 'unsafe-inline'; style-src 'self' 'unsafe-inline' https://fonts.googleapis.com; font-src 'self' https://fonts.gstatic.com data:; connect-src 'self' https://*.supabase.co https://api.whatsapp.com https://wa.me; frame-ancestors 'self'; base-uri 'self'; form-action 'self'; object-src 'none';"`	`Unknown directive`
147	`/>`	`Syntax not understood`
148	`<meta`	`Syntax not understood`
149	`http-equiv="Permissions-Policy"`	`Syntax not understood`
150	`content="camera=(), microphone=(), geolocation=(), payment=(), usb=(), magnetometer=(), gyroscope=(), accelerometer=()"`	`Syntax not understood`
151	`/>`	`Syntax not understood`
152	`<link rel="preconnect" href="https://fonts.googleapis.com" />`	`Unknown directive`
153	`<link rel="preconnect" href="https://fonts.gstatic.com" crossorigin />`	`Unknown directive`
154	`<link`	`Syntax not understood`
155	`href="https://fonts.googleapis.com/css2?family=Cairo:wght@400;600;700&family=Inter:wght@400;500;600;700&display=swap"`	`Unknown directive`
156	`rel="stylesheet"`	`Syntax not understood`
157	`/>`	`Syntax not understood`
158	`<title>حِرفة (Hirfa) — حرف مغربية أصيلة</title>`	`Syntax not understood`
159	`<meta property="og:image" content="https://bolt.new/static/og_default.png">`	`Unknown directive`
160	`<meta name="twitter:card" content="summary_large_image">`	`Unknown directive`
161	`<meta name="twitter:image" content="https://bolt.new/static/og_default.png">`	`Unknown directive`
162	`<script type="module" crossorigin src="/assets/index-C9QJKPma.js"></script>`	`Syntax not understood`
163	`<link rel="stylesheet" crossorigin href="/assets/index-NL90mH8n.css">`	`Syntax not understood`
164	`<script async src="https://bolt.new/badge.js?s=f5ffad85-4029-419f-ab67-8cf25eacd7f1"></script><script async src="https://bolt.new/deployed-preview-script.js?origin=https%3A%2F%2Fbolt.new"></script></head>`	`Unknown directive`
165	`<body>`	`Syntax not understood`
166	`<div id="root"></div>`	`Syntax not understood`
167	`</body>`	`Syntax not understood`
168	`</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 are crawlable

●Image elements have `[alt]` attributes

●Document has a valid `hreflang`

○Document has a valid `rel=canonical`