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.

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

title: Preconnected origins

value: no origins were preconnected

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

title: Preconnect candidates

value: No additional origins are good candidates for preconnecting

A long cache lifetime can speed up repeat visits to your page. Learn more about caching.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Request	Cache TTL	Transfer Size
gu-st.ru/portal-st/lib-assets/fonts/Lato-Regular.woff2	7200.0 s	0 B
gu-st.ru/portal-st/lib-assets/fonts/Lato-Bold.woff2	7200.0 s	0 B

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

The maximum potential First Input Delay that your users could experience is the duration of the longest task. Learn more about the Maximum Potential First Input Delay metric.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 353 ms

URL	Time Spent
gosuslugi.ru/	302 ms
gosuslugi.ru/	51 ms
www.gosuslugi.ru/	0.0 ms

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
gosuslugi.ru/__jsch/static/script.js	2.0 s	1.9 s	1.4 ms
www.gosuslugi.ru/__jsch/static/script.js	1.4 s	1.4 s	1.2 ms
www.gosuslugi.ru/	116 ms	1.9 ms	0.3 ms
Unattributable	67 ms	0.6 ms	0.0 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	3.3 s
Other	220 ms
Style & Layout	43 ms
Garbage Collection	39 ms
Rendering	19 ms
Script Parsing & Compilation	2.9 ms
Parse HTML & CSS	2.8 ms

Many navigations are performed by going back to a previous page, or forwards again. The back/forward cache (bfcache) can speed up these return navigations. Learn more about the bfcache

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failure reason	Failure type
Pages with cache-control:no-store header cannot enter back/forward cache.	Actionable
Pages with WebSocket cannot enter back/forward cache.	Pending browser support
Pages whose main resource has cache-control:no-store cannot enter back/forward cache.	Not actionable
Back/forward cache is disabled because some JavaScript network request received resource with Cache-Control: no-store header.	Not actionable
Back/forward cache is disabled because WebSocket has been used.	Not actionable

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: 0.0 ms 17.6 KiB

URL	Transfer Size	Est Savings
gu-st.ru/portal-st/styles.7d48372f563bb034.css	17.7 KiB	17.6 KiB

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

●Time to Interactive 2.2 s

●Layout shift culprits

●Optimize DOM size

●Font display

●Forced reflow

●Improve image delivery

●LCP breakdown

●Modern HTTP

●Render blocking requests

●Optimize viewport for mobile

●Minify CSS

●Minify JavaScript

●Reduce unused JavaScript

●Avoids enormous network payloads Total size was 265 KiB

●Avoid long main-thread tasks 2 long tasks found

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

●Network Requests

●Network Round Trip Times 90 ms

●Server Backend Latencies 10 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

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

○INP breakdown

○LCP request discovery

○User Timing marks and measures

○Avoid non-composited animations

○Avoid large layout shifts

100

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.

○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

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

●Document has a main landmark.

●Deprecated ARIA roles were not used

○`[accesskey]` values are unique

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

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

○Buttons have an accessible name

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

○Background and foreground colors have a sufficient contrast ratio

○`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.

○Definition list items are wrapped in `<dl>` elements

○ARIA IDs are unique

○No form fields have multiple labels

○`<frame>` or `<iframe>` elements have a title

○Heading elements appear in a sequentially-descending order

○`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.

○Image elements have `[alt]` attributes

○Input buttons have discernible text.

○`<input type="image">` elements have `[alt]` text

○Form elements have associated labels

○Links are distinguishable without relying on color.

○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

○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

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

