Website review, no card needed
mamanboo.com website review
Visit site (opens in a new tab)Reviewed 11 November 202643 issues · 81 checks
This review found 43 issues worth fixing on mamanboo.com, 16 of them high impact, across 81 checks. The most urgent: reduce unused JavaScript. 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
58FClosest competitors among reviewed websites
Compare side by sideOne score from every part of this review. How it works
Speed
Reduce unused JavaScript
1.6 s · 329 KiBAbout 329 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.6 s faster on a phone.
Render-blocking requests
1.9 s5 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.9 s.
Minify JavaScript
1.3 s · 247 KiB247 KiB could be saved by minifying JavaScript.
Mobile performance score: 39
39/100Your mobile performance score is 39. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Use efficient cache lifetimes
950 ms · 298 KiB57 files are served with short cache lifetimes, so returning visitors download them again (298 KiB).
Avoid multiple page redirects
780 msThe page goes through 1 redirect before it starts loading, costing about 780 ms. Link and advertise the final URL directly.
Document request latency
750 msThe HTML itself could arrive about 750 ms sooner: redirects, a slow server response or missing compression delay everything after it.
Improve image delivery
300 ms · 244 KiB13 images could be 244 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 300 ms faster on a phone.
3 long tasks on the main thread
3 long tasks block the main thread while loading, the longest for 133 ms. During a long task the page ignores taps.
8 third-party services on the page
8 third-party services load with your homepage (pstatic.net, poxo.com and SnapWidget and others), adding 104 KiB and 77 ms of main-thread time.
Legacy JavaScript
21 KiBPolyfills for old browsers add 21 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.
Forced reflow
Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.
2 checks passed
Main-thread work: 1.3 s
A phone's processor spends 1.3 s on main-thread work while loading, 382 ms of it running JavaScript. That is comfortably low.
Server response: 186 ms
186 msYour server sent the HTML in 186 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 10.5 s
10.5 sYour largest element takes 10.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Cumulative Layout Shift: 0.605
0.605The layout shifts by 0.605 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Speed Index: 8.2 s
8.2 sVisually, the page fills in at 8.2 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 10.7 s
10.7 sThe page becomes fully interactive after 10.7 s. Good is under 3.8 s.
First Contentful Paint: 3.2 s
3.2 sThe first text or image appears after 3.2 s on a phone. Good is under 1.8 s.
37 images without width and height
37 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.
1 checks passed
Total Blocking Time: 78 ms
78 msScripts block the page for only 78 ms while loading. Good is under 200 ms.
Images and page weight
7 images in older formats
7 images (460 KiB) are 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.
2 images below the first screen load straight away
2 images further down the page (48 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 0.5 g of CO₂ per visit
0.47 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.47 g of CO₂e: 56.5 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 checks passed
Page weight: 1.7 MB in 77 requests
1.7 MBYour homepage downloads 1.7 MB in 77 requests on a phone: scripts 922 KiB (17), images 716 KiB (44) and HTML 31 KiB (3). That is a lean page.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
22 text elements with low contrast
22 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.
Frames without titles
1 frame has no title, so screen-reader users cannot tell what it contains.
7 images without alt text
7 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (22 elements)
All page content should be contained by landmarks: 22 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.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
13 links without text
13 visible links have no text or label, so screen readers cannot say where they go.
1 form field without a label
1 form field has no label, so screen readers announce an empty box and autofill guesses.
Headings should not be empty (1 element)
Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.
1 checks passed
28 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 37 WCAG 2.2 A/AA and best-practice rules on the phone render: 28 passed and 9 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is short (8 characters)
Your title is only 8 characters: “2+1 마마앤부”. 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.
Meta description is short (30 characters)
Your meta description is only 30 characters: “아기와 온가족이 함께 쓰는 친환경 천연세탁세제 마마앤부”. 70 to 160 characters is enough to sell the click.
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://mamanboo.com/sitemap.xml, so Google discovers your pages only by following links.
No favicon declared
No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.
One H1 headline
Your <h1> is empty.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
55 internal links, 1 external
The homepage links to 55 pages on mamanboo.com and 1 external page.
2 checks passed
Canonical URL set
The canonical URL is https://mamanboo.com/.
robots.txt in place
robots.txt is in place.
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://mamanboo.com/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 linked pages are broken
Your homepage links to https://mamanboo.com/product/11-%EB%A7%88%EB%A7%88%EC%95%A4%EB%B6%80-%ED%94%8C%EB%9F%AC%EC%8A%A4-%EC%9C%A0%EC%95%84%EC%9A%A9%EC%84%B8%EC%A0%9C/1/category/56/display/1 and https://mamanboo.com/product/11-%EB%A7%88%EB%A7%88%EC%95%A4%EB%B6%80-%EC%9C%A0%EC%97%B0%EC%A0%9C-%EC%B2%B4%EB%A6%AC%ED%97%88%EB%8B%88/101/category/59/display/1, which answer with an error. Visitors hit a dead end and search engines drop them.
1 page without a title
https://mamanboo.com/board/free/read.html has no <title>, so Google invents the link text in results.
13 pages share 2 titles
/ and https://mamanboo.com/myshop/index.html all use the title “2+1 마마앤부”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.
6 pages without a meta description
https://mamanboo.com/board/free/read.html, https://mamanboo.com/board/free/list.html, https://mamanboo.com/product/%EB%A7%88%EB%A7%88%EC%95%A4%EB%B6%80-%ED%94%84%EB%A6%AC%EB%AF%B8%EC%97%84-%EC%8B%A0%EC%83%9D%EC%95%84%EC%84%B8%EC%A0%9C/96/category/1/display/2, https://mamanboo.com/product/%EB%A7%88%EB%A7%88%EC%95%A4%EB%B6%80-%EC%B9%9C%ED%99%98%EA%B2%BD-%EC%98%A8%EA%B0%80%EC%A1%B1%EC%9A%A9%EC%84%B8%EC%A0%9C/37/category/1/display/2, https://mamanboo.com/product/%EB%A7%88%EB%A7%88%EC%95%A4%EB%B6%80-%EC%9C%A0%EC%97%B0%EC%A0%9C-%EB%B2%A0%EC%9D%B4%EB%B9%84%ED%94%8C%EB%A1%9C%EB%9E%84/39/category/58/display/1 and https://mamanboo.com/product/11-%EB%A7%88%EB%A7%88%EC%95%A4%EB%B6%80-%EC%84%AC%EC%9C%A0%EC%9C%A0%EC%97%B0%EC%A0%9C-%EB%B2%A0%EC%9D%B4%EB%B9%84%ED%8C%8C%EC%9A%B0%EB%8D%94-2l/38/category/57/display/1 have no meta description, so Google writes the search snippet from whatever text it finds.
4 links to non-canonical URLs
Your homepage links to 4 pages by a URL that isn't their canonical one, for example https://mamanboo.com/product/%EB%A7%88%EB%A7%88%EC%95%A4%EB%B6%80-%ED%94%84%EB%A6%AC%EB%AF%B8%EC%97%84-%EC%8B%A0%EC%83%9D%EC%95%84%EC%84%B8%EC%A0%9C/96/category/1/display/2, whose canonical is https://mamanboo.com/product/%ED%94%84%EB%A6%AC%EB%AF%B8%EC%97%84-%EC%8B%A0%EC%83%9D%EC%95%84%EC%84%B8%EC%A0%9C-2l%EB%91%90%EA%B0%9C%EA%B5%AC%EB%A7%A4%EC%8B%9C%ED%95%98%EB%82%98%EB%8D%94/96. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
1 page without an H1
https://mamanboo.com/board/free/read.html has no <h1> headline, so visitors and search engines get no clear main topic.
8 pages with very little text
https://mamanboo.com/board/free/list.html, https://mamanboo.com/myshop/index.html, https://mamanboo.com/category/detergent/47, https://mamanboo.com/category/softener/48, https://mamanboo.com/category/refill/49 and https://mamanboo.com/category/detergent-bottle/50 and 2 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.
1 page slow to respond
https://mamanboo.com/product/%EB%A7%88%EB%A7%88%EC%95%A4%EB%B6%80-%EC%9C%A0%EC%97%B0%EC%A0%9C-%EB%B2%A0%EC%9D%B4%EB%B9%84%ED%94%8C%EB%A1%9C%EB%9E%84/39/category/58/display/1 took over 3 s to send its HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 29 found) and read each the way a search engine does.
1 checks passed
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Best practices
No mobile viewport
No viewport meta tag, so phones render the desktop layout zoomed out.
32 small tap targets
32 of 46 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Cannot read properties of undefined (reading 'getRegistration')”.
3 low-resolution images
3 images are served at too low a resolution for sharp phone screens.
Browser-reported issues
Chrome logged issues while loading the page (“Mixed content”).
Missing source maps
Large scripts ship without source maps.
Content and conversion
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 44 words
The homepage has only about 44 words of visible text; thin pages give Google and first-time buyers little to go on.
No form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
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
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “JOIN” and “ORDER”.
6 calls to action
The homepage has 6 calls to action, for example “JOIN” and “SHOP NOW”.
Analytics in place
Analytics detected: Meta Pixel.
Direct contact links
Visitors can reach you directly: 0 phone links and 1 email link.
Privacy and tracking
15 cookies set on arrival
15Opening the homepage sets 15 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.
15 other companies contacted
Loading the homepage contacts 15 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 mamanboo.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
- Korea Telecom
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 43 issues on mamanboo.com, including 14 speed issues, 7 SEO issues and 2 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.