keng.ru website review

About 446 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.5 s faster on a phone.

Your mobile performance score is 69 (desktop: 78). Pages that score under 90 lose visitors before the first paint.

2 files block the first paint until they finish downloading. Deferring or inlining them could save about 900 ms.

5 long tasks block the main thread while loading, the longest for 283 ms. During a long task the page ignores taps.

4 files are served with short cache lifetimes, so returning visitors download them again (83 KiB).

2 third-party services load with your homepage (mail.ru and Yandex Metrica), adding 130 KiB and 68 ms of main-thread time.

Polyfills for old browsers add 34 KiB JavaScript that modern phones do not need.

About 13 KiB of CSS is downloaded but never applied on this page.

Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.

Your largest element takes 4.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Женщины”.

The page becomes fully interactive after 9.3 s. Good is under 3.8 s.

Visually, the page fills in at 6.4 s (Speed Index). Good is under 3.4 s.

Real visitors see the first content after 2.1 s (75th percentile). Good is under 1.8 s.

Real visitors wait 1.5 s for your server to start answering (75th percentile). Good is under 800 ms.

Scripts block taps and scrolling for 328 ms in total while the page loads. Good is under 200 ms.

Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 163 ms to 171 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

image is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

By the Sustainable Web Design model, a visit to your homepage emits about 0.43 g of CO₂e: 51.1 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

ARIA dialog and alertdialog nodes should have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

4 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

1 visible link has no text or label, so screen readers cannot say where it goes.

There is no <h1>, so neither visitors nor Google get a clear main headline.

Your title is only 13 characters: “Выбор раздела”. Between 30 and 65 characters leaves room to say what you do and for whom.

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

Your meta description is 233 characters; Google truncates after about 160, so the end of your pitch is cut.

The homepage links to only 1 page on your own site, so visitors and crawlers find few routes into the rest of it.

There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

There is no https://www.keng.ru/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.

https://www.keng.ru/welcome and / all use the title “Выбор раздела”. Search engines can't tell which page to show for a search, so each competes with the others.

Your homepage links to 1 page by a URL that isn't its canonical one, for example /, whose canonical is https://www.keng.ru/welcome. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

/ has no <h1> headline, so visitors and search engines get no clear main topic.

We fetched 1 page linked from your homepage and read each the way a search engine does.

The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

Large scripts ship without source maps.

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

The homepage has only about 0 words of visible text; thin pages give Google and first-time buyers little to go on.

There is no form on the homepage, so every lead has to click through to another page first.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

No known cookie consent tool loads with the page. Some sites build their own banner, and some only show one to visitors from the EU.

Loading the homepage contacts 1 host run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.