C — https://bget.ru | BeaverCheck Audit

Site Health

Score: 75 / 100

Based on 8 categories, 0 sections

Fast site — your users get a smooth experience.

Several missing protections leave your users and data exposed.

Several issues make your site difficult for assistive technology users.

Solid SEO basics — a few optimizations could boost rankings.

Solid infrastructure — fast server responses across the board.

Mostly compliant — a few items need attention.

Missing metadata means poor previews on social media and search.

Lean and efficient — low environmental impact per visit.

How is this calculated?

The overall score is a weighted average of individual category scores. Categories with more impact on user experience and security carry more weight.

Performance 25%Security 25%Accessibility 15%SEO 10%Infrastructure 10%Compliance 8%Content 5%Sustainability 2%

Weights reflect general web best practices. Individual needs may differ.

How the composite score is calculated

How you compare

Google Font API · 938 peers

You 75

Avg 73

At average

0 50 100

Better than 66% of Google Font API sites See full Google Font API benchmark →

Tailwind CSS · 1169 peers

You 75

Avg 74

At average

0 50 100

Better than 57% of Tailwind CSS sites See full Tailwind CSS benchmark →

Top Priorities (5)

Content-Security-Policy header is missing

Security gaps expose your site and users to attacks, eroding trust.

Security › Security Headers

HSTS header is missing

Security gaps expose your site and users to attacks, eroding trust.

Security › Security Headers

No Content-Security-Policy header found

Security gaps expose your site and users to attacks, eroding trust.

Security › Content Security Policy

2 image(s) missing alt attribute

Accessibility issues exclude users with disabilities — up to 15% of your potential audience.

Accessibility › Alt Text Quality

No <main> landmark found

Accessibility issues exclude users with disabilities — up to 15% of your potential audience.

Accessibility › Landmark Structure

View fix priority matrix

Fix Priority Matrix

5 findings

Impact

Quick Wins

High impact, low effort — start here.

Strategic

High impact, requires investment.

Easy Improvements

Small gains, minimal effort.

Nothing in this quadrant — good news.

Deprioritize

Low impact, high effort — do last.

Nothing in this quadrant — good news.

← Low effort High effort →

Embed this badge

Markdown

[![BeaverCheck](https://beavercheck.com/badge?url=https%3A%2F%2Fbget.ru)](https://beavercheck.com/results/685c6ff7-1a80-4c99-8999-ed5d4b092def)

HTML

<a href="https://beavercheck.com/results/685c6ff7-1a80-4c99-8999-ed5d4b092def"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fbget.ru" alt="BeaverCheck Score"></a>

Image URL

https://beavercheck.com/badge?url=https%3A%2F%2Fbget.ru

This badge auto-updates with your latest scan result.

What fixing these means

Your site performs reasonably well, but a few targeted fixes could meaningfully improve results. Accessibility issues exclude users who rely on assistive technology — an estimated 15% of your potential audience. Addressing the critical issues below would have the most immediate impact on your user trust.

3 security gaps detected — browsers may warn visitors about your site.

2 accessibility issues exclude users who rely on assistive technology.

Conversion Barriers

1 critical 8 warning

9 barrier(s) likely increasing bounce by ~31%.

Speed (1)

Page takes 5.6s to load

+12% bounce

Users abandon at ~3s — you're 3.1s over the 2.5s threshold

Fix: Optimize render-blocking resources, preload the hero image, and compress images

Trust (2)

No HSTS header

+1% bounce

Returning visitors are briefly exposed to downgrade attacks on first request

Fix: Set Strict-Transport-Security: max-age=31536000; includeSubDomains

No Content-Security-Policy header

+1% bounce

Higher XSS blast radius — one compromised script can exfiltrate the checkout form

Fix: Ship a reporting-only CSP first, then enforce once violations are clean

Usability (1)

Layout shifts during page load

+3% bounce

Content movement causes mis-clicks on CTAs and form fields

Fix: Add width/height to images; reserve space for late-loading embeds

Content (3)

No Open Graph tags

+2% bounce

Links shared on LinkedIn / Slack / Facebook show bare URLs — referral clicks drop

Fix: Add og:title, og:description, og:image, og:url to the page head

No structured data

+2% bounce

No rich-result eligibility in Google — lower SERP CTR vs competitors with stars and prices

Fix: Add JSON-LD for your page type (Product, Article, FAQPage, LocalBusiness, …)

Thin content

+3% bounce

Under 300 words — visitors bounce looking for substance, search engines rank competitors first

Fix: Add a substantive FAQ, product detail, or case-study section

Navigation (2)

No skip-to-content link

+1% bounce

Keyboard and screen-reader users must tab through the entire header on every page

Fix: Add a visible-on-focus <a href="#main">Skip to content</a> as the first focusable element

2 broken link(s) on the page

+3% bounce

Clicks land on 404s — trust drops and the session often ends

Fix: Fix or remove the broken destinations surfaced on the Content tab

Preliminary CRO audit — each barrier links to the tab with detailed analysis.

Return on Investment

₽15,750 investment → ₽93,570/month returns

Payback period: < 1 month First-year ROI: +7029%

Investment

₽15,750

4h · 5 findings

Monthly returns

₽93,570 /mo

~₽1,122,834 / year

Conversions recovered ₽93,557
Bandwidth savings ₽13

Regulatory risk avoided

No applicable regulations in this jurisdiction

Payback period

0 12mo 24mo

₽5,250 — in quick wins — start here for the fastest payback

Figures combine localized regulatory fine ceilings, search/conversion value priced against local CPC, and bandwidth waste estimates. Results depend on implementation quality and audience composition. Not legal or financial advice.

Full methodology & sources

Estimated Remediation Cost

₽15,750

4.5 developer hours at ₽3500/hr

Based on Russia rates (₽3500/hr)

Quick wins

₽5,250 3 fixes in ~90 minutes

Start here for the best return on investment

Cost by category

Cost by effort level

Adjust assumptions

Custom rate

₽ /hr

Rates reflect fully-loaded developer cost including overhead

How developer rates are sourced

What Inaction Is Costing You

₽13 / month at risk

~₽151 / year if left unfixed

Bandwidth Waste

₽13 /mo

1734.6 MB/mo × 7.273 RUB/GB

Optimize transfer: save ~173 KB per page load
Saves ₽13/mo

Compliance figures represent the statutory maximum fine for the most severe triggered category, capped per regulation — not the sum of per-finding penalties. Based on published regulatory fine ranges. This is not legal advice.

Compliance methodology · SEO assumptions · Bandwidth model

Your performance is already good — improvements may show diminishing returns

Monthly visitors

Unique monthly visitors from your analytics

Conversion rate (%)

Purchases, signups, or key actions

Avg. order value

Optional — for revenue estimation

additional conversions/month

more engaged visitors from reduced bounce

potential monthly revenue

Current bounce (est.)

After fixes (est.)

Estimated bounce reduction

Fix 5 critical issues to capture this value

How this is calculated

Based on Google/Deloitte research ("Milliseconds Make Millions") showing a ~7% bounce rate increase per additional second of LCP above the 2.5s "Good" threshold.

Your site's LCP: → estimated after fixes.

These are estimates based on industry research — actual results vary

Bounce-rate model & assumptions

Your data stays in your browser — nothing is sent to our servers

Was this report useful?

Thanks for your feedback!

We'll use a cached audit if available, or offer to scan.

Checking for existing audit...

Press ? for shortcuts

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse.

Performance

Accessibility

100

Best Practices

SEO

Core Web Vitals

Key metrics that affect user experience.

First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.

2.98 s

Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.

5.57 s

Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.

0 ms

Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.

0.228

Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.

3.14 s

Time to Interactive Time to Interactive — how long until the page is fully interactive and responds to user input. Under 3.8s is good.

5.57 s

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

Shipping ES5 transpiled code to modern browsers wastes bytes — every user with an evergreen browser pays for compatibility you don't need.

Learn more ▾

Most users today run browsers that natively support ES6+, async/await, optional chaining, and the rest of modern JavaScript. Transpiling to ES5 'just in case' adds 20-40% to your bundle for no benefit. Configure your build to target a modern browserslist, or ship a differential bundle pair (modern + legacy) with the module/nomodule pattern.

Source: Google web.dev / Lighthouse

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
bget.ru/images/octopus@2x.png	0.0 ms	476.8 KiB
bget.ru/images/logo@2x.png	0.0 ms	19.3 KiB

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.228366] map[node:map[boundingRect:map[bottom:921 height:805 left:20 right:392 top:116 width:372] lhId:page-3-DIV nodeLabel:Bget.ru Это технический домен, который бесплатно предоставлялся клиентам хости… path:1,HTML,1,BODY,0,DIV,1,DIV selector:body > div.content > div.align-items-center snippet:<div class="align-items-center row"> type:node] score:0.228366 subItems:map[items:[map[cause:Unsized image element extra:map[boundingRect:map[bottom:112 height:92 left:106 right:306 top:20 width:200] lhId:page-1-IMG nodeLabel:body > div.content > div.text-center > img.logo-image path:1,HTML,1,BODY,0,DIV,0,DIV,0,IMG selector:body > div.content > div.text-center > img.logo-image snippet:<img class="logo-image" src="https://bget.ru/images/logo@2x.png" srcset="/images/logo@2x.png 2x"> type:node]]] type:subitems]]]

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
div.content > div.align-items-center > div.text-center > img.side-image `div.content > div.align-items-center > div.text-center > img.side-image`	bget.ru/images/octopus@2x.png	476.1 KiB	462.4 KiB
body > div.content > div.text-center > img.logo-image `body > div.content > div.text-center > img.logo-image`	bget.ru/images/logo@2x.png	19.2 KiB	6.6 KiB

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.

