sleep29.com website review

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

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

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

PayPal costs a phone 200 ms of main-thread work and 392 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.

4 third-party services load with your homepage (PayPal, loox.io and Shopify and others), adding 540 KiB and 312 ms of main-thread time.

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

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

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

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

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

6 KiB could be saved by minifying CSS.

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 7.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “A better pillow for your baby's sleep We believe that your …”.

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

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

Visually, the page fills in at 4.1 s (Speed Index). Good is under 3.4 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.

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

Certain ARIA roles must be contained by particular parents: 4 elements on the page fail this check, rated critical by axe-core.

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

1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

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

All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

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

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

Your title is only 12 characters: “KidsPillow29”. Between 30 and 65 characters leaves room to say what you do and for whom.

Structured data found (Organization, Product and WebSite) but with 1 problem, for example “WebSite: potentialAction.target is not an absolute URL ("https://sleep29.com{{ routes.search_url }}…”.

No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

The homepage links to 26 pages on sleep29.com and 5 external pages.

https://sleep29.com/collections/all has no meta description, so Google writes the search snippet from whatever text it finds.

https://sleep29.com/pages/shipping-tracking 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 6 pages linked from your homepage and read each the way a search engine does.

1 of 5 tappable elements near the top of the page is smaller than 24 px, hard to hit with a thumb.

2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

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.

The homepage carries about 479 words of visible text.

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