mb-nn.ru website review

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

8 third-party services load with your homepage (YouTube, Google Tag Manager and Yandex Metrica and others), adding 1.8 MB and 1.1 s of main-thread time.

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

About 1.0 MB of JavaScript is downloaded but never used on this page.

Your mobile performance score is 82. Pages that score under 90 lose visitors before the first paint.

YouTube costs a phone 486 ms of main-thread work and 990 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.

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

Google Tag Manager costs a phone 195 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.

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

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

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

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

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

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

8 KiB could be saved by minifying CSS.

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

5 KiB could be saved by minifying JavaScript.

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

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

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

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

4 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 19.0 MB in 150 requests on a phone: images 10.4 MB (76), other files 5.7 MB (25) and scripts 1.8 MB (30). Under 2 MB keeps phones on slow connections fast.

35 images are downloaded at several times the size a phone draws them, for example Мегабайт.png at 3,393 px wide, shown at 200 px. Resized copies would save about 6.5 MB.

3 images weigh 1.6 MB together. On a phone connection a single image that size takes seconds.

40 images (9.6 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.

36 images further down the page (8.9 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

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

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

<dt> and <dd> elements must be contained by a <dl>: 67 elements on the page fail this check, rated serious by axe-core.

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

All page content should be contained by landmarks: 232 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.

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

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

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

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

1 tap target is too small or too close together to hit reliably with a finger.

ARIA role should be appropriate for the element: 4 elements on the page fail this check, rated minor by axe-core.

Elements marked as presentational should be consistently ignored: 4 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 69 characters, so Google will cut it off around 60: “ИТ-аутсорсинг в Нижнем Новгороде: обслуживание компьютеров и серверов”.

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

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

The homepage links to 129 pages on mb-nn.ru and 7 external pages.

Your robots.txt lets ChatGPT search (OAI-SearchBot), ChatGPT (ChatGPT-User), Claude (Claude-User), Perplexity (PerplexityBot) and Perplexity (Perplexity-User) read the homepage but closes other sections to them, so answers about those pages can't cite you.

https://mb-nn.ru/novosty and https://mb-nn.ru/kompaniya/blog all use the title “Новости - Мегабайт”. Search engines can't tell which page to show for a search, so each competes with the others.

https://mb-nn.ru/novosty, https://mb-nn.ru/kompaniya/tseli-tsennosti-i-printsipy, https://mb-nn.ru/kompaniya/vakansii, https://mb-nn.ru/kompaniya/blog, https://mb-nn.ru/uslugi/abonentskoe-obsluzhivanie and https://mb-nn.ru/uslugi/warning and 9 others use the same meta description. A description written for each page earns more clicks.

https://mb-nn.ru/novosty, https://mb-nn.ru/kompaniya/tseli-tsennosti-i-printsipy, https://mb-nn.ru/kompaniya/vakansii, https://mb-nn.ru/kompaniya/blog, https://mb-nn.ru/uslugi/abonentskoe-obsluzhivanie and https://mb-nn.ru/uslugi/warning and 7 others have no <h1> headline, so visitors and search engines get no clear main topic.

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

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

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

4 errors were logged to the browser console while the page loaded, for example “a.indexOf is not a function”.

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 131 words of visible text; thin pages give Google and first-time buyers little to go on.

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

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 Ads, Google Analytics, Google Tag Manager and 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 7 cookies, 1 of them by other companies (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 17 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.