Skip to content
https://sert-nfpmk.ru

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.

94

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.

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.

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-0-DIV
nodeLabel: div#allrecords > div#rec1477248061 > div#recorddiv1477248061 > div#coverCarry1477248061
path: 1,HTML,1,BODY,1,DIV,2,DIV,1,DIV,0,DIV
selector: div#allrecords > div#rec1477248061 > div#recorddiv1477248061 > div#coverCarry1477248061
snippet: <div class="t-cover__carrier loaded" id="coverCarry1477248061" data-content-cover-id="1477248061" data-content-cover-bg="https://static.tildacdn.com/tild3836-3432-4231-a630-393738386665/pexels-fa…" data-display-changed="true" data-content-cover-height="70vh" data-content-cover-parallax="dynamic" data-content-use-image-for-mobile-cover="" style="height: 846px; background-attachment: scroll; top: -19px;" itemscope="" itemtype="http://schema.org/ImageObject" data-content-cover-updated-height="846px">

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

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.

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
neo.tildacdn.com/js/tilda-fallback-1.0.min.js604800.0 s1.1 KiB

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.t228__leftside > div.t228__leftcontainer > a.t228__imgwrapper > img.t228__imglogo div.t228__leftside > div.t228__leftcontainer > a.t228__imgwrapper > img.t228__imglogo
static.tildacdn.com/tild3561-3233-4465-b034-353964313035/nfpmk_logo_color.png27.1 KiB27.0 KiB

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: 60 ms 56.9 KiB
URLTransfer SizeEst Savings
sert-nfpmk.ru/29.4 KiB29.4 KiB
static.tildacdn.com/js/tilda-forms-1.0.min.js31.4 KiB27.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
div.t228__leftside > div.t228__leftcontainer > a.t228__imgwrapper > img.t228__imglogo div.t228__leftside > div.t228__leftcontainer > a.t228__imgwrapper > img.t228__imglogo
static.tildacdn.com/tild3561-3233-4465-b034-353964313035/nfpmk_logo_color.png
div.t396__artboard > div.t396__elem > a.tn-atom > img.tn-atom__img div.t396__artboard > div.t396__elem > a.tn-atom > img.tn-atom__img
/tild3331-3665-4334-b334-326166316464/-/resize/552x/-/for...

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

●Time to Interactive 1.4 s
●Layout shift culprits
●Document request latency
●Optimize DOM size
●Forced reflow
●LCP breakdown
●Modern HTTP
●Optimize viewport for mobile
●Max Potential First Input Delay 20 ms
●Minify CSS
●Minify JavaScript
●Reduce unused CSS
●Avoids enormous network payloads Total size was 508 KiB
●JavaScript execution time 0.0 s
●Minimizes main-thread work 0.5 s
●Avoid non-composited animations 4 animated elements found
●Page didn't prevent back/forward cache restoration
●Network Requests
●Network Round Trip Times 50 ms
●Server Backend Latencies 110 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 100 ms
○INP breakdown
○User Timing marks and measures
○Avoid long main-thread tasks
○Avoid large layout shifts
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
Бизнес коуч (СПБК НФПМК), победитель Премии “ТОП-3 executive&business коучей” 2… li.t524__col > div.t524__itemwrapper > div.t524__wrappercenter > div.t524__persdescr
Сертифицированный коуч (СПК НФПМК), невербальный коуч, телесно-ориентированный … li.t524__col > div.t524__itemwrapper > div.t524__wrappercenter > div.t524__persdescr
Executive, бизнес и командный коуч (СПБК НФПМК), сертифицированный WingWave коуч li.t524__col > div.t524__itemwrapper > div.t524__wrappercenter > div.t524__persdescr
Бизнес коуч (СПБК НФПМК), командный коуч, автор программ по навыкам управления … li.t524__col > div.t524__itemwrapper > div.t524__wrappercenter > div.t524__persdescr
Бизнес коуч (СПБК НФПМК), экспоненциальный коуч, ментор и инструктор в Сколково li.t524__col > div.t524__itemwrapper > div.t524__wrappercenter > div.t524__persdescr
Сертифицированный коуч (СПК НФПМК), действующий директор по персоналу li.t524__col > div.t524__itemwrapper > div.t524__wrappercenter > div.t524__persdescr
Бизнес коуч (СПБК НФПМК), командный коуч, преподавать коучинговых программ li.t524__col > div.t524__itemwrapper > div.t524__wrappercenter > div.t524__persdescr
Бизнес коуч (СПБК НФПМК), телесно-ориентированный терапевт, бизнес-тренер li.t524__col > div.t524__itemwrapper > div.t524__wrappercenter > div.t524__persdescr
политикой конфиденциальности div.t678__form-bottom-text > strong > u > a
политикой конфиденциальности div.t678__form-bottom-text > strong > u > a
Made on div#tildacopy > a.t-tildalabel__link > div.t-tildalabel__wrapper > div.t-tildalabel__txtleft
Tilda div#tildacopy > a.t-tildalabel__link > div.t-tildalabel__wrapper > div.t-tildalabel__txtright

