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.

Your first network request is the most important. Reduce its latency by avoiding redirects, ensuring a fast server response, and enabling text compression.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

value: no origins were preconnected

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

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
mc.yandex.ru/metrika/tag.js	3600.0 s	85.1 KiB
mc.yandex.com/metrika/advert.gif?t=gdpr(14)ti(4)	3600.0 s	409 B
/sync_cookie_image_decide_secondary?cid=25327145&scid=94f...	0.0 ms	267 B
disk.2gis.com/rubricator/groceryb92f2cf09392e989ec78e9026c3f8a1f.svg	604800.0 s	1.2 KiB
disk.2gis.com/rubricator/goods54885a80ce4819a89378601544764fe1.svg	604800.0 s	1.1 KiB
disk.2gis.com/rubricator/eat594ef1a575533c3c1b558ee032dad50c.svg	604800.0 s	1.1 KiB
/sync_cookie_image_decide?cid=25327145&scid=fc8b6859-1433...	0.0 ms	79 B
/sync_cookie_image_decide?cid=25327145&scid=4414264b-b26e...	0.0 ms	70 B

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.

Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 1.3 s

URL	Time Spent
2gis.com/	1.3 s
2gis.ae/	0.0 ms

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: 300 ms 1.3 MiB

URL	Transfer Size	Est Savings
d-assets.2gis.ru/app.2e8768b4ddad7bc68b2e.js	1.1 MiB	886.3 KiB
d-assets.2gis.ru/rarity.54c06eac54e71c325094.js	364.7 KiB	228.0 KiB
www.googletagmanager.com/gtag/js?id=G-WBWHTEG07F	160.3 KiB	66.5 KiB
d-assets.2gis.ru/vendor.84c807e27de31298c2c0.js	66.2 KiB	50.3 KiB
mc.yandex.ru/metrika/tag.js	84.5 KiB	49.5 KiB
d-assets.2gis.ru/react.73aed46cec595fcc5c25.js	65.4 KiB	25.3 KiB

Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to reduce Javascript execution time.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Total CPU Time	Script Evaluation	Script Parse
d-assets.2gis.ru/app.2e8768b4ddad7bc68b2e.js	70.0 s	867 ms	392 ms
d-assets.2gis.ru/rarity.54c06eac54e71c325094.js	8.5 s	8.1 s	232 ms
Unattributable	2.9 s	1.2 s	0.0 ms
d-assets.2gis.ru/core.5b88348a8d69b31f9f2c.js	1.4 s	1.4 s	18 ms
d-assets.2gis.ru/react.73aed46cec595fcc5c25.js	640 ms	586 ms	25 ms
2gis.ae/	542 ms	196 ms	67 ms
d-assets.2gis.ru/map3d.e5b25ddeca605c1e7a93.js	488 ms	487 ms	0.6 ms
mc.yandex.ru/metrika/tag.js	364 ms	306 ms	33 ms
d-assets.2gis.ru/jquery-1.3.2.50af6a12b468a1d91600.js	300 ms	198 ms	11 ms
www.googletagmanager.com/gtag/js?id=G-WBWHTEG07F	192 ms	112 ms	60 ms
d-assets.2gis.ru/en-po.11dffd054200ab933d0b.js	80 ms	59 ms	21 ms

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	70.3 s
Script Evaluation	14.2 s
Script Parsing & Compilation	922 ms
Garbage Collection	425 ms
Parse HTML & CSS	125 ms
Style & Layout	121 ms
Rendering	107 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
The page has an unload handler in the main frame.	Actionable
Pages with cache-control:no-store header cannot enter back/forward cache.	Actionable
Pages with WebSocket cannot enter back/forward cache.	Pending browser support
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
Back/forward cache is disabled because WebSocket has been used.	Not actionable

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 7.0 KiB

