Website review, no card needed

buymamacoco.com logo

buymamacoco.com website review

Visit site (opens in a new tab)Reviewed 8 November 202643 issues · 86 checks

This review found 43 issues worth fixing on buymamacoco.com, 15 of them high impact, across 86 checks. The most urgent: improve image delivery. 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

Real-visitor load time (LCP)75th percentile, phones
2.6 s2.1 sMay 16Oct 312.3 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20262.4 s
May 23, 20262.4 s
May 30, 20262.3 s
Jun 6, 20262.3 s
Jun 13, 20262.2 s
Jun 20, 20262.2 s
Jun 27, 20262.2 s
Jul 4, 20262.2 s
Jul 11, 20262.2 s
Jul 18, 20262.3 s
Jul 25, 20262.3 s
Aug 1, 20262.3 s
Aug 8, 20262.3 s
Aug 15, 20262.3 s
Aug 22, 20262.4 s
Aug 29, 20262.5 s
Sep 5, 20262.5 s
Sep 12, 20262.5 s
Sep 19, 20262.5 s
Sep 26, 20262.3 s
Oct 3, 20262.3 s
Oct 10, 20262.3 s
Oct 17, 20262.3 s
Oct 24, 20262.3 s
Oct 31, 20262.3 s
Real-visitor tap response (INP)75th percentile, phones
396 ms253 msMay 16Oct 31372 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026297 ms
May 23, 2026300 ms
May 30, 2026304 ms
Jun 6, 2026297 ms
Jun 13, 2026295 ms
Jun 20, 2026287 ms
Jun 27, 2026286 ms
Jul 4, 2026269 ms
Jul 11, 2026279 ms
Jul 18, 2026284 ms
Jul 25, 2026278 ms
Aug 1, 2026276 ms
Aug 8, 2026271 ms
Aug 15, 2026280 ms
Aug 22, 2026287 ms
Aug 29, 2026294 ms
Sep 5, 2026291 ms
Sep 12, 2026294 ms
Sep 19, 2026296 ms
Sep 26, 2026296 ms
Oct 3, 2026345 ms
Oct 10, 2026351 ms
Oct 17, 2026364 ms
Oct 24, 2026379 ms
Oct 31, 2026372 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

Full-page screenshot of buymamacoco.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. buymamacoco.com at 1.3 s1.3 s
  2. buymamacoco.com at 2.6 s2.6 s
  3. buymamacoco.com at 3.9 s3.9 s
  4. buymamacoco.com at 5.3 s5.3 s
  5. buymamacoco.com at 6.6 s6.6 s
  6. buymamacoco.com at 7.9 s7.9 s
  7. buymamacoco.com at 9.2 s9.2 s
  8. buymamacoco.com at 10.5 s10.5 s

Speed

12 to fix38
  • Improve image delivery

    4.0 s · 3.5 MB

    64 images could be 3.5 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 4.0 s faster on a phone.

  • Reduce unused JavaScript

    2.9 s · 493 KiB

    About 493 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.9 s faster on a phone.

  • 14,550 HTML elements

    The page has 14,550 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

  • Main-thread work: 11.5 s

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

  • Mobile performance score: 38

    38/100

    Your mobile performance score is 38. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

  • 8 third-party services on the page

    8 third-party services load with your homepage (Shopify, rebuyengine.com and gotolstoy.com and others), adding 5.5 MB and 941 ms of main-thread time.

  • Shopify adds 339 ms

    339 ms

    Shopify costs a phone 339 ms of main-thread work and 3.6 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

    600 ms · 63 KiB

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

  • Render-blocking requests

    650 ms

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

  • rebuyengine.com adds 335 ms

    335 ms

    rebuyengine.com costs a phone 335 ms of main-thread work and 918 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.

  • 20 long tasks on the main thread

    20 long tasks block the main thread while loading, the longest for 332 ms. During a long task the page ignores taps.

  • smartrmail.com adds 8 ms

    8 ms

    smartrmail.com costs a phone 8 ms of main-thread work and 921 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.

  • Legacy JavaScript

    150 ms · 29 KiB

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

  • Use efficient cache lifetimes

    150 ms · 26 KiB

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

  • Font display

    50 ms

    Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).

  • 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: 37 ms

    37 ms

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

Core Web Vitals

9 to fix33
  • 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.

  • Largest Contentful Paint: 40.7 s

    40.7 s

    Your largest element takes 40.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “UNLOCK 10% OFF your first purchase Plus be the first to kno…”.

  • Time to Interactive: 42.0 s

    42.0 s

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

  • Speed Index: 12.5 s

    12.5 s

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

  • Total Blocking Time: 1.6 s

    1.6 s

    Scripts block taps and scrolling for 1.6 s in total while the page loads. Good is under 200 ms.

  • Real-user LCP: 2.7 s

    2.7 s

    Real visitors wait 2.7 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Real-user INP: 328 ms

    328 ms

    Real visitors wait 328 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Tap response (INP) got 26% slower for real visitors

    +26%

    Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 297 ms to 372 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Real-user FCP: 2.5 s

    2.5 s

    Real visitors see the first content after 2.5 s (75th percentile). Good is under 1.8 s.

  • Largest content (LCP) held steady for real visitors

    -3%

    Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 2.4 s to 2.3 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

4 checks passed
  • Real-user CLS: 0.08

    0.08

    For real visitors the layout shifts by 0.08 (75th percentile). Good is under 0.1.

  • Real-user TTFB: 783 ms

    783 ms

    Real visitors wait 783 ms for your server to start answering (75th percentile). Good is under 800 ms.

  • First Contentful Paint: 1.7 s

    1.7 s

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

  • Cumulative Layout Shift: 0.019

    0.019

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

Images and page weight

