Website review, no card needed

motka.ru logo

motka.ru website review

Visit site (opens in a new tab)Reviewed 8 November 202631 issues · 71 checks

This review found 31 issues worth fixing on motka.ru, 7 of them high impact, across 71 checks. The most urgent: page weight: 41.0 MB in 68 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 motka.ru (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. motka.ru at 0.4 s0.4 s
  2. motka.ru at 0.8 s0.8 s
  3. motka.ru at 1.1 s1.1 s
  4. motka.ru at 1.5 s1.5 s
  5. motka.ru at 1.9 s1.9 s
  6. motka.ru at 2.3 s2.3 s
  7. motka.ru at 2.6 s2.6 s
  8. motka.ru at 3.0 s3.0 s

Speed

5 to fix80
  • Use efficient cache lifetimes

    300 ms · 16.7 MB

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

  • Mobile performance score: 80

    80/100

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

  • Render-blocking requests

    850 ms

    2 files block the first paint until they finish downloading. Deferring or inlining them could save about 850 ms.

  • Reduce unused CSS

    300 ms · 76 KiB

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

  • website-files.com adds 0 ms

    0 ms

    website-files.com costs a phone 0 ms of main-thread work and 449 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.

  • Improve image delivery

    86 KiB

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

  • 5 third-party services on the page

    5 third-party services load with your homepage (Yandex Metrica, website-files.com and Embedly and others), adding 519 KiB and 21 ms of main-thread time.

  • Reduce unused JavaScript

    55 KiB

    About 55 KiB of JavaScript is downloaded but never used on this page.

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

  • Minify CSS

    3 KiB

    3 KiB could be saved by minifying CSS.

2 checks passed
  • Main-thread work: 1.0 s

    A phone's processor spends 1.0 s on main-thread work while loading, 317 ms of it running JavaScript. That is comfortably low.

  • Server response: 136 ms

    136 ms

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

Core Web Vitals

4 to fix77
  • Largest Contentful Paint: 4.8 s

    4.8 s

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

  • Speed Index: 4.3 s

    4.3 s

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

  • Time to Interactive: 4.8 s

    4.8 s

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

  • 11 images without width and height

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

3 checks passed
  • First Contentful Paint: 1.4 s

    1.4 s

    The first text or image appears after 1.4 s, inside the 1.8 s “good” threshold.

  • Cumulative Layout Shift: 0

    0

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

  • Total Blocking Time: 0 ms

    0 ms

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

Images and page weight

1 to fix70
  • Page weight: 41.0 MB in 68 requests

    41.0 MB

    Your homepage downloads 41.0 MB in 68 requests on a phone: media 39.7 MB (14), images 574 KiB (34) and fonts 449 KiB (4). Under 2 MB keeps phones on slow connections fast.

  • 1 image in older formats

    1 image (34 KiB) is 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.

  • About 11.6 g of CO₂ per visit

    11.61 g

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

2 checks passed
  • 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

7 to fixGoogle 7890
  • 23 text elements with low contrast

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

  • ARIA commands must have an accessible name (1 element)

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

  • 1 image without alt text

    1 image has no alt text, which hurts accessibility and image search.

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

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

  • 6 form fields without a label

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

  • 3 links without text

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

  • Headings skip levels

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

1 checks passed
  • 44 automated accessibility rules passed

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

SEO

4 to fixGoogle 9283
  • No structured data

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

  • Meta description is long (207 characters)

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

  • No XML sitemap

    No XML sitemap at https://motka.ru/sitemap.xml, so Google discovers your pages only by following links.

  • No robots.txt

    There is no robots.txt at motka.ru/robots.txt, the first file search crawlers ask for.

  • 107 internal links, 18 external

    The homepage links to 107 pages on motka.ru and 18 external pages.

4 checks passed
  • One H1 headline

    Your main headline reads: “Умныйпродуктовый дизайн”.

  • Title: 56 characters

    Your title is a healthy 56 characters: “Дизайн-студия Мотка - продуктовый дизайн и UX/UI решения”.

  • Canonical URL set

    The canonical URL is https://www.motka.ru/.

  • Open Graph tags complete

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

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://motka.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

    There is no robots.txt, so nothing stops the crawlers behind ChatGPT search, Claude and Perplexity from reading the site and cite it in answers.

Other pages

2 to fix93
  • 2 pages without a meta description

    https://motka.ru/portfolio/connect and https://motka.ru/portfolio/deepgeo have no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 pages share a meta description

    https://motka.ru/portfolio/globallab and https://motka.ru/portfolio/logistic-saas-platform use the same meta description. A description written for each page earns more clicks.

  • 14 pages with very little text

    https://motka.ru/portfolio, https://motka.ru/portfolio/chitay-gorod, https://motka.ru/portfolio/gramota, https://motka.ru/portfolio/algoritmika, https://motka.ru/portfolio/globallab and https://motka.ru/portfolio/scan and 8 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.

  • 7 pages slow to respond

    https://motka.ru/portfolio/ai-body, https://motka.ru/portfolio/globallab, https://motka.ru/portfolio/scan, https://motka.ru/portfolio/spherum, https://motka.ru/portfolio/connect and https://motka.ru/portfolio/deepgeo and 1 other took over 3 s to send their HTML from our server.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 21 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

1 to fixGoogle 9693
  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

2 checks passed
  • Tap targets are thumb-sized

    13 of 14 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

5 to fix50
  • 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.

  • A 25-field form

    Your longest form asks for 25 fields (5 required). Every extra field lowers completion.

  • Only about 48 words

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

2 checks passed
  • Social proof on the page

    Social proof on the homepage: 52 testimonial or review blocks and 3 trust badges.

  • Direct contact links

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

Privacy and tracking

1 to fix
  • 1 tracker load before any consent

    1

    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.

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

  • 5 other companies contacted

    Loading the homepage contacts 5 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 motka.ru, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

CMS
Webflow
Hosting
Dmitrii Vladimirovich Malkov

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 31 issues on motka.ru, including 9 speed issues, 4 SEO issues and 5 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