Lighthouse Desktop

· 0 checks — Desktop 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
ads.digitalcaramel.com/caramel.js?ts=1776896586109	0.0 ms	166.8 KiB
js.mbidinp.com/skins/nmain.m.js	300.0 s	144.7 KiB
mc.yandex.ru/metrika/tag.js	3600.0 s	85.4 KiB
js.mbidinp.com/npc/sdk/wpu/npush.m.js	300.0 s	69.1 KiB
x01.aidata.io/lib/aidata.fp.latest.js?pixel=0892394	0.0 ms	59.5 KiB
static.a.mts.ru/id/pixel.js	1800.0 s	60.1 KiB
js.mbidadm.com/static/scripts.js	300.0 s	47.1 KiB
privacy-cs.mail.ru/static/sync-loader.js	600.0 s	21.9 KiB
cdnrtbsape.ru/js/vast/vpaid-ssp.min.js	86400.0 s	47.8 KiB
www.google-analytics.com/analytics.js	7200.0 s	20.9 KiB
content.adriver.ru/AdRiverFPS.js	3600.0 s	16.2 KiB
static.kimberlite.io/js/thumbmark.umd.js	0.0 ms	12.6 KiB
static.kimberlite.io/js/botd.js	0.0 ms	8.0 KiB
/roxot-wrapper/js/roxot-manager.js?pid=19e08d82-9ec3-4dda...	600.0 s	8.6 KiB
assets.ahmybid.net/7613a052-b5f5-4f9f-942a-01aba386e713.jpg	43200.0 s	14.1 KiB
abt.s3.yandex.net/expjs/latest/exp.js	0.0 ms	6.4 KiB
www.acint.net/aci.js	43200.0 s	8.9 KiB
acint.net/aci.js	43200.0 s	8.9 KiB
tube.buzzoola.com/js/lib/buzzoola_ufp.js	2157.0 s	4.8 KiB
tube.buzzoola.com//js/lib/buzzoola_ufp.js	2157.0 s	4.8 KiB
assets.ahmybid.net/57eeb89c-3a3a-4981-8a6d-970d24be8ac5.jpg	43200.0 s	6.8 KiB
sb.scorecardresearch.com/beacon.js	86400.0 s	6.7 KiB
cdn-rtb.sape.ru/js/uids.js	86400.0 s	6.7 KiB
dic.academic.ru/images/sprites.png?150326	864000.0 s	15.4 KiB
academic.ru/js/academic.min.js?150324	1209600.0 s	12.7 KiB
/wrapper/js/rp-core-engine.js?v=s-dc1af2de-5f10-4ef6-a4db...	345600.0 s	3.7 KiB
tube.buzzoola.com/js/lib/buzzoola_ext.js	2157.0 s	772 B
academic.ru/css/academic_v2.css?20210501a	1209600.0 s	6.3 KiB
mc.yandex.com/metrika/advert.gif?t=gdpr(14)ti(4)	3600.0 s	316 B
dic.academic.ru/images/sprites_flags.png?150326	864000.0 s	1.6 KiB
sync.opendsp.ru/match/sp.img?chk=1	0.0 ms	157 B
academic.ru/images/Logo.png	864000.0 s	1.5 KiB
academic.ru/images/Logo_h.png	864000.0 s	1.4 KiB
sync.digitalcaramel.com/match/sp?chk=1	0.0 ms	133 B
/sync_cookie_image_decide_secondary?cid=70309897&scid=15a...	0.0 ms	79 B
/sync_cookie_image_decide?cid=70309897&scid=1608550f-cbb9...	0.0 ms	67 B
academic.ru/css/mobile-menu.css?20190810	1209600.0 s	624 B
static.a.mts.ru/id/pixel.js	1800.0 s	0 B
x01.aidata.io/lib/aidata.fp.latest.js?pixel=0892394	0.0 ms	0 B
cdnrtbsape.ru/js/vast/vpaid-ssp.min.js	86400.0 s	0 B
cdnrtbsape.ru/js/vast/vpaid-ssp.min.js	86400.0 s	0 B
www.acint.net/aci.js	43200.0 s	0 B
www.acint.net/aci.js	43200.0 s	0 B
www.acint.net/aci.js	43200.0 s	0 B

Layout shifts occur when elements move absent any user interaction. Investigate the causes of layout shifts, such as elements being added, removed, or their fonts changing as the page loads.

Why this matters

