Website review, no card needed

maddie-moo.com logo

maddie-moo.com website review

Visit site (opens in a new tab)Reviewed 20 November 202620 issues · 59 checks

This review found 20 issues worth fixing on maddie-moo.com, 10 of them high impact, across 59 checks. The most urgent: render-blocking requests. 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

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

How it loaded on a phone

  1. maddie-moo.com at 0.5 s0.5 s
  2. maddie-moo.com at 0.9 s0.9 s
  3. maddie-moo.com at 1.4 s1.4 s
  4. maddie-moo.com at 1.9 s1.9 s
  5. maddie-moo.com at 2.3 s2.3 s
  6. maddie-moo.com at 2.8 s2.8 s
  7. maddie-moo.com at 3.3 s3.3 s
  8. maddie-moo.com at 3.7 s3.7 s

Speed

3 to fix64
  • Render-blocking requests

    1.5 s

    36 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.5 s.

  • Mobile performance score: 64

    64/100

    Your mobile performance score is 64. Pages that score under 90 lose visitors before the first paint.

  • Reduce unused JavaScript

    600 ms · 118 KiB

    About 118 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 600 ms faster on a phone.

  • Improve image delivery

    200 ms · 183 KiB

    4 images could be 183 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 200 ms faster on a phone.

  • Reduce unused CSS

    150 ms · 13 KiB

    About 13 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 113 KiB and 2 ms of main-thread time.

  • 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: 0.9 s

    A phone's processor spends 0.9 s on main-thread work while loading, 425 ms of it running JavaScript. That is comfortably low.

  • Server response: 6 ms

    6 ms

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

Core Web Vitals

4 to fix67
  • Largest Contentful Paint: 11.8 s

    11.8 s

    Your largest element takes 11.8 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: 12.2 s

    12.2 s

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

  • Speed Index: 6.4 s

    6.4 s

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

  • First Contentful Paint: 3.0 s

    3.0 s

    The first text or image appears after 3.0 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.

2 checks passed
  • Cumulative Layout Shift: 0

    0

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

  • Total Blocking Time: 0 ms

    0 ms

    Scripts block the page for only 0 ms while loading. Good is under 200 ms.

Images and page weight

1 to fix70
  • Page weight: 5.5 MB in 82 requests

    5.5 MB

    Your homepage downloads 5.5 MB in 82 requests on a phone: images 4.9 MB (15), scripts 346 KiB (29) and fonts 106 KiB (5). Under 2 MB keeps phones on slow connections fast.

  • 1 image below the first screen load straight away

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

  • About 1.5 g of CO₂ per visit

    1.55 g

    By the Sustainable Web Design model, a visit to your homepage emits about 1.55 g of CO₂e: 185.6 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

7 to fixGoogle 8891
  • 38 text elements with low contrast

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

  • 10 tap targets too small

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

  • [role="img"] and [role="image"] elements must have alternative text (7 elements)

    [role="img"] and [role="image"] elements must have alternative text: 7 elements on the page fail this check, rated serious by axe-core.

  • Contentinfo landmark should not be contained in another landmark (1 element)

    Contentinfo landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.

  • Document should not have more than one contentinfo landmark (1 element)

    Document should not have more than one contentinfo landmark: 1 element on the page fails this check, rated moderate by axe-core.

  • Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)

    Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

  • 9 links without text

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

  • Headings skip levels

    Headings skip levels (h2 → h5, h2 → h4 and h2 → h5), which makes the page harder to scan with a screen reader.

2 checks passed
  • Every image has alt text

    All 10 images in the HTML carry an alt attribute.

  • 47 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 55 WCAG 2.2 A/AA and best-practice rules on the phone render: 47 passed and 8 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

1 to fixGoogle 10093
  • Title is short (23 characters)

    Your title is only 23 characters: “Maddie Moo | Maddie Moo”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • 15 internal links, 8 external

    The homepage links to 15 pages on maddie-moo.com and 8 external pages.

7 checks passed
  • Meta description: 154 characters

    Your meta description is 154 characters: “At Maddie Moo, we celebrate every moment of your pregnancy! Our curated collection offers everything from stylish belly…”.

  • One H1 headline

    Your main headline reads: “Embrace your journey with style and comfort!”.

  • Canonical URL set

    The canonical URL is https://maddie-moo.com/.

  • Structured data in place

    Structured data found: ImageObject, Organization, WebPage 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://maddie-moo.com/sitemap_index.xml.

AI search readiness

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

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

  • No llms.txt

    There is no https://maddie-moo.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.

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 (1,873 words), so crawlers that don't run JavaScript still read it.

Best practices

1 to fixGoogle 9692
  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “wp is not defined”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix75
  • 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 analytics detected

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

  • 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 1,484 words of copy

    The homepage carries about 1,484 words of visible text.

4 checks passed
  • 7 calls to action

    The homepage has 7 calls to action, for example “Contact”, “Learn More” and “Shop Now”.

  • 1 short form

    A short form (3 fields at most) is right on the homepage, asking for an email.

  • Social proof on the page

    Social proof on the homepage: 71 testimonial or review blocks and a star rating.

  • Direct contact links

    Visitors can reach you directly: 0 phone links and 1 email link.

Privacy and tracking

  • 7 cookies set on arrival

    7

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

  • 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 maddie-moo.com, 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 © 2025.

Stack

CMS
WordPress
E-commerce
WooCommerce
Hosting
DigitalOcean

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 20 issues on maddie-moo.com, including 7 speed issues, 1 SEO issue 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