Website review, no card needed

mumsrusandmore.com logo

mumsrusandmore.com website review

Visit site (opens in a new tab)Reviewed 8 November 202629 issues · 63 checks

This review found 29 issues worth fixing on mumsrusandmore.com, 8 of them high impact, across 63 checks. The most urgent: 4 text elements with low contrast. 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
797 ms615 msMay 30Oct 24661 ms
Show as table
DateReal-visitor load time (LCP)
May 30, 2026679 ms
Jun 6, 2026660 ms
Jun 13, 2026667 ms
Jun 20, 2026668 ms
Jun 27, 2026714 ms
Jul 4, 2026747 ms
Jul 11, 2026732 ms
Jul 18, 2026772 ms
Jul 25, 2026754 ms
Aug 1, 2026756 ms
Aug 8, 2026776 ms
Aug 15, 2026745 ms
Aug 22, 2026759 ms
Aug 29, 2026735 ms
Sep 5, 2026722 ms
Sep 12, 2026720 ms
Sep 19, 2026698 ms
Sep 26, 2026677 ms
Oct 3, 2026662 ms
Oct 10, 2026653 ms
Oct 17, 2026636 ms
Oct 24, 2026661 ms
Real-visitor tap response (INP)75th percentile, phones
97 ms86 msJun 6Oct 2487 ms
Show as table
DateReal-visitor tap response (INP)
Jun 6, 202687 ms
Jun 13, 202688 ms
Jun 20, 202689 ms
Jun 27, 202690 ms
Jul 4, 202695 ms
Jul 11, 202687 ms
Jul 18, 202692 ms
Jul 25, 202692 ms
Aug 1, 202691 ms
Aug 8, 202695 ms
Aug 15, 202694 ms
Aug 22, 202696 ms
Aug 29, 202694 ms
Sep 5, 202694 ms
Sep 12, 202695 ms
Sep 19, 202695 ms
Sep 26, 202694 ms
Oct 3, 202694 ms
Oct 10, 202692 ms
Oct 17, 202687 ms
Oct 24, 202687 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 mumsrusandmore.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. mumsrusandmore.com at 0.4 s0.4 s
  2. mumsrusandmore.com at 0.8 s0.8 s
  3. mumsrusandmore.com at 1.1 s1.1 s
  4. mumsrusandmore.com at 1.5 s1.5 s
  5. mumsrusandmore.com at 1.9 s1.9 s
  6. mumsrusandmore.com at 2.3 s2.3 s
  7. mumsrusandmore.com at 2.6 s2.6 s
  8. mumsrusandmore.com at 3.0 s3.0 s

Speed

6 to fix85
  • Mobile performance score: 85

    85/100

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

  • 7 third-party services on the page

    7 third-party services load with your homepage (Google CDN, Shopify and Clarity and others), adding 1.2 MB and 362 ms of main-thread time.

  • Reduce unused JavaScript

    464 KiB

    About 464 KiB of JavaScript is downloaded but never used on this page.

  • Improve image delivery

    285 KiB

    1 image could be 285 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Shopify adds 124 ms

    124 ms

    Shopify costs a phone 124 ms of main-thread work and 816 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 CDN adds 151 ms

    151 ms

    Google CDN costs a phone 151 ms of main-thread work and 298 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.

  • 4 long tasks on the main thread

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

  • Render-blocking requests

    150 ms

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

  • Use efficient cache lifetimes

    51 KiB

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

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

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

  • Server response: 5 ms

    5 ms

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

Core Web Vitals

4 to fix89
  • Time to Interactive: 10.5 s

    10.5 s

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

  • First Contentful Paint: 3.2 s

    3.2 s

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

  • Largest Contentful Paint: 3.2 s

    3.2 s

    Your largest element takes 3.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Daniel will remain involved as Founder & Strategic Advisor,…”. Most of its time is element render delay (1.4 s).

  • 1 image without width and height

    1 image have no width and height attributes, so the layout jumps as each one loads.

  • Tap response (INP) held steady for real visitors

    -1%

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

  • 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 0.7 s to 0.7 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

3 checks passed
  • Speed Index: 3.4 s

    3.4 s

    Visually, the page fills in at 3.4 s (Speed Index), inside the 3.4 s “good” threshold.

  • Total Blocking Time: 151 ms

    151 ms

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

  • Cumulative Layout Shift: 0.009

    0.009

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

Images and page weight

2 to fix75
  • Page weight: 2.1 MB in 151 requests

    2.1 MB

    Your homepage downloads 2.1 MB in 151 requests on a phone: other files 849 KiB (98), scripts 845 KiB (40) and images 289 KiB (2). Under 2 MB keeps phones on slow connections fast.

  • 1 image far larger than shown

    283 KiB

    1 image is downloaded at several times the size a phone draws it, for example Mums_R_Us_More_Logo_page-0001.png at 4,600 px wide, shown at 200 px. Resized copies would save about 283 KiB.

  • About 0.6 g of CO₂ per visit

    0.59 g

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

4 to fixGoogle 8087
  • 4 text elements with low contrast

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

  • Frames without titles

    1 frame has no title, so screen-reader users cannot tell what it contains.

  • No main landmark

    The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

  • All page content should be contained by landmarks (1 element)

    All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

2 checks passed
  • Every image has alt text

    All 1 image in the HTML carry an alt attribute.

  • 18 automated accessibility rules passed

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

SEO

6 to fixGoogle 9271
  • No meta description

    No meta description, so Google writes its own snippet from whatever text it finds.

  • Title is short (16 characters)

    Your title is only 16 characters: “Mums R Us & More”. 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.

  • No XML sitemap

    No XML sitemap at https://mumsrusandmore.com/sitemap.xml, so Google discovers your pages only by following links.

  • Only 0 internal links

    The homepage links to only 0 pages on your own site, so visitors and crawlers find few routes into the rest of it.

  • No favicon declared

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

  • Open Graph partly set

    Open Graph is missing og:title and og:description, so shared links fall back to guesses.

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is incomplete here.

3 checks passed
  • One H1 headline

    Your main headline reads: “Mums R Us and More Is Growing”.

  • Canonical URL set

    The canonical URL is https://mumsrusandmore.com/password.

  • robots.txt in place

    robots.txt is in place.

AI search readiness

1 to fix88
  • 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://mumsrusandmore.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 (154 words), so crawlers that don't run JavaScript still read it.

Best practices

1 to fixGoogle 9292
  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.

  • Browser-reported issues

    Chrome logged issues while loading the page (“Content security policy”).

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix42
  • 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 calls to action

    We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

  • No social proof

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

  • Only about 154 words

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

2 checks passed
  • Analytics in place

    Analytics detected: Microsoft Clarity.

  • Direct contact links

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

Privacy and tracking

1 to fix
  • 3 trackers load before any consent

    3

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

  • 11 cookies set on arrival

    11

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

  • 17 other companies contacted

    Loading the homepage contacts 17 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 mumsrusandmore.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 6 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Microsoft Clarity · Wishlist Hero · Google Youtube · Judge Me Reviews · Instafeed · Forms

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
Analytics
Microsoft Clarity
Hosting
Shopify

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 29 issues on mumsrusandmore.com, including 10 speed issues, 6 SEO 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