owen.ru website review

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

26 images could be 448 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 850 ms faster on a phone.

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

About 80 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 300 ms faster on a phone.

About 329 KiB of JavaScript is downloaded but never used on this page.

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

8 third-party services load with your homepage (webvisor.org, Yandex Metrica and mail.ru and others), adding 331 KiB and 282 ms of main-thread time.

12 KiB could be saved by minifying CSS.

141 KiB could be saved by minifying JavaScript.

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

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

Desktop scores 97 but mobile only 56. A gap that wide usually means heavy scripts and images that hit phones hardest.

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

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.

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

Your largest element takes 4.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “35”.

The layout shifts by 0.357 while loading, so content jumps under the reader's thumb. Good is under 0.1.

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

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

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

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

Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 1.4 s to 1.3 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

7 images (348 KiB) are JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.

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

Some list items are not inside a list.

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

2 tap targets are too small or too close together to hit reliably with a finger.

All page content should be contained by landmarks: 99 elements on the page fail this check, rated moderate by axe-core.

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

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

13 visible links have no text or label, so screen readers cannot say where they go.

1 form field has no label, so screen readers announce an empty box and autofill guesses.

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

Your title is 115 characters, so Google will cut it off around 60: “Контрольно-измерительные приборы ОВЕН: датчики, контроллеры, регуляторы, измерители, блок…”.

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

No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

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

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

No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

Open Graph is missing og:description, so shared links fall back to guesses.

No twitter:card tag. X falls back to Open Graph, which is incomplete here.

The homepage links to 671 pages on owen.ru and 22 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.

https://owen.ru/contact_form is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

https://owen.ru/address/36251584, https://owen.ru/zavod_423, https://owen.ru/regional_nie_dileri, https://owen.ru/spisok_sistemnih_integratorov, https://owen.ru/servisnie_centri and https://owen.ru/contact_form have no meta description, so Google writes the search snippet from whatever text it finds.

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

https://owen.ru/address/36251584, https://owen.ru/zavod_423, https://owen.ru/regional_nie_dileri, https://owen.ru/spisok_sistemnih_integratorov, https://owen.ru/catalog/analizatori_zhidkosti and https://owen.ru/catalog/kontrolleri_dlya_sistem_ventilyatcii_otopleniya_i_gvs and 4 others have 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 15 pages linked from your homepage (of 183 found) and read each the way a search engine does.

94 of 158 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

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

2 errors were logged to the browser console while the page loaded, for example “cannot call methods on slider prior to initialization; attempted to call method 'option'”.

2 images are served at too low a resolution for sharp phone screens.

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.

Social proof on the homepage: 3 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.

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

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

The homepage carries about 633 words of visible text.

Before a visitor clicks anything, the page loads Yandex Metrica (measured from a US location before any click). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.

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