m2.ru website review

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

About 1.8 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 5.8 s faster on a phone.

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

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

36 files are served with short cache lifetimes, so returning visitors download them again (1.1 MB).

6 third-party services load with your homepage (yandex.ru, Google Tag Manager and Yandex Metrica and others), adding 1.2 MB and 897 ms of main-thread time.

yandex.ru costs a phone 570 ms of main-thread work and 889 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.

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

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

8 images could be 157 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

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

7 KiB JavaScript is shipped twice across bundles.

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.

Your largest element takes 22.1 s to render on a phone. Google's threshold for “good” is 2.5 s.

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

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

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

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

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

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

Your homepage downloads 7.2 MB in 218 requests on a phone: scripts 3.9 MB (80), images 2.1 MB (83) and stylesheets 510 KiB (5). Under 2 MB keeps phones on slow connections fast.

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

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

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

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

Interactive controls must not be nested: 1 element on the page fails this check, rated serious by axe-core.

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

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

Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

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

Your title is 66 characters, so Google will cut it off around 60: “Метр квадратный (М2): новостройки, ипотека, сделки с недвижимостью”.

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

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

Your <h1> is empty.

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

The homepage links to 243 pages on m2.ru and 14 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://m2.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://m2.ru/personal-area is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

https://m2.ru/personal-area has no meta description, so Google writes the search snippet from whatever text it finds.

https://m2.ru/personal-area has no <h1> headline, so visitors and search engines get no clear main topic.

https://m2.ru/ipoteka, https://m2.ru/ipoteka/na-zhile-na-pervichnom-rynke, https://m2.ru/services/checkup and https://m2.ru/legal-advice 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://m2.ru/personal-area, https://m2.ru/ipoteka, https://m2.ru/ipoteka/na-zhile-na-pervichnom-rynke, https://m2.ru/services/checkup and https://m2.ru/legal-advice took over 3 s to send their HTML from our server.

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

8 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

Large scripts ship without source maps.

Chrome logged issues while loading the page (“Cookie”).

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.

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

Before a visitor clicks anything, the page loads Google Tag Manager (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 5 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 2 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.