miratorg.ru website review

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

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

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

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

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

The HTML itself could arrive about 950 ms sooner: redirects, a slow server response or missing compression delay everything after it.

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

The page goes through 1 redirect before it starts loading, costing about 810 ms. Link and advertise the final URL directly.

176 KiB could be saved by minifying JavaScript.

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

Yandex CDN costs a phone 99 ms of main-thread work and 306 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.

5 third-party services load with your homepage (yandex.ru, Yandex CDN and Yandex Metrica and others), adding 711 KiB and 316 ms of main-thread time.

22 KiB could be saved by minifying CSS.

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

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

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

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

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.

Real visitors wait 4.8 s for the largest content to appear (75th percentile). Good is under 2.5 s.

For real visitors the layout shifts by 0.61 (75th percentile). Good is under 0.1.

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

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

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

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

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

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

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

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

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

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

Your homepage downloads 12.5 MB in 128 requests on a phone: images 10.7 MB (50), scripts 1.3 MB (38) and fonts 301 KiB (9). Under 2 MB keeps phones on slow connections fast.

5 images (505 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 3.54 g of CO₂e: 424.5 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

3 buttons have no accessible name, so screen readers announce just “button”.

1 element use ARIA attributes their role does not allow, which confuses screen readers.

Certain ARIA roles must contain particular children: 1 element on the page fails this check, rated critical by axe-core.

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

ARIA input fields must have an accessible name: 3 elements on the page fail this check, rated serious by axe-core.

Interactive controls must not be nested: 2 elements on the page fail this check, rated serious by axe-core.

ARIA toggle fields must have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

<html> element must have a lang attribute: 1 element on the page fails this check, rated serious by axe-core.

Heading levels should only increase by one: 2 elements on the page fail this check, rated moderate by axe-core.

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

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

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

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

Elements marked as presentational should be consistently ignored: 1 element on the page fails this check, rated minor by axe-core.

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

There are 4 <h1> headlines (“Аренда и оказание услуг по сельхозоборудованию”, “Возьмем в аренду сельхозтехнику” and “Производство желатина”). One clear main headline is easier for people and search engines.

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

No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

8 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

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

The homepage links to 44 pages on miratorg.ru and 10 external pages.

A phone browser shows 1,190 words, but the HTML your server sends has only 20. GPTBot, ClaudeBot and PerplexityBot read that HTML without running JavaScript, so they see an almost empty page. Server-side rendering or pre-rendering fixes 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://miratorg.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.

robots.txt blocks CCBot, 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://miratorg.ru/contacts, https://miratorg.ru/purchasegrain, https://miratorg.ru/procurement and https://miratorg.ru/luch use the same meta description. A description written for each page earns more clicks.

https://miratorg.ru/products/brand/arendaiuslugi, https://miratorg.ru/products/brand/zhelatin, https://miratorg.ru/products/brand/proizvodstvo-kombikormov, https://miratorg.ru/products/brand/osmotr, https://miratorg.ru/purchasegrain and https://miratorg.ru/burger-n-fries and 4 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://miratorg.ru/about, https://miratorg.ru/contacts, https://miratorg.ru/products/brand/arendaiuslugi, https://miratorg.ru/products/brand/zhelatin, https://miratorg.ru/products/brand/proizvodstvo-kombikormov and https://miratorg.ru/products/brand/osmotr and 9 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://miratorg.ru/about, https://miratorg.ru/products/brand/arendaiuslugi and https://miratorg.ru/products/brand/zhelatin took over 3 s to send their HTML from our server.

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

On a 390 px-wide phone the page scrolls sideways, a sign that something is wider than the screen.

1 error was logged to the browser console while the page loaded, for example “Bad element for Flickity: null”.

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