Website review, no card needed

Babylist logo

babylist.com website review

Visit site (opens in a new tab)Reviewed 11 October 202630 issues · 79 checks

This review found 30 issues worth fixing on babylist.com, 14 of them high impact, across 79 checks. The most urgent: render-blocking requests. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

Read the full growth playbook for Babylist

  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
2.1 s1.9 sApr 18Oct 32.0 s
Show as table
DateReal-visitor load time (LCP)
Apr 18, 20261.9 s
Apr 25, 20261.9 s
May 2, 20262.0 s
May 9, 20262.0 s
May 16, 20262.0 s
May 23, 20262.0 s
May 30, 20262.0 s
Jun 6, 20262.0 s
Jun 13, 20262.1 s
Jun 20, 20262.0 s
Jun 27, 20262.0 s
Jul 4, 20262.0 s
Jul 11, 20262.0 s
Jul 18, 20262.0 s
Jul 25, 20262.0 s
Aug 1, 20262.0 s
Aug 8, 20261.9 s
Aug 15, 20261.9 s
Aug 22, 20261.9 s
Aug 29, 20261.9 s
Sep 5, 20262.0 s
Sep 12, 20262.0 s
Sep 19, 20262.0 s
Sep 26, 20262.0 s
Oct 3, 20262.0 s
Real-visitor tap response (INP)75th percentile, phones
181 ms157 msApr 18Oct 3160 ms
Show as table
DateReal-visitor tap response (INP)
Apr 18, 2026170 ms
Apr 25, 2026171 ms
May 2, 2026171 ms
May 9, 2026171 ms
May 16, 2026171 ms
May 23, 2026172 ms
May 30, 2026172 ms
Jun 6, 2026171 ms
Jun 13, 2026169 ms
Jun 20, 2026166 ms
Jun 27, 2026165 ms
Jul 4, 2026169 ms
Jul 11, 2026170 ms
Jul 18, 2026171 ms
Jul 25, 2026173 ms
Aug 1, 2026175 ms
Aug 8, 2026176 ms
Aug 15, 2026177 ms
Aug 22, 2026178 ms
Aug 29, 2026177 ms
Sep 5, 2026171 ms
Sep 12, 2026170 ms
Sep 19, 2026162 ms
Sep 26, 2026161 ms
Oct 3, 2026160 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 babylist.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

4 to fix68
  • Render-blocking requests

    2.2 s

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

  • Reduce unused CSS

    1.4 s · 259 KiB

    About 259 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.4 s faster on a phone.

  • Improve image delivery

    600 ms · 577 KiB

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

  • Mobile performance score: 68

    68/100

    Your mobile performance score is 68 (desktop: 95). Pages that score under 90 lose visitors before the first paint.

  • Phones get a much slower page than desktops

    Desktop scores 95 but mobile only 68. A gap that wide usually means heavy scripts and images that hit phones hardest.

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

  • 3 third-party services on the page

    3 third-party services load with your homepage (Google Fonts, Impact Radius and Yahoo!), adding 3 KiB and 0 ms of main-thread time.

2 checks passed
  • Main-thread work: 0.3 s

    A phone's processor spends 0.3 s on main-thread work while loading, 9 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

5 to fix100
  • Largest Contentful Paint: 7.4 s

    7.4 s

    Your largest element takes 7.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “The baby registry that grows with your family Start a Babyl…”.

  • Time to Interactive: 7.6 s

    7.6 s

    The page becomes fully interactive after 7.6 s. Good is under 3.8 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.

  • Speed Index: 4.4 s

    4.4 s

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

  • 22 images without width and height

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

  • Tap response (INP) held steady for real visitors

    -6%

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

  • Largest content (LCP) held steady for real visitors

    +5%

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

8 checks passed
  • Passes Core Web Vitals for real visitors

    Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).

  • Real-user LCP: 1.4 s

    1.4 s

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

  • Real-user INP: 137 ms

    137 ms

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

  • Real-user CLS: 0.00

    0.00

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

  • Real-user FCP: 1.3 s

    1.3 s

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

  • Real-user TTFB: 507 ms

    507 ms

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

  • 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 fix90
  • 1 image far larger than shown

    89 KiB

    1 image is downloaded at several times the size a phone draws it, for example AddAnything_Phone_rllgoq.png at 1,488 px wide, shown at 293 px. Resized copies would save about 89 KiB.

  • About 0.4 g of CO₂ per visit

    0.42 g

    By the Sustainable Web Design model, a visit to your homepage emits about 0.42 g of CO₂e: 50.2 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: 1.5 MB in 33 requests

    1.5 MB

    Your homepage downloads 1.5 MB in 33 requests on a phone: images 869 KiB (21), fonts 353 KiB (7) and stylesheets 271 KiB (4). That is a lean page.

  • 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

