Name: Website audit: https://лимаркет.рф
Creator: BeaverCheck
License: https://beavercheck.com/methodology

Site Health

Score: 81 / 100

Based on 8 categories, 0 sections

Fast site — your users get a smooth experience.

Good foundation, but a few gaps could be exploited.

Mostly accessible, but some users still face barriers.

Solid SEO basics — a few optimizations could boost rankings.

Infrastructure issues create a speed ceiling frontend fixes can't overcome.

Strong compliance posture across regulations.

Good content signals with minor gaps.

Reasonable footprint with room for optimization.

How is this calculated?

The overall score is a weighted average of individual category scores. Categories with more impact on user experience and security carry more weight.

Performance 25%Security 25%Accessibility 15%SEO 10%Infrastructure 10%Compliance 8%Content 5%Sustainability 2%

Weights reflect general web best practices. Individual needs may differ.

How the composite score is calculated

How you compare

Bootstrap · 825 peers

You 81

Avg 73

+8 above average

0 50 100

Better than 96% of Bootstrap sites See full Bootstrap benchmark →

Bootstrap Icons · 28 peers

You 81

Avg 72

+9 above average

0 50 100

Better than 92% of Bootstrap Icons sites See full Bootstrap Icons benchmark →

Top Priorities (5)

'unsafe-inline' found in script source

Security gaps expose your site and users to attacks, eroding trust.

Security › Content Security Policy

6 button(s) with no accessible text

Accessibility issues exclude users with disabilities — up to 15% of your potential audience.

Accessibility › Link & Button Quality

Cross-Origin-Embedder-Policy header is missing

Security gaps expose your site and users to attacks, eroding trust.

Security › Security Headers

Images are 1.2 MB — compress or use modern formats

Performance issues directly impact user engagement and conversion rates.

Performance › Page Weight Budget

No DMARC record found

Without DMARC, anyone can send phishing emails using your domain name.

Security › Email Security

View fix priority matrix

Fix Priority Matrix

5 findings

Impact

Quick Wins

High impact, low effort — start here.

Strategic

High impact, requires investment.

Easy Improvements

Small gains, minimal effort.

Nothing in this quadrant — good news.

Deprioritize

Low impact, high effort — do last.

Nothing in this quadrant — good news.

← Low effort High effort →

Embed this badge

Markdown

