Website review, no card needed
dreame.tech website review
Visit site (opens in a new tab)Reviewed 21 October 202653 issues · 74 checks
This review found 53 issues worth fixing on dreame.tech, 18 of them high impact, across 74 checks. The most urgent: clink.cn adds 1.6 s. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
63DClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 7.2 s |
| May 9, 2026 | 7.2 s |
| May 16, 2026 | 7.2 s |
| May 23, 2026 | 7.0 s |
| May 30, 2026 | 7.2 s |
| Jun 6, 2026 | 7.3 s |
| Jun 13, 2026 | 7.4 s |
| Jun 20, 2026 | 7.8 s |
| Jun 27, 2026 | 7.9 s |
| Jul 4, 2026 | 7.9 s |
| Jul 11, 2026 | 7.9 s |
| Jul 18, 2026 | 7.5 s |
| Jul 25, 2026 | 7.1 s |
| Aug 1, 2026 | 7.2 s |
| Aug 8, 2026 | 7.1 s |
| Aug 15, 2026 | 7.6 s |
| Aug 22, 2026 | 7.3 s |
| Aug 29, 2026 | 7.3 s |
| Sep 5, 2026 | 7.5 s |
| Sep 12, 2026 | 7.2 s |
| Sep 19, 2026 | 7.1 s |
| Sep 26, 2026 | 6.7 s |
| Oct 3, 2026 | 6.6 s |
| Oct 10, 2026 | 6.4 s |
| Oct 17, 2026 | 6.6 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 113 ms |
| May 9, 2026 | 122 ms |
| May 16, 2026 | 118 ms |
| May 23, 2026 | 120 ms |
| May 30, 2026 | 119 ms |
| Jun 6, 2026 | 111 ms |
| Jun 13, 2026 | 113 ms |
| Jun 20, 2026 | 110 ms |
| Jun 27, 2026 | 111 ms |
| Jul 4, 2026 | 117 ms |
| Jul 11, 2026 | 115 ms |
| Jul 18, 2026 | 113 ms |
| Jul 25, 2026 | 109 ms |
| Aug 1, 2026 | 113 ms |
| Aug 8, 2026 | 112 ms |
| Aug 15, 2026 | 113 ms |
| Aug 22, 2026 | 108 ms |
| Aug 29, 2026 | 104 ms |
| Sep 5, 2026 | 102 ms |
| Sep 12, 2026 | 101 ms |
| Sep 19, 2026 | 101 ms |
| Sep 26, 2026 | 98 ms |
| Oct 3, 2026 | 103 ms |
| Oct 10, 2026 | 104 ms |
| Oct 17, 2026 | 107 ms |
Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.
One score from every part of this review. How it works
How it loaded on a phone
1.9 s
3.9 s
5.8 s
7.7 s
9.6 s
11.6 s
13.5 s
15.4 s
Speed
clink.cn adds 1.6 s
1.6 sclink.cn costs a phone 1.6 s of main-thread work and 44 KiB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.
3 long tasks on the main thread
3 long tasks block the main thread while loading, the longest for 1.9 s. During a long task the page ignores taps.
1 third-party service on the page
1 third-party service load with your homepage (clink.cn), adding 44 KiB and 1.6 s of main-thread time.
Document request latency
800 ms · 227 KiBThe HTML itself could arrive about 800 ms sooner: redirects, a slow server response or missing compression delay everything after it.
Mobile performance score: 55
55/100Your mobile performance score is 55 (desktop: 39). Pages that score under 90 lose visitors before the first paint.
Reduce initial server response time
777 msReduce initial server response time. Google estimates savings of 777 ms on a phone.
Render-blocking requests
700 ms11 files block the first paint until they finish downloading. Deferring or inlining them could save about 700 ms.
Main-thread work: 3.7 s
A phone's processor spends 3.7 s on main-thread work while loading, 2.6 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Use efficient cache lifetimes
322 KiB11 files are served with short cache lifetimes, so returning visitors download them again (322 KiB).
Server response: 877 ms
877 msYour server takes 877 ms to send the HTML. Google recommends under 600 ms; everything else waits for it.
Improve image delivery
210 KiB3 images could be 210 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Reduce unused CSS
194 KiBAbout 194 KiB of CSS is downloaded but never applied on this page.
Reduce unused JavaScript
178 KiBAbout 178 KiB of JavaScript is downloaded but never used on this page.
Chained critical requests
Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.
Core Web Vitals
Fails Core Web Vitals for real visitors
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.
Real-user LCP: 6.6 s
6.6 sReal visitors wait 6.6 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user CLS: 0.56
0.56For real visitors the layout shifts by 0.56 (75th percentile). Good is under 0.1.
Real-user FCP: 4.0 s
4.0 sReal visitors see the first content after 4.0 s (75th percentile). Good is under 1.8 s.
Time to Interactive: 13.4 s
13.4 sThe page becomes fully interactive after 13.4 s. Good is under 3.8 s.
Speed Index: 9.1 s
9.1 sVisually, the page fills in at 9.1 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 1.0 s
1.0 sScripts block taps and scrolling for 1.0 s in total while the page loads. Good is under 200 ms.
First Contentful Paint: 3.2 s
3.2 sThe first text or image appears after 3.2 s on a phone. Good is under 1.8 s.
Real-user TTFB: 1.6 s
1.6 sReal visitors wait 1.6 s for your server to start answering (75th percentile). Good is under 800 ms.
Largest Contentful Paint: 3.5 s
3.5 sYour largest element takes 3.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “创新尖端科技,普惠智能生活/家庭智能清洁全场景解决方案”. Most of its time is element render delay (2.0 s).
1 image without width and height
1 image have no width and height attributes, so the layout jumps as each one loads.
4 checks passed
Real-user INP: 114 ms
114 msReal visitors wait 114 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Tap response (INP) got 10% faster for real visitors
-10%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 113 ms to 107 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 10% faster for real visitors
-10%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 7.2 s to 6.6 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0.029
0.029The layout barely moves while loading (CLS 0.029, good is under 0.1).
Images and page weight
9 images over 500 KB
9 images weigh 6.9 MB together. On a phone connection a single image that size takes seconds.
9 images far larger than shown
2.3 MB9 images are downloaded at several times the size a phone draws them, for example 6a79a5eae34619310576879.png at 1,170 px wide, shown at 121 px. Resized copies would save about 2.3 MB.
20 images in older formats
20 images (9.3 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.
7 images below the first screen load straight away
7 images further down the page (2.0 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 0.4 g of CO₂ per visit
0.43 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.43 g of CO₂e: 52.1 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Page weight: 1.5 MB in 171 requests
1.5 MBYour homepage downloads 1.5 MB in 171 requests on a phone: scripts 744 KiB (60), HTML 343 KiB (2) and images 290 KiB (34). That is a lean page.
Accessibility
3 buttons without a name
3 buttons have no accessible name, so screen readers announce just “button”.
17 text elements with low contrast
17 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)
Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.
3 images without alt text
3 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (10 elements)
All page content should be contained by landmarks: 10 elements on the page fail this check, rated moderate by axe-core.
No main landmark
The page has no <main> landmark, so screen-reader users cannot jump straight to the content.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
5 links without text
5 visible links have no text or label, so screen readers cannot say where they go.
1 checks passed
40 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 48 WCAG 2.2 A/AA and best-practice rules on the phone render: 40 passed and 8 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is short (7 characters)
Your title is only 7 characters: “追觅商城-首页”. Between 30 and 65 characters leaves room to say what you do and for whom.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
Meta description is short (4 characters)
Your meta description is only 4 characters: “追觅商城”. 70 to 160 characters is enough to sell the click.
3 H1 headlines
There are 3 <h1> headlines (“全系产品站”, “品牌故事” and “会员臻享服务”). One clear main headline is easier for people and search engines.
No canonical URL
No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.
No social preview image
No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.
No XML sitemap
No XML sitemap at https://www.dreame.tech/sitemap.xml, so Google discovers your pages only by following links.
No robots.txt
There is no robots.txt at dreame.tech/robots.txt, the first file search crawlers ask for.
Only 1 internal link
The homepage links to only 1 page on your own site, so visitors and crawlers find few routes into the rest of it.
3 links crawlers can't follow
3 links have no real href, so search engines can't follow them.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
AI search readiness
No Organization structured data
There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.
No llms.txt
There is no https://www.dreame.tech/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.
Best practices
4 small tap targets
4 of 12 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
Deprecated browser APIs
The page uses 2 deprecated browser APIs that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).
8 distorted images
8 images are displayed at the wrong aspect ratio, so they look stretched or squashed.
Missing source maps
Large scripts ship without source maps.
2 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No call to action on the first screen
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 calls to action
We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.
No social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
No analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
No direct contact details
No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.
Only about 30 words
The homepage has only about 30 words of visible text; thin pages give Google and first-time buyers little to go on.
No form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
No risk reducer
No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.
Privacy and tracking
No consent tool detected
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.
2 other companies contacted
Loading the homepage contacts 2 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
No known trackers before consent
No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).
Security, domain, email and software versions
The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at dreame.tech, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Go beyond the website
What your $25 Growth Playbook adds
This review found 53 issues on dreame.tech, including 21 speed issues, 10 SEO issues and 6 conversion gaps. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.
- 28 research agents read your site, reviews, competitors, communities and public filings
- Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
- Competitor intelligence with battlecards for your closest rivals
- Ideal customer profile, buyer segments and buying-stage funnel
- Ranked channels, outreach sequences and content angles
- Live Reddit threads where buyers ask for what you sell, with draft replies
- Earned media and PR openings
- At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
- PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
- Refresh the playbook later to see what changed
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.