moonboon.hr website review

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

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

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

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

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

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

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

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

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

8 third-party services load with your homepage (Klaviyo, Shopify and 9gtb.com and others), adding 707 KiB and 466 ms of main-thread time.

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

4 KiB could be saved by minifying JavaScript.

11 long tasks block the main thread while loading, the longest for 134 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.

Your largest element takes 23.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Moonboon cradle in a calm bedroom”.

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

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

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

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 24.3 MB in 360 requests on a phone: media 19.7 MB (3), images 2.1 MB (117) and other files 1.2 MB (112). Under 2 MB keeps phones on slow connections fast.

5581ded5-7862-4993-ad3d-669858ca95bb.png weighs 1.5 MB. On a phone connection a single image that size takes seconds.

1 image is downloaded at several times the size a phone draws it, for example 5581ded5-7862-4993-ad3d-669858ca95bb.png at 1,181 px wide, shown at 320 px. Resized copies would save about 510 KiB.

1 image (1.5 MB) is 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.

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

19 text elements don'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.

Some list items are not inside a list.

Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

Summary elements must have discernible text: 1 element on the page fails this check, rated serious by axe-core.

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

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

Banner landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.

Document should not have more than one banner landmark: 1 element on the page fails this check, rated moderate by axe-core.

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

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

1 visible link has no text or label, so screen readers cannot say where it goes.

Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

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

Structured data found (Organization and WebSite) but with 1 problem, for example “Organization: url points at a different host (https://moonboon.com)”.

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

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

The homepage links to 314 pages on moonboon.hr and 59 external pages.

https://moonboon.hr/pages/klarna-faqs and https://moonboon.hr/collections/accessories are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

https://moonboon.hr/pages/klarna-faqs, https://moonboon.hr/collections/bundles, https://moonboon.hr/collections/cradle-bouncers, https://moonboon.hr/collections/cradle and https://moonboon.hr/collections/accessories have no meta description, so Google writes the search snippet from whatever text it finds.

https://moonboon.hr/pages/klarna-faqs and https://moonboon.hr/collections/cradle have no <h1> headline, so visitors and search engines get no clear main topic.

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

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

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

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

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