Website review, no card needed

mabeproducts.com logo

mabeproducts.com website review

Visit site (opens in a new tab)Reviewed 20 November 202638 issues · 84 checks

This review found 38 issues worth fixing on mabeproducts.com, 19 of them high impact, across 84 checks. The most urgent: reduce unused JavaScript. 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
1.5 s1.3 sMay 30Nov 141.4 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20261.4 s
Jun 6, 20261.3 s
Jun 13, 20261.4 s
Jun 20, 20261.4 s
Jun 27, 20261.4 s
Jul 4, 20261.3 s
Jul 11, 20261.3 s
Jul 18, 20261.5 s
Jul 25, 20261.5 s
Aug 1, 20261.5 s
Aug 8, 20261.5 s
Aug 15, 20261.3 s
Aug 22, 20261.3 s
Aug 29, 20261.3 s
Sep 5, 20261.3 s
Sep 12, 20261.3 s
Sep 19, 20261.3 s
Sep 26, 20261.3 s
Oct 3, 20261.4 s
Oct 10, 20261.4 s
Oct 17, 20261.4 s
Oct 24, 20261.4 s
Oct 31, 20261.5 s
Nov 7, 20261.4 s
Nov 14, 20261.4 s
Real-visitor tap response (INP)75th percentile, phones
140 ms115 msMay 30Nov 14137 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 2026129 ms
Jun 6, 2026125 ms
Jun 13, 2026120 ms
Jun 20, 2026118 ms
Jun 27, 2026120 ms
Jul 4, 2026118 ms
Jul 11, 2026121 ms
Jul 18, 2026129 ms
Jul 25, 2026127 ms
Aug 1, 2026127 ms
Aug 8, 2026121 ms
Aug 15, 2026120 ms
Aug 22, 2026121 ms
Aug 29, 2026123 ms
Sep 5, 2026127 ms
Sep 12, 2026123 ms
Sep 19, 2026123 ms
Sep 26, 2026128 ms
Oct 3, 2026126 ms
Oct 10, 2026125 ms
Oct 17, 2026123 ms
Oct 24, 2026121 ms
Oct 31, 2026129 ms
Nov 7, 2026133 ms
Nov 14, 2026137 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 mabeproducts.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. mabeproducts.com at 4.3 s4.3 s
  2. mabeproducts.com at 8.6 s8.6 s
  3. mabeproducts.com at 12.9 s12.9 s
  4. mabeproducts.com at 17.3 s17.3 s
  5. mabeproducts.com at 21.6 s21.6 s
  6. mabeproducts.com at 25.9 s25.9 s
  7. mabeproducts.com at 30.2 s30.2 s
  8. mabeproducts.com at 34.5 s34.5 s

Speed

14 to fix43
  • Reduce unused JavaScript

    4.4 s · 1.2 MB

    About 1.2 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 4.4 s faster on a phone.

  • Use efficient cache lifetimes

    1.6 s · 543 KiB

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

  • Improve image delivery

    1.3 s · 560 KiB

    15 images could be 560 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.3 s faster on a phone.

  • Mobile performance score: 43

    43/100

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

  • Main-thread work: 6.1 s

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

  • 3,529 HTML elements

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Clarity, clym-widget.net and Curalate and others), adding 2.0 MB and 1.2 s of main-thread time.

  • Reduce unused CSS

    600 ms · 127 KiB

    About 127 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.

  • 12 long tasks on the main thread

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

  • clym-widget.net adds 207 ms

    207 ms

    clym-widget.net costs a phone 207 ms of main-thread work and 396 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.

  • Google Tag Manager adds 164 ms

    164 ms

    Google Tag Manager costs a phone 164 ms of main-thread work and 324 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.

  • Klaviyo adds 122 ms

    122 ms

    Klaviyo costs a phone 122 ms of main-thread work and 324 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.

  • rebuyengine.com adds 102 ms

    102 ms

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

  • azurefd.net adds 51 ms

    51 ms

    azurefd.net costs a phone 51 ms of main-thread work and 315 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

    200 ms · 66 KiB

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

  • Minify CSS

    150 ms · 12 KiB

    12 KiB could be saved by minifying CSS.

  • Render-blocking requests

    150 ms

    8 files block the first paint until they finish downloading. Deferring or inlining them could save about 150 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.

1 checks passed
  • Server response: 23 ms

    23 ms

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

Core Web Vitals

7 to fix67
  • 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: 23.2 s

    23.2 s

    Your largest element takes 23.2 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: 16.2 s

    16.2 s

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

  • Time to Interactive: 28.5 s

    28.5 s

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

  • First Contentful Paint: 3.6 s

    3.6 s

    The first text or image appears after 3.6 s on a phone. Good is under 1.8 s.

  • Total Blocking Time: 612 ms

    612 ms

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

  • Real-user CLS: 0.12

    0.12

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

  • Tap response (INP) held steady for real visitors

    +6%

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

  • Largest content (LCP) held steady for real visitors

    +6%

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