[![BeaverCheck](https://beavercheck.com/badge?url=https%3A%2F%2F%D0%BB%D0%B8%D0%BC%D0%B0%D1%80%D0%BA%D0%B5%D1%82.%D1%80%D1%84)](https://beavercheck.com/results/36744aa0-4be8-4eb4-95f8-c8df29c9ffe7)

HTML

<a href="https://beavercheck.com/results/36744aa0-4be8-4eb4-95f8-c8df29c9ffe7"><img src="https://beavercheck.com/badge?url=https%3A%2F%2F%D0%BB%D0%B8%D0%BC%D0%B0%D1%80%D0%BA%D0%B5%D1%82.%D1%80%D1%84" alt="BeaverCheck Score"></a>

Image URL

https://beavercheck.com/badge?url=https%3A%2F%2F%D0%BB%D0%B8%D0%BC%D0%B0%D1%80%D0%BA%D0%B5%D1%82.%D1%80%D1%84

This badge auto-updates with your latest scan result.

What fixing these means

Your site performs reasonably well, but a few targeted fixes could meaningfully improve results. Your LCP of 5.5s exceeds Google's 2.5s 'Good' threshold and the 1 performance issue below directly contributes to it. Addressing the critical issues below would have the most immediate impact on your user trust.

3 security gaps detected — browsers may warn visitors about your site.

1 accessibility issue excludes users who rely on assistive technology.

Your LCP is 5.5s — fixing the 1 performance critical could bring it under Google's 2.5s 'Good' threshold.

Conversion Barriers

1 critical 4 warning

5 barrier(s) likely increasing bounce by ~23%.

Speed (1)

Page takes 5.5s to load

+12% bounce

Users abandon at ~3s — you're 3.0s over the 2.5s threshold

Fix: Optimize render-blocking resources, preload the hero image, and compress images

Trust (1)

No Content-Security-Policy header

+1% bounce

Higher XSS blast radius — one compromised script can exfiltrate the checkout form

Fix: Ship a reporting-only CSP first, then enforce once violations are clean

Content (2)

No structured data

+2% bounce

No rich-result eligibility in Google — lower SERP CTR vs competitors with stars and prices

Fix: Add JSON-LD for your page type (Product, Article, FAQPage, LocalBusiness, …)

Thin content

+3% bounce

Under 300 words — visitors bounce looking for substance, search engines rank competitors first

Fix: Add a substantive FAQ, product detail, or case-study section

Navigation (1)

No skip-to-content link

+1% bounce

Keyboard and screen-reader users must tab through the entire header on every page

Fix: Add a visible-on-focus <a href="#main">Skip to content</a> as the first focusable element

Preliminary CRO audit — each barrier links to the tab with detailed analysis.

Return on Investment

€468 investment → €2,701/month returns + EUR 500,000 risk avoided

Payback period: < 1 month First-year ROI: +6833%

Investment

€468

6h · 5 findings

Monthly returns

€2,701 /mo

~€32,410 / year

Conversions recovered €2,700
Bandwidth savings €0.41

Regulatory risk avoided

EUR 500,000

if kept compliant

EAA EUR 500,000

Payback period

0 12mo 24mo

€85 — in quick wins — start here for the fastest payback

Figures combine localized regulatory fine ceilings, search/conversion value priced against local CPC, and bandwidth waste estimates. Results depend on implementation quality and audience composition. Not legal or financial advice.

Full methodology & sources

Estimated Remediation Cost

€468

5.5 developer hours at €85/hr

Based on European Union rates (€85/hr)

Quick wins

€85 2 fixes in ~60 minutes

Start here for the best return on investment

Cost by category

Cost by effort level

Adjust assumptions

Custom rate

€ /hr

Rates reflect fully-loaded developer cost including overhead

How developer rates are sourced

What Inaction Is Costing You

€41,667 / month at risk

~€500,005 / year if left unfixed

Compliance Risk

€500,000

EAA

1 of 2 <nav> elements are unlabeled
EAA: EUR 1,000 – EUR 500,000
Skip navigation link is missing (WCAG 2.4.1)
EAA: EUR 1,000 – EUR 500,000
Heading level skipped: H2 → H6 (missing H3)
EAA: EUR 1,000 – EUR 500,000

Bandwidth Waste

€0.41 /mo

5596.3 MB/mo × 0.074 EUR/GB

Optimize transfer: save ~560 KB per page load
Saves €0.41/mo

Compliance figures represent the statutory maximum fine for the most severe triggered category, capped per regulation — not the sum of per-finding penalties. Based on published regulatory fine ranges. This is not legal advice.

Compliance methodology · SEO assumptions · Bandwidth model

Your performance is already good — improvements may show diminishing returns

Monthly visitors

Unique monthly visitors from your analytics

Conversion rate (%)

Purchases, signups, or key actions

Avg. order value

Optional — for revenue estimation

additional conversions/month

more engaged visitors from reduced bounce

potential monthly revenue

Current bounce (est.)

After fixes (est.)

Estimated bounce reduction

Fix 2 critical issues to capture this value

How this is calculated

Based on Google/Deloitte research ("Milliseconds Make Millions") showing a ~7% bounce rate increase per additional second of LCP above the 2.5s "Good" threshold.

Your site's LCP: → estimated after fixes.

These are estimates based on industry research — actual results vary

Bounce-rate model & assumptions

Your data stays in your browser — nothing is sent to our servers

Was this report useful?

Thanks for your feedback!

Global Performance 6/6 locations ✓

SG Singapore

Full audit

1330ms

DNS 651ms · TLS 205ms

NL Amsterdam

397ms

DNS 115ms · TLS 48ms

UN New York

741ms

DNS 244ms · TLS 119ms

ES Madrid

412ms

DNS 146ms · TLS 70ms

US Santa Clara

1068ms

DNS 441ms · TLS 193ms

BR Sao Paulo

1504ms

DNS 726ms · TLS 248ms

CDN: No CDN · Avg TTFB: 909ms · Cache: No cache headers

We'll use a cached audit if available, or offer to scan.

Checking for existing audit...

Press ? for shortcuts

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse.

Performance

Accessibility

Best Practices

100

SEO

Core Web Vitals

Key metrics that affect user experience.

First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.

3.45 s

Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.

5.48 s

Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.

0 ms

Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.

0.000

Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.

4.68 s

Time to Interactive Time to Interactive — how long until the page is fully interactive and responds to user input. Under 3.8s is good.

5.49 s

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

Shipping ES5 transpiled code to modern browsers wastes bytes — every user with an evergreen browser pays for compatibility you don't need.

Learn more ▾

Most users today run browsers that natively support ES6+, async/await, optional chaining, and the rest of modern JavaScript. Transpiling to ES5 'just in case' adds 20-40% to your bundle for no benefit. Configure your build to target a modern browserslist, or ship a differential bundle pair (modern + legacy) with the module/nomodule pattern.

Source: Google web.dev / Lighthouse

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.

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
/static/vendor/bootstrap-icons/font/fonts/bootstrap-icons...	595 ms

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:36.831 source:map[type:text value:[unattributed]]]]

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
Куртка зимняя женская `div.col-6 > div.card > div.position-relative > img.card-img-top`	xn--80akhjch3as.xn--p1ai/media/products/2026/04/6893259915.jpg	784.5 KiB	761.5 KiB
Тёплый войлок `div.col-6 > div.card > div.position-relative > img.card-img-top`	xn--80akhjch3as.xn--p1ai/media/products/2026/04/1.webp	174.0 KiB	151.0 KiB
LI Маркет `body > main.container > div.hero-section > img.hero-banner-img`	xn--80akhjch3as.xn--p1ai/static/img/hero-banner.c85bba9aa466.jpg	129.3 KiB	97.9 KiB
Дорада Лодка, 260 см `div.col-6 > div.card > div.position-relative > img.card-img-top`	xn--80akhjch3as.xn--p1ai/media/products/2026/04/photo_5384476787213459205_y.webp	92.6 KiB	72.3 KiB
Блузка нарядная леопардовая `div.col-6 > div.card > div.position-relative > img.card-img-top`	/media/products/2026/04/блузка_белая_2.webp	40.9 KiB	30.7 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-2-IMG

