Website review, no card needed

mellowmummy.co.uk logo

mellowmummy.co.uk website review

Visit site (opens in a new tab)Reviewed 20 November 202629 issues · 73 checks

This review found 29 issues worth fixing on mellowmummy.co.uk, 8 of them high impact, across 73 checks. The most urgent: unlabelled dropdowns. 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 mellowmummy.co.uk (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

2 to fix93
  • Avoid multiple page redirects

    608 ms

    The page goes through 1 redirect before it starts loading, costing about 608 ms. Link and advertise the final URL directly.

  • Reduce unused JavaScript

    300 ms · 39 KiB

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

  • Improve image delivery

    57 KiB

    3 images could be 57 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Document request latency

    50 ms

    The HTML itself could arrive about 50 ms sooner: redirects, a slow server response or missing compression delay everything after it.

  • 3 third-party services on the page

    3 third-party services load with your homepage (Blogger, Google/Doubleclick Ads and googleusercontent.com), adding 156 KiB and 19 ms of main-thread time.

  • Use efficient cache lifetimes

    32 KiB

    9 files are served with short cache lifetimes, so returning visitors download them again (32 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.

3 checks passed
  • Mobile performance score: 93

    93/100

    Your mobile performance score is 93. That is in Google's “good” band (90 and up).

  • Main-thread work: 0.1 s

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

  • Server response: 2 ms

    2 ms

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

Core Web Vitals

3 to fix92
  • Cumulative Layout Shift: 0.14

    0.14

    The layout shifts by 0.14 while loading, so content jumps under the reader's thumb. Good is under 0.1.

  • First Contentful Paint: 1.8 s

    1.8 s

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

  • 6 images without width and height

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

4 checks passed
  • Largest Contentful Paint: 2.0 s

    2.0 s

    Your largest element renders in 2.0 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the text “This site uses cookies from Google to deliver its services …”.

  • Time to Interactive: 2.0 s

    2.0 s

    The page is fully interactive after 2.0 s.

  • Speed Index: 1.8 s

    1.8 s

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

  • 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

100
  • 1 image in older formats

    1 image (54 KiB) is 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.

  • About 0.05 g of CO₂ per visit

    0.05 g

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

3 checks passed
  • Page weight: 169 KiB in 15 requests

    169 KiB

    Your homepage downloads 169 KiB in 15 requests on a phone: images 81 KiB (7), scripts 70 KiB (4) and HTML 9 KiB (1). That is a lean page.

  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

  • Images are sized for phones

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

Accessibility

10 to fixGoogle 5380
  • Unlabelled dropdowns

    1 dropdown has no label.

  • 14 text elements with low contrast

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

  • <dl> elements must only directly contain properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements (1 element)

    <dl> elements must only directly contain properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements: 1 element on the page fails this check, rated serious by axe-core.

  • Links look like plain text

    1 link inside paragraphs relies on colour alone to stand out.

  • 18 images without alt text

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

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

    All page content should be contained by landmarks: 3 elements on the page fail 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.

  • Zoom is disabled

    The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

  • 1 form field without a label

    1 form field has no label, so screen readers announce an empty box and autofill guesses.

  • No page language

    The <html> element has no lang attribute, so screen readers may read the page in the wrong voice and accent.

1 checks passed
  • 27 automated accessibility rules passed

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

SEO

4 to fixGoogle 8581
  • No H1 headline

    There is no <h1>, so neither visitors nor Google get a clear main headline.

  • No structured data

    No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

  • No social preview image

    No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

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

  • No X (Twitter) card tag

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

  • 126 internal links, 56 external

    The homepage links to 126 pages on mellowmummy.co.uk and 56 external pages.

5 checks passed
  • Meta description: 148 characters

    Your meta description is 148 characters: “Taking motherhood as it comes! Real-life experiences of a second-time mummy. Honest parent reviews of mother and baby A…”.

  • Title: 41 characters

    Your title is a healthy 41 characters: “Mellow Mummy : Taking life as it comes...”.

  • Canonical URL set

    The canonical URL is http://www.mellowmummy.co.uk/.

  • robots.txt in place

    robots.txt is in place and points crawlers to your sitemap.

  • XML sitemap found

    Your XML sitemap is reachable at http://www.mellowmummy.co.uk/sitemap.xml.

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://www.mellowmummy.co.uk/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,587 words), so crawlers that don't run JavaScript still read it.

Other pages

4 to fix74
  • 1 page without a title

    https://www.mellowmummy.co.uk/feeds/posts/default has no <title>, so Google invents the link text in results.

  • 1 page without a meta description

    https://www.mellowmummy.co.uk/feeds/posts/default has no meta description, so Google writes the search snippet from whatever text it finds.

  • 14 pages share a meta description

    https://www.mellowmummy.co.uk/p/about-me.html, https://www.mellowmummy.co.uk/p/birthday-cakes.html, https://www.mellowmummy.co.uk/p/recipes.html, https://www.mellowmummy.co.uk/p/disclosure-policy.html, https://www.mellowmummy.co.uk/p/privacycookie-policy.html and https://www.mellowmummy.co.uk/2017/06/feeling-refreshd-with-robinsons.html and 8 others use the same meta description. A description written for each page earns more clicks.

  • 15 pages without an H1

    https://www.mellowmummy.co.uk/p/about-me.html, https://www.mellowmummy.co.uk/p/birthday-cakes.html, https://www.mellowmummy.co.uk/p/recipes.html, https://www.mellowmummy.co.uk/p/disclosure-policy.html, https://www.mellowmummy.co.uk/p/privacycookie-policy.html and https://www.mellowmummy.co.uk/2017/06/feeling-refreshd-with-robinsons.html and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 15 internal pages checked

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

4 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

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

Best practices

3 to fixGoogle 7461
  • No mobile viewport

    No viewport meta tag, so phones render the desktop layout zoomed out.

  • 8 small tap targets

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

  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://www.blogger.com/static/v1/widgets/3772415480-widget_css_mobile_2_bundle.css' from …”.

  • 4 low-resolution images

    4 images are served at too low a resolution for sharp phone screens.

Content and conversion

1 to fix92
  • 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 252 words of copy

    The homepage carries about 252 words of visible text.

5 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “LEARN MORE”.

  • 2 calls to action

    The homepage has 2 calls to action, for example “book review” and “Subscribe”.

  • 1 short form

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

  • Social proof on the page

    Social proof on the homepage: a star rating and 8 trust badges.

  • Analytics in place

    Analytics detected: Google Tag Manager and Google Analytics.

Privacy and tracking

1 to fix
  • 1 tracker load before any consent

    1

    Before a visitor clicks anything, the page loads Google Ads (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.

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

  • 3 other companies contacted

    Loading the homepage contacts 3 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 mellowmummy.co.uk, 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
Analytics
Google Analytics | Google Tag Manager
Hosting
Google

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 mellowmummy.co.uk, including 5 speed issues, 4 SEO issues and 1 conversion gap. 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