Website review, no card needed
mnogomebeli.com website review
Visit site (opens in a new tab)Reviewed 29 October 202637 issues · 94 checks
This review found 37 issues worth fixing on mnogomebeli.com, 12 of them high impact, across 94 checks. The most urgent: render-blocking requests. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
82BClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 2.8 s |
| May 16, 2026 | 2.7 s |
| May 23, 2026 | 2.7 s |
| May 30, 2026 | 2.5 s |
| Jun 6, 2026 | 2.1 s |
| Jun 13, 2026 | 1.7 s |
| Jun 20, 2026 | 1.3 s |
| Jun 27, 2026 | 1.2 s |
| Jul 4, 2026 | 1.2 s |
| Jul 11, 2026 | 1.2 s |
| Jul 18, 2026 | 1.2 s |
| Jul 25, 2026 | 1.2 s |
| Aug 1, 2026 | 1.2 s |
| Aug 8, 2026 | 1.2 s |
| Aug 15, 2026 | 1.2 s |
| Aug 22, 2026 | 1.2 s |
| Aug 29, 2026 | 1.2 s |
| Sep 5, 2026 | 1.1 s |
| Sep 12, 2026 | 1.0 s |
| Sep 19, 2026 | 958 ms |
| Sep 26, 2026 | 880 ms |
| Oct 3, 2026 | 872 ms |
| Oct 10, 2026 | 869 ms |
| Oct 17, 2026 | 855 ms |
| Oct 24, 2026 | 840 ms |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 146 ms |
| May 16, 2026 | 140 ms |
| May 23, 2026 | 135 ms |
| May 30, 2026 | 134 ms |
| Jun 6, 2026 | 135 ms |
| Jun 13, 2026 | 142 ms |
| Jun 20, 2026 | 148 ms |
| Jun 27, 2026 | 150 ms |
| Jul 4, 2026 | 151 ms |
| Jul 11, 2026 | 150 ms |
| Jul 18, 2026 | 149 ms |
| Jul 25, 2026 | 149 ms |
| Aug 1, 2026 | 148 ms |
| Aug 8, 2026 | 148 ms |
| Aug 15, 2026 | 147 ms |
| Aug 22, 2026 | 146 ms |
| Aug 29, 2026 | 143 ms |
| Sep 5, 2026 | 140 ms |
| Sep 12, 2026 | 137 ms |
| Sep 19, 2026 | 132 ms |
| Sep 26, 2026 | 127 ms |
| Oct 3, 2026 | 124 ms |
| Oct 10, 2026 | 121 ms |
| Oct 17, 2026 | 118 ms |
| Oct 24, 2026 | 118 ms |
Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.
One score from every part of this review. How it works
How it loaded on a phone
1.0 s
2.1 s
3.1 s
4.2 s
5.2 s
6.3 s
7.3 s
8.4 s
Speed
Render-blocking requests
1.7 s13 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.7 s.
5,357 HTML elements
The page has 5,357 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Mobile performance score: 87
87/100Your mobile performance score is 87. Pages that score under 90 lose visitors before the first paint.
8 third-party services on the page
8 third-party services load with your homepage (diginetica.net, rfc-group.ru and yandex.ru and others), adding 1,017 KiB and 507 ms of main-thread time.
Reduce unused JavaScript
576 KiBAbout 576 KiB of JavaScript is downloaded but never used on this page.
Use efficient cache lifetimes
358 KiB18 files are served with short cache lifetimes, so returning visitors download them again (358 KiB).
Main-thread work: 2.6 s
A phone's processor spends 2.6 s on main-thread work while loading, 888 ms of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
rfc-group.ru adds 131 ms
131 msrfc-group.ru costs a phone 131 ms of main-thread work and 506 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.
7 long tasks on the main thread
7 long tasks block the main thread while loading, the longest for 221 ms. During a long task the page ignores taps.
Reduce unused CSS
211 KiBAbout 211 KiB of CSS is downloaded but never applied on this page.
Legacy JavaScript
35 KiBPolyfills for old browsers add 35 KiB JavaScript that modern phones do not need.
Improve image delivery
22 KiB1 image could be 22 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Minify CSS
6 KiB6 KiB could be saved by minifying CSS.
Minify JavaScript
6 KiB6 KiB could be saved by minifying JavaScript.
Chained critical requests
Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.
Forced reflow
Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.
1 checks passed
Server response: 5 ms
5 msYour server sent the HTML in 5 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Time to Interactive: 13.8 s
13.8 sThe page becomes fully interactive after 13.8 s. Good is under 3.8 s.
Speed Index: 6.9 s
6.9 sVisually, the page fills in at 6.9 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 306 ms
306 msScripts block taps and scrolling for 306 ms in total while the page loads. Good is under 200 ms.
3 images without width and height
3 images have no width and height attributes, so the layout jumps as each one loads.
11 checks passed
Passes Core Web Vitals for real visitors
Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).
Real-user LCP: 1.2 s
1.2 sReal visitors wait 1.2 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 125 ms
125 msReal visitors wait 125 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user FCP: 1.2 s
1.2 sReal visitors see the first content after 1.2 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 689 ms
689 msReal visitors wait 689 ms for your server to start answering (75th percentile). Good is under 800 ms.
Tap response (INP) got 17% faster for real visitors
-17%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 146 ms to 118 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 69% faster for real visitors
-69%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 2.8 s to 0.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
First Contentful Paint: 1.2 s
1.2 sThe first text or image appears after 1.2 s, inside the 1.8 s “good” threshold.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Largest Contentful Paint: 1.4 s
1.4 sYour largest element renders in 1.4 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the image “Вместительный по максимуму”.
Images and page weight
Page weight: 2.3 MB in 122 requests
2.3 MBYour homepage downloads 2.3 MB in 122 requests on a phone: scripts 1.0 MB (26), images 752 KiB (60) and fonts 259 KiB (4). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
MM_2026_sept_web_mobile_600kh800_pl_1x.webp is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).
8 images below the first screen load straight away
8 images further down the page (261 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 0.6 g of CO₂ per visit
0.65 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.65 g of CO₂e: 77.8 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
44 buttons without a name
44 buttons have no accessible name, so screen readers announce just “button”.
5 text elements with low contrast
5 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
2 tap targets too small
2 tap targets are too small or too close together to hit reliably with a finger.
Malformed lists
Some lists contain elements other than list items, which screen readers announce wrongly.
Interactive controls must not be nested (1 element)
Interactive controls must not be nested: 1 element on the page fails this check, rated serious by axe-core.
All page content should be contained by landmarks (27 elements)
All page content should be contained by landmarks: 27 elements on the page fail this check, rated moderate by axe-core.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
Alternative text of images should not be repeated as text (36 elements)
Alternative text of images should not be repeated as text: 36 elements on the page fail this check, rated minor by axe-core.
2 form fields without a label
2 form fields have no label, so screen readers announce an empty box and autofill guesses.
1 link without text
1 visible link has no text or label, so screen readers cannot say where it goes.
Headings skip levels
Headings skip levels (h2 → h4), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 81 images in the HTML carry an alt attribute.
47 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 58 WCAG 2.2 A/AA and best-practice rules on the phone render: 47 passed and 11 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
Title is long (106 characters)
Your title is 106 characters, so Google will cut it off around 60: “Много Мебели — интернет-магазин недорогой мебели. Продажа мебели в Москве по низким ценам…”.
Structured data has 1 problem
Structured data found (WebSite) but with 1 problem, for example “WebSite: missing name”.
1 link crawlers can't follow
1 link has no real href, so search engines can't follow it.
Open Graph partly set
Open Graph is missing og:title, so shared links fall back to guesses.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
367 internal links, 5 external
The homepage links to 367 pages on mnogomebeli.com and 5 external pages.
4 checks passed
Meta description: 159 characters
Your meta description is 159 characters: “Широкий ассортимент корпусной мебели собственного производства в наличии и под заказ. Цены от производителя, быстрая до…”.
Canonical URL set
The canonical URL is https://mnogomebeli.com/.
robots.txt in place
robots.txt is in place and points crawlers to your sitemap.
XML sitemap found
Your XML sitemap is reachable at https://mnogomebeli.com/sitemap.xml.
AI search readiness
No Organization structured data
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.
Opted out of AI training for 1 crawler
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.
3 checks passed
AI answer engines may read the site
Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.
Text is in the HTML
Your server sends the page's text in the HTML (763 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://mnogomebeli.com/llms.txt (8 KiB, 89 links), a plain-text guide to the site for AI tools.
Other pages
2 pages without a meta description
https://mnogomebeli.com/loyalty-program and https://mnogomebeli.com/personal/favorites have no meta description, so Google writes the search snippet from whatever text it finds.
6 pages with very little text
https://mnogomebeli.com/action, https://mnogomebeli.com/about/salony, https://mnogomebeli.com/about/dostavka, https://mnogomebeli.com/about/status, https://mnogomebeli.com/loyalty-program and https://mnogomebeli.com/personal/favorites 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.
4 pages slow to respond
https://mnogomebeli.com/about/status, https://mnogomebeli.com/personal/favorites, https://mnogomebeli.com/promo/rasprodazha and https://mnogomebeli.com/divany took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 172 found) and read each the way a search engine does.
6 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
Titles are unique
Every page we checked has its own title.
Every page has an H1
Each page we checked has a main headline.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 15 pages that loaded have a <title>.
Best practices
48 small tap targets
48 of 224 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
Deprecated browser APIs
The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).
4 JavaScript errors while loading
4 errors were logged to the browser console while the page loaded, for example “Cannot read properties of null (reading 'classList')”.
2 low-resolution images
2 images are served at too low a resolution for sharp phone screens.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No call to action on the first screen
On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.
No calls to action
We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.
No analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
No risk reducer
No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.
About 254 words of copy
The homepage carries about 254 words of visible text.
3 checks passed
1 short form
A short form (1 field at most) is right on the homepage.
Social proof on the page
Social proof on the homepage: 51 testimonial or review blocks and a star rating.
Direct contact links
Visitors can reach you directly: 1 phone link and 0 email links.
Privacy and tracking
1 tracker load before any consent
1Before 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.
14 cookies set on arrival
14Opening the homepage sets 14 cookies (measured from a US location before any click).
No consent tool detected
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.
22 other companies contacted
Loading the homepage contacts 22 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
Security, domain, email and software versions
The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at mnogomebeli.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Framework
- jQuery
- Hosting
- Beget
Company
- Founded
- 2009
- Headquarters
- Saratov
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 37 issues on mnogomebeli.com, including 12 speed issues, 4 SEO issues and 3 conversion gaps. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.
- 28 research agents read your site, reviews, competitors, communities and public filings
- Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
- Competitor intelligence with battlecards for your closest rivals
- Ideal customer profile, buyer segments and buying-stage funnel
- Ranked channels, outreach sequences and content angles
- Live Reddit threads where buyers ask for what you sell, with draft replies
- Earned media and PR openings
- At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
- PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
- Refresh the playbook later to see what changed
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.