nodeLabel: LI Маркет

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

selector: body > main.container > div.hero-section > img.hero-banner-img

snippet: <img src="/static/img/hero-banner.c85bba9aa466.jpg" alt="LI Маркет" class="hero-banner-img" loading="eager" onerror="this.style.display='none'; this.parentElement.classList.add('hero-no-img');">

HTTP/2 and HTTP/3 offer many benefits over HTTP/1.1, such as multiplexing. Learn more about using modern HTTP.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Protocol
xn--80akhjch3as.xn--p1ai/	http/1.1
/static/vendor/bootstrap/css/bootstrap.min.38ba4e3f15ed.css	http/1.1
/static/vendor/bootstrap-icons/font/bootstrap-icons.bfa6e...	http/1.1
xn--80akhjch3as.xn--p1ai/static/css/style.d1f1670bf430.css	http/1.1
xn--80akhjch3as.xn--p1ai/static/css/components.147ba0aad865.css	http/1.1
xn--80akhjch3as.xn--p1ai/static/img/hero-banner.c85bba9aa466.jpg	http/1.1
/static/vendor/bootstrap/js/bootstrap.bundle.min.6196d53d...	http/1.1
xn--80akhjch3as.xn--p1ai/static/js/main.74fc091e21c0.js	http/1.1
xn--80akhjch3as.xn--p1ai/static/manifest.7514c1b0e83a.json	http/1.1
/static/vendor/bootstrap-icons/font/fonts/bootstrap-icons...	http/1.1
xn--80akhjch3as.xn--p1ai/media/products/2026/04/photo_5384476787213459205_y.webp	http/1.1
xn--80akhjch3as.xn--p1ai/media/products/2026/04/6893259915.jpg	http/1.1
/media/products/2026/04/блузка_белая_2.webp	http/1.1
xn--80akhjch3as.xn--p1ai/media/products/2026/04/1.webp	http/1.1
xn--80akhjch3as.xn--p1ai/static/css/style.css	http/1.1
xn--80akhjch3as.xn--p1ai/static/css/components.css	http/1.1
xn--80akhjch3as.xn--p1ai/static/js/main.js	http/1.1
xn--80akhjch3as.xn--p1ai/static/img/favicon.svg	http/1.1
xn--80akhjch3as.xn--p1ai/static/img/pwa/icon-192.png	http/1.1
xn--80akhjch3as.xn--p1ai/static/img/pwa/icon-512.png	http/1.1
xn--80akhjch3as.xn--p1ai/static/img/favicon.978725d6fa6b.svg	http/1.1

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

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
/static/vendor/bootstrap/css/bootstrap.min.38ba4e3f15ed.css	227.7 KiB	2.4 s
xn--80akhjch3as.xn--p1ai/static/css/style.d1f1670bf430.css	30.8 KiB	907 ms
/static/vendor/bootstrap-icons/font/bootstrap-icons.bfa6e...	96.3 KiB	1.7 s
xn--80akhjch3as.xn--p1ai/static/css/components.147ba0aad865.css	9.4 KiB	607 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

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: 150 ms 21.7 KiB

