Programmable

Website review, no card needed

getthatbaby.com logo

getthatbaby.com website review

Visit site (opens in a new tab)Reviewed 11 November 202628 issues · 72 checks

This review found 28 issues worth fixing on getthatbaby.com, 10 of them high impact, across 72 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

Site score

75C

Closest competitors among WooCommerce stores

Compare side by side

One score from every part of this review. How it works

getthatbaby.com (opens in a new tab)
Full-page screenshot of getthatbaby.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. getthatbaby.com at 0.6 s0.6 s
  2. getthatbaby.com at 1.3 s1.3 s
  3. getthatbaby.com at 1.9 s1.9 s
  4. getthatbaby.com at 2.6 s2.6 s
  5. getthatbaby.com at 3.2 s3.2 s
  6. getthatbaby.com at 3.8 s3.8 s
  7. getthatbaby.com at 4.5 s4.5 s
  8. getthatbaby.com at 5.1 s5.1 s

Speed

6 to fix66

  • Improve image delivery

    2.1 s · 419 KiB

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

  • Render-blocking requests

    2.1 s

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

  • Mobile performance score: 66

    66/100

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

  • Reduce unused JavaScript

    300 ms · 369 KiB

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

  • Reduce unused CSS

    300 ms · 93 KiB

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

  • Google CDN adds 266 ms

    266 ms

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

  • 3 third-party services on the page

    3 third-party services load with your homepage (Google CDN, Other Google APIs/SDKs and Google Fonts), adding 813 KiB and 294 ms of main-thread time.

  • Font display

    100 ms

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

  • 4 long tasks on the main thread

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

  • Legacy JavaScript

    10 KiB

    Polyfills for old browsers add 10 KiB JavaScript that modern phones do not need.

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

  • Minify JavaScript

    4 KiB

    4 KiB could be saved by minifying JavaScript.

2 checks passed

  • Main-thread work: 1.4 s

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

  • Server response: 3 ms

    3 ms

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

Core Web Vitals

4 to fix67

  • Largest Contentful Paint: 8.1 s

    8.1 s

    Your largest element takes 8.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Boosting fertility, naturally... Herbal Baby™ is a natural …”.

  • Time to Interactive: 12.3 s

    12.3 s

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

  • Speed Index: 8.2 s

    8.2 s

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

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

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

    0.004

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

  • Total Blocking Time: 32 ms

    32 ms

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

Images and page weight

1 to fix85

  • Page weight: 2.6 MB in 101 requests

    2.6 MB

    Your homepage downloads 2.6 MB in 101 requests on a phone: scripts 987 KiB (52), images 745 KiB (8) and other files 357 KiB (4). Under 2 MB keeps phones on slow connections fast.

  • 1 image in older formats

    1 image (180 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.7 g of CO₂ per visit

    0.73 g

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

4 to fixGoogle 9294

  • 5 text elements with low contrast

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

  • 2 tap targets too small

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

  • Links must have discernible text (1 element)

    Links must have discernible text: 1 element on the page fails this check, rated serious by axe-core.

  • 2 form fields without a label

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

  • Headings skip levels

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

2 checks passed

  • Every image has alt text

    All 17 images in the HTML carry an alt attribute.

  • 51 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: 51 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

4 to fixGoogle 8581

  • No meta description

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

  • 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 (also missing: og:title, og:description), 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.

  • 35 internal links, 8 external

    The homepage links to 35 pages on getthatbaby.com and 8 external pages.

5 checks passed

  • One H1 headline

    Your main headline reads: “Boosting fertility, naturally...”.

  • Title: 33 characters

    Your title is a healthy 33 characters: “Get That Baby – My WordPress Blog”.

  • Canonical URL set

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

  • 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://getthatbaby.com/wp-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://getthatbaby.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,079 words), so crawlers that don't run JavaScript still read it.

Other pages

3 to fix65

  • 1 linked page is broken

    Your homepage links to https://getthatbaby.com/ssl, which answers with an error. Visitors hit a dead end and search engines drop it.

  • 14 pages without a meta description

    https://getthatbaby.com/about-herbal-baby, https://getthatbaby.com/buy-herbal-baby, https://getthatbaby.com/product-background, https://getthatbaby.com/blog, https://getthatbaby.com/fertility-resources and https://getthatbaby.com/contact and 8 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 7 pages without an H1

    https://getthatbaby.com/blog, https://getthatbaby.com/2011/03/27/veg-michigan-vegfest-vegetarian-taste-fest-expo-huge-turnout, https://getthatbaby.com/2010/05/12/herbal-baby-vs-in-vitro-fertilization, https://getthatbaby.com/2010/04/01/guys-theyre-important-too, https://getthatbaby.com/2010/03/12/herbal-baby-ella-born-today and https://getthatbaby.com/2010/01/24/when-should-i-see-a-doctor-about-fertility and 1 other have no <h1> headline, so visitors and search engines get no clear main topic.

  • 4 pages slow to respond

    https://getthatbaby.com/2010/05/12/herbal-baby-vs-in-vitro-fertilization, https://getthatbaby.com/2010/01/24/when-should-i-see-a-doctor-about-fertility, https://getthatbaby.com/testimonials and https://getthatbaby.com/press-room took over 3 s to send their HTML from our server.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 16 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 14 pages that loaded have a <title>.

Best practices

2 to fixGoogle 9687

  • 10 small tap targets

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

  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

1 checks passed

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix75

  • Thin social proof

    Social proof on the homepage: 60 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

  • 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 256 words of copy

    The homepage carries about 256 words of visible text.

3 checks passed

  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “learn more about us” and “Learn More”.

  • 9 calls to action

    The homepage has 9 calls to action, for example “Buy Herbal Baby”, “Contact” and “learn more about us”.

  • 1 short form

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

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.

  • 4 other companies contacted

    Loading the homepage contacts 4 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 getthatbaby.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 © 2020.

Stack

CMS
WordPress
Framework
jQuery
E-commerce
WooCommerce
Hosting
Liquid Web

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 28 issues on getthatbaby.com, including 10 speed issues, 4 SEO issues and 3 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