8 to fixGoogle 8686
  • 6 tap targets too small

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

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

  • Interactive controls must not be nested (5 elements)

    Interactive controls must not be nested: 5 elements on the page fail this check, rated serious by axe-core.

  • Hidden but focusable

    2 elements hidden from screen readers can still receive keyboard focus.

  • Malformed lists

    Some lists contain elements other than list items, which screen readers announce wrongly.

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

  • 1 form field without a label

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

  • Links look like plain text

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

2 checks passed
  • Every image has alt text

    All 6 images in the HTML carry an alt attribute.

  • 39 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 45 WCAG 2.2 A/AA and best-practice rules on the phone render: 39 passed and 6 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 10097
  • 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.

  • No X (Twitter) card tag

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

  • 96 internal links, 11 external

    The homepage links to 96 pages on babylist.com and 11 external pages.

7 checks passed
  • Meta description: 157 characters

    Your meta description is 157 characters: “Babylist is the best baby registry for growing families. Add baby gear from any store including Amazon, Target, and Ets…”.

  • One H1 headline

    Your main headline reads: “The baby registry that grows with your family”.

  • Title: 33 characters

    Your title is a healthy 33 characters: “Babylist - The Best Baby Registry”.

  • Canonical URL set

    The canonical URL is https://www.babylist.com/.

  • Structured data in place

    Structured data found: FAQPage, Organization, WebPage and WebSite.

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

AI search readiness

1 to fix88
  • Some text only appears after JavaScript runs

    37%

    The HTML your server sends has 525 of the 1,434 words a browser shows. AI crawlers don't run JavaScript, so they miss the rest.

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.

  • Organization data: 6 of 6 facts

    Your Organization JSON-LD gives name, url, logo, sameAs (social profiles), description and contact details.

  • llms.txt published

    The site publishes https://www.babylist.com/llms.txt (30 KiB, 146 links), a plain-text guide to the site for AI tools.

Other pages

5 to fix58
  • 2 pages without a title

    https://www.babylist.com/hello-baby and https://www.babylist.com/hello-baby/how-to-create-a-baby-registry have no <title>, so Google invents the link text in results.

  • 1 page points its canonical at the homepage

    https://www.babylist.com/index declares the homepage as its canonical URL, which tells Google it is a copy of the homepage and keeps it out of search results. A site-wide template setting usually causes this.

  • 2 pages share a title

    / and https://www.babylist.com/index all use the title “Babylist - The Best Baby Registry”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 4 pages without a meta description

    https://www.babylist.com/store, https://www.babylist.com/hello-baby, https://www.babylist.com/reservations and https://www.babylist.com/hello-baby/how-to-create-a-baby-registry have no meta description, so Google writes the search snippet from whatever text it finds.

  • 8 pages without an H1

    https://www.babylist.com/store, https://www.babylist.com/hello-baby, https://www.babylist.com/money, https://www.babylist.com/money/early-investor, https://www.babylist.com/health and https://www.babylist.com/reservations and 2 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 3 pages with very little text

    https://www.babylist.com/store, https://www.babylist.com/registry/new and https://www.babylist.com/hello-baby/how-to-create-a-baby-registry 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.

  • 15 internal pages checked

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

2 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

Best practices

3 to fixGoogle 10071
  • 1 broken image

    1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=5708904&tm=gtm002&Ver=2&mid=a94f02b4-a632-4223-bfcb-79d8906e24fc&bo=1&sid=858aae00c5ac11f189cdb5014fad6038&vid=858b7320c5ac11f19f35271ca989287e&vids=1&msclkid=N&pi=918.

  • 6 small tap targets

    6 of 25 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 “Uncaught Error: Minified React error #418; visit https://reactjs.org/docs/error-decoder.html?invariant=418 for the full…”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix70
  • 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.

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

  • About 1,434 words of copy

    The homepage carries about 1,434 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: “Sign up” and “Start a Babylist”.

  • 21 calls to action

    The homepage has 21 calls to action, for example “Sign up”, “Shop” and “Sign Up”.

  • Analytics in place

    Analytics detected: Google Analytics and Meta Pixel.

Privacy and tracking

  • 11 trackers load before any consent

    11

    Before a visitor clicks anything, the page loads Amplitude, Comscore, Criteo, Google Ads and Google Analytics and 6 mores (measured from a US location before any click). A consent tool (Osano) is installed; check it blocks these until visitors agree where the law requires it.

  • 34 cookies set on arrival

    34

    Opening the homepage sets 34 cookies (measured from a US location before any click).

  • 43 other companies contacted

    Loading the homepage contacts 43 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.

1 checks passed
  • Consent tool: Osano

    A consent management tool (Osano) loads with the page.

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 babylist.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
Shopify
Analytics
Google Analytics

Hiring

Hiring
42 open roles
Teams
Product (12), Engineering (8), Data (4), Fulfillment (3)
Job board
greenhouse

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 30 issues on babylist.com, including 9 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