These are opportunities to improve the legibility of your content.

Internationalization and localization

If a page doesn't specify a `lang` attribute, a screen reader assumes that the page is in the default language that the user chose when setting up the screen reader. If the page isn't actually in the default language, then the screen reader might not announce the page's text correctly. Learn more about the `lang` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html html

These are opportunities to improve the interpretation of your content by users in different locales.

Names and labels

Labels ensure that form controls are announced properly by assistive technologies, like screen readers. Learn more about form element labels.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.t-input-group > div.t-input-block > div.t-datepicker__wrapper > input#input_5854200896061 div.t-input-group > div.t-input-block > div.t-datepicker__wrapper > input#input_5854200896061

Form elements without effective labels can create frustrating experiences for screen reader users. Learn more about the `select` element.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
наблюдатель коуч клиент div.t-input-group > div.t-input-block > div.t-select__wrapper > select#input_1762624253478

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.t228__maincontainer > div.t228__leftside > div.t228__leftcontainer > a.t228__imgwrapper div.t228__maincontainer > div.t228__leftside > div.t228__leftcontainer > a.t228__imgwrapper
div.t396 > div.t396__artboard > div.t396__elem > a.tn-atom div.t396 > div.t396__artboard > div.t396__elem > a.tn-atom
div.t396 > div.t396__artboard > div.t396__elem > a.tn-atom div.t396 > div.t396__artboard > div.t396__elem > a.tn-atom
div.t-persons-social-links > div.t-persons-social-links__wrapper > div.t-persons-social-links__item > a div.t-persons-social-links > div.t-persons-social-links__wrapper > div.t-persons-social-links__item > a
div.t-persons-social-links > div.t-persons-social-links__wrapper > div.t-persons-social-links__item > a div.t-persons-social-links > div.t-persons-social-links__wrapper > div.t-persons-social-links__item > a
div.t-persons-social-links > div.t-persons-social-links__wrapper > div.t-persons-social-links__item > a div.t-persons-social-links > div.t-persons-social-links__wrapper > div.t-persons-social-links__item > a
div.t-persons-social-links > div.t-persons-social-links__wrapper > div.t-persons-social-links__item > a div.t-persons-social-links > div.t-persons-social-links__wrapper > div.t-persons-social-links__item > a
div.t-persons-social-links > div.t-persons-social-links__wrapper > div.t-persons-social-links__item > a div.t-persons-social-links > div.t-persons-social-links__wrapper > div.t-persons-social-links__item > a
div.t-persons-social-links > div.t-persons-social-links__wrapper > div.t-persons-social-links__item > a div.t-persons-social-links > div.t-persons-social-links__wrapper > div.t-persons-social-links__item > a
div.t-persons-social-links > div.t-persons-social-links__wrapper > div.t-persons-social-links__item > a div.t-persons-social-links > div.t-persons-social-links__wrapper > div.t-persons-social-links__item > a
div.t-persons-social-links > div.t-persons-social-links__wrapper > div.t-persons-social-links__item > a div.t-persons-social-links > div.t-persons-social-links__wrapper > div.t-persons-social-links__item > 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.

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-*]` attributes match their roles
●`[aria-hidden="true"]` is not present on the document `<body>`
●`[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]` values are valid
●`[aria-*]` attributes have valid values
●`[aria-*]` attributes are valid and not misspelled
●Buttons have an accessible name
●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
●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.
●Deprecated ARIA roles were not used
●Identical links have the same purpose.
○`[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
○`[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
○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
○Heading elements appear in a sequentially-descending order
○`<html>` element has a valid value for its `[lang]` attribute
○`<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
○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