Website review, no card needed

mb-design.ru logo

mb-design.ru website review

Visit site (opens in a new tab)Reviewed 16 November 202644 issues · 81 checks

This review found 44 issues worth fixing on mb-design.ru, 13 of them high impact, across 81 checks. The most urgent: render-blocking requests. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Full-page screenshot of mb-design.ru (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. mb-design.ru at 0.8 s0.8 s
  2. mb-design.ru at 1.7 s1.7 s
  3. mb-design.ru at 2.5 s2.5 s
  4. mb-design.ru at 3.3 s3.3 s
  5. mb-design.ru at 4.2 s4.2 s
  6. mb-design.ru at 5.0 s5.0 s
  7. mb-design.ru at 5.8 s5.8 s
  8. mb-design.ru at 6.7 s6.7 s

Speed

10 to fix68
  • Render-blocking requests

    2.2 s

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

  • Reduce unused JavaScript

    940 ms · 163 KiB

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

  • Mobile performance score: 68

    68/100

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

  • 6 third-party services on the page

    6 third-party services load with your homepage (Tilda, jivo.ru and tildaapi.com and others), adding 2.2 MB and 553 ms of main-thread time.

  • Use efficient cache lifetimes

    300 ms · 255 KiB

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

  • Tilda adds 308 ms

    308 ms

    Tilda costs a phone 308 ms of main-thread work and 1.4 MB 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 long task on the main thread

    1 long task block the main thread while loading, the longest for 345 ms. During a long task the page ignores taps.

  • jivo.ru adds 197 ms

    197 ms

    jivo.ru costs a phone 197 ms of main-thread work and 375 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.

  • Main-thread work: 2.3 s

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

  • Google Fonts adds 0 ms

    0 ms

    Google Fonts costs a phone 0 ms of main-thread work and 319 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.

  • Reduce unused CSS

    160 ms · 33 KiB

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

  • Legacy JavaScript

    150 ms · 19 KiB

    Polyfills for old browsers add 19 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.

  • Improve image delivery

    50 ms · 36 KiB

    5 images could be 36 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 50 ms faster on a phone.

  • 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.

1 checks passed
  • Server response: 234 ms

    234 ms

    Your server sent the HTML in 234 ms, well inside Google's 600 ms guideline.

Core Web Vitals

5 to fix66
  • Largest Contentful Paint: 7.9 s

    7.9 s

    Your largest element takes 7.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.

  • Time to Interactive: 12.0 s

    12.0 s

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

  • Speed Index: 4.8 s

    4.8 s

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

  • First Contentful Paint: 2.5 s

    2.5 s

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

  • 26 images without width and height

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

  • Not enough real-visitor data yet

    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.

2 checks passed
  • Total Blocking Time: 148 ms

    148 ms

    Scripts block the page for only 148 ms while loading. Good is under 200 ms.

  • Cumulative Layout Shift: 0

    0

    The layout barely moves while loading (CLS 0, good is under 0.1).

Images and page weight

1 to fix85
  • Page weight: 2.2 MB in 170 requests

    2.2 MB

    Your homepage downloads 2.2 MB in 170 requests on a phone: scripts 944 KiB (52), images 821 KiB (64) and fonts 316 KiB (8). Under 2 MB keeps phones on slow connections fast.

  • About 0.6 g of CO₂ per visit

    0.64 g

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

3 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

12 to fixGoogle 8483
  • 45 text elements with low contrast

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

  • 4 tap targets too small

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

  • [role="img"] and [role="image"] elements must have alternative text (3 elements)

    [role="img"] and [role="image"] elements must have alternative text: 3 elements on the page fail this check, rated serious by axe-core.

  • Scrollable region must have keyboard access (2 elements)

    Scrollable region must have keyboard access: 2 elements on the page fail this check, rated serious by axe-core.

  • Elements must only use permitted ARIA attributes (1 element)

    Elements must only use permitted ARIA attributes: 1 element on the page fails this check, rated serious by axe-core.

  • Links look like plain text

    1 link inside paragraphs relies on colour alone to stand out.

  • All page content should be contained by landmarks (14 elements)

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

  • No main landmark

    The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

  • Page should contain a level-one heading (1 element)

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

  • 7 links without text

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

  • 4 form fields without a label

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

  • ARIA role should be appropriate for the element (2 elements)

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

2 checks passed
  • Every image has alt text

    All 27 images in the HTML carry an alt attribute.

  • 40 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 51 WCAG 2.2 A/AA and best-practice rules on the phone render: 40 passed and 11 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

3 to fixGoogle 10081
  • No H1 headline

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

  • Meta description is short (57 characters)

    Your meta description is only 57 characters: “Эргорюкзаки для детей, рюкзаки-переноски для кукол Реборн”. 70 to 160 characters is enough to sell the click.

  • Structured data has 2 problems

    Structured data found (WebSite) but with 2 problems, for example “WebSite: missing name”.

  • No X (Twitter) card tag

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

  • 31 internal links, 14 external

    The homepage links to 31 pages on mb-design.ru and 14 external pages.

5 checks passed
  • Title: 31 characters

    Your title is a healthy 31 characters: “ЭРГОРЮКЗАКИ с рождения MBDESIGN”.

  • Canonical URL set

    The canonical URL is https://mbdesign-ergo.ru/.

  • Open Graph tags complete

    Open Graph tags are complete, so shared links show a title, description and image.

  • 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://mbdesign-ergo.ru/sitemap.xml.

AI search readiness

1 to fix83
  • 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.

  • No llms.txt

    There is no https://mbdesign-ergo.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.

1 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.

Other pages

6 to fix50
  • 1 linked page is broken

    Your homepage links to https://mbdesign-ergo.ru/%7B%7Bback-link%7D%7D, which answers with an error. Visitors hit a dead end and search engines drop it.

  • 4 linked pages hidden from search

    https://mbdesign-ergo.ru/page97504166.html, https://mbdesign-ergo.ru/cookie, https://mbdesign-ergo.ru/politika and https://mbdesign-ergo.ru/page89696866.html are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

  • 2 pages share a title

    https://mbdesign-ergo.ru/page132815506.html and https://mbdesign-ergo.ru/ergoryukzak all use the title “Эргорюкзаки с рождения MB”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 3 pages without a meta description

    https://mbdesign-ergo.ru/cookie, https://mbdesign-ergo.ru/politika and https://mbdesign-ergo.ru/page89696866.html have no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 pages share a meta description

    https://mbdesign-ergo.ru/page132815506.html and https://mbdesign-ergo.ru/ergoryukzak use the same meta description. A description written for each page earns more clicks.

  • 7 pages without an H1

    https://mbdesign-ergo.ru/page132815506.html, https://mbdesign-ergo.ru/reborn, https://mbdesign-ergo.ru/ergoryukzak, https://mbdesign-ergo.ru/accessories, https://mbdesign-ergo.ru/cookie and https://mbdesign-ergo.ru/politika and 1 other have no <h1> headline, so visitors and search engines get no clear main topic.

  • 5 pages with very little text

    https://mbdesign-ergo.ru/page132815506.html, https://mbdesign-ergo.ru/instructions, https://mbdesign-ergo.ru/reborn, https://mbdesign-ergo.ru/ergoryukzak and https://mbdesign-ergo.ru/accessories 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.

  • 7 pages slow to respond

    https://mbdesign-ergo.ru/page97504166.html, https://mbdesign-ergo.ru/reborn, https://mbdesign-ergo.ru/ergoryukzak, https://mbdesign-ergo.ru/accessories, https://mbdesign-ergo.ru/cookie and https://mbdesign-ergo.ru/politika and 1 other took over 3 s to send their HTML from our server.

  • 10 internal pages checked

    We fetched 10 pages linked from your homepage and read each the way a search engine does.

2 checks passed
  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • Every page has a title

    All 9 pages that loaded have a <title>.

Best practices

2 to fixGoogle 10087
  • 4 small tap targets

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

  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://robokassa.com/media/widget/robokassa-tilda.css' from origin 'https://mbdesign-ergo…”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix57
  • 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.

  • Thin social proof

    Social proof on the homepage: 1 testimonial or review block. Pairing it with named testimonials or customer logos makes it far more convincing.

  • Only about 39 words

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

  • 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.

3 checks passed
  • 3 short forms

    3 short forms (6 fields at most) are right on the homepage, asking for an email.

  • Analytics in place

    Analytics detected: Google Analytics.

  • Direct contact links

    Visitors can reach you directly: 3 phone links and 3 email links.

Privacy and tracking

  • 4 cookies set on arrival

    4

    Opening the homepage sets 4 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.

  • 13 other companies contacted

    Loading the homepage contacts 13 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.

1 checks passed
  • No known trackers before consent

    No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).

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 mb-design.ru, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

Analytics
Google Analytics
Hosting
"Domain names registrar REG.RU", Ltd

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 44 issues on mb-design.ru, including 15 speed issues, 3 SEO issues and 4 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

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25