URL	Transfer Size	Duration
/css2?family=PT+Sans+Caption&family=PT+Sans:wght@400;700&...	1.1 KiB	176 ms
fonts.googleapis.com/css?family=PT+Sans&subset=cyrillic,latin-ext	566 B	835 ms

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
Bget.ru Это технический домен, который бесплатно предоставлялся клиентам хости… `body > div.content > div.align-items-center`	0.228

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

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.content > div.align-items-center > div.text-center > img.side-image `div.content > div.align-items-center > div.text-center > img.side-image`	bget.ru/images/octopus@2x.png
body > div.content > div.text-center > img.logo-image `body > div.content > div.text-center > img.logo-image`	bget.ru/images/logo@2x.png

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

●Optimize viewport for mobile

●Max Potential First Input Delay 20 ms

●Minify CSS

●Minify JavaScript

●Reduce unused CSS

●Reduce unused JavaScript

●Avoids enormous network payloads Total size was 565 KiB

●JavaScript execution time 0.0 s

●Minimizes main-thread work 0.2 s

●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 80 ms

○INP breakdown

○LCP request discovery

○User Timing marks and measures

○Avoid long main-thread tasks

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

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
Bget.ru `div.content > div.align-items-center > div.col-100 > h1#information-title`
Наши услуги `div.align-items-center > div.col-100 > h2.mt-45 > a`
Хостинг `div.col-100 > div.row > div.col-50 > a`
VPS `div.col-100 > div.row > div.col-50 > a`
Домены `div.col-100 > div.row > div.col-50 > a`
Аренда серверов `div.col-100 > div.row > div.col-50 > a`
Перейти в панель управления `div.align-items-center > div.col-100 > h2.mt-45 > a`
support@beget.com `div.col-100 > div.contacts-block > div.d-flex > a`
abuse@beget.com `div.col-100 > div.contacts-block > div.d-flex > a`
+7 (800) 700-06-08 `div.col-100 > div.contacts-block > div.d-flex > a`
+380 (800) 802-192 `div.col-100 > div.contacts-block > div.d-flex > a`

These are opportunities to improve the legibility of your content.

