Skip to content
https://moe.video

Lighthouse Desktop

· 0 checks — Desktop Lighthouse audit -- Performance, Accessibility, Best Practices, and SEO category breakdown.
SCORE
0
GRADE
FIX
0
REVIEW
0
PASS
0
INFO
0

Detailed Report

Audit breakdown by category with detailed findings.

83

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 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:45.669 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.

URLResource SizeEst Savings
div.rounded-lg > div.w-full > a.aspect-3/2 > img.w-full div.rounded-lg > div.w-full > a.aspect-3/2 > img.w-full
moe.video/storage/content/fhpfe95afiwhpb.jpg132.6 KiB119.8 KiB
div.rounded-lg > div.w-full > a.aspect-3/2 > img.w-full div.rounded-lg > div.w-full > a.aspect-3/2 > img.w-full
moe.video/storage/content/ava2xln2bhfvll.jpg128.1 KiB115.2 KiB
div.rounded-lg > div.w-full > a.aspect-3/2 > img.w-full div.rounded-lg > div.w-full > a.aspect-3/2 > img.w-full
moe.video/storage/content/zdyryezwpzsltd.jpg92.4 KiB79.5 KiB
body.bg-white > header#pageHeader > div.flex > img.w-[280px] body.bg-white > header#pageHeader > div.flex > img.w-[280px]
moe.video/storage/content/main.webp74.2 KiB57.9 KiB
section.content > div.w-full > div.flex > img.w-[220px] section.content > div.w-full > div.flex > img.w-[220px]
moe.video/storage/content/publishers.webp51.8 KiB38.9 KiB
section.content > div.w-full > div.flex > img.w-[220px] section.content > div.w-full > div.flex > img.w-[220px]
moe.video/storage/content/advertiser.webp39.1 KiB30.5 KiB
div.rounded-lg > div.w-full > div.w-[60px] > img.w-full div.rounded-lg > div.w-full > div.w-[60px] > img.w-full
moe.video/storage/content/24ddxfv6lkminr.jpg27.3 KiB26.7 KiB
div.rounded-lg > div.w-full > div.w-[60px] > img.w-full div.rounded-lg > div.w-full > div.w-[60px] > img.w-full
moe.video/storage/content/9cmhlpc3ka3ps7.jpg24.6 KiB24.0 KiB
div.rounded-lg > div.w-full > div.w-[60px] > img.w-full div.rounded-lg > div.w-full > div.w-[60px] > img.w-full
moe.video/storage/content/wf8vxewoaqcujp.jpg12.1 KiB11.6 KiB
div.rounded-lg > div.w-full > div.w-full > img.w-full div.rounded-lg > div.w-full > div.w-full > img.w-full
moe.video/storage/content/peqpucrz1dooqk.png6.5 KiB5.8 KiB
div.rounded-lg > div.w-full > div.w-full > img.w-full div.rounded-lg > div.w-full > div.w-full > img.w-full
moe.video/storage/content/bchzejoeqwrqjp.png5.5 KiB4.9 KiB
div.rounded-lg > div.w-full > div.w-full > img.w-full div.rounded-lg > div.w-full > div.w-full > img.w-full
moe.video/storage/content/ffjol0tcz7ttbr.png5.4 KiB4.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-3-IMG
nodeLabel: body.bg-white > header#pageHeader > div.flex > img.w-[280px]
path: 1,HTML,1,BODY,0,HEADER,1,DIV,1,IMG
selector: body.bg-white > header#pageHeader > div.flex > img.w-[280px]
snippet: <img src="/storage/content/main.webp" alt="" loading="eager" class="w-[280px] md:w-[360px] xl:w-auto xl:h-[375px] flex shrink-0 relative z-10">

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.

