mimibeds.com website review

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

23 images could be 12.2 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 800 ms faster on a phone.

8 third-party services load with your homepage (Shopify, Hotjar and Klaviyo and others), adding 13.3 MB and 1.4 s of main-thread time.

Shopify costs a phone 436 ms of main-thread work and 11.8 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 790 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 300 ms faster on a phone.

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

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

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

Hotjar costs a phone 397 ms of main-thread work and 280 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.

Klaviyo costs a phone 325 ms of main-thread work and 670 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.

The page has 2,419 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

fwcdn3.com costs a phone 97 ms of main-thread work and 406 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.

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

About 67 KiB of CSS is downloaded but never applied on this page.

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

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

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

5 KiB could be saved by minifying JavaScript.

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

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

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

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

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

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

7 images weigh 19.2 MB together. On a phone connection a single image that size takes seconds.

8 images are downloaded at several times the size a phone draws them, for example Toddler-Approved.gif at 512 px wide, shown at 16 px. Resized copies would save about 19.2 MB.

Your homepage downloads 17.5 MB in 582 requests on a phone: images 12.7 MB (38), scripts 2.3 MB (243) and other files 1.6 MB (241). Under 2 MB keeps phones on slow connections fast.

7 images (19.2 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.

Mobile-last-sec-image_50636bfc-054a-429d-9ab2-42ffeb75bee2.p is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

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

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

Scrollable region must have keyboard access: 2 elements on the page fail this check, rated serious by axe-core.

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

51 form fields have no label, so screen readers announce an empty box and autofill guesses.

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

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

Elements with visible text labels do not have matching accessible names. (1 element).

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

No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

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

Your <h1> is empty.

The homepage links to 82 pages on mimibeds.com and 15 external pages.

https://www.mimibeds.com/customer_authentication/redirect has no <title>, so Google invents the link text in results.

https://www.mimibeds.com/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

https://www.mimibeds.com/collections/nursery and https://www.mimibeds.com/pages/nursery all use the title “NURSERY – Mimi Beds”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.mimibeds.com/collections/all, https://www.mimibeds.com/customer_authentication/redirect, https://www.mimibeds.com/collections/all-products, https://www.mimibeds.com/collections/montessori-bed, https://www.mimibeds.com/collections/convertible-cribs and https://www.mimibeds.com/collections/nursery and 7 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.mimibeds.com/collections/all, https://www.mimibeds.com/customer_authentication/redirect, https://www.mimibeds.com/collections/all-products, https://www.mimibeds.com/collections/montessori-bed, https://www.mimibeds.com/collections/convertible-cribs and https://www.mimibeds.com/collections/nursery and 4 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.mimibeds.com/collections/convertible-cribs, https://www.mimibeds.com/collections/nursery, https://www.mimibeds.com/collections/mattress-combos, https://www.mimibeds.com/collections/accessories-1, https://www.mimibeds.com/pages/nursery and https://www.mimibeds.com/pages/transition-room-starter-kit and 5 others took over 3 s to send their HTML from our server.

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

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

4 errors were logged to the browser console while the page loaded, for example “Unexpected token '}'”.

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.

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

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 1,260 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Hotjar and Klaviyo and 3 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 22 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 44 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.