Names and labels

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
body > div.content > div.text-center > img.logo-image `body > div.content > div.text-center > img.logo-image`
div.content > div.align-items-center > div.text-center > img.side-image `div.content > div.align-items-center > div.text-center > img.side-image`

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-hidden="true"]` is not present on the document `<body>`

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

●Document has a `<title>` element

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

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

●Links have a discernible name

●Touch targets have sufficient size and spacing.

●Heading elements appear in a sequentially-descending order

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

○Input buttons have discernible text.

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

○Form elements have associated labels

○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

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

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

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 lang="en">`	`Syntax not understood`
3	`<head>`	`Syntax not understood`
4	`<link href="https://fonts.googleapis.com/css?family=PT+Sans&subset=cyrillic,latin-ext" rel="stylesheet">`	`Unknown directive`
5	`<link rel="preconnect" href="https://fonts.googleapis.com">`	`Unknown directive`
6	`<link rel="preconnect" href="https://fonts.gstatic.com" crossorigin>`	`Unknown directive`
7	`<link href="https://fonts.googleapis.com/css2?family=PT+Sans+Caption&family=PT+Sans:wght@400;700&display=swap" rel="stylesheet"><meta charset="utf-8">`	`Unknown directive`
8	`<meta name="viewport" content="width=device-width, initial-scale=1">`	`Syntax not understood`
9	`<meta name="description" content="Это технический домен, предоставляемый клиентам хостинг-провайдера beget.com. Домен можно использовать для доступа к различным приложениям, установленным на виртуальном сервере или хостинге.">`	`Syntax not understood`
10	`<title>Beget</title>`	`Syntax not understood`
11	`<link rel="icon" type="image/x-icon" sizes="16x16" href="https://beget.com/favicon.ico">`	`Unknown directive`
12	`<link rel="shortcut icon" sizes="16x16" href="https://beget.com/favicon.png">`	`Unknown directive`
13	`<link rel="icon" type="image/x-icon" sizes="32x32" href="https://beget.com/favicon@2x.ico">`	`Unknown directive`
14	`<link rel="shortcut icon" sizes="32x32" href="https://beget.com/favicon@2x.png">`	`Unknown directive`
16	`<link rel="apple-touch-icon-precomposed" href="https://beget.com/apple-touch-icon-57x57-precomposed.png">`	`Unknown directive`
17	`<link rel="apple-touch-icon-precomposed" sizes="72x72" href="https://beget.com/apple-touch-icon-72x72-precomposed.png">`	`Unknown directive`
18	`<link rel="apple-touch-icon-precomposed" sizes="76x76" href="https://beget.com/apple-touch-icon-76x76-precomposed.png">`	`Unknown directive`
19	`<link rel="apple-touch-icon-precomposed" sizes="114x114" href="https://beget.com/apple-touch-icon-114x114-precomposed.png">`	`Unknown directive`
20	`<link rel="apple-touch-icon-precomposed" sizes="120x120" href="https://beget.com/apple-touch-icon-120x120-precomposed.png">`	`Unknown directive`
21	`<link rel="apple-touch-icon-precomposed" sizes="144x144" href="https://beget.com/apple-touch-icon-144x144-precomposed.png">`	`Unknown directive`
22	`<link rel="apple-touch-icon-precomposed" sizes="152x152" href="https://beget.com/apple-touch-icon-152x152-precomposed.png">`	`Unknown directive`
23	`<link rel="apple-touch-icon-precomposed" sizes="195x195" href="https://beget.com/apple-touch-icon-195x195-precomposed.png">`	`Unknown directive`
25	`<style>`	`Syntax not understood`
26	`body {`	`Syntax not understood`
27	`font-family: 'PT Sans', Arial, sans-serif;`	`Unknown directive`
28	`font-size: 16px;`	`Unknown directive`
29	`max-width: 1060px;`	`Unknown directive`
30	`min-width: 320px;`	`Unknown directive`
31	`margin: auto;`	`Unknown directive`
32	`}`	`Syntax not understood`
34	`.content {`	`Syntax not understood`
35	`width: auto;`	`Unknown directive`
36	`padding: 20px;`	`Unknown directive`
37	`margin: auto;`	`Unknown directive`
38	`}`	`Syntax not understood`
40	`.logo-image {`	`Syntax not understood`
41	`max-width: 200px;`	`Unknown directive`
42	`}`	`Syntax not understood`
44	`h1, h2 {`	`Syntax not understood`
45	`font-family: 'PT Sans Caption', Arial, sans-serif;`	`Unknown directive`
46	`font-style: normal;`	`Unknown directive`
47	`font-weight: normal;`	`Unknown directive`
48	`}`	`Syntax not understood`
50	`h1 {`	`Syntax not understood`
51	`font-size: 30px;`	`Unknown directive`
52	`line-height: 36px;`	`Unknown directive`
53	`color: #2FA3E7;`	`Unknown directive`
54	`margin: 0;`	`Unknown directive`
55	`}`	`Syntax not understood`
57	`h2 {`	`Syntax not understood`
58	`font-size: 20px;`	`Unknown directive`
59	`line-height: 26px;`	`Unknown directive`
60	`color: #2FA3E7;`	`Unknown directive`
61	`}`	`Syntax not understood`
63	`a {`	`Syntax not understood`
64	`color: #2FA3E7;`	`Unknown directive`
65	`text-decoration: none;`	`Unknown directive`
66	`}`	`Syntax not understood`
68	`.text-center {`	`Syntax not understood`
69	`text-align: center;`	`Unknown directive`
70	`}`	`Syntax not understood`
72	`.d-flex {`	`Syntax not understood`
73	`display: flex;`	`Unknown directive`
74	`}`	`Syntax not understood`
76	`.justify-content-between {`	`Syntax not understood`
77	`justify-content: space-between;`	`Unknown directive`
78	`}`	`Syntax not understood`
80	`.align-items-center {`	`Syntax not understood`
81	`align-items: center;`	`Unknown directive`
82	`}`	`Syntax not understood`
84	`.price {`	`Syntax not understood`
85	`font-size: 25px;`	`Unknown directive`
86	`font-weight: bold;`	`Unknown directive`
87	`}`	`Syntax not understood`
89	`.side-image {`	`Syntax not understood`
90	`max-height: 144px;`	`Unknown directive`
91	`}`	`Syntax not understood`
93	`.mt-5 {`	`Syntax not understood`
94	`margin-top: 5px!important;`	`Unknown directive`
95	`}`	`Syntax not understood`
97	`.mt-10 {`	`Syntax not understood`
98	`margin-top: 10px!important;`	`Unknown directive`
99	`}`	`Syntax not understood`
101	`.mt-20 {`	`Syntax not understood`
102	`margin-top: 20px!important;`	`Unknown directive`
103	`}`	`Syntax not understood`
105	`.mt-45 {`	`Syntax not understood`
106	`margin-top: 45px!important;`	`Unknown directive`
107	`}`	`Syntax not understood`
109	`.row {`	`Syntax not understood`
110	`display: flex;`	`Unknown directive`
111	`flex-wrap: wrap;`	`Unknown directive`
112	`}`	`Syntax not understood`
114	`.col-50 {`	`Syntax not understood`
115	`flex: 0 0 50%;`	`Unknown directive`
116	`max-width: 50%;`	`Unknown directive`
117	`}`	`Syntax not understood`
119	`.col-100 {`	`Syntax not understood`
120	`flex: 0 0 100%;`	`Unknown directive`
121	`max-width: 100%;`	`Unknown directive`
122	`}`	`Syntax not understood`
124	`@media (min-width: 576px) {`	`Unknown directive`
125	`.side-image {`	`Syntax not understood`
126	`max-height: 212px;`	`Unknown directive`
127	`}`	`Syntax not understood`
129	`.content {`	`Syntax not understood`
130	`width: 500px;`	`Unknown directive`
131	`max-width: 500px;`	`Unknown directive`
132	`}`	`Syntax not understood`
134	`.col-md-25 {`	`Syntax not understood`
135	`flex: 0 0 25%;`	`Unknown directive`
136	`max-width: 25%;`	`Unknown directive`
137	`}`	`Syntax not understood`
139	`.mt-md-0 {`	`Syntax not understood`
140	`margin-top: 0px!important;`	`Unknown directive`
141	`}`	`Syntax not understood`
142	`}`	`Syntax not understood`
144	`@media (min-width: 1024px) {`	`Unknown directive`
145	`.content {`	`Syntax not understood`
146	`width: 980px;`	`Unknown directive`
147	`max-width: 980px;`	`Unknown directive`
148	`}`	`Syntax not understood`
150	`.side-image {`	`Syntax not understood`
151	`max-height: 288px;`	`Unknown directive`
152	`}`	`Syntax not understood`
154	`.contacts-block {`	`Syntax not understood`
155	`max-width: 327px;`	`Unknown directive`
156	`}`	`Syntax not understood`
158	`.mr-lg-60 {`	`Syntax not understood`
159	`margin-right: 60px!important;`	`Unknown directive`
160	`}`	`Syntax not understood`
162	`.col-lg-50 {`	`Syntax not understood`
163	`flex: 0 0 50%;`	`Unknown directive`
164	`max-width: 50%;`	`Unknown directive`
165	`}`	`Syntax not understood`
166	`}`	`Syntax not understood`
167	`</style>`	`Syntax not understood`
168	`</head>`	`Syntax not understood`
169	`<body>`	`Syntax not understood`
170	`<div class="content">`	`Syntax not understood`
171	`<div class="text-center">`	`Syntax not understood`
172	`<img class="logo-image" src="/images/logo.png" srcset="/images/logo@2x.png 2x">`	`Syntax not understood`
173	`</div>`	`Syntax not understood`
174	`<div class="align-items-center row">`	`Syntax not understood`
175	`<div class="text-center col-100 col-lg-50 mt-20 mt-lg-0">`	`Syntax not understood`
176	`<img class="side-image mr-lg-60" src="/images/octopus.png" srcset="/images/octopus@2x.png 2x">`	`Syntax not understood`
177	`</div>`	`Syntax not understood`
178	`<div class="col-100 col-lg-50 mt-45">`	`Syntax not understood`
179	`<h1 id="information-title"></h1>`	`Syntax not understood`
180	`<p class="mt-20" id="information-body">`	`Syntax not understood`
181	`Это технический домен, предоставляемый клиентам beget.com`	`Syntax not understood`
182	`</p>`	`Syntax not understood`
183	`<h2 class="mt-45">`	`Syntax not understood`
184	`<a href="https://beget.com">`	`Unknown directive`
185	`Наши услуги`	`Syntax not understood`
186	`</a>`	`Syntax not understood`
187	`</h2>`	`Syntax not understood`
188	`<div class="row mt-20">`	`Syntax not understood`
189	`<div class="col-50 col-md-25">`	`Syntax not understood`
190	`<a href="https://beget.com/ru/hosting/virtual">Хостинг</a>`	`Unknown directive`
191	`<div class="mt-5">`	`Syntax not understood`
192	`от <span class="price">420 ₽</span>`	`Syntax not understood`
193	`</div>`	`Syntax not understood`
194	`</div>`	`Syntax not understood`
195	`<div class="col-50 col-md-25">`	`Syntax not understood`
196	`<a href="https://beget.com/ru/vps">VPS</a>`	`Unknown directive`
197	`<div class="mt-5">`	`Syntax not understood`
198	`от <span class="price">7 ₽</span>`	`Syntax not understood`
199	`</div>`	`Syntax not understood`
200	`</div>`	`Syntax not understood`
201	`<div class="col-50 col-md-25 mt-10 mt-md-0">`	`Syntax not understood`
202	`<a href="https://beget.com/ru/domains">Домены</a>`	`Unknown directive`
203	`<div class="mt-5">`	`Syntax not understood`
204	`от <span class="price">179 ₽</span>`	`Syntax not understood`
205	`</div>`	`Syntax not understood`
206	`</div>`	`Syntax not understood`
207	`<div class="col-50 col-md-25 mt-10 mt-md-0">`	`Syntax not understood`
208	`<a href="https://beget.com/ru/dedicated-servers">Аренда серверов</a>`	`Unknown directive`
209	`<div class="mt-5">`	`Syntax not understood`
210	`от <span class="price">9 300 ₽</span>`	`Syntax not understood`
211	`</div>`	`Syntax not understood`
212	`</div>`	`Syntax not understood`
213	`</div>`	`Syntax not understood`
214	`<h2 class="mt-45">`	`Syntax not understood`
215	`<a href="https://cp.beget.com">`	`Unknown directive`
216	`Перейти в панель управления`	`Syntax not understood`
217	`</a>`	`Syntax not understood`
218	`</h2>`	`Syntax not understood`
220	`<div class="contacts-block">`	`Syntax not understood`
221	`<div class="d-flex justify-content-between mt-20">`	`Syntax not understood`
222	`<strong>Тех. поддержка:</strong>`	`Unknown directive`
223	`<a href="mailto:support@beget.com">support@beget.com</a>`	`Unknown directive`
224	`</div>`	`Syntax not understood`
225	`<div class="d-flex justify-content-between mt-10">`	`Syntax not understood`
226	`<strong>Обработка жалоб:</strong>`	`Unknown directive`
227	`<a href="mailto:abuse@beget.com">abuse@beget.com</a>`	`Unknown directive`
228	`</div>`	`Syntax not understood`
229	`<div class="d-flex justify-content-between mt-10">`	`Syntax not understood`
230	`<strong>Россия:</strong>`	`Unknown directive`
231	`<a href="tel:+7 (800) 700-06-08">+7 (800) 700-06-08</a>`	`Unknown directive`
232	`</div>`	`Syntax not understood`
233	`<div class="d-flex justify-content-between mt-10">`	`Syntax not understood`
234	`<strong>Украина:</strong>`	`Unknown directive`
235	`<a href="tel:+380 (800) 802-192">+380 (800) 802-192</a>`	`Unknown directive`
236	`</div>`	`Syntax not understood`
237	`</div>`	`Syntax not understood`
238	`</div>`	`Syntax not understood`
239	`</div>`	`Syntax not understood`
240	`</div>`	`Syntax not understood`
241	`</body>`	`Syntax not understood`
242	`<script>`	`Syntax not understood`
243	`document.addEventListener("DOMContentLoaded", function(event) {`	`Syntax not understood`
244	`switch (window.location.hostname) {`	`Syntax not understood`
245	`case "beget.app":`	`Unknown directive`
246	`document.getElementById("information-title").innerText = "Beget.app";`	`Syntax not understood`
247	`document.getElementById("information-body").innerHTML = "Это технический домен, предоставляемый клиентам хостинг-провайдера beget.com, которые пользуются услугой VPS. Домен можно использовать для доступа к различным приложениям, установленным на виртуальном сервере.";`	`Syntax not understood`
248	`document.title = "beget.app";`	`Syntax not understood`
249	`break;`	`Syntax not understood`
250	`case "begetcdn.cloud":`	`Unknown directive`
251	`document.getElementById("information-title").innerText = "BegetCDN.cloud";`	`Syntax not understood`
252	`document.getElementById("information-body").innerHTML = "Это технический домен, предоставляемый клиентам хостинг-провайдера beget.com, которые пользуются услугой CDN. Его можно использовать для доступа к CDN-ресурсу.";`	`Syntax not understood`
253	`document.title = "begetcdn.cloud";`	`Syntax not understood`
254	`break;`	`Syntax not understood`
255	`case "beget.tech":`	`Unknown directive`
256	`document.getElementById("information-title").innerText = "Beget.tech";`	`Syntax not understood`
257	`document.getElementById("information-body").innerHTML = "Это технический домен, предоставляемый клиентам хостинг-провайдера beget.com. Его можно использовать на своё усмотрение — например, для тестирования сайтов.";`	`Syntax not understood`
258	`document.title = "beget.tech";`	`Syntax not understood`
259	`break;`	`Syntax not understood`
260	`case "bget.ru":`	`Unknown directive`
261	`document.getElementById("information-title").innerText = "Bget.ru";`	`Syntax not understood`
262	document.getElementById("information-body").innerHTML = "Это технический домен, который бесплатно предоставлялся клиентам хостинг-провайдера beget.com. Если этот домен присутствует на вашем аккаунте, его можно использовать на своё усмотрение — например, для тестирования сайтов до приобретения собственного домена.";	`Syntax not understood`
263	`document.title = "bget.ru";`	`Syntax not understood`
264	`break;`	`Syntax not understood`
265	`}`	`Syntax not understood`
266	`});`	`Syntax not understood`
267	`</script>`	`Syntax not understood`
268	`</html>`	`Syntax not understood`

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