URLProtocol
moe.video/http/1.1
moe.video/build/assets/app-DCHd-HBj.csshttp/1.1
moe.video/build/assets/app-DP80toBK.jshttp/1.1
moe.video/storage/content/main.webphttp/1.1
moe.video/storage/content/ava2xln2bhfvll.jpghttp/1.1
moe.video/storage/content/fhpfe95afiwhpb.jpghttp/1.1
moe.video/storage/content/zdyryezwpzsltd.jpghttp/1.1
moe.video/storage/content/icon-vk.webphttp/1.1
moe.video/storage/content/logo-arir.webphttp/1.1
moe.video/storage/content/logo-akar.webphttp/1.1
moe.video/build/assets/geologica-v1-cyrillic_latin-600-DfnMEVEx.woff2http/1.1
moe.video/build/assets/geologica-v1-cyrillic_latin-regular-BW-dXBRg.woff2http/1.1
moe.video/storage/content/publishers.webphttp/1.1
moe.video/storage/content/advertiser.webphttp/1.1
moe.video/storage/content/homepage-icon-like.webphttp/1.1
moe.video/storage/content/homepage-icon-player.webphttp/1.1
moe.video/storage/content/homepage-icon-quality.webphttp/1.1
moe.video/storage/content/homepage-icon-monetization.webphttp/1.1
moe.video/storage/content/homepage-icon-heart.webphttp/1.1
moe.video/storage/content/homepage-icon-manager.webphttp/1.1
moe.video/storage/content/peqpucrz1dooqk.pnghttp/1.1
moe.video/storage/content/9cmhlpc3ka3ps7.jpghttp/1.1
moe.video/storage/content/bchzejoeqwrqjp.pnghttp/1.1
moe.video/storage/content/24ddxfv6lkminr.jpghttp/1.1
moe.video/storage/content/ffjol0tcz7ttbr.pnghttp/1.1
moe.video/storage/content/wf8vxewoaqcujp.jpghttp/1.1
moe.video/storage/content/zmdianoam1lx7i.pnghttp/1.1

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.

RequestCache TTLTransfer Size
mc.yandex.ru/metrika/tag.js3600.0 s85.1 KiB
moe.video/build/assets/app-DP80toBK.js0.0 ms63.9 KiB
privacy-cs.mail.ru/static/sync-loader.js600.0 s21.9 KiB
counter.reddigital.ru/DSPCounter.js0.0 ms17.2 KiB
moe.video/build/assets/app-DCHd-HBj.css0.0 ms14.6 KiB
mc.yandex.com/metrika-tags/_/tag_ec.js7193.0 s15.7 KiB
mc.yandex.com/metrika/advert.gif?t=gdpr(14)ti(4)3600.0 s363 B
/sync_cookie_image_decide_secondary?cid=94135832&scid=75f...0.0 ms255 B
/sync_cookie_image_decide?cid=94135832&scid=d8dfe71a-b279...0.0 ms67 B

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

Diagnostics

Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 0.0 ms 91.8 KiB
URLTransfer SizeEst Savings
moe.video/build/assets/app-DP80toBK.js63.5 KiB47.2 KiB
mc.yandex.ru/metrika/tag.js84.5 KiB44.6 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
body.bg-white > header#pageHeader > div.flex > img.w-[280px] body.bg-white > header#pageHeader > div.flex > img.w-[280px]
moe.video/storage/content/main.webp
section.content > div.w-full > div.flex > img.w-[220px] section.content > div.w-full > div.flex > img.w-[220px]
moe.video/storage/content/advertiser.webp
section.content > div.w-full > div.flex > img.w-[220px] section.content > div.w-full > div.flex > img.w-[220px]
moe.video/storage/content/publishers.webp
div.rounded-lg > div.w-full > div.w-full > img.w-full div.rounded-lg > div.w-full > div.w-full > img.w-full
moe.video/storage/content/peqpucrz1dooqk.png
div.rounded-lg > div.w-full > div.w-full > img.w-full div.rounded-lg > div.w-full > div.w-full > img.w-full
moe.video/storage/content/bchzejoeqwrqjp.png
div.rounded-lg > div.w-full > div.w-full > img.w-full div.rounded-lg > div.w-full > div.w-full > img.w-full
moe.video/storage/content/ffjol0tcz7ttbr.png
section.content > div.w-full > div.bg-black/[3%] > img.w-[54px] section.content > div.w-full > div.bg-black/[3%] > img.w-[54px]
moe.video/storage/content/homepage-icon-like.webp
section.content > div.w-full > div.bg-black/[3%] > img.w-[54px] section.content > div.w-full > div.bg-black/[3%] > img.w-[54px]
moe.video/storage/content/homepage-icon-player.webp
section.content > div.w-full > div.bg-black/[3%] > img.w-[54px] section.content > div.w-full > div.bg-black/[3%] > img.w-[54px]
moe.video/storage/content/homepage-icon-monetization.webp
section.content > div.w-full > div.bg-black/[3%] > img.w-[54px] section.content > div.w-full > div.bg-black/[3%] > img.w-[54px]
moe.video/storage/content/homepage-icon-heart.webp
section.content > div.w-full > div.bg-black/[3%] > img.w-[54px] section.content > div.w-full > div.bg-black/[3%] > img.w-[54px]
moe.video/storage/content/homepage-icon-quality.webp
section.content > div.w-full > div.bg-black/[3%] > img.w-[54px] section.content > div.w-full > div.bg-black/[3%] > img.w-[54px]
moe.video/storage/content/homepage-icon-manager.webp
Логотип АРИР footer.w-full > div.content > div.w-full > img.w-[80px]
moe.video/storage/content/logo-arir.webp
Логотип АКАР footer.w-full > div.content > div.w-full > img.w-[80px]
moe.video/storage/content/logo-akar.webp

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