URL	Transfer Size	Est Savings
/static/vendor/bootstrap-icons/font/bootstrap-icons.bfa6e...	96.3 KiB	10.1 KiB
xn--80akhjch3as.xn--p1ai/static/css/style.d1f1670bf430.css	30.8 KiB	8.9 KiB
xn--80akhjch3as.xn--p1ai/static/css/components.147ba0aad865.css	9.4 KiB	2.7 KiB

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: 1.8 s 326.5 KiB

URL	Transfer Size	Est Savings
/static/vendor/bootstrap/css/bootstrap.min.38ba4e3f15ed.css	227.4 KiB	212.9 KiB
/static/vendor/bootstrap-icons/font/bootstrap-icons.bfa6e...	96.0 KiB	95.3 KiB
xn--80akhjch3as.xn--p1ai/static/css/style.d1f1670bf430.css	30.5 KiB	18.4 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

Multi-megabyte JavaScript bundles delay every interactive feature on the page.

Learn more ▾

This is the Lighthouse audit fired when too much JS is shipped relative to what executes. The fix isn't a config flag — it requires bundle analysis (webpack-bundle-analyzer, rollup-plugin-visualizer), splitting routes into chunks, lazy-loading off-screen components, and removing unused dependencies. Fundamentally different from minification: minifying reduces byte count, this reduces what's downloaded at all.

Source: Google web.dev / Lighthouse

Estimated savings: 450 ms 65.9 KiB

URL	Transfer Size	Est Savings
/static/vendor/bootstrap/js/bootstrap.bundle.min.6196d53d...	78.5 KiB	65.9 KiB

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

URL	Transfer Size	Est Savings
xn--80akhjch3as.xn--p1ai/static/js/main.74fc091e21c0.js	18.5 KiB	6.1 KiB

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

●Use efficient cache lifetimes

●Layout shift culprits

●Document request latency

●Optimize DOM size

●LCP breakdown

●Optimize viewport for mobile

●Max Potential First Input Delay 20 ms

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

●JavaScript execution time 0.0 s

●Minimizes main-thread work 1.0 s

●Avoid long main-thread tasks 3 long tasks found

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

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 200 ms

●Server Backend Latencies 0 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 250 ms

●Avoid large layout shifts 1 layout shift found

○INP breakdown

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

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
body > nav.navbar > div.container > button.navbar-toggler `body > nav.navbar > div.container > button.navbar-toggler`

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
LI Маркет `body > nav.navbar > div.container > a.navbar-brand`
12500 ₽ `div.card-body > div.mt-auto > div.d-flex > span.fw-bold`
6000 ₽ `div.card-body > div.mt-auto > div.d-flex > span.fw-bold`
1200 ₽ `div.card-body > div.mt-auto > div.d-flex > span.fw-bold`
400 ₽ `div.card-body > div.mt-auto > div.d-flex > span.fw-bold`
Осталось 1 шт. `div.card > div.card-body > div.mt-auto > span.badge`
Главная `body > nav.mobile-bottom-nav > a.mbn-item > span`
Каталог товаров села Иглино. Находите товары и связывайтесь с продавцами напрям… `div.container > div.row > div.col-md-4 > p.text-white-50`
с. Иглино, Республика Башкортостан `div.container > div.row > div.col-md-4 > p.text-white-50`
LI Маркет — информационный каталог. Сделки совершаются напрямую между покупател… `body > footer.mt-5 > div.container > p.text-center`
© 2026 LI Маркет. Все права защищены. `body > footer.mt-5 > div.container > p.text-center`