Content Best Practices

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
body > div.content > div.text-center > img.logo-image `body > div.content > div.text-center > img.logo-image`
div.content > div.align-items-center > div.text-center > img.side-image `div.content > div.align-items-center > div.text-center > img.side-image`

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

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

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse. — Desktop

Performance

Accessibility

100

Best Practices

SEO

Core Web Vitals

Key metrics that affect user experience. — Desktop

First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.

790 ms

Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.

1.00 s

Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.

0 ms

Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.

0.033

Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.

790 ms

Time to Interactive Time to Interactive — how long until the page is fully interactive and responds to user input. Under 3.8s is good.

1.00 s

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.

Why this matters

Shipping ES5 transpiled code to modern browsers wastes bytes — every user with an evergreen browser pays for compatibility you don't need.

Learn more ▾

Source: Google web.dev / Lighthouse

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.

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

nodeLabel: div.content > div.align-items-center > div.text-center > img.side-image

path: 1,HTML,1,BODY,0,DIV,1,DIV,0,DIV,0,IMG

selector: div.content > div.align-items-center > div.text-center > img.side-image

snippet: <img class="side-image mr-lg-60" src="/images/octopus.png" srcset="/images/octopus@2x.png 2x">

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.

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

value: No additional origins are good candidates for preconnecting

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.

