tmktools.ru website review

164 images could be 6.8 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.5 s faster on a phone.

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

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

8 third-party services load with your homepage (Google CDN, Yandex Metrica and mail.ru and others), adding 1.0 MB and 1.2 s of main-thread time.

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

Google CDN costs a phone 580 ms of main-thread work and 743 KiB 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.

1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 650 ms.

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

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

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

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

Polyfills for old browsers add 44 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.

4 KiB could be saved by minifying JavaScript.

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.

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

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

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

Your largest element takes 4.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image. Most of its time is resource load delay (1.8 s).

Real visitors wait 201 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

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

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

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

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

Your homepage downloads 18.8 MB in 663 requests on a phone: images 16.7 MB (608), scripts 1,019 KiB (19) and other files 458 KiB (25). Under 2 MB keeps phones on slow connections fast.

40 images (2.4 MB) 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.

5 images are downloaded at several times the size a phone draws them, for example 5bb4f06b6eb72d3e8358179bf8ed7be3303aeec5.png at 997 px wide, shown at 279 px. Resized copies would save about 286 KiB.

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

314 elements hidden from screen readers can still receive keyboard focus.

1 button has no accessible name, so screen readers announce just “button”.

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

Elements must only use permitted ARIA attributes: 5 elements on the page fail this check, rated serious by axe-core.

1 frame has no title, so screen-reader users cannot tell what it contains.

Some lists contain elements other than list items, which screen readers announce wrongly.

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

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

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

2 form fields have no label, so screen readers announce an empty box and autofill guesses.

Alternative text of images should not be repeated as text: 5 elements on the page fail this check, rated minor by axe-core.

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

Your title is 114 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.

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

No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

The homepage links to 2,068 pages on tmktools.ru and 19 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.

robots.txt blocks Applebot-Extended, which collect pages to train models. That's a legitimate choice and doesn't by itself stop the site appearing in AI answers, which the crawlers above handle.

https://www.tmktools.ru/catalog/sales, https://www.tmktools.ru/compare and https://www.tmktools.ru/personal/favorite all use the title “Интернет-магазин ТМК Инструмент в Нижнем Новгороде - электроинструмен…”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.tmktools.ru/company, https://www.tmktools.ru/vacancies, https://www.tmktools.ru/contacts, https://www.tmktools.ru/catalog/sales, https://www.tmktools.ru/compare and https://www.tmktools.ru/personal/favorite use the same meta description. A description written for each page earns more clicks.

Your homepage links to 6 pages by a URL that isn't their canonical one, for example https://www.tmktools.ru/index.php/catalog/instrumenty, whose canonical is https://www.tmktools.ru/catalog/instrumenty. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://www.tmktools.ru/shops, https://www.tmktools.ru/company, https://www.tmktools.ru/vacancies, https://www.tmktools.ru/contacts, https://www.tmktools.ru/catalog/sales and https://www.tmktools.ru/compare and 7 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.tmktools.ru/shops, https://www.tmktools.ru/company, https://www.tmktools.ru/vacancies, https://www.tmktools.ru/contacts, https://www.tmktools.ru/catalog/sales and https://www.tmktools.ru/compare and 7 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.

https://www.tmktools.ru/company, https://www.tmktools.ru/vacancies, https://www.tmktools.ru/contacts, https://www.tmktools.ru/catalog/sales, https://www.tmktools.ru/compare and https://www.tmktools.ru/personal/favorite and 4 others took over 3 s to send their HTML from our server.

We fetched 15 pages linked from your homepage (of 197 found) and read each the way a search engine does.

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_TUNNEL_CONNECTION_FAILED”.

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 analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

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

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

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