5 checks passed
  • Real-user LCP: 2.0 s

    2.0 s

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

  • Real-user INP: 163 ms

    163 ms

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

  • Real-user FCP: 1.6 s

    1.6 s

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

  • Real-user TTFB: 708 ms

    708 ms

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

  • Cumulative Layout Shift: 0.022

    0.022

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

Images and page weight

1 to fix70
  • Page weight: 25.0 MB in 573 requests

    25.0 MB

    Your homepage downloads 25.0 MB in 573 requests on a phone: media 18.8 MB (2), scripts 3.1 MB (230) and other files 1.5 MB (290). Under 2 MB keeps phones on slow connections fast.

  • 1 image below the first screen load straight away

    1 image further down the page (20 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

  • About 7.1 g of CO₂ per visit

    7.10 g

    By the Sustainable Web Design model, a visit to your homepage emits about 7.10 g of CO₂e: 851.8 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 are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

6 to fixGoogle 8892
  • Certain ARIA roles must be contained by particular parents (2 elements)

    Certain ARIA roles must be contained by particular parents: 2 elements on the page fail this check, rated critical by axe-core.

  • 6 text elements with low contrast

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

  • 2 images without alt text

    2 images have no alt text, which hurts accessibility and image search.

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

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

  • 13 links without text

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

  • Alternative text of images should not be repeated as text (4 elements)

    Alternative text of images should not be repeated as text: 4 elements on the page fail this check, rated minor by axe-core.

1 checks passed
  • 47 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: 47 passed and 5 failed. 4 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

Google 92100
  • 64 internal links, 5 external

    The homepage links to 64 pages on mabeproducts.com and 5 external pages.

8 checks passed
  • Meta description: 123 characters

    Your meta description is 123 characters: “Affordable baby carriers and toddler sling designed for comfort, breathability, and everyday wear, from newborn to todd…”.

  • One H1 headline

    Your main headline reads: “Mabē”.

  • Title: 34 characters

    Your title is a healthy 34 characters: “MABĒ - Luxury Baby Carriers – Mabē”.

  • Canonical URL set

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

  • Structured data in place

    Structured data found: Organization.

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

AI search readiness

1 to fix88
  • Organization data is thin (3 of 6 facts)

    Your Organization JSON-LD is missing 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.

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.

  • Text is in the HTML

    Your server sends the page's text in the HTML (1,425 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

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

Other pages

3 to fix65
  • 3 linked pages are broken

    Your homepage links to https://mabeproducts.com/customer_authentication/redirect, https://mabeproducts.com/pages/houndstooth-collection and https://mabeproducts.com/pages/the-houndstooth-collection, which answer with an error. Visitors hit a dead end and search engines drop them.

  • 2 pages without a meta description

    https://mabeproducts.com/pages/bundles and https://mabeproducts.com/pages/her-nature-collection have no meta description, so Google writes the search snippet from whatever text it finds.

  • 12 pages without an H1

    https://mabeproducts.com/collections/houndstooth, https://mabeproducts.com/collections/all, https://mabeproducts.com/collections/the-monarch-buckle-carrier, https://mabeproducts.com/collections/monarch-toddler-sling, https://mabeproducts.com/collections/monarch-accessory-bags and https://mabeproducts.com/pages/bundles and 6 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 2 pages with very little text

    https://mabeproducts.com/collections/all and https://mabeproducts.com/products/monarch-carrier-indigo-houndstooth 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://mabeproducts.com/collections/bestsellers took over 3 s to send its HTML from our server.

  • 15 internal pages checked

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

4 checks passed
  • 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.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 12 pages that loaded have a <title>.

Best practices

1 to fixGoogle 9293
  • 5 JavaScript errors while loading

    5 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

  • 1 low-resolution image

    1 image is served at too low a resolution for sharp phone screens.

2 checks passed
  • Tap targets are thumb-sized

    20 of 21 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix57
  • 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 social proof

    No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

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

  • Only about 200 words

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

3 checks passed
  • 12 calls to action

    The homepage has 12 calls to action, for example “Shop All”, “Shop Monarch baby carriers” and “Shop monarch toddler slings”.

  • 4 short forms

    4 short forms (1 field at most) are right on the homepage.

  • Analytics in place

    Analytics detected: Google Tag Manager and Microsoft Clarity.

Privacy and tracking

1 to fix
  • 6 trackers load before any consent

    6

    Before a visitor clicks anything, the page loads Google Ads, Google Tag Manager, Klaviyo, Microsoft Clarity and Pinterest Tag 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.

  • 19 cookies set on arrival

    19

    Opening the homepage sets 19 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.

  • 46 other companies contacted

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

Upkeep, stack and company

Stack

E-commerce
10 Shopify Products;Shopify;Shopify Plus
Hosting
Shopify

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 38 issues on mabeproducts.com, including 21 speed issues and 4 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