○`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.

○`[lang]` attributes have a valid value

○`<video>` elements contain a `<track>` element with `[kind="captions"]`

○Tables have different content in the summary attribute and `<caption>`.

○All heading elements contain content.

○Uses ARIA roles only on compatible elements

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

○Identical links have the same purpose.

○Elements with visible text labels have matching accessible names.

○Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.

○`<td>` elements in a large `<table>` have one or more table headers.

—

Best Practices

Browser Compatibility

A character encoding declaration is required. It can be done with a `<meta>` tag in the first 1024 bytes of the HTML or in the Content-Type HTTP response header. Learn more about declaring the character encoding.

Why this matters

Performance issues directly impact user engagement and conversion rates.

●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

●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 clickjacking with XFO or CSP

●Mitigate DOM-based XSS with Trusted Types

●Detected JavaScript libraries

●Page has valid source maps

○Redirects HTTP traffic to HTTPS

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

If your robots.txt file is malformed, crawlers may not be able to understand how you want your website to be crawled or indexed. Learn more about robots.txt.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Line #	Content	Error
1	`<!DOCTYPE html>`	`Syntax not understood`
2	`<html>`	`Syntax not understood`
3	`<head>`	`Syntax not understood`
4	`<title>Ошибка</title>`	`Syntax not understood`
5	`<meta http-equiv="pragma" content="no-cache"/>`	`Syntax not understood`
6	`<meta http-equiv="cache-control" content="no-cache, must-revalidate"/>`	`Syntax not understood`
7	`<meta http-equiv="cache-control" content="no-store, post-check=0, pre-check=0"/>`	`Syntax not understood`
8	`<meta http-equiv="content-type" content="text/html; charset=utf-8"/>`	`Syntax not understood`
9	`<meta http-equiv="X-UA-Compatible" content="IE=edge;chrome=1"/>`	`Syntax not understood`
10	`<meta name="viewport" content="width=device-width, initial-scale=1.0"/>`	`Syntax not understood`
11	`<meta name="SKYPE_TOOLBAR" content="SKYPE_TOOLBAR_PARSER_COMPATIBLE"/>`	`Syntax not understood`
12	`<meta name="description" content=""/>`	`Syntax not understood`
13	`<meta name="robots" content="none"/>`	`Syntax not understood`
14	`<link rel="shortcut icon" href="https://gu-st.ru/static_errors/imperva/img/favicon.ico"/>`	`Unknown directive`
15	`<link type="text/css" rel="stylesheet" href="https://gu-st.ru/static_errors/imperva/css/error.css"/>`	`Unknown directive`
16	`</head>`	`Syntax not understood`
17	`<body class="error-page">`	`Syntax not understood`
18	`<div class="baseheader-wrap simple">`	`Syntax not understood`
19	`<div class="page-wrap baseheader">`	`Syntax not understood`
20	`<a href="/" class="logo" title="">`	`Syntax not understood`
21	`ГОСУСЛУГИ`	`Syntax not understood`
22	`</a>`	`Syntax not understood`
23	`<div class="slogan">`	`Syntax not understood`
24	`Доступ к сервисам электронного правительства`	`Syntax not understood`
25	`</div>`	`Syntax not understood`
26	`</div>`	`Syntax not understood`
27	`</div>`	`Syntax not understood`
29	`<div class="basecontent-wrap">`	`Syntax not understood`
30	`<div class="page-wrap basecontent">`	`Syntax not understood`
31	`<div class="base-cover simple">`	`Syntax not understood`
32	`<section class="b-error">`	`Syntax not understood`
33	`<h1 class="b-error__title">`	`Syntax not understood`
34	`Во время обработки запроса произошла ошибка`	`Syntax not understood`
35	`</h1>`	`Syntax not understood`
36	`<p class="b-error__text">Код ошибки: <b class="error-code">№8525106826964900110</b></p>`	`Unknown directive`
37	`<p class="b-error__text">IP address: <b class="error-code"><script type="text/javascript" src="https://ip.gosuslugi.ru/query/ip.js" "></script></b></p>`	`Unknown directive`
38	`<p class="b-error__text">Время инцидента: <b class="error-code"><script type="text/javascript" src="https://ip.gosuslugi.ru/query/date.js" "></script></b></p>`	`Unknown directive`
39	`<p class="b-error__text">Приносим извинения за временные неудобства</p>`	`Syntax not understood`
41	`<div class="b-error__buttons">`	`Syntax not understood`
42	`<a class="b-error__button" href="javascript: history.back();">`	`Unknown directive`
43	`Вернуться назад`	`Syntax not understood`
44	`</a>`	`Syntax not understood`
45	`<a class="b-error__button b-error__button_main" href="/">`	`Syntax not understood`
46	`Перейти на главную`	`Syntax not understood`
47	`</a>`	`Syntax not understood`
48	`</div>`	`Syntax not understood`
49	`</section>`	`Syntax not understood`
50	`</div>`	`Syntax not understood`
51	`</div>`	`Syntax not understood`
52	`</div>`	`Syntax not understood`
54	`<div class="basefooter-wrap">`	`Syntax not understood`
55	`<div class="page-wrap basefooter">`	`Syntax not understood`
56	`<div class="logo-dept mks"></div>`	`Syntax not understood`
57	`<div class="logo-dept rtk"></div>`	`Syntax not understood`
58	`<div class="copyright" id="copyright"></div>`	`Syntax not understood`
59	`</div>`	`Syntax not understood`
60	`</div>`	`Syntax not understood`
62	`<script type="text/javascript">`	`Syntax not understood`
63	`var copyrightText = "Официальный интернет-портал государственных услуг, " + new Date().getFullYear() + " г.";`	`Syntax not understood`
64	`document.getElementById('copyright').innerText = copyrightText;`	`Syntax not understood`
65	`</script>`	`Syntax not understood`
67	`</body>`	`Syntax not understood`
68	`</html>`	`Syntax not understood`

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

●Links are crawlable

●Document has a valid `hreflang`

●Document has a valid `rel=canonical`

○Image elements have `[alt]` attributes