These are opportunities to improve the legibility of your content.

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
Дорада Лодка, 260 см `div.col-6 > div.card > div.card-body > h6.card-title`

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
Главная `div.col-md-4 > ul.list-unstyled > li > a`
Каталог `div.col-md-4 > ul.list-unstyled > li > a`
Избранное `div.col-md-4 > ul.list-unstyled > li > a`
О проекте `div.col-md-4 > ul.list-unstyled > li > a`
Условия использования `div.col-md-4 > ul.list-unstyled > li > a`
Политика конфиденциальности `div.col-md-4 > ul.list-unstyled > li > a`

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

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

●Document has a main landmark.

●Identical links have the same purpose.

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

○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

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
xn--80akhjch3as.xn--p1ai/	`Loading the stylesheet 'https://fonts.googleapis.com/css2?family=Inter:wght@300;400;500;600;700;800&display=swap' violates the following Content Security Policy directive: "style-src 'self' 'unsafe-inline'". Note that 'style-src-elem' was not explicitly set, so 'style-src' is used as a fallback. The action has been blocked.`

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

●Mitigate DOM-based XSS with Trusted Types

●Page has valid source maps

○Redirects HTTP traffic to HTTPS

○Use a strong HSTS policy

○Ensure proper origin isolation with COOP

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

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse. — Desktop

Performance

Accessibility

Best Practices

100

SEO

Core Web Vitals

Key metrics that affect user experience. — Desktop

First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.

726 ms

Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.

1.05 s

Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.

0 ms

Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.

0.000

Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.

1.85 s

Time to Interactive Time to Interactive — how long until the page is fully interactive and responds to user input. Under 3.8s is good.

1.05 s

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.

Why this matters

Shipping ES5 transpiled code to modern browsers wastes bytes — every user with an evergreen browser pays for compatibility you don't need.

Learn more ▾

Source: Google web.dev / Lighthouse

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.

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
/static/vendor/bootstrap-icons/font/fonts/bootstrap-icons...	610 ms

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:33.885 source:map[type:text value:[unattributed]]]]

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
Куртка зимняя женская `div.col-6 > div.card > div.position-relative > img.card-img-top`	xn--80akhjch3as.xn--p1ai/media/products/2026/04/6893259915.jpg	784.5 KiB	769.1 KiB
Тёплый войлок `div.col-6 > div.card > div.position-relative > img.card-img-top`	xn--80akhjch3as.xn--p1ai/media/products/2026/04/1.webp	174.0 KiB	158.5 KiB
Дорада Лодка, 260 см `div.col-6 > div.card > div.position-relative > img.card-img-top`	xn--80akhjch3as.xn--p1ai/media/products/2026/04/photo_5384476787213459205_y.webp	92.6 KiB	79.8 KiB
LI Маркет `body > main.container > div.hero-section > img.hero-banner-img`	xn--80akhjch3as.xn--p1ai/static/img/hero-banner.c85bba9aa466.jpg	129.3 KiB	56.9 KiB
Блузка нарядная леопардовая `div.col-6 > div.card > div.position-relative > img.card-img-top`	/media/products/2026/04/блузка_белая_2.webp	40.9 KiB	34.5 KiB

Each subpart has specific improvement strategies. Ideally, most of the LCP time should be spent on loading the resources, not within delays.

Why this matters

Performance issues directly impact user engagement and conversion rates.

headings: [map[key:label label:Subpart valueType:text] map[key:duration label:Duration valueType:ms]]

items: [map[duration:1355.787 label:Time to first byte subpart:timeToFirstByte] map[duration:24.328 label:Resource load delay subpart:resourceLoadDelay] map[duration:1263.032 label:Resource load duration subpart:resourceLoadDuration] map[duration:75.689 label:Element render delay subpart:elementRenderDelay]]

lhId: page-3-IMG

nodeLabel: LI Маркет

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

selector: body > main.container > div.hero-section > img.hero-banner-img

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-3-IMG

nodeLabel: LI Маркет

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

selector: body > main.container > div.hero-section > img.hero-banner-img

