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
tonmr.shop/public/style.css?v=1778858898	0.0 ms	27.7 KiB
/pagead/managed/js/adsense/m202605260101/show_ads_impl_fy...	1209600.0 s	172.8 KiB
tonmr.shop/uploads/2026/02/service_cover_f_20260207_143543_d61decb96cf0.webp	604800.0 s	82.8 KiB
tonmr.shop/uploads/settings/2026/05/banner_f_20260515_200941_ae6ec54ff58d.webp	604800.0 s	74.8 KiB
tonmr.shop/uploads/2026/02/service_cover_f_20260216_215500_4a0e8ef30624.webp	604800.0 s	64.6 KiB
tonmr.shop/uploads/2026/02/service_cover_f_20260205_045245_35fd4adeaf8b.webp	604800.0 s	63.8 KiB
tonmr.shop/public/assets/js/app-v4.js?v=1778531112	0.0 ms	6.1 KiB
tonmr.shop/uploads/2026/02/listing_f_20260215_201555_d030aa708758.webp	604800.0 s	51.4 KiB
tonmr.shop/public/assets/js/addictive-ui-v1.js?v=1769510210	0.0 ms	3.0 KiB
tonmr.shop/uploads/2026/02/listing_f_20260215_114214_ea6c64485053.webp	604800.0 s	26.0 KiB
/uploads/2026/05/thumbs/listing_extra_f_20260517_102319_8...	604800.0 s	25.9 KiB
tonmr.shop/public/js/image-auto-compress.js?v=1770339878	0.0 ms	2.5 KiB
/uploads/2026/05/thumbs/listing_extra_f_20260517_110040_d...	604800.0 s	24.2 KiB
tonmr.shop/public/assets/css/inline-v4.css?v=1778597220	0.0 ms	2.4 KiB
tonmr.shop/public/assets/js/lightbox-v6.js?v=1769335224	0.0 ms	1.9 KiB
tonmr.shop/public/assets/js/home-2026.js?v=1769344256	0.0 ms	1.9 KiB
tonmr.shop/public/assets/css/premium.css?v=1778400896	0.0 ms	1.7 KiB
tonmr.shop/uploads/2026/02/listing_f_20260218_143109_6258de65a970.webp	604800.0 s	15.8 KiB
tonmr.shop/uploads/2026/02/listing_f_20260215_115342_acc2c4346524.webp	604800.0 s	14.8 KiB
tonmr.shop/public/js/form-progress.js?v=1769805998	0.0 ms	1.2 KiB
tonmr.shop/public/assets/js/ga-init-v5.js?v=1769334606	0.0 ms	809 B
tonmr.shop/public/assets/js/consent-v7.js?v=1769334606	0.0 ms	789 B
tonmr.shop/public/assets/js/pwa-install-v1.js?v=1778858708	0.0 ms	691 B
/uploads/2026/02/thumbs/service_cover_f_20260223_130701_f...	604800.0 s	6.6 KiB
tonmr.shop/public/js/category-description.js?v=1769809078	0.0 ms	620 B
tonmr.shop/public/assets/js/helpers-v5.js?v=1769334606	0.0 ms	442 B
tonmr.shop/uploads/settings/2026/05/logo_f_20260515_174901_a7f5bfc1d2c7.webp	604800.0 s	4.1 KiB

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:60.588 source:map[column:23 line:35 type:source-location url:https://tonmr.shop/public/assets/js/addictive-ui-v1.js?v=1769510210 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
TONMR banner `body.is-home > div.site-banner > img`	tonmr.shop/uploads/settings/2026/05/banner_f_20260515_200941_ae6ec54ff58d.webp	74.6 KiB	50.2 KiB
Lunasoft.az – Peşəkar Proqram Təminatı və Rəqəmsal Xidmətlər `div.card-service > a.block > div.aspect-video > img.w-full`	tonmr.shop/uploads/2026/02/service_cover_f_20260207_143543_d61decb96cf0.webp	82.5 KiB	49.9 KiB
Veb sayt hazırlanması və texniki dəstək xidməti `div.card-service > a.block > div.aspect-video > img.w-full`	tonmr.shop/uploads/2026/02/service_cover_f_20260205_045245_35fd4adeaf8b.webp	63.5 KiB	39.2 KiB
Şəkildən Video və Mini Film Hazırlanması (Canlandırma) `div.card-service > a.block > div.aspect-video > img.w-full`	tonmr.shop/uploads/2026/02/service_cover_f_20260216_215500_4a0e8ef30624.webp	64.4 KiB	38.8 KiB
PUBG mobile konsolu `div.card-listing > a.block > div.card-listing-image > img.is-loaded`	tonmr.shop/uploads/2026/02/listing_f_20260215_201555_d030aa708758.webp	51.1 KiB	33.6 KiB
🌿 YENİ MODEL METAL YELLƏNCƏK 🌿 `div.card-listing > a.block > div.card-listing-image > img.is-loaded`	/uploads/2026/05/thumbs/listing_extra_f_20260517_102319_8...	25.7 KiB	13.5 KiB
🌿 YENİ MODEL BAĞ VƏ BALKON YELLƏNCƏYİ 🌿 `div.card-listing > a.block > div.card-listing-image > img.is-loaded`	/uploads/2026/05/thumbs/listing_extra_f_20260517_110040_d...	24.0 KiB	11.8 KiB

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: TONMR banner

path: 0,HTML,1,BODY,4,DIV,0,IMG

selector: body.is-home > div.site-banner > img

snippet: <img src="https://tonmr.shop/uploads/settings/2026/05/banner_f_20260515_200941_ae6ec…" alt="TONMR banner">

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

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
tonmr.shop/public/assets/css/inline-v4.css?v=1778597220	2.4 KiB	198 ms
tonmr.shop/public/style.css?v=1778858898	27.7 KiB	793 ms
tonmr.shop/public/assets/css/premium.css?v=1778400896	1.7 KiB

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
/npm/@phosphor-icons/web@2.1.2/src/duotone/Phosphor-Duoto...	5.0 ms
cdn.jsdelivr.net/npm/@phosphor-icons/web@2.1.2/src/regular/Phosphor.woff2	5.0 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

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: 200 ms 66.2 KiB

URL	Transfer Size	Est Savings
cdn.jsdelivr.net/npm/@phosphor-icons/web@2.1.2/src/duotone/style.css	22.1 KiB	21.9 KiB
tonmr.shop/public/style.css?v=1778858898	27.5 KiB	20.5 KiB
cdn.jsdelivr.net/npm/@phosphor-icons/web@2.1.2/src/light/style.css	11.9 KiB	11.9 KiB
cdn.jsdelivr.net/npm/@phosphor-icons/web@2.1.2/src/bold/style.css	11.9 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: 1.2 s 159.8 KiB

URL	Transfer Size	Est Savings
/pagead/managed/js/adsense/m202605260101/show_ads_impl_fy...	172.8 KiB	131.2 KiB
/pagead/js/adsbygoogle.js?client=pub-5577298515381191	53.9 KiB	28.5 KiB

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

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

URL	Transfer Size	Est Savings
tonmr.shop/public/style.css?v=1778858898	27.7 KiB	6.1 KiB
cdn.jsdelivr.net/npm/@phosphor-icons/web@2.1.2/src/duotone/style.css	22.2 KiB	3.2 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
TONMR `div.footer-grid > div.footer-col > a.logo > img.footer-logo-img`	tonmr.shop/uploads/settings/2026/05/logo_f_20260515_174901_a7f5bfc1d2c7.webp

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

●Max Potential First Input Delay 130 ms

●Layout shift culprits

●Document request latency

●Optimize DOM size

●LCP breakdown

●Modern HTTP

●Optimize viewport for mobile

●Minify JavaScript

●Avoids enormous network payloads Total size was 1,227 KiB

●JavaScript execution time 0.4 s

●Minimizes main-thread work 1.5 s

●Avoid long main-thread tasks 4 long tasks found

●Avoid non-composited animations 20 animated elements found

●Network Requests

●Network Round Trip Times 50 ms

●Server Backend Latencies 20 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 60 ms

●Avoid large layout shifts 1 layout shift found

○INP breakdown

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

ARIA

ARIA dialog elements without accessible names may prevent screen readers users from discerning the purpose of these elements. Learn how to make ARIA dialog elements more accessible.

Why this matters

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

Source: MDN Permissions-Policy

Failing Elements
✕‹› `body.is-home > div.tonmr-lightbox-overlay > div.tonmr-lightbox-modal`

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
header.navbar > div.container-custom > div.navbar-actions > button.mobile-nav-toggle `header.navbar > div.container-custom > div.navbar-actions > button.mobile-nav-toggle`

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
header.navbar > div.container-custom > div.navbar-actions > a.p-2 `header.navbar > div.container-custom > div.navbar-actions > a.p-2`

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.

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
Abunə ol `div.footer-col > div.newsletter-premium > form#newsletter-form > button`
© 2026 TONMR. Bütün hüquqlar qorunur. `footer.premium-footer > div.container > div.footer-bottom > p`
Qəbul edirəm `div#cookie-consent-banner > div.cc-wrap > div.cc-actions > button`

These are opportunities to improve the legibility of your content.

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
✕ `body.is-home > div.tonmr-lightbox-overlay > div.tonmr-lightbox-modal > button.tonmr-lightbox-close`
‹ `body.is-home > div.tonmr-lightbox-overlay > div.tonmr-lightbox-modal > button.tonmr-lightbox-prev`
› `body.is-home > div.tonmr-lightbox-overlay > div.tonmr-lightbox-modal > button.tonmr-lightbox-next`

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
Tətbiqi yüklə `body.is-home > div.mobile-menu > button.btn-secondary`

○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

●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

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

●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).

●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

●Deprecated ARIA roles were not used

●Identical links have the same purpose.

○`[accesskey]` values are unique

○`button`, `link`, and `menuitem` elements 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.

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

○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

Browser Compatibility

Specifying a doctype prevents the browser from switching to quirks-mode. Learn more about the doctype declaration.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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
tonmr.shop/	`The Content Security Policy directive 'upgrade-insecure-requests' is ignored when delivered in a report-only policy.`
/pagead/managed/js/adsense/m202605260101/show_ads_impl_fy... line 713, col 1920	`The Content Security Policy directive 'upgrade-insecure-requests' is ignored when delivered in a report-only policy.`
/pagead/managed/js/adsense/m202605260101/show_ads_impl_fy... line 786, col 745	`The Content Security Policy directive 'upgrade-insecure-requests' is ignored when delivered in a report-only policy.`
ep2.adtrafficquality.google/sodar/sodar2.js line 30, col 245	`The Content Security Policy directive 'upgrade-insecure-requests' is ignored when delivered in a report-only 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

●Properly defines charset

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