babyume.com website review

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

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

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

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

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

6 third-party services load with your homepage (Google CDN, Blogger and Cloudflare CDN and others), adding 1.7 MB and 80 ms of main-thread time.

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

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

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

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

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

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

Your largest element takes 5.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.

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

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

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

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

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

12 images (1.4 MB) 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.

1 image is downloaded at several times the size a phone draws it, for example image1-36.jpeg at 1,154 px wide, shown at 330 px. Resized copies would save about 105 KiB.

7 images further down the page (320 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 0.52 g of CO₂e: 62.1 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

1 element use ARIA attributes their role does not allow, which confuses screen readers.

Certain ARIA roles must contain particular children: 1 element on the page fails this check, rated critical by axe-core.

ARIA attributes must conform to valid values: 1 element on the page fails this check, rated critical by axe-core.

5 links inside paragraphs rely on colour alone to stand out.

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

ARIA input fields must have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

<html> element must have a lang attribute: 1 element on the page fails this check, rated serious by axe-core.

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

Interactive controls must not be nested: 1 element on the page fails this check, rated serious by axe-core.

All page content should be contained by landmarks: 11 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.

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

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

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

Elements marked as presentational should be consistently ignored: 1 element on the page fails this check, rated minor by axe-core.

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

Your title is only 8 characters: “BABY UME”. 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.

No Open Graph image (also missing: og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

5 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

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

The homepage links to 47 pages on babyume.com and 11 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.babyume.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.

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

https://www.babyume.com/p/about.html, https://www.babyume.com/p/contact.html, https://www.babyume.com/2017/06/bedtime-routines.html, https://www.babyume.com/2018/09/my-favorite-lip-conditioners.html, https://www.babyume.com/2018/07/10-ways-to-practice-self-love.html and https://www.babyume.com/2018/07/8-beauty-products-im-crushing-on-this.html and 6 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.babyume.com/feeds/posts/default has no <h1> headline, so visitors and search engines get no clear main topic.

https://www.babyume.com/p/contact.html has 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 12 pages linked from your homepage and read each the way a search engine does.

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

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/2872013778-css_bundle_v2.css' from origin 'http:…”.

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 testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

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

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

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 487 words of visible text.

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 7 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.