2 to fix60
  • Page weight: 9.5 MB in 489 requests

    9.5 MB

    Your homepage downloads 9.5 MB in 489 requests on a phone: images 5.9 MB (130), other files 1.8 MB (252) and scripts 1.1 MB (73). Under 2 MB keeps phones on slow connections fast.

  • 4 images far larger than shown

    390 KiB

    4 images are downloaded at several times the size a phone draws them, for example reversible-baby-beanie-teddy-tiles-design.jpg at 2,048 px wide, shown at 237 px. Resized copies would save about 390 KiB.

  • About 2.7 g of CO₂ per visit

    2.70 g

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

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

Accessibility

7 to fixGoogle 8591
  • 12 tap targets too small

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

  • 7 text elements with low contrast

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

  • Interactive controls must not be nested (2 elements)

    Interactive controls must not be nested: 2 elements on the page fail this check, rated serious by axe-core.

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

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

  • 6 links without text

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

  • 2 form fields without a label

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

  • Headings should not be empty (2 elements)

    Headings should not be empty: 2 elements on the page fail this check, rated minor by axe-core.

  • Elements with visible text labels do not have matching accessible names.

    Elements with visible text labels do not have matching accessible names. (4 elements).

2 checks passed
  • Every image has alt text

    All 594 images in the HTML carry an alt attribute.

  • 46 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: 46 passed and 6 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 8591
  • No favicon declared

    No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

  • 1 link with vague text

    1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

  • One H1 headline

    Your <h1> is empty.

  • 71 internal links, 1 external

    The homepage links to 71 pages on buymamacoco.com and 1 external page.

7 checks passed
  • Meta description: 160 characters

    Your meta description is 160 characters: “Shop the cutest collection of baby wear essentials online at Mama Coco. Browse all our newborn outfits, swaddles and pr…”.

  • Title: 54 characters

    Your title is a healthy 54 characters: “Buy Baby Wear Essentials - Newborn Outfits | Mama Coco”.

  • Canonical URL set

    The canonical URL is https://buymamacoco.com/.

  • Structured data in place

    Structured data found: BreadcrumbList, ClothingStore, Organization and WebSite.

  • 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://buymamacoco.com/sitemap.xml.

AI search readiness

1 to fix88
  • Some text only appears after JavaScript runs

    42%

    The HTML your server sends has 932 of the 2,216 words a browser shows. AI crawlers don't run JavaScript, so they miss the rest.

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

  • Organization data: 4 of 6 facts

    Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.

  • llms.txt published

    The site publishes https://buymamacoco.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.

Other pages

4 to fix58
  • 1 linked page is broken

    Your homepage links to https://buymamacoco.com/blogs/press-contd/mama-coco-organic-baby-awards-2026-gold, which answers with an error. Visitors hit a dead end and search engines drop it.

  • 2 pages share a title

    https://buymamacoco.com/products/cocoon-swaddle-classic-brushed and https://buymamacoco.com/products/cocoon-swaddle-silky-modal all use the title “Cocoon Swaddles for Newborn - Shop Swaddles | Mama Coco”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 2 pages without a meta description

    https://buymamacoco.com/policies/shipping-policy and https://buymamacoco.com/pages/newborn-essentials-bundle-builder have no meta description, so Google writes the search snippet from whatever text it finds.

  • 14 pages without an H1

    https://buymamacoco.com/collections/gifting, https://buymamacoco.com/products/cocoon-swaddle-classic-brushed, https://buymamacoco.com/products/flutter-sleeve-winged-bodysuit-classic-brushed, https://buymamacoco.com/collections/bundle-sets, https://buymamacoco.com/collections/shop-essentials-2 and https://buymamacoco.com/pages/about and 8 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 14 pages with very little text

    https://buymamacoco.com/collections/gifting, https://buymamacoco.com/products/cocoon-swaddle-classic-brushed, https://buymamacoco.com/products/flutter-sleeve-winged-bodysuit-classic-brushed, https://buymamacoco.com/collections/bundle-sets, https://buymamacoco.com/collections/shop-essentials-2 and https://buymamacoco.com/pages/about 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.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 37 found) and read each the way a search engine does.

3 checks passed
  • Canonical URLs point to themselves

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

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 14 pages that loaded have a <title>.

Best practices

2 to fixGoogle 9687
  • 19 small tap targets

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

  • 5 JavaScript errors while loading

    5 errors were logged to the browser console while the page loaded, for example “Error sending user session Error: Shopify session id is missing”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix83
  • No analytics detected

    No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

  • No direct contact details

    No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

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

  • About 2,216 words of copy

    The homepage carries about 2,216 words of visible text.

4 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Shop the drop” and “SHOP SWADDLES”.

  • 11 calls to action

    The homepage has 11 calls to action, for example “Shop the drop”, “Shop Bundles” and “SHOP ALL”.

  • 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: 108 testimonial or review blocks, a star rating and 3 trust badges.

Privacy and tracking

1 to fix
  • 6 trackers load before any consent

    6

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and Microsoft Ads and 1 more (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.

  • 17 cookies set on arrival

    17

    Opening the homepage sets 17 cookies, 1 of them by other companies (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.

  • 40 other companies contacted

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

Apps on your store

Your storefront loads 10 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Judge Me Reviews · Tinyseo Ai Seo Speed · Instafeed · Redo · Tolstoy · Rebuy Personalization Engine · Smartrmail · Dealeasy · getredo.com · rebuyengine.com

Apps found in the homepage's code. Apps that only run in checkout or the admin aren't seen, and a headless storefront shows none. App data from programmable.info

Upkeep, stack and company

Stack

E-commerce
Shopify
Hosting
Shopify

Company

Headquarters
Manhattan Beach

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 buymamacoco.com, including 21 speed issues, 3 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

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