dreamlab.shop website review

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

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

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

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

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

6 third-party services load with your homepage (Google Tag Manager, Shopify and shop.app and others), adding 375 KiB and 161 ms of main-thread time.

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

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

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

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

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 11.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image. Most of its time is element render delay (4.6 s).

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

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

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 2.0 MB in 248 requests on a phone: other files 1.0 MB (178), scripts 477 KiB (49) and images 343 KiB (8). Under 2 MB keeps phones on slow connections fast.

1 image is downloaded at several times the size a phone draws it, for example fairy1_640x.png at 582 px wide, shown at 162 px. Resized copies would save about 16 KiB.

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

1 dropdown has no label.

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

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

1 element has a tabindex above 0, which scrambles the keyboard order.

All page content should be contained by landmarks: 4 elements on the page fail 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 elements hidden from screen readers can still receive keyboard focus.

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

Your meta description is only 14 characters: “We love you. ❤”. 70 to 160 characters is enough to sell the click.

Structured data found (BreadcrumbList and Organization) but with 1 problem, for example “Organization: potentialAction.target is not an absolute URL ("https://dreamlab.shop/en-us/search?q={search_term}")”.

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

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

Your <h1> is empty.

The homepage links to 33 pages on dreamlab.shop and 2 external pages.

Your Organization JSON-LD is missing logo, sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

Your homepage links to https://dreamlab.shop/en-us/collections/vendors, which answers with an error. Visitors hit a dead end and search engines drop it.

https://dreamlab.shop/en-us/blogs/news, https://dreamlab.shop/en-us/pages/events, https://dreamlab.shop/en-us/pages/8-directions, https://dreamlab.shop/en-us/pages/contact and https://dreamlab.shop/en-us/collections/all have no meta description, so Google writes the search snippet from whatever text it finds.

https://dreamlab.shop/en-us/pages/events has no <h1> headline, so visitors and search engines get no clear main topic.

https://dreamlab.shop/en-us/pages/events, https://dreamlab.shop/en-us/pages/8-directions and https://dreamlab.shop/en-us/pages/contact have 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 20 found) and read each the way a search engine does.

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

1 error was logged to the browser console while the page loaded, for example “Error producing monorail event MonorailRequestError: Error completing request. A network failure may have prevented the…”.

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

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