URL	Transfer Size	Est Savings
d-assets.2gis.ru/afScript/script.js	17.5 KiB	7.0 KiB

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
d-assets.2gis.ru/app.2e8768b4ddad7bc68b2e.js	1.1 MiB
/vt?r=CggInQUQygQYCg%3D%3D&ts=vector_a&key=10153539-2026-...	433.0 KiB
/vt?r=CggInQUQygQYCg%3D%3D&ts=vector_a&key=10153539-2026-...	432.5 KiB
d-assets.2gis.ru/rarity.54c06eac54e71c325094.js	365.2 KiB
/styles/assets/icons/forest_texture-da0093b7eb7624ad1690f...	197.1 KiB
favorites.api.2gis.ru/2.0/public/sync	188.2 KiB
/vt?r=CggInQUQyQQYCg%3D%3D&ts=vector_a&key=10153539-2026-...	163.4 KiB
/vt?r=CggInQUQyQQYCg%3D%3D&ts=vector_a&key=10153539-2026-...	163.4 KiB
www.googletagmanager.com/gtag/js?id=G-WBWHTEG07F	160.7 KiB
/vt?r=CggInAUQyQQYCg%3D%3D&ts=vector_a&key=10153539-2026-...	146.8 KiB

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

●Layout shift culprits

●Optimize DOM size

●Font display

●Forced reflow

●Improve image delivery

●LCP breakdown

●Modern HTTP

●Render blocking requests

●Optimize viewport for mobile

●Minify CSS

●Reduce unused CSS

●User Timing marks and measures 15 user timings

●Avoid long main-thread tasks 20 long tasks found

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

●Network Requests

●Network Round Trip Times 170 ms

●Server Backend Latencies 710 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

●Initial server response time was short Root document took 330 ms

●Avoid large layout shifts 1 layout shift found

○INP breakdown

○LCP request discovery

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

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
My location `div._47hinf > div._rz58lf5 > div._1abq30r9 > div._m7vswb`

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.

Names and labels

When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
form > div._11i5b2y > div._1uw08vz > button._1rno74z `form > div._11i5b2y > div._1uw08vz > button._1rno74z`
div._rz58lf5 > div._1abq30r9 > div._m7vswb > button._wutyzg `div._rz58lf5 > div._1abq30r9 > div._m7vswb > button._wutyzg`

Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div._gor68n > div._1sizveq > div._5zlfoj > a._krkgna `div._gor68n > div._1sizveq > div._5zlfoj > a._krkgna`

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

Best practices

Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a web page. Learn more about the viewport meta tag.

Why this matters

Informational: a Permissions-Policy directive showing feature -> allowed origins.

Source: MDN Permissions-Policy

Failing Elements
head > meta `head > meta`

These items highlight common accessibility best practices.

○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

●Image elements have `[alt]` attributes

●Form elements have associated labels

●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

●No element has a `[tabindex]` value greater than 0

●Touch targets have sufficient size and spacing.

●Document has a main landmark.

●The page contains a heading, skip link, or landmark region

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

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

○Heading elements appear in a sequentially-descending order

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

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

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

Best Practices

General

Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Deprecation / Warning	Source
Unload event listeners are deprecated and will be removed.	2gis.ae/dubai line 232, col 11

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
d-assets.2gis.ru/rarity.54c06eac54e71c325094.js	`Error: [RTL Plugin]: loading failed. Failed to fetch at https://d-assets.2gis.ru/rarity.54c06eac54e71c325094.js:1:799974`
mapgl.2gis.com/api/js/plugins/rtl-v1.1.1.js	`Failed to load resource: net::ERR_TIMED_OUT`
2gis.ae/dubai	`SecurityError: Failed to register a ServiceWorker for scope ('https://2gis.ae/') with script ('https://2gis.ae/public/service-worker.js'): The script resource is behind a redirect, which is disallowed.`
	`The script resource is behind a redirect, which is disallowed.`

●Uses HTTPS

●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 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 DOM-based XSS with Trusted Types

●Page has valid source maps

○Redirects HTTP traffic to HTTPS

○Mitigate clickjacking with XFO or CSP

○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
law.2gis.ae/privacy/cookie	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.

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`