HTTP/2 and HTTP/3 offer many benefits over HTTP/1.1, such as multiplexing. Learn more about using modern HTTP.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Protocol
xn--80akhjch3as.xn--p1ai/	http/1.1
/static/vendor/bootstrap/css/bootstrap.min.38ba4e3f15ed.css	http/1.1
/static/vendor/bootstrap-icons/font/bootstrap-icons.bfa6e...	http/1.1
xn--80akhjch3as.xn--p1ai/static/css/style.d1f1670bf430.css	http/1.1
xn--80akhjch3as.xn--p1ai/static/css/components.147ba0aad865.css	http/1.1
xn--80akhjch3as.xn--p1ai/static/img/hero-banner.c85bba9aa466.jpg	http/1.1
/static/vendor/bootstrap/js/bootstrap.bundle.min.6196d53d...	http/1.1
xn--80akhjch3as.xn--p1ai/static/js/main.74fc091e21c0.js	http/1.1
xn--80akhjch3as.xn--p1ai/static/manifest.7514c1b0e83a.json	http/1.1
/static/vendor/bootstrap-icons/font/fonts/bootstrap-icons...	http/1.1
xn--80akhjch3as.xn--p1ai/media/products/2026/04/photo_5384476787213459205_y.webp	http/1.1
xn--80akhjch3as.xn--p1ai/media/products/2026/04/6893259915.jpg	http/1.1
/media/products/2026/04/блузка_белая_2.webp	http/1.1
xn--80akhjch3as.xn--p1ai/media/products/2026/04/1.webp	http/1.1
xn--80akhjch3as.xn--p1ai/static/css/style.css	http/1.1
xn--80akhjch3as.xn--p1ai/static/css/components.css	http/1.1
xn--80akhjch3as.xn--p1ai/static/js/main.js	http/1.1
xn--80akhjch3as.xn--p1ai/static/img/favicon.svg	http/1.1
xn--80akhjch3as.xn--p1ai/static/img/pwa/icon-192.png	http/1.1
xn--80akhjch3as.xn--p1ai/static/img/pwa/icon-512.png	http/1.1
xn--80akhjch3as.xn--p1ai/static/img/favicon.978725d6fa6b.svg	http/1.1

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.

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

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
/static/vendor/bootstrap/css/bootstrap.min.38ba4e3f15ed.css	227.7 KiB	447 ms
xn--80akhjch3as.xn--p1ai/static/css/style.d1f1670bf430.css	30.8 KiB	207 ms
/static/vendor/bootstrap-icons/font/bootstrap-icons.bfa6e...	96.3 KiB	327 ms
xn--80akhjch3as.xn--p1ai/static/css/components.147ba0aad865.css	9.4 KiB	127 ms

These insights are also available in the Chrome DevTools Performance Panel - record a trace to view more detailed information.

Diagnostics

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: 40 ms 21.7 KiB

URL	Transfer Size	Est Savings
/static/vendor/bootstrap-icons/font/bootstrap-icons.bfa6e...	96.3 KiB	10.1 KiB
xn--80akhjch3as.xn--p1ai/static/css/style.d1f1670bf430.css	30.8 KiB	8.9 KiB
xn--80akhjch3as.xn--p1ai/static/css/components.147ba0aad865.css	9.4 KiB	2.7 KiB

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: 280 ms 326.8 KiB

URL	Transfer Size	Est Savings
/static/vendor/bootstrap/css/bootstrap.min.38ba4e3f15ed.css	227.4 KiB	209.0 KiB
/static/vendor/bootstrap-icons/font/bootstrap-icons.bfa6e...	96.0 KiB	95.3 KiB
xn--80akhjch3as.xn--p1ai/static/css/style.d1f1670bf430.css	30.5 KiB	22.5 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

Multi-megabyte JavaScript bundles delay every interactive feature on the page.

Learn more ▾

Source: Google web.dev / Lighthouse

Estimated savings: 40 ms 65.9 KiB

URL	Transfer Size	Est Savings
/static/vendor/bootstrap/js/bootstrap.bundle.min.6196d53d...	78.5 KiB	65.9 KiB

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

URL	Transfer Size	Est Savings
xn--80akhjch3as.xn--p1ai/static/js/main.74fc091e21c0.js	18.5 KiB	6.1 KiB

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

●Use efficient cache lifetimes

●Layout shift culprits

●Document request latency

●Optimize DOM size

●Optimize viewport for mobile

