switch-bot.com website review

About 620 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.5 s faster on a phone.

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

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

The page has 4,261 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 joy.so and others), adding 6.8 MB and 1.6 s of main-thread time.

16 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 550 ms faster on a phone.

Google Tag Manager costs a phone 956 ms of main-thread work and 785 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 80 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 750 ms faster on a phone.

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

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

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

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

3 KiB could be saved by minifying CSS.

Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).

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

8 KiB could be saved by minifying JavaScript.

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.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “正式[email protected]__PID:dd31cf78-e041-466c-94c6-ed23594085ad”.

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

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

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

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

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

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

Soft_Bundle_2x_3a3d067e-f025-4384-97a6-35983435c3e7.webp weighs 12.7 MB. On a phone connection a single image that size takes seconds.

Your homepage downloads 8.2 MB in 275 requests on a phone: images 5.0 MB (51), scripts 2.0 MB (119) and other files 711 KiB (77). Under 2 MB keeps phones on slow connections fast.

6 images are downloaded at several times the size a phone draws them, for example LockVisionPro_EN_AmazonImages_2000x2000_01_2x_1aea4332-5d6c- at 4,000 px wide, shown at 198 px. Resized copies would save about 919 KiB.

5 images (13.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.

Banner2-375_565_2x_92a57d52-9fb1-4ee4-8d78-6b50f7c060c6.png 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).

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

1 button has no accessible name, so screen readers announce just “button”.

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

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

All page content should be contained by landmarks: 7 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.

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

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

There is no <h1>, so neither visitors nor Google get a clear main headline.

Your title is 89 characters, so Google will cut it off around 60: “SwitchBot Official Website - Your Simple Switch to a Smart Home – SwitchBot International”.

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

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

6 links have no real href, so search engines can't follow them.

The homepage links to 361 pages on switch-bot.com and 11 external pages.

https://www.switch-bot.com/products/onero-arm-a1 and https://www.switch-bot.com/products/onero-a1 all use the title “onero Robotic Arm A1 – SwitchBot International”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.switch-bot.com/pages/switchbot-deals, https://www.switch-bot.com/pages/new-arrivals and https://www.switch-bot.com/pages/switchbot-points have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.switch-bot.com/products/onero-arm-a1 and https://www.switch-bot.com/products/onero-a1 use the same meta description. A description written for each page earns more clicks.

Your homepage links to 2 pages by a URL that isn't their canonical one, for example https://www.switch-bot.com/collections/robot-vacuums, whose canonical is https://www.switch-bot.com/collections/household-robot. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://www.switch-bot.com/pages/switchbot-deals, https://www.switch-bot.com/pages/new-arrivals, https://www.switch-bot.com/pages/switchbot-points, https://www.switch-bot.com/products/switchbot-gift-card, https://www.switch-bot.com/collections/robot-vacuums and https://www.switch-bot.com/products/switchbot-robot-vacuum-k11-pro and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.switch-bot.com/products/onero-a1 took over 3 s to send its HTML from our server.

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

1 image failed to load on a phone, for example https://lantern.roeye.com/track.php?fingerprint=d45260e0-d734-4a26-8a95-8146fe5ff8d1&referrer=&landingpage=https%3A%2F%2Fwww.switch-bot.com%2F&useragent=Mozilla%2F5.0%20(iPhone%3B%20CPU%20iPhone%20OS%.

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

6 errors were logged to the browser console while the page loaded, for example “Identifier 'urlToPreload' has already been declared”.

A form field blocks pasting, which frustrates password managers and people on phones.

1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

Social proof on the homepage: 2 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 1,097 words of visible text.

The page uses urgency cues (a countdown or limited-time wording).

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