dreametech.com website review

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

Your mobile performance score is 14 (desktop: 52). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

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

8 third-party services load with your homepage (Google Tag Manager, Shopify and Klaviyo and others), adding 3.0 MB and 2.0 s of main-thread time.

About 1.3 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 150 ms faster on a phone.

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

Google Tag Manager costs a phone 674 ms of main-thread work and 689 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.

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

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

Shopify costs a phone 396 ms of main-thread work and 1.3 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.

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

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

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

111 KiB could be saved by minifying JavaScript.

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

Desktop scores 52 but mobile only 14. A gap that wide usually means heavy scripts and images that hit phones hardest.

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.

Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.

Your largest element takes 10.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Oct.22 - Nov.1”.

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

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

The layout shifts by 0.736 while loading, so content jumps under the reader's thumb. Good is under 0.1.

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

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

Real visitors wait 206 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

Real visitors see the first content after 2.1 s (75th percentile). Good is under 1.8 s.

Real visitors wait 1.4 s for your server to start answering (75th percentile). Good is under 800 ms.

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

Your homepage downloads 7.6 MB in 618 requests on a phone: scripts 3.8 MB (306), images 1.4 MB (68) and other files 1.3 MB (188). Under 2 MB keeps phones on slow connections fast.

homepage-af30-kv-m-new.webp 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).

10 images (951 KiB) 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.

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

Images must have alternative text: 2 elements on the page fail this check, rated critical by axe-core.

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

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

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

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

Alternative text of images should not be repeated as text: 1 element on the page fails this check, rated minor by axe-core.

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

Your title is 67 characters, so Google will cut it off around 60: “Dreame US Official Site | Robot Vacuums, Smart Home Cleaning & Tech”.

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

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

The homepage links to 244 pages on dreametech.com and 58 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.

/pages/dreame-membership, /pages/halloween-sale, /products/matrix10-ultra-robot-vacuum, /products/matrix10-pro-robot-vacuum, /products/aqua10-ultra-roller-robot-vacuum and /products/aqua10-roller-robot-vacuum and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

/products/matrix10-ultra-robot-vacuum and /products/aqua10-roller-robot-vacuum 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.

/products/l60-ultra-fe-robot-vacuum and /products/l50-ultra-robot-vacuum took over 3 s to send their HTML from our server.

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

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

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

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

Requests the notification permission on page load.

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

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.

dreametech.com's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.

Social proof on the homepage: 24 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach 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 723 words of visible text.

dreametech.com has no SPF record, so mail servers can't tell which servers may send email as you. Your mail lands in spam more often, and anyone can send mail pretending to be you.

DMARC is set to p=none, so mail pretending to be dreametech.com is still delivered. Add a report address, check the reports, then move to quarantine.

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 Criteo, Google Ads, Google Analytics, Google Tag Manager and Hotjar and 9 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 35 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 83 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.