●Time to Interactive 1.0 s

●Max Potential First Input Delay 20 ms

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

●JavaScript execution time 0.0 s

●Minimizes main-thread work 0.3 s

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

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 200 ms

●Server Backend Latencies 0 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 260 ms

●Avoid large layout shifts 1 layout shift found

○INP breakdown

○User Timing marks and measures

○Avoid long main-thread tasks

○Avoid non-composited animations

Accessibility

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
div#navbarNav > form#searchForm > div.input-group > button.btn `div#navbarNav > form#searchForm > div.input-group > button.btn`

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#navbarNav > ul.navbar-nav > li.nav-item > a.nav-link `div#navbarNav > ul.navbar-nav > li.nav-item > a.nav-link`

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
LI Маркет `body > nav.navbar > div.container > a.navbar-brand`
Каталог `div#navbarNav > ul.navbar-nav > li.nav-item > a.nav-link`
Войти `div#navbarNav > ul.navbar-nav > li.nav-item > a.nav-link`
12500 ₽ `div.card-body > div.mt-auto > div.d-flex > span.fw-bold`
6000 ₽ `div.card-body > div.mt-auto > div.d-flex > span.fw-bold`
1200 ₽ `div.card-body > div.mt-auto > div.d-flex > span.fw-bold`
400 ₽ `div.card-body > div.mt-auto > div.d-flex > span.fw-bold`
Осталось 1 шт. `div.card > div.card-body > div.mt-auto > span.badge`
Каталог товаров села Иглино. Находите товары и связывайтесь с продавцами напрям… `div.container > div.row > div.col-md-4 > p.text-white-50`
с. Иглино, Республика Башкортостан `div.container > div.row > div.col-md-4 > p.text-white-50`
LI Маркет — информационный каталог. Сделки совершаются напрямую между покупател… `body > footer.mt-5 > div.container > p.text-center`
© 2026 LI Маркет. Все права защищены. `body > footer.mt-5 > div.container > p.text-center`

These are opportunities to improve the legibility of your content.

Navigation

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Дорада Лодка, 260 см `div.col-6 > div.card > div.card-body > h6.card-title`

These are opportunities to improve keyboard navigation in your application.

○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-hidden="true"]` is not present on the document `<body>`

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

●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

●Touch targets have sufficient size and spacing.

●Document has a main landmark.

●Identical links have the same purpose.

○`[accesskey]` values are unique

○`[aria-*]` attributes match their roles

○`button`, `link`, and `menuitem` elements have accessible names

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

○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

○Elements use only permitted ARIA attributes

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

○`[aria-*]` attributes have valid values

○`[aria-*]` attributes are valid and not misspelled

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

○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

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
xn--80akhjch3as.xn--p1ai/	`Loading the stylesheet 'https://fonts.googleapis.com/css2?family=Inter:wght@300;400;500;600;700;800&display=swap' violates the following Content Security Policy directive: "style-src 'self' 'unsafe-inline'". Note that 'style-src-elem' was not explicitly set, so 'style-src' is used as a fallback. The action has been blocked.`

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

●Mitigate DOM-based XSS with Trusted Types

●Page has valid source maps

○Redirects HTTP traffic to HTTPS

○Use a strong HSTS policy

○Ensure proper origin isolation with COOP

○Mitigate clickjacking with XFO or CSP

○Detected JavaScript libraries

100

SEO

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

Results for https://лимаркет.рф

Site Health

How you compare

Top Priorities (5)

Fix Priority Matrix

Quick Wins

Strategic

Easy Improvements

Deprioritize

What fixing these means

Conversion Barriers

Speed (1)

Trust (1)

Content (2)

Navigation (1)

Return on Investment

Investment

Monthly returns

Regulatory risk avoided

Payback period

Estimated Remediation Cost

Cost by category

Cost by effort level

What Inaction Is Costing You

Compliance Risk

Bandwidth Waste

Lighthouse Scores

Core Web Vitals

Detailed Report

Performance

Insights

Diagnostics

Accessibility

Names and labels

Contrast

Navigation

Best practices

Best Practices

General

SEO

Lighthouse Scores

Core Web Vitals

Detailed Report

Performance

Insights

Diagnostics

Accessibility

Names and labels

Contrast

Navigation

Best Practices

General

SEO

Keyboard Shortcuts