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
/l/font?kit=nuFcD-vYSZviVYUb_rj3ij__anPXJzDwcbmjWBN2PKdFv...	86400.0 s	38.3 KiB
/l/font?kit=LDIWaomQNQcsA88c7O9yZ4KMCoOg4IA6-91aHEjcWuA_9...	86400.0 s	27.1 KiB

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
	/photo-1578985545062-69928b1d9587?w=1000&h=1000&fit=crop&...	135.2 KiB	115.9 KiB
Noir Velvet 70% Qora Shokoladli Tort `div.grid > div.group > div.aspect-square > img.w-full`	/photo-1578985545062-69928b1d9587?w=600&h=600&fit=crop&au...	65.4 KiB	60.0 KiB
Candora Confectionery Atelier Chef Hand Crafting `div.max-w-7xl > div.grid > div.relative > img.w-full`	/photo-1583338917451-face2751d8d5?w=1000&h=800&fit=crop&a...	66.6 KiB	57.0 KiB
Qirollik Rezavorli Bayram Torti `div.grid > div.group > div.aspect-square > img.w-full`	/photo-1464349095431-e9a21285b5f3?w=600&h=600&fit=crop&au...	44.9 KiB	40.8 KiB
Mijoz `div.pt-6 > div.flex > div.flex > img.inline-block`	/photo-1500648767791-00dcc994a43e?w=100&h=100&fit=crop&cr...	6.6 KiB	6.4 KiB
Mijoz `div.pt-6 > div.flex > div.flex > img.inline-block`	/photo-1494790108377-be9c29b29330?w=100&h=100&fit=crop&cr...	6.4 KiB	6.2 KiB
Mijoz `div.pt-6 > div.flex > div.flex > img.inline-block`	/photo-1507003211169-0a1dd7228f2d?w=100&h=100&fit=crop&cr...	6.2 KiB	6.1 KiB
Mijoz `div.pt-6 > div.flex > div.flex > img.inline-block`	/photo-1534528741775-53994a69daeb?w=100&h=100&fit=crop&cr...	5.8 KiB	5.6 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

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
candora-omega.vercel.app/assets/index-BFJJyiZz.css	23.7 KiB	302 ms
/css2?family=Playfair+Display:ital,wght@0,400..900;1,400....	1.2 KiB	846 ms
/css2?family=Playfair+Display:ital,wght@0,400;0,500;0,600...	1.2 KiB	181 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 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: 760 ms 144.7 KiB

URL	Transfer Size	Est Savings
candora-omega.vercel.app/assets/index-Dr_R8s02.js	287.9 KiB	144.7 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
Style & Layout	1.1 s
Other	930 ms
Script Evaluation	614 ms
Rendering	179 ms
Parse HTML & CSS	19 ms
Script Parsing & Compilation	3.8 ms

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

●Layout shift culprits

●Document request latency

●Optimize DOM size

●Font display

●Forced reflow

●LCP breakdown

●Modern HTTP

●Optimize viewport for mobile

●Minify CSS

●Minify JavaScript

●Reduce unused CSS

●Avoids enormous network payloads Total size was 854 KiB

●JavaScript execution time 0.6 s

●Avoid long main-thread tasks 12 long tasks found

●Avoid non-composited animations 95 animated elements found

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

○INP breakdown

○LCP request discovery

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

ARIA

Using ARIA attributes in roles where they are prohibited can mean that important information is not communicated to users of assistive technologies. Learn more about prohibited ARIA roles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Reyting: 4.7 yulduz `div > div.flex > div.flex > div.flex`
Reyting: 4.8 yulduz `div > div.flex > div.flex > div.flex`
Reyting: 4.9 yulduz `div > div.flex > div.flex > div.flex`
Reyting: 5 yulduz `div > div.flex > div.flex > div.flex`
Reyting: 4.7 yulduz `div > div.flex > div.flex > div.flex`
Reyting: 4.8 yulduz `div > div.flex > div.flex > div.flex`
Reyting: 4.9 yulduz `div > div.flex > div.flex > div.flex`
Reyting: 5 yulduz `div > div.flex > div.flex > div.flex`
Reyting: 4.7 yulduz `div > div.flex > div.flex > div.flex`
Reyting: 4.8 yulduz `div > div.flex > div.flex > div.flex`
Reyting: 4.9 yulduz `div > div.flex > div.flex > div.flex`
Reyting: 5 yulduz `div > div.flex > div.flex > div.flex`
Reyting: 5 yulduz `div.grid > div.p-6 > div.space-y-3 > div.flex`
Reyting: 5 yulduz `div.grid > div.p-6 > div.space-y-3 > div.flex`
Reyting: 5 yulduz `div.grid > div.p-6 > div.space-y-3 > div.flex`
Reyting: 5 yulduz `div.grid > div.p-6 > div.space-y-3 > div.flex`

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

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
Saralangan Xomashyo `div.space-y-4 > div.flex > div > h4.text-sm`

These are opportunities to improve keyboard navigation in your application.

