Website review, no card needed
micuna.online website review
Visit site (opens in a new tab)Reviewed 24 October 202630 issues · 68 checks
This review found 30 issues worth fixing on micuna.online, 14 of them high impact, across 68 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
62D- #103,466 of 107,732 reviewed websitesbeats 3%
- #59,938 of 60,952 online storesbeats 1%
- #2,363 of 2,468 WooCommerce storesbeats 3%
Closest competitors among WooCommerce stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 7.1 s |
| May 9, 2026 | 7.5 s |
| May 16, 2026 | 7.7 s |
| May 23, 2026 | 7.6 s |
| May 30, 2026 | 7.6 s |
| Jun 6, 2026 | 7.7 s |
| Jun 13, 2026 | 7.7 s |
| Jun 20, 2026 | 7.9 s |
| Jun 27, 2026 | 8.4 s |
| Jul 4, 2026 | 8.3 s |
| Jul 11, 2026 | 8.3 s |
| Jul 18, 2026 | 7.6 s |
| Jul 25, 2026 | 7.4 s |
| Aug 1, 2026 | 7.2 s |
| Aug 8, 2026 | 7.1 s |
| Aug 15, 2026 | 7.1 s |
| Aug 22, 2026 | 7.1 s |
| Aug 29, 2026 | 7.4 s |
| Sep 5, 2026 | 6.6 s |
| Sep 12, 2026 | 5.6 s |
| Sep 19, 2026 | 5.5 s |
| Sep 26, 2026 | 5.3 s |
| Oct 3, 2026 | 5.6 s |
| Oct 10, 2026 | 5.8 s |
| Oct 17, 2026 | 5.8 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 88 ms |
| May 9, 2026 | 96 ms |
| May 16, 2026 | 96 ms |
| May 23, 2026 | 101 ms |
| May 30, 2026 | 96 ms |
| Jun 6, 2026 | 94 ms |
| Jun 13, 2026 | 95 ms |
| Jun 20, 2026 | 94 ms |
| Jun 27, 2026 | 96 ms |
| Jul 4, 2026 | 93 ms |
| Jul 11, 2026 | 87 ms |
| Jul 18, 2026 | 84 ms |
| Jul 25, 2026 | 82 ms |
| Aug 1, 2026 | 83 ms |
| Aug 8, 2026 | 83 ms |
| Aug 15, 2026 | 83 ms |
| Aug 22, 2026 | 83 ms |
| Aug 29, 2026 | 81 ms |
| Sep 5, 2026 | 85 ms |
| Sep 12, 2026 | 84 ms |
| Sep 19, 2026 | 87 ms |
| Sep 26, 2026 | 86 ms |
| Oct 3, 2026 | 87 ms |
| Oct 10, 2026 | 89 ms |
| Oct 17, 2026 | 89 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
Speed
Improve image delivery
7.8 s · 16.7 MB10 images could be 16.7 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 7.8 s faster on a phone.
Mobile performance score: 42
42/100Your mobile performance score is 42 (desktop: 66). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Render-blocking requests
850 ms14 files block the first paint until they finish downloading. Deferring or inlining them could save about 850 ms.
Reduce unused JavaScript
300 ms · 67 KiBAbout 67 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 300 ms faster on a phone.
Reduce unused CSS
150 ms · 97 KiBAbout 97 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.
1 third-party service on the page
1 third-party service load with your homepage (Google Fonts), adding 90 KiB and 0 ms of main-thread time.
Legacy JavaScript
8 KiBPolyfills for old browsers add 8 KiB JavaScript that modern phones do not need.
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.
2 checks passed
Main-thread work: 0.7 s
A phone's processor spends 0.7 s on main-thread work while loading, 240 ms of it running JavaScript. That is comfortably low.
Server response: 223 ms
223 msYour server sent the HTML in 223 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Fails Core Web Vitals for real visitors
Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.
Real-user CLS: 0.48
0.48For real visitors the layout shifts by 0.48 (75th percentile). Good is under 0.1.
Real-user FCP: 5.8 s
5.8 sReal visitors see the first content after 5.8 s (75th percentile). Good is under 1.8 s.
Largest Contentful Paint: 14.3 s
14.3 sYour largest element takes 14.3 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: 14.3 s
14.3 sThe page becomes fully interactive after 14.3 s. Good is under 3.8 s.
Speed Index: 9.9 s
9.9 sVisually, the page fills in at 9.9 s (Speed Index). Good is under 3.4 s.
Cumulative Layout Shift: 0.442
0.442The layout shifts by 0.442 while loading, so content jumps under the reader's thumb. Good is under 0.1.
First Contentful Paint: 2.6 s
2.6 sThe first text or image appears after 2.6 s on a phone. Good is under 1.8 s.
Tap response (INP) held steady for real visitors
-3%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 88 ms to 89 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
2 checks passed
Largest content (LCP) got 20% faster for real visitors
-20%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 7.1 s to 5.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Total Blocking Time: 0 ms
0 msScripts block the page for only 0 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 20.8 MB in 38 requests
20.8 MBYour homepage downloads 20.8 MB in 38 requests on a phone: images 20.2 MB (11), fonts 318 KiB (8) and scripts 152 KiB (10). Under 2 MB keeps phones on slow connections fast.
About 5.9 g of CO₂ per visit
5.89 gBy the Sustainable Web Design model, a visit to your homepage emits about 5.89 g of CO₂e: 706.9 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
3 text elements with low contrast
3 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
3 images without alt text
3 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (10 elements)
All page content should be contained by landmarks: 10 elements on the page fail this check, rated moderate by axe-core.
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.
11 links without text
11 visible links have no text or label, so screen readers cannot say where they go.
1 checks passed
42 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 47 WCAG 2.2 A/AA and best-practice rules on the phone render: 42 passed and 5 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.
Canonical points to another host
Your canonical URL points to micuna.online, not micuna.com, so Google may credit that host instead.
Meta description is short (23 characters)
Your meta description is only 23 characters: “baby furniture and cots”. 70 to 160 characters is enough to sell the click.
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
No XML sitemap
No XML sitemap at https://www.micuna.com/sitemap.xml, so Google discovers your pages only by following links.
108 internal links, 6 external
The homepage links to 108 pages on micuna.online and 6 external pages.
3 checks passed
Title: 32 characters
Your title is a healthy 32 characters: “Baby Furniture and Cots - Micuna”.
Structured data in place
Structured data found: Article, Organization, Person, WebPage and WebSite.
robots.txt in place
robots.txt is in place and points crawlers to your sitemap.
AI search readiness
Organization data is thin (2 of 6 facts)
Your Organization JSON-LD is missing logo, sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.
2 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 (271 words), so crawlers that don't run JavaScript still read it.
Other pages
12 linked pages hidden from search
https://micuna.com/en/contact, https://micuna.com/en/purpose, https://micuna.com/en/blog, https://micuna.com/en/category-product/cots, https://micuna.com/en/category-product/cots/minicots and https://micuna.com/en/category-product/cots/all-cots and 6 others are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.
10 pages without a meta description
https://micuna.com/en/blog, https://micuna.com/en/category-product/cots, https://micuna.com/en/category-product/cots/minicots, https://micuna.com/en/category-product/cots/all-cots, https://micuna.com/en/category-product/cots/co-sleeping-cots and https://micuna.com/en/category-product/cots/big-baby-bed-cots and 4 others have no meta description, so Google writes the search snippet from whatever text it finds.
15 pages without an H1
https://micuna.com/en/contact, https://micuna.com/fr, https://micuna.com/it, https://micuna.com/en/who-we-are, https://micuna.com/en/purpose and https://micuna.com/en/blog and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.
5 pages slow to respond
https://micuna.com/it, https://micuna.com/en/blog, https://micuna.com/en/category-product/cots/all-cots, https://micuna.com/en/category-product/cots/co-sleeping-cots and https://micuna.com/en/category-product/cots/big-baby-bed-cots took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 53 found) and read each the way a search engine does.
4 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 a title
All 15 pages that loaded have a <title>.
Best practices
3 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Tap targets are thumb-sized
70 of 72 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
No analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
Only about 188 words
The homepage has only about 188 words of visible text; thin pages give Google and first-time buyers little to go on.
Phone number is not tap-to-call
Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.
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
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Contact”.
5 calls to action
The homepage has 5 calls to action, for example “Contact”, “Contact us” and “Where to buy Micuna”.
3 short forms
3 short forms (1 field at most) are right on the homepage.
Privacy and tracking
10 cookies set on arrival
10Opening the homepage sets 10 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.
1 other company contacted
Loading the homepage contacts 1 host 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 micuna.online, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
- The footer still says © 2021.
Stack
- CMS
- WordPress
- Framework
- jQuery
- E-commerce
- WooCommerce
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 30 issues on micuna.online, including 12 speed issues, 5 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.