otdel24.ru website review

26 files block the first paint until they finish downloading. Deferring or inlining them could save about 5.2 s.

About 189 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.1 s faster on a phone.

Your mobile performance score is 44. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

3 images could be 1.4 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

4 third-party services load with your homepage (Google CDN, bitrix24.ru and Other Google APIs/SDKs and others), adding 3.6 MB and 981 ms of main-thread time.

About 710 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 420 ms faster on a phone.

Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 850 ms).

Google CDN costs a phone 702 ms of main-thread work and 1.1 MB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

bitrix24.ru costs a phone 217 ms of main-thread work and 2.4 MB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

A phone's processor spends 3.4 s on main-thread work while loading, 1.8 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

The page has 1,724 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

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

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

4 KiB JavaScript is shipped twice across bundles.

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

Your largest element takes 14.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Битрикс24 помогает бизнесу работать Единый сервис со всем н…”.

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

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

The first text or image appears after 3.1 s on a phone. Good is under 1.8 s.

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

11 images have no width and height attributes, so the layout jumps as each one loads.

Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

Your homepage downloads 5.2 MB in 104 requests on a phone: images 2.0 MB (12), scripts 1.6 MB (45) and fonts 888 KiB (8). Under 2 MB keeps phones on slow connections fast.

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

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

1 link inside paragraphs relies on colour alone to stand out.

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.

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

Headings should not be empty: 2 elements on the page fail this check, rated minor by axe-core.

Headings skip levels (h2 → h5, h2 → h5 and h2 → h5), which makes the page harder to scan with a screen reader.

No meta description, so Google writes its own snippet from whatever text it finds.

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

Your title is only 23 characters: “Сайт партнера Битрикс24”. 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.

No XML sitemap at https://otdel24.ru/sitemap.xml, so Google discovers your pages only by following links.

1 link has no real href, so search engines can't follow it.

The homepage links to 22 pages on otdel24.ru and 6 external pages.

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://otdel24.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://otdel24.ru/privacy has no meta description, so Google writes the search snippet from whatever text it finds.

https://otdel24.ru/privacy has no <h1> headline, so visitors and search engines get no clear main topic.

https://otdel24.ru/privacy has under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

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

1 image is served at too low a resolution for sharp phone screens.

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.

The homepage has only about 69 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.

Opening the homepage sets 1 cookie (measured from a US location before any click).

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 4 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.