Website review, no card needed
mimiboom.ru website review
Visit site (opens in a new tab)Reviewed 11 November 202645 issues · 81 checks
This review found 45 issues worth fixing on mimiboom.ru, 15 of them high impact, across 81 checks. The most urgent: improve image delivery. 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
57FClosest competitors among reviewed websites
Compare side by sideOne score from every part of this review. How it works
Speed
Improve image delivery
23.8 s · 5.1 MB19 images could be 5.1 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 23.8 s faster on a phone.
Use efficient cache lifetimes
1.3 s · 12.2 MB195 files are served with short cache lifetimes, so returning visitors download them again (12.2 MB).
Reduce unused JavaScript
3.8 s · 1.9 MBAbout 1.9 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 3.8 s faster on a phone.
Render-blocking requests
2.3 s22 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.3 s.
Font display
1.4 sWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 1.4 s).
Mobile performance score: 26
26/100Your mobile performance score is 26. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 4.8 s
A phone's processor spends 4.8 s on main-thread work while loading, 2.0 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
8 third-party services on the page
8 third-party services load with your homepage (vk.ru, Google Tag Manager and VK and others), adding 4.1 MB and 1.8 s of main-thread time.
vk.ru adds 716 ms
716 msvk.ru costs a phone 716 ms of main-thread work and 1.9 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.
Reduce unused CSS
150 ms · 554 KiBAbout 554 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 150 ms faster on a phone.
14 long tasks on the main thread
14 long tasks block the main thread while loading, the longest for 481 ms. During a long task the page ignores taps.
Google Tag Manager adds 362 ms
362 msGoogle Tag Manager costs a phone 362 ms of main-thread work and 747 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.
VK adds 309 ms
309 msVK costs a phone 309 ms of main-thread work and 935 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.
Minify JavaScript
300 ms · 100 KiB100 KiB could be saved by minifying JavaScript.
Legacy JavaScript
300 ms · 36 KiBPolyfills for old browsers add 36 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 300 ms faster on a phone.
1,781 HTML elements
The page has 1,781 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Minify CSS
8 KiB8 KiB could be saved by minifying CSS.
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: 3 ms
3 msYour server sent the HTML in 3 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 93.2 s
93.2 sYour largest element takes 93.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Speed Index: 37.0 s
37.0 sVisually, the page fills in at 37.0 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 107.6 s
107.6 sThe page becomes fully interactive after 107.6 s. Good is under 3.8 s.
Total Blocking Time: 968 ms
968 msScripts block taps and scrolling for 968 ms in total while the page loads. Good is under 200 ms.
Cumulative Layout Shift: 0.339
0.339The layout shifts by 0.339 while loading, so content jumps under the reader's thumb. Good is under 0.1.
36 images without width and height
36 images have no width and height attributes, so the layout jumps as each one loads.
First Contentful Paint: 1.8 s
1.8 sThe first text or image appears after 1.8 s on a phone. Good is under 1.8 s.
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.
Images and page weight
Page weight: 37.1 MB in 365 requests
37.1 MBYour homepage downloads 37.1 MB in 365 requests on a phone: images 21.1 MB (103), media 11.3 MB (2) and scripts 3.8 MB (188). Under 2 MB keeps phones on slow connections fast.
About 10.5 g of CO₂ per visit
10.51 gBy the Sustainable Web Design model, a visit to your homepage emits about 10.51 g of CO₂e: 1261.4 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
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.
16 text elements with low contrast
16 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Frames without titles
1 frame has no title, so screen-reader users cannot tell what it contains.
Headings skip levels
Headings skip levels (h1 → h3, h2 → h4 and h3 → h6), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 43 images in the HTML carry an alt attribute.
5 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 7 WCAG 2.2 A/AA and best-practice rules on the phone render: 5 passed and 2 failed. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is short (16 characters)
Your title is only 16 characters: “Интернет-магазин”. Between 30 and 65 characters leaves room to say what you do and for whom.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
3 H1 headlines
There are 3 <h1> headlines (“Все лучшее для малышей”, “Будь стильный с Mimiboom” and “”). One clear main headline is easier for people and search engines.
No canonical URL
No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.
No social preview image
No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.
No XML sitemap
No XML sitemap at https://mimiboom.ru/sitemap.xml, so Google discovers your pages only by following links.
7 links crawlers can't follow
7 links have no real href, so search engines can't follow them.
No favicon declared
No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
175 internal links, 4 external
The homepage links to 175 pages on mimiboom.ru and 4 external pages.
2 checks passed
Meta description: 77 characters
Your meta description is 77 characters: “Собственное производство детской одежды, конвертов и одежды для новорожденных”.
robots.txt in place
robots.txt is in place and points crawlers to your sitemap.
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.
No llms.txt
There is no https://mimiboom.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
2 pages share a title
https://mimiboom.ru/catalog and https://mimiboom.ru/catalog/konverty-osen-zima-vesna-2022-2023 all use the title “Конверты "Зима/Весна" 2024/2025"”. Search engines can't tell which page to show for a search, so each competes with the others.
12 pages share a meta description
https://mimiboom.ru/policy, https://mimiboom.ru/polzovatelskoe-soglashenie, https://mimiboom.ru/personal and https://mimiboom.ru/izbrannoe use the same meta description. A description written for each page earns more clicks.
13 pages with very little text
https://mimiboom.ru/policy, https://mimiboom.ru/polzovatelskoe-soglashenie, https://mimiboom.ru/personal, https://mimiboom.ru/izbrannoe, https://mimiboom.ru/catalog and https://mimiboom.ru/catalog/konverty-osen-zima-vesna-2022-2023 and 7 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.
3 pages slow to respond
https://mimiboom.ru/polzovatelskoe-soglashenie, https://mimiboom.ru/personal and https://mimiboom.ru/izbrannoe took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 67 found) and read each the way a search engine does.
6 checks passed
Linked pages load
13 pages of 15 loaded without an error (the rest turned automated requests away).
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
Every page has a meta description
All 13 pages that loaded have a meta description.
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 13 pages that loaded have a <title>.
Best practices
3 third-party cookies
3 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.
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.”).
22 distorted images
22 images are displayed at the wrong aspect ratio, so they look stretched or squashed.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
2 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
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.
Only about 107 words
The homepage has only about 107 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.
4 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: 18 testimonial or review blocks and 2 trust badges.
Analytics in place
Analytics detected: Google Tag Manager, Google Analytics and Meta Pixel.
Direct contact links
Visitors can reach you directly: 2 phone links and 2 email links.
Privacy and tracking
1 cookie set on arrival
1Opening the homepage sets 1 cookie (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.
2 other companies contacted
Loading the homepage contacts 2 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 mimiboom.ru, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Go beyond the website
What your $25 Growth Playbook adds
This review found 45 issues on mimiboom.ru, including 23 speed issues, 8 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.