URL	Transfer Size	Duration
/css2?family=PT+Sans+Caption&family=PT+Sans:wght@400;700&...	707 B	66 ms
fonts.googleapis.com/css?family=PT+Sans&subset=cyrillic,latin-ext	937 B	284 ms

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
bget.ru/images/octopus.png	0.0 ms	155.9 KiB
bget.ru/images/logo.png	0.0 ms	8.0 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.

	URL	Resource Size	Est Savings
div.content > div.align-items-center > div.text-center > img.side-image `div.content > div.align-items-center > div.text-center > img.side-image`	bget.ru/images/octopus.png	155.6 KiB	137.6 KiB
body > div.content > div.text-center > img.logo-image `body > div.content > div.text-center > img.logo-image`	bget.ru/images/logo.png	7.8 KiB	4.7 KiB

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

Diagnostics

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.content > div.align-items-center > div.text-center > img.side-image `div.content > div.align-items-center > div.text-center > img.side-image`	bget.ru/images/octopus.png
body > div.content > div.text-center > img.logo-image `body > div.content > div.text-center > img.logo-image`	bget.ru/images/logo.png

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

●Layout shift culprits

●Document request latency

●Optimize DOM size

●Font display

●Forced reflow

●LCP breakdown

●Modern HTTP

●Optimize viewport for mobile

●Time to Interactive 1.0 s

●Max Potential First Input Delay 20 ms

●Minify CSS

●Minify JavaScript

●Reduce unused CSS

●Reduce unused JavaScript

●Avoids enormous network payloads Total size was 232 KiB

●Minimizes main-thread work 0.1 s

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 80 ms

●Server Backend Latencies 40 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 80 ms

●Avoid large layout shifts 4 layout shifts found

○INP breakdown

○User Timing marks and measures

○JavaScript execution time

○Avoid long main-thread tasks

