esemblybaby.com website review

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

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

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

8 third-party services load with your homepage (ZenDesk, rebuyengine.com and Affirm and others), adding 1.9 MB and 831 ms of main-thread time.

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

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

Polyfills for old browsers add 54 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 450 ms faster on a phone.

A phone's processor spends 3.2 s on main-thread work while loading, 1.7 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

rebuyengine.com costs a phone 174 ms of main-thread work and 713 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.

ZenDesk costs a phone 177 ms of main-thread work and 395 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.

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

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

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.

4 KiB could be saved by minifying CSS.

4 KiB could be saved by minifying JavaScript.

Your largest element takes 18.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “A stack of reusable cloth diapers in various patterns and c…”.

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

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

Scripts block taps and scrolling for 363 ms in total while the page loads. Good is under 200 ms.

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

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

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

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

Your homepage downloads 4.2 MB in 343 requests on a phone: scripts 1.8 MB (106), other files 1.1 MB (193) and images 651 KiB (22). Under 2 MB keeps phones on slow connections fast.

3 images are downloaded at several times the size a phone draws them, for example Home_Homepage_Image-100_1600x.jpg at 1,600 px wide, shown at 390 px. Resized copies would save about 166 KiB.

1 image further down the page (336 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

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

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

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

There are 2 <h1> headlines (“A diapering system for sustainability” and “Home Goods”). One clear main headline is easier for people and search engines.

Your meta description is 175 characters; Google truncates after about 160, so the end of your pitch is cut.

1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

The homepage links to 57 pages on esemblybaby.com and 6 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.

/collections/home-goods has no meta description, so Google writes the search snippet from whatever text it finds.

/pages/esemble-your-system has no <h1> headline, so visitors and search engines get no clear main topic.

/pages/esemble-your-system 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 15 pages linked from your homepage (of 27 found) and read each the way a search engine does.

5 errors were logged to the browser console while the page loaded, for example “Uncaught SyntaxError: Failed to execute 'querySelector' on 'Document': '.https://esemblybaby.com/checkouts/cn/hWN19PTcJ…”.

10 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

HSTS is set, but max-age is 91 days; one year is the recommended minimum.

1 link go through two or more redirects, for example https://esemblybaby.com/account.

No Referrer-Policy header, so full URLs can leak to the sites you link to.

No Permissions-Policy header to switch off camera, microphone and location for embedded content.

X-XSS-Protection is set to “1; mode=block”; the header is deprecated and can introduce bugs. Use 0 or remove it.

There is no /.well-known/security.txt telling researchers how to report a security problem to you.

esemblybaby.com has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

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

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

The homepage has only about 195 words of visible text; thin pages give Google and first-time buyers little to go on.

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

DMARC is set to p=none, so mail pretending to be esemblybaby.com is still delivered. Reports are on, so moving to quarantine is the next step.

Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Hotjar and Klaviyo and 4 mores (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.

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