Performance issues directly impact user engagement and conversion rates.

headings: [map[key:node label:Element subItemsHeading:map[key:extra] valueType:node] map[granularity:0.001 key:score label:Layout shift score subItemsHeading:map[key:cause valueType:text] valueType:numeric]]

items: [map[node:map[type:text value:Total] score:0.433098] map[node:map[boundingRect:map[bottom:774 height:490 left:165 right:385 top:284 width:220] lhId:page-1-UL nodeLabel:Медицинская энциклопедия Большой медицинский словарь Медицинские термины Атлас … path:1,HTML,1,BODY,1,DIV,2,DIV,0,DIV,1,DIV,1,UL selector:div#content > div#diclist > div.column > ul snippet:<ul> type:node] score:0.433098]]

Avoid chaining critical requests by reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.

Why this matters

Performance issues directly impact user engagement and conversion rates.

description: [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints help the browser establish a connection earlier in the page load, saving time when the first request for that origin is made. The following are the origins that the page preconnected to.

title: Preconnected origins

description: Add [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints to your most important origins, but try to use no more than 4.

title: Preconnect candidates

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
latina ka new style `body > div.f2dD3zSK_nwV685NTQBQ > div.gSPZ4JykommM8jYG8Zck > img.f1dg4DSssPPtX9CCBMLQ`	assets.ahmybid.net/7613a052-b5f5-4f9f-942a-01aba386e713.jpg	13.8 KiB	7.3 KiB

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

These are the largest layout shifts observed on the page. Each table item represents a single layout shift, and shows the element that shifted the most. Below each item are possible root causes that led to the layout shift. Some of these layout shifts may not be included in the CLS metric value due to windowing. Learn how to improve CLS

Why this matters

Performance issues directly impact user engagement and conversion rates.

Element	Layout shift score
Медицинская энциклопедия Большой медицинский словарь Медицинские термины Атлас … `div#content > div#diclist > div.column > ul`	0.433

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.

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

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
js.mbidinp.com/npc/sdk/wpu/npush.m.js	1.3 s	341 ms	5.1 ms
Unattributable	492 ms	75 ms	0.0 ms
academic.ru/	365 ms	5.1 ms	1.1 ms
static.a.mts.ru/id/pixel.js	223 ms	164 ms	8.5 ms
static.kimberlite.io/js/thumbmark.umd.js	204 ms	197 ms	0.0 ms
mc.yandex.ru/metrika/tag.js	180 ms	161 ms	7.1 ms
yandex.ru/ads/system/adsdk.js	176 ms	163 ms	3.6 ms
js.mbidadm.com/static/scripts.js	158 ms	126 ms	15 ms
/partner-code-bundles/1304651/vas-bundles/bundles-es2017/...	150 ms	120 ms	17 ms
yandex.ru/ads/system/context.js	137 ms	102 ms	10 ms
cdnrtbsape.ru/js/vast/vpaid-ssp.min.js	130 ms	108 ms	14 ms
yastatic.net/partner-code-bundles/1304651/22d10f9d8e892aab.js	121 ms	82 ms	4.0 ms
x01.aidata.io/lib/aidata.fp.latest.js?pixel=0892394	115 ms	97 ms	6.9 ms
yandex.ru/ads/system/header-bidding.js	105 ms	57 ms	2.8 ms
ads.digitalcaramel.com/caramel.js?ts=1776896586109	97 ms	83 ms	3.8 ms
privacy-cs.mail.ru/static/sync-loader.js	71 ms	60 ms	2.2 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
Script Evaluation	2.2 s
Other	1.5 s
Style & Layout	369 ms
Script Parsing & Compilation	157 ms
Rendering	111 ms
Garbage Collection	82 ms
Parse HTML & CSS	20 ms

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

URL	Transfer Size	Est Savings
static.kimberlite.io/js/botd.js	7.7 KiB	3.0 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: 0.0 ms 745.2 KiB

URL	Transfer Size	Est Savings
yastatic.net/partner-code-bundles/1304651/00cc0164cd639ddf.js	129.7 KiB	103.0 KiB
/partner-code-bundles/1304651/vas-bundles/bundles-es2017/...	206.0 KiB	98.2 KiB
ads.digitalcaramel.com/caramel.js?ts=1776896586109	166.2 KiB	72.8 KiB
www.googletagmanager.com/gtag/js?id=G-QXJR5FPYJ8&cx=c&_slc=1	150.8 KiB	62.1 KiB
js.mbidinp.com/skins/nmain.m.js	143.5 KiB	56.0 KiB
mc.yandex.ru/metrika/tag.js	84.7 KiB	43.3 KiB
yandex.ru/ads/system/context.js	103.8 KiB	38.2 KiB
x01.aidata.io/lib/aidata.fp.latest.js?pixel=0892394	59.4 KiB	35.5 KiB
x01.aidata.io/lib/aidata.fp.latest.js?pixel=0892394	59.4 KiB	34.4 KiB
cdnrtbsape.ru/js/vast/vpaid-ssp.min.js	47.3 KiB	26.6 KiB
cdnrtbsape.ru/js/vast/vpaid-ssp.min.js	47.3 KiB	26.6 KiB
cdnrtbsape.ru/js/vast/vpaid-ssp.min.js	47.3 KiB	26.6 KiB
cdnrtbsape.ru/js/vast/vpaid-ssp.min.js	47.3 KiB	26.6 KiB
cdnrtbsape.ru/js/vast/vpaid-ssp.min.js	47.3 KiB	26.6 KiB
cdnrtbsape.ru/js/vast/vpaid-ssp.min.js	47.3 KiB	26.5 KiB
yastatic.net/partner-code-bundles/1304651/22d10f9d8e892aab.js	31.8 KiB	21.6 KiB
js.mbidinp.com/npc/sdk/wpu/npush.m.js	68.8 KiB	20.5 KiB

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

●Document request latency

●Optimize DOM size

●Font display

●Forced reflow

●LCP breakdown

●Modern HTTP

●Render blocking requests

●Optimize viewport for mobile

●Minify CSS

●Reduce unused CSS

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

●User Timing marks and measures 5 user timings

●Avoid long main-thread tasks 1 long task found

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

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 110 ms

●Server Backend Latencies 300 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 170 ms

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

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 > iframe `body > iframe`
body > iframe `body > iframe`
body > iframe `body > iframe`
body > iframe `body > iframe`
body > iframe `body > iframe`
body > iframe `body > iframe`
body > iframe `body > iframe`
body > iframe `body > iframe`
body > iframe `body > iframe`
body > iframe `body > iframe`
body > iframe `body > iframe`
body > iframe `body > iframe`
body > iframe `body > iframe`
body > iframe `body > 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#page > div#footer > div#liveinternet > a `div#page > div#footer > div#liveinternet > a`

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.

Tables and lists

Screen readers have a specific way of announcing lists. Ensuring proper list structure aids screen reader output. Learn more about proper list structure.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Правила русского правописания Справочник по правописанию и стилистике Словарь-с… `div#content > div#diclist > div.column > ul`

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Best practices

One main landmark helps screen reader users navigate a web page. Learn more about landmarks.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html `html`

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

●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.

●Background and foreground colors have a sufficient contrast ratio

●Document has a `<title>` element

●`<html>` element has a `[lang]` attribute

●`<html>` element has a valid value for its `[lang]` attribute

●Links are distinguishable without relying on color.

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

●Touch targets have sufficient size and spacing.

●Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.

●Heading elements appear in a sequentially-descending order

●Image elements do not have `[alt]` attributes that are redundant text.

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

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

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

○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
Topics	js.mbidadm.com/static/scripts.js

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
academic.ru/ line 959, col 0	`ReferenceError: googletag is not defined at https://academic.ru/:960:1`

●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

●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

SEO

These checks ensure that your page is following basic search engine optimization advice. There are many additional factors Lighthouse does not score here that may affect your search ranking, including performance on Core Web Vitals. Learn more about Google Search Essentials.

Crawling and Indexing

Search engines may use `href` attributes on links to crawl websites. Ensure that the `href` attribute of anchor elements links to an appropriate destination, so more pages of the site can be discovered. Learn how to make links crawlable

Why this matters

Performance issues directly impact user engagement and conversion rates.

Uncrawlable Link
tr > td#td-search > div#translate-arrow > a `tr > td#td-search > div#translate-arrow > a`

To appear in search results, crawlers need access to your app.

○Structured data is valid

●Page isn’t blocked from indexing

●Document has a `<title>` element

●Document has a meta description

●Page has successful HTTP status code

●Links have descriptive text

●robots.txt is valid

●Image elements have `[alt]` attributes

●Document has a valid `hreflang`

●Document has a valid `rel=canonical`