●Time to Interactive 2.4 s
●Layout shift culprits
●Document request latency
●Optimize DOM size
●Font display
●LCP breakdown
●Network dependency tree
●Render blocking requests
●Optimize viewport for mobile
●Max Potential First Input Delay 50 ms
●Minify CSS
●Minify JavaScript
●Reduce unused CSS
●Avoids enormous network payloads Total size was 961 KiB
●JavaScript execution time 0.3 s
●Minimizes main-thread work 0.6 s
●Page didn't prevent back/forward cache restoration
●Network Requests
●Network Round Trip Times 230 ms
●Server Backend Latencies 240 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 210 ms
●Avoid large layout shifts 2 layout shifts found
○INP breakdown
○User Timing marks and measures
○Avoid long main-thread tasks
○Avoid non-composited animations
77

Accessibility

These checks highlight opportunities to improve the accessibility of your web app. Automatic detection can only detect a subset of issues and does not guarantee the accessibility of your web app, so manual testing is also encouraged.

Contrast

Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
12+ лет section.content > ul.w-full > li.text-brand-copy > span.block
90+ тыс section.content > ul.w-full > li.text-brand-copy > span.block
100+ млрд section.content > ul.w-full > li.text-brand-copy > span.block
150 млн section.content > ul.w-full > li.text-brand-copy > span.block
> 90% section.content > ul.w-full > li.text-brand-copy > span.block
CTR 1,5% section.content > ul.w-full > li.text-brand-copy > span.block
Для паблишеров section.content > div.w-full > div.w-full > h3.font-semibold
Для рекламодателей section.content > div.w-full > div.w-full > h3.font-semibold
Работаем в соответствии с требованиями федерального законодательства body.bg-white > main.w-full > section.content > h2.section-heading-blue
Своевременно исполняем требования ст.18.1 ФЗ № 38 “О рекламе” от 13.03.2006 и о… body.bg-white > main.w-full > section.content > p.text-lg
31.03.2026 div.w-full > div.rounded-lg > div.w-full > div.text-brand-copy/50
Подробнее div.w-full > div.rounded-lg > div.w-full > a.font-semibold
12.02.2026 div.w-full > div.rounded-lg > div.w-full > div.text-brand-copy/50
Подробнее div.w-full > div.rounded-lg > div.w-full > a.font-semibold
05.12.2025 div.w-full > div.rounded-lg > div.w-full > div.text-brand-copy/50
Подробнее div.w-full > div.rounded-lg > div.w-full > a.font-semibold

These are opportunities to improve the legibility of your content.

Names and labels

Screen reader users rely on frame titles to describe the contents of frames. Learn more about frame titles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
body.bg-white > iframe body.bg-white > iframe

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.w-full > div.rounded-lg > div.w-full > a.aspect-3/2 div.w-full > div.rounded-lg > div.w-full > a.aspect-3/2
div.w-full > div.rounded-lg > div.w-full > a.aspect-3/2 div.w-full > div.rounded-lg > div.w-full > a.aspect-3/2
div.w-full > div.rounded-lg > div.w-full > a.aspect-3/2 div.w-full > div.rounded-lg > div.w-full > a.aspect-3/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.

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-hidden="true"]` is not present on the document `<body>`
●Buttons have an accessible name
●Image elements have `[alt]` attributes
●Form elements have associated labels
●`[aria-hidden="true"]` elements do not contain focusable descendents
●Document has a `<title>` element
●`<html>` element has a `[lang]` attribute
●`<html>` element has a valid value for its `[lang]` attribute
●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
●Touch targets have sufficient size and spacing.
●Heading elements appear in a sequentially-descending order
●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 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
○`<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
○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.
100

Best Practices

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

Send Feedback