○Avoid non-composited animations

Accessibility

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
Bget.ru `div.content > div.align-items-center > div.col-100 > h1#information-title`
Наши услуги `div.align-items-center > div.col-100 > h2.mt-45 > a`
Хостинг `div.col-100 > div.row > div.col-50 > a`
VPS `div.col-100 > div.row > div.col-50 > a`
Домены `div.col-100 > div.row > div.col-50 > a`
Аренда серверов `div.col-100 > div.row > div.col-50 > a`
Перейти в панель управления `div.align-items-center > div.col-100 > h2.mt-45 > a`
support@beget.com `div.col-100 > div.contacts-block > div.d-flex > a`
abuse@beget.com `div.col-100 > div.contacts-block > div.d-flex > a`
+7 (800) 700-06-08 `div.col-100 > div.contacts-block > div.d-flex > a`
+380 (800) 802-192 `div.col-100 > div.contacts-block > div.d-flex > a`

These are opportunities to improve the legibility of your content.

Names and labels

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
body > div.content > div.text-center > img.logo-image `body > div.content > div.text-center > img.logo-image`
div.content > div.align-items-center > div.text-center > img.side-image `div.content > div.align-items-center > div.text-center > img.side-image`

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-hidden="true"]` is not present on the document `<body>`

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

●Document has a `<title>` element

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

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

●Links have a discernible name

●Touch targets have sufficient size and spacing.

●Heading elements appear in a sequentially-descending order

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

○Input buttons have discernible text.

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

○Form elements have associated labels

○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

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

○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

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 lang="en">`	`Syntax not understood`
3	`<head>`	`Syntax not understood`
4	`<link href="https://fonts.googleapis.com/css?family=PT+Sans&subset=cyrillic,latin-ext" rel="stylesheet">`	`Unknown directive`
5	`<link rel="preconnect" href="https://fonts.googleapis.com">`	`Unknown directive`
6	`<link rel="preconnect" href="https://fonts.gstatic.com" crossorigin>`	`Unknown directive`
7	`<link href="https://fonts.googleapis.com/css2?family=PT+Sans+Caption&family=PT+Sans:wght@400;700&display=swap" rel="stylesheet"><meta charset="utf-8">`	`Unknown directive`
8	`<meta name="viewport" content="width=device-width, initial-scale=1">`	`Syntax not understood`
9	`<meta name="description" content="Это технический домен, предоставляемый клиентам хостинг-провайдера beget.com. Домен можно использовать для доступа к различным приложениям, установленным на виртуальном сервере или хостинге.">`	`Syntax not understood`
10	`<title>Beget</title>`	`Syntax not understood`
11	`<link rel="icon" type="image/x-icon" sizes="16x16" href="https://beget.com/favicon.ico">`	`Unknown directive`
12	`<link rel="shortcut icon" sizes="16x16" href="https://beget.com/favicon.png">`	`Unknown directive`
13	`<link rel="icon" type="image/x-icon" sizes="32x32" href="https://beget.com/favicon@2x.ico">`	`Unknown directive`
14	`<link rel="shortcut icon" sizes="32x32" href="https://beget.com/favicon@2x.png">`	`Unknown directive`
16	`<link rel="apple-touch-icon-precomposed" href="https://beget.com/apple-touch-icon-57x57-precomposed.png">`	`Unknown directive`
17	`<link rel="apple-touch-icon-precomposed" sizes="72x72" href="https://beget.com/apple-touch-icon-72x72-precomposed.png">`	`Unknown directive`
18	`<link rel="apple-touch-icon-precomposed" sizes="76x76" href="https://beget.com/apple-touch-icon-76x76-precomposed.png">`	`Unknown directive`
19	`<link rel="apple-touch-icon-precomposed" sizes="114x114" href="https://beget.com/apple-touch-icon-114x114-precomposed.png">`	`Unknown directive`
20	`<link rel="apple-touch-icon-precomposed" sizes="120x120" href="https://beget.com/apple-touch-icon-120x120-precomposed.png">`	`Unknown directive`
21	`<link rel="apple-touch-icon-precomposed" sizes="144x144" href="https://beget.com/apple-touch-icon-144x144-precomposed.png">`	`Unknown directive`
22	`<link rel="apple-touch-icon-precomposed" sizes="152x152" href="https://beget.com/apple-touch-icon-152x152-precomposed.png">`	`Unknown directive`
23	`<link rel="apple-touch-icon-precomposed" sizes="195x195" href="https://beget.com/apple-touch-icon-195x195-precomposed.png">`	`Unknown directive`
25	`<style>`	`Syntax not understood`
26	`body {`	`Syntax not understood`
27	`font-family: 'PT Sans', Arial, sans-serif;`	`Unknown directive`
28	`font-size: 16px;`	`Unknown directive`
29	`max-width: 1060px;`	`Unknown directive`
30	`min-width: 320px;`	`Unknown directive`
31	`margin: auto;`	`Unknown directive`
32	`}`	`Syntax not understood`
34	`.content {`	`Syntax not understood`
35	`width: auto;`	`Unknown directive`
36	`padding: 20px;`	`Unknown directive`
37	`margin: auto;`	`Unknown directive`
38	`}`	`Syntax not understood`
40	`.logo-image {`	`Syntax not understood`
41	`max-width: 200px;`	`Unknown directive`
42	`}`	`Syntax not understood`
44	`h1, h2 {`	`Syntax not understood`
45	`font-family: 'PT Sans Caption', Arial, sans-serif;`	`Unknown directive`
46	`font-style: normal;`	`Unknown directive`
47	`font-weight: normal;`	`Unknown directive`
48	`}`	`Syntax not understood`
50	`h1 {`	`Syntax not understood`
51	`font-size: 30px;`	`Unknown directive`
52	`line-height: 36px;`	`Unknown directive`
53	`color: #2FA3E7;`	`Unknown directive`
54	`margin: 0;`	`Unknown directive`
55	`}`	`Syntax not understood`
57	`h2 {`	`Syntax not understood`
58	`font-size: 20px;`	`Unknown directive`
59	`line-height: 26px;`	`Unknown directive`
60	`color: #2FA3E7;`	`Unknown directive`
61	`}`	`Syntax not understood`
63	`a {`	`Syntax not understood`
64	`color: #2FA3E7;`	`Unknown directive`
65	`text-decoration: none;`	`Unknown directive`
66	`}`	`Syntax not understood`
68	`.text-center {`	`Syntax not understood`
69	`text-align: center;`	`Unknown directive`
70	`}`	`Syntax not understood`
72	`.d-flex {`	`Syntax not understood`
73	`display: flex;`	`Unknown directive`
74	`}`	`Syntax not understood`
76	`.justify-content-between {`	`Syntax not understood`
77	`justify-content: space-between;`	`Unknown directive`
78	`}`	`Syntax not understood`
80	`.align-items-center {`	`Syntax not understood`
81	`align-items: center;`	`Unknown directive`
82	`}`	`Syntax not understood`
84	`.price {`	`Syntax not understood`
85	`font-size: 25px;`	`Unknown directive`
86	`font-weight: bold;`	`Unknown directive`
87	`}`	`Syntax not understood`
89	`.side-image {`	`Syntax not understood`
90	`max-height: 144px;`	`Unknown directive`
91	`}`	`Syntax not understood`
93	`.mt-5 {`	`Syntax not understood`
94	`margin-top: 5px!important;`	`Unknown directive`
95	`}`	`Syntax not understood`
97	`.mt-10 {`	`Syntax not understood`
98	`margin-top: 10px!important;`	`Unknown directive`
99	`}`	`Syntax not understood`
101	`.mt-20 {`	`Syntax not understood`
102	`margin-top: 20px!important;`	`Unknown directive`
103	`}`	`Syntax not understood`
105	`.mt-45 {`	`Syntax not understood`
106	`margin-top: 45px!important;`	`Unknown directive`
107	`}`	`Syntax not understood`
109	`.row {`	`Syntax not understood`
110	`display: flex;`	`Unknown directive`
111	`flex-wrap: wrap;`	`Unknown directive`
112	`}`	`Syntax not understood`
114	`.col-50 {`	`Syntax not understood`
115	`flex: 0 0 50%;`	`Unknown directive`
116	`max-width: 50%;`	`Unknown directive`
117	`}`	`Syntax not understood`
119	`.col-100 {`	`Syntax not understood`
120	`flex: 0 0 100%;`	`Unknown directive`
121	`max-width: 100%;`	`Unknown directive`
122	`}`	`Syntax not understood`
124	`@media (min-width: 576px) {`	`Unknown directive`
125	`.side-image {`	`Syntax not understood`
126	`max-height: 212px;`	`Unknown directive`
127	`}`	`Syntax not understood`
129	`.content {`	`Syntax not understood`
130	`width: 500px;`	`Unknown directive`
131	`max-width: 500px;`	`Unknown directive`
132	`}`	`Syntax not understood`
134	`.col-md-25 {`	`Syntax not understood`
135	`flex: 0 0 25%;`	`Unknown directive`
136	`max-width: 25%;`	`Unknown directive`
137	`}`	`Syntax not understood`
139	`.mt-md-0 {`	`Syntax not understood`
140	`margin-top: 0px!important;`	`Unknown directive`
141	`}`	`Syntax not understood`
142	`}`	`Syntax not understood`
144	`@media (min-width: 1024px) {`	`Unknown directive`
145	`.content {`	`Syntax not understood`
146	`width: 980px;`	`Unknown directive`
147	`max-width: 980px;`	`Unknown directive`
148	`}`	`Syntax not understood`
150	`.side-image {`	`Syntax not understood`
151	`max-height: 288px;`	`Unknown directive`
152	`}`	`Syntax not understood`
154	`.contacts-block {`	`Syntax not understood`
155	`max-width: 327px;`	`Unknown directive`
156	`}`	`Syntax not understood`
158	`.mr-lg-60 {`	`Syntax not understood`
159	`margin-right: 60px!important;`	`Unknown directive`
160	`}`	`Syntax not understood`
162	`.col-lg-50 {`	`Syntax not understood`
163	`flex: 0 0 50%;`	`Unknown directive`
164	`max-width: 50%;`	`Unknown directive`
165	`}`	`Syntax not understood`
166	`}`	`Syntax not understood`
167	`</style>`	`Syntax not understood`
168	`</head>`	`Syntax not understood`
169	`<body>`	`Syntax not understood`
170	`<div class="content">`	`Syntax not understood`
171	`<div class="text-center">`	`Syntax not understood`
172	`<img class="logo-image" src="/images/logo.png" srcset="/images/logo@2x.png 2x">`	`Syntax not understood`
173	`</div>`	`Syntax not understood`
174	`<div class="align-items-center row">`	`Syntax not understood`
175	`<div class="text-center col-100 col-lg-50 mt-20 mt-lg-0">`	`Syntax not understood`
176	`<img class="side-image mr-lg-60" src="/images/octopus.png" srcset="/images/octopus@2x.png 2x">`	`Syntax not understood`
177	`</div>`	`Syntax not understood`
178	`<div class="col-100 col-lg-50 mt-45">`	`Syntax not understood`
179	`<h1 id="information-title"></h1>`	`Syntax not understood`
180	`<p class="mt-20" id="information-body">`	`Syntax not understood`
181	`Это технический домен, предоставляемый клиентам beget.com`	`Syntax not understood`
182	`</p>`	`Syntax not understood`
183	`<h2 class="mt-45">`	`Syntax not understood`
184	`<a href="https://beget.com">`	`Unknown directive`
185	`Наши услуги`	`Syntax not understood`
186	`</a>`	`Syntax not understood`
187	`</h2>`	`Syntax not understood`
188	`<div class="row mt-20">`	`Syntax not understood`
189	`<div class="col-50 col-md-25">`	`Syntax not understood`
190	`<a href="https://beget.com/ru/hosting/virtual">Хостинг</a>`	`Unknown directive`
191	`<div class="mt-5">`	`Syntax not understood`
192	`от <span class="price">420 ₽</span>`	`Syntax not understood`
193	`</div>`	`Syntax not understood`
194	`</div>`	`Syntax not understood`
195	`<div class="col-50 col-md-25">`	`Syntax not understood`
196	`<a href="https://beget.com/ru/vps">VPS</a>`	`Unknown directive`
197	`<div class="mt-5">`	`Syntax not understood`
198	`от <span class="price">7 ₽</span>`	`Syntax not understood`
199	`</div>`	`Syntax not understood`
200	`</div>`	`Syntax not understood`
201	`<div class="col-50 col-md-25 mt-10 mt-md-0">`	`Syntax not understood`
202	`<a href="https://beget.com/ru/domains">Домены</a>`	`Unknown directive`
203	`<div class="mt-5">`	`Syntax not understood`
204	`от <span class="price">179 ₽</span>`	`Syntax not understood`
205	`</div>`	`Syntax not understood`
206	`</div>`	`Syntax not understood`
207	`<div class="col-50 col-md-25 mt-10 mt-md-0">`	`Syntax not understood`
208	`<a href="https://beget.com/ru/dedicated-servers">Аренда серверов</a>`	`Unknown directive`
209	`<div class="mt-5">`	`Syntax not understood`
210	`от <span class="price">9 300 ₽</span>`	`Syntax not understood`
211	`</div>`	`Syntax not understood`
212	`</div>`	`Syntax not understood`
213	`</div>`	`Syntax not understood`
214	`<h2 class="mt-45">`	`Syntax not understood`
215	`<a href="https://cp.beget.com">`	`Unknown directive`
216	`Перейти в панель управления`	`Syntax not understood`
217	`</a>`	`Syntax not understood`
218	`</h2>`	`Syntax not understood`
220	`<div class="contacts-block">`	`Syntax not understood`
221	`<div class="d-flex justify-content-between mt-20">`	`Syntax not understood`
222	`<strong>Тех. поддержка:</strong>`	`Unknown directive`
223	`<a href="mailto:support@beget.com">support@beget.com</a>`	`Unknown directive`
224	`</div>`	`Syntax not understood`
225	`<div class="d-flex justify-content-between mt-10">`	`Syntax not understood`
226	`<strong>Обработка жалоб:</strong>`	`Unknown directive`
227	`<a href="mailto:abuse@beget.com">abuse@beget.com</a>`	`Unknown directive`
228	`</div>`	`Syntax not understood`
229	`<div class="d-flex justify-content-between mt-10">`	`Syntax not understood`
230	`<strong>Россия:</strong>`	`Unknown directive`
231	`<a href="tel:+7 (800) 700-06-08">+7 (800) 700-06-08</a>`	`Unknown directive`
232	`</div>`	`Syntax not understood`
233	`<div class="d-flex justify-content-between mt-10">`	`Syntax not understood`
234	`<strong>Украина:</strong>`	`Unknown directive`
235	`<a href="tel:+380 (800) 802-192">+380 (800) 802-192</a>`	`Unknown directive`
236	`</div>`	`Syntax not understood`
237	`</div>`	`Syntax not understood`
238	`</div>`	`Syntax not understood`
239	`</div>`	`Syntax not understood`
240	`</div>`	`Syntax not understood`
241	`</body>`	`Syntax not understood`
242	`<script>`	`Syntax not understood`
243	`document.addEventListener("DOMContentLoaded", function(event) {`	`Syntax not understood`
244	`switch (window.location.hostname) {`	`Syntax not understood`
245	`case "beget.app":`	`Unknown directive`
246	`document.getElementById("information-title").innerText = "Beget.app";`	`Syntax not understood`
247	`document.getElementById("information-body").innerHTML = "Это технический домен, предоставляемый клиентам хостинг-провайдера beget.com, которые пользуются услугой VPS. Домен можно использовать для доступа к различным приложениям, установленным на виртуальном сервере.";`	`Syntax not understood`
248	`document.title = "beget.app";`	`Syntax not understood`
249	`break;`	`Syntax not understood`
250	`case "begetcdn.cloud":`	`Unknown directive`
251	`document.getElementById("information-title").innerText = "BegetCDN.cloud";`	`Syntax not understood`
252	`document.getElementById("information-body").innerHTML = "Это технический домен, предоставляемый клиентам хостинг-провайдера beget.com, которые пользуются услугой CDN. Его можно использовать для доступа к CDN-ресурсу.";`	`Syntax not understood`
253	`document.title = "begetcdn.cloud";`	`Syntax not understood`
254	`break;`	`Syntax not understood`
255	`case "beget.tech":`	`Unknown directive`
256	`document.getElementById("information-title").innerText = "Beget.tech";`	`Syntax not understood`
257	`document.getElementById("information-body").innerHTML = "Это технический домен, предоставляемый клиентам хостинг-провайдера beget.com. Его можно использовать на своё усмотрение — например, для тестирования сайтов.";`	`Syntax not understood`
258	`document.title = "beget.tech";`	`Syntax not understood`
259	`break;`	`Syntax not understood`
260	`case "bget.ru":`	`Unknown directive`
261	`document.getElementById("information-title").innerText = "Bget.ru";`	`Syntax not understood`
262	document.getElementById("information-body").innerHTML = "Это технический домен, который бесплатно предоставлялся клиентам хостинг-провайдера beget.com. Если этот домен присутствует на вашем аккаунте, его можно использовать на своё усмотрение — например, для тестирования сайтов до приобретения собственного домена.";	`Syntax not understood`
263	`document.title = "bget.ru";`	`Syntax not understood`
264	`break;`	`Syntax not understood`
265	`}`	`Syntax not understood`
266	`});`	`Syntax not understood`
267	`</script>`	`Syntax not understood`
268	`</html>`	`Syntax not understood`

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

Content Best Practices

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
body > div.content > div.text-center > img.logo-image `body > div.content > div.text-center > img.logo-image`
div.content > div.align-items-center > div.text-center > img.side-image `div.content > div.align-items-center > div.text-center > img.side-image`

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

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

Results for https://bget.ru

Site Health

How you compare

Top Priorities (5)

Fix Priority Matrix

Quick Wins

Strategic

Easy Improvements

Deprioritize

What fixing these means

Conversion Barriers

Speed (1)

Trust (2)

Usability (1)

Content (3)

Navigation (2)

Return on Investment

Investment

Monthly returns

Regulatory risk avoided

Payback period

Estimated Remediation Cost

Cost by category

Cost by effort level

What Inaction Is Costing You

Bandwidth Waste

Lighthouse Scores

Core Web Vitals

Detailed Report

Performance

Insights

Diagnostics

Accessibility

Contrast

Names and labels

Best practices

Best Practices

SEO

Crawling and Indexing

Content Best Practices

Lighthouse Scores

Core Web Vitals

Detailed Report

Performance

Insights

Diagnostics

Accessibility

Contrast

Names and labels

Best practices

Best Practices

SEO

Crawling and Indexing

Content Best Practices

Keyboard Shortcuts