Best practices

Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Desert 1 `div.aspect-square > div.absolute > div.flex > button.h-1.5`
Desert 2 `div.aspect-square > div.absolute > div.flex > button.h-1.5`
Desert 3 `div.aspect-square > div.absolute > div.flex > button.h-1.5`

These items highlight common accessibility best practices.

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
UZ `nav.max-w-7xl > div.flex > div.relative > button.flex`

○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

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

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

●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

●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

●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

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

○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

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.

URL
candora-omega.vercel.app/assets/index-Dr_R8s02.js

●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 clickjacking with XFO or CSP

●Mitigate DOM-based XSS with Trusted Types

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

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="uz">`	`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>Candora — Haute Confectionery Atelier</title>`	`Syntax not understood`
7	`<meta name="description" content="Candora — Qo'lda tayyorlangan hashamatli shirinliklar, eksklyuziv tortlar, fransuz makaronlari va artisan shokoladlar atelesi. Shirinlik emas. Bir lahza." />`	`Syntax not understood`
8	`<meta name="keywords" content="Candora, shirinliklar Toshkent, tort buyurtma qilish, premium tortlar, fransuz makaronlari, to'y torti, artisanal desserts Tashkent" />`	`Syntax not understood`
9	`<meta name="author" content="Candora Haute Confectionery" />`	`Syntax not understood`
10	`<meta name="robots" content="index, follow, max-image-preview:large, max-snippet:-1, max-video-preview:-1" />`	`Unknown directive`
11	`<link rel="canonical" href="https://candora-omega.vercel.app/" />`	`Unknown directive`
13	`<!-- Favicon (Inline SVG Luxury Golden Spark) -->`	`Syntax not understood`
14	`<link rel="icon" type="image/svg+xml" href="data:image/svg+xml,%3Csvg xmlns='http://www.w3.org/2000/svg' viewBox='0 0 32 32'%3E%3Crect width='32' height='32' rx='8' fill='%23140e0b'/%3E%3Cpath d='M16 4 L18.5 13.5 L28 16 L18.5 18.5 L16 28 L13.5 18.5 L4 16 L13.5 13.5 Z' fill='%23D9B36A'/%3E%3Ccircle cx='16' cy='16' r='2' fill='%23fff'/%3E%3C/svg%3E" />`	`Unknown directive`
15	`<link rel="apple-touch-icon" href="data:image/svg+xml,%3Csvg xmlns='http://www.w3.org/2000/svg' viewBox='0 0 180 180'%3E%3Crect width='180' height='180' rx='40' fill='%23140e0b'/%3E%3Cpath d='M90 20 L105 75 L160 90 L105 105 L90 160 L75 105 L20 90 L75 75 Z' fill='%23D9B36A'/%3E%3Ccircle cx='90' cy='90' r='10' fill='%23ffffff'/%3E%3C/svg%3E" />`	`Unknown directive`
17	`<!-- Open Graph / Facebook / Telegram / WhatsApp -->`	`Syntax not understood`
18	`<meta property="og:type" content="website" />`	`Unknown directive`
19	`<meta property="og:url" content="https://candora-omega.vercel.app/" />`	`Unknown directive`
20	`<meta property="og:site_name" content="Candora Atelier" />`	`Unknown directive`
21	`<meta property="og:title" content="Candora — Haute Confectionery Atelier" />`	`Unknown directive`
22	`<meta property="og:description" content="Shirinlik emas. Bir lahza. Qo'lda tayyorlangan hashamatli desertlar, eksklyuziv to'y va bayram tortlari, fransuz makaronlari atelesi." />`	`Unknown directive`
23	`<meta property="og:image" content="https://images.unsplash.com/photo-1578985545062-69928b1d9587?w=1200&h=630&fit=crop&q=85" />`	`Unknown directive`
24	`<meta property="og:image:width" content="1200" />`	`Unknown directive`
25	`<meta property="og:image:height" content="630" />`	`Unknown directive`
26	`<meta property="og:image:alt" content="Candora Haute Confectionery Atelier" />`	`Unknown directive`
27	`<meta property="og:locale" content="uz_UZ" />`	`Unknown directive`
29	`<!-- Twitter Card -->`	`Syntax not understood`
30	`<meta name="twitter:card" content="summary_large_image" />`	`Unknown directive`
31	`<meta name="twitter:url" content="https://candora-omega.vercel.app/" />`	`Unknown directive`
32	`<meta name="twitter:title" content="Candora — Haute Confectionery Atelier" />`	`Unknown directive`
33	`<meta name="twitter:description" content="Shirinlik emas. Bir lahza. Qo'lda tayyorlangan hashamatli desertlar va eksklyuziv tortlar atelesi." />`	`Unknown directive`
34	`<meta name="twitter:image" content="https://images.unsplash.com/photo-1578985545062-69928b1d9587?w=1200&h=630&fit=crop&q=85" />`	`Unknown directive`
36	`<!-- Google Fonts -->`	`Syntax not understood`
37	`<link rel="preconnect" href="https://fonts.googleapis.com">`	`Unknown directive`
38	`<link rel="preconnect" href="https://fonts.gstatic.com" crossorigin>`	`Unknown directive`
39	`<link href="https://fonts.googleapis.com/css2?family=Playfair+Display:ital,wght@0,400..900;1,400..900&family=Plus+Jakarta+Sans:ital,wght@0,300..800;1,300..800&display=swap" rel="stylesheet">`	`Unknown directive`
40	`<style>html, body { height: 100%; margin: 0; } #root { height: 100%; }</style>`	`Unknown directive`
42	`<!-- Structured Data (JSON-LD schema.org) for Search Engines -->`	`Syntax not understood`
43	`<script type="application/ld+json">`	`Syntax not understood`
44	`{`	`Syntax not understood`
45	`"@context": "https://schema.org",`	`Unknown directive`
46	`"@graph": [`	`Unknown directive`
47	`{`	`Syntax not understood`
48	`"@type": "Bakery",`	`Unknown directive`
49	`"@id": "https://candora-omega.vercel.app/#bakery",`	`Unknown directive`
50	`"name": "Candora — Haute Confectionery Atelier",`	`Unknown directive`
51	`"url": "https://candora-omega.vercel.app",`	`Unknown directive`
52	`"logo": "https://images.unsplash.com/photo-1578985545062-69928b1d9587?w=500&h=500&fit=crop",`	`Unknown directive`
53	`"image": "https://images.unsplash.com/photo-1578985545062-69928b1d9587?w=1200&h=630&fit=crop&q=85",`	`Unknown directive`
54	`"description": "Toshkentdagi qo'lda tayyorlangan hashamatli shirinliklar, eksklyuziv to'y va bayram tortlari, fransuz makaronlari hamda artisan shokoladlar atelesi.",`	`Unknown directive`
55	`"telephone": "+998 91 099 99 50",`	`Unknown directive`
56	`"priceRange": "$$$$",`	`Unknown directive`
57	`"servesCuisine": "French Haute Confectionery, Artisan Cakes, Luxury Macarons, Belgian Chocolates",`	`Unknown directive`
58	`"address": {`	`Unknown directive`
59	`"@type": "PostalAddress",`	`Unknown directive`
60	`"streetAddress": "Amir Temur shoh ko'chasi",`	`Unknown directive`
61	`"addressLocality": "Toshkent",`	`Unknown directive`
62	`"addressRegion": "Toshkent shahri",`	`Unknown directive`
63	`"postalCode": "100000",`	`Unknown directive`
64	`"addressCountry": "UZ"`	`Unknown directive`
65	`},`	`Syntax not understood`
66	`"geo": {`	`Unknown directive`
67	`"@type": "GeoCoordinates",`	`Unknown directive`
68	`"latitude": 41.311081,`	`Unknown directive`
69	`"longitude": 69.240562`	`Unknown directive`
70	`},`	`Syntax not understood`
71	`"openingHoursSpecification": [`	`Unknown directive`
72	`{`	`Syntax not understood`
73	`"@type": "OpeningHoursSpecification",`	`Unknown directive`
74	`"dayOfWeek": ["Monday", "Tuesday", "Wednesday", "Thursday", "Friday", "Saturday", "Sunday"],`	`Unknown directive`
75	`"opens": "09:00",`	`Unknown directive`
76	`"closes": "22:00"`	`Unknown directive`
77	`}`	`Syntax not understood`
78	`],`	`Syntax not understood`
79	`"hasMenu": "https://candora-omega.vercel.app/#catalog"`	`Unknown directive`
80	`},`	`Syntax not understood`
81	`{`	`Syntax not understood`
82	`"@type": "WebSite",`	`Unknown directive`
83	`"@id": "https://candora-omega.vercel.app/#website",`	`Unknown directive`
84	`"url": "https://candora-omega.vercel.app",`	`Unknown directive`
85	`"name": "Candora Atelier",`	`Unknown directive`
86	`"description": "Shirinlik emas. Bir lahza. Haute Confectionery Atelier Toshkent",`	`Unknown directive`
87	`"inLanguage": "uz-UZ",`	`Unknown directive`
88	`"potentialAction": {`	`Unknown directive`
89	`"@type": "SearchAction",`	`Unknown directive`
90	`"target": "https://candora-omega.vercel.app/?search={search_term_string}",`	`Unknown directive`
91	`"query-input": "required name=search_term_string"`	`Unknown directive`
92	`}`	`Syntax not understood`
93	`}`	`Syntax not understood`
94	`]`	`Syntax not understood`
95	`}`	`Syntax not understood`
96	`</script>`	`Syntax not understood`
97	`<script type="module" crossorigin src="/assets/index-Dr_R8s02.js"></script>`	`Syntax not understood`
98	`<link rel="stylesheet" crossorigin href="/assets/index-BFJJyiZz.css">`	`Syntax not understood`
99	`</head>`	`Syntax not understood`
101	`<body>`	`Syntax not understood`
102	`<div id="root"></div>`	`Syntax not understood`
103	`</body>`	`Syntax not understood`
104	`</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`