babymaybe.co website review

12 images could be 3.2 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 11.6 s faster on a phone.

17 files are served with short cache lifetimes, so returning visitors download them again (2.7 MB).

About 448 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.3 s faster on a phone.

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

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

4 third-party services load with your homepage (format.com, Vimeo and format-assets.com and others), adding 4.4 MB and 187 ms of main-thread time.

creatorcdn.com costs a phone 0 ms of main-thread work and 3.9 MB 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.

55 KiB could be saved by minifying JavaScript.

Vimeo costs a phone 71 ms of main-thread work and 373 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.

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

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

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

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

Your largest element takes 20.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Babymaybe.co”.

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

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

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

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

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.

Your homepage downloads 4.7 MB in 52 requests on a phone: images 3.9 MB (16), scripts 765 KiB (17) and stylesheets 69 KiB (13). Under 2 MB keeps phones on slow connections fast.

5 images (899 KiB) are 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.

7 images further down the page (610 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

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

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

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

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

All page content should be contained by landmarks: 9 elements on the page fail this check, rated moderate by axe-core.

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

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

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

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

Your title is only 25 characters: “Baby Maybe - Babymaybe.co”. Between 30 and 65 characters leaves room to say what you do and for whom.

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

1 link has no real href, so search engines can't follow it.

The homepage links to 14 pages on babymaybe.co and 13 external pages.

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.

There is no https://www.babymaybe.co/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.

robots.txt blocks GPTBot, ClaudeBot, Google-Extended, Applebot-Extended and CCBot, which collect pages to train models. That's a legitimate choice and doesn't by itself stop the site appearing in AI answers, which the crawlers above handle.

https://www.babymaybe.co/untitled-custom-page 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.

/ and https://www.babymaybe.co/untitled-custom-page all use the title “Baby Maybe - Babymaybe.co”, and 2 other titles repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.babymaybe.co/about, https://www.babymaybe.co/7128251-press-news, https://www.babymaybe.co/the-interactive-gallery-experience, https://www.babymaybe.co/4495281-gallery, https://www.babymaybe.co/interview and https://www.babymaybe.co/we-are-here-here-we-are and 3 others use the same meta description. A description written for each page earns more clicks.

https://www.babymaybe.co/untitled-custom-page, https://www.babymaybe.co/about, https://www.babymaybe.co/7128251-press-news, https://www.babymaybe.co/the-interactive-gallery-experience, https://www.babymaybe.co/4495281-gallery and https://www.babymaybe.co/interview and 4 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.babymaybe.co/the-interactive-gallery-experience, https://www.babymaybe.co/4495281-gallery, https://www.babymaybe.co/interview, https://www.babymaybe.co/contact and https://www.babymaybe.co/store 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.

We fetched 10 pages linked from your homepage and read each the way a search engine does.

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

2 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

2 errors were logged to the browser console while the page loaded, for example “%c%d font-size:0;color:transparent NaN”.

Chrome logged issues while loading the page (“Cookie”).

Large scripts ship without source maps.

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

Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

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

The homepage shows no opening hours. If customers visit or call, show when.

There is no form on the homepage, so every lead has to click through to another page first.

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

The homepage carries about 583 words of visible text.

Opening the homepage sets 8 cookies, 6 of them by other companies (measured from a US location before any click).

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.

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