Lighthouse Mobile

· 0 checks — Mobile Lighthouse audit -- Performance, Accessibility, Best Practices, and SEO category breakdown.

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Detailed Report

Audit breakdown by category with detailed findings.

Performance

Insights

Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Polyfills and transforms enable older browsers to use new JavaScript features. However, many aren't necessary for modern browsers. Consider modifying your JavaScript build process to not transpile Baseline features, unless you know you must support older browsers. Learn why most sites can deploy ES6+ code without transpiling

Why this matters

Performance issues directly impact user engagement and conversion rates.

3rd party code can significantly impact load performance. Reduce and defer loading of 3rd party code to prioritize your page's content.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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	179.4 KiB
gu-st.ru/portal-st/lib-assets/fonts/Lato-Bold.woff2	7200.0 s	28.7 KiB

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.

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.

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
gosuslugi.ru/__jsch/static/script.js	10.5 s	10.0 s	4.6 ms
gosuslugi.ru/	467 ms	3.6 ms	0.6 ms
Unattributable	216 ms	4.7 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	10.0 s
Other	645 ms
Garbage Collection	215 ms
Style & Layout	155 ms
Rendering	82 ms
Parse HTML & CSS	6.4 ms
Script Parsing & Compilation	5.2 ms

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

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

●Reduce unused JavaScript

●Avoids enormous network payloads Total size was 236 KiB

●Avoid long main-thread tasks 20 long tasks found

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

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 80 ms

●Server Backend Latencies 80 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

●Avoid multiple page redirects

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

○INP breakdown

○LCP request discovery

○User Timing marks and measures

○Avoid non-composited animations

○Avoid large layout shifts

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.

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

●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

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

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

○Buttons have an accessible name

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

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

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

●Mitigate DOM-based XSS with Trusted Types

●Page has valid source maps

○Redirects HTTP traffic to HTTPS

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

Content Best Practices

Meta descriptions may be included in search results to concisely summarize page content. Learn more about the meta description.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Format your HTML in a way that enables crawlers to better understand your app’s content.

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">№8525106823901541735</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

●Page has successful HTTP status code

●Links have descriptive text

●Links are crawlable

●Document has a valid `hreflang`

○Image elements have `[alt]` attributes

○Document has a valid `rel=canonical`