smartthings.com website review

audioeye.com costs a phone 13.4 s of main-thread work and 407 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.

199 files are served with short cache lifetimes, so returning visitors download them again (2.0 MB).

About 1.6 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.1 s faster on a phone.

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

21 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.3 s.

Quantum Metric costs a phone 1.6 s of main-thread work and 121 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.

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

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

8 third-party services load with your homepage (audioeye.com, Quantum Metric and Google Tag Manager and others), adding 2.6 MB and 18.1 s of main-thread time.

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

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

Decibel Insight costs a phone 669 ms of main-thread work and 65 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.

Wunderkind costs a phone 421 ms of main-thread work and 354 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 78 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 360 ms faster on a phone.

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

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

10 KiB could be saved by minifying JavaScript.

6 KiB could be saved by minifying CSS.

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.

For real visitors the layout shifts by 0.34 (75th percentile). Good is under 0.1.

Your largest element takes 18.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

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

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

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

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

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

Real visitors wait 3.6 s for the largest content to appear (75th percentile). Good is under 2.5 s.

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

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 350 ms to 412 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 2.6 s to 2.6 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 8.0 MB in 488 requests on a phone: scripts 4.3 MB (172), images 1.8 MB (62) and other files 1,001 KiB (179). Under 2 MB keeps phones on slow connections fast.

1 image further down the page (33 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

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

ARIA commands must have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

1 tap target is too small or too close together to hit reliably with a finger.

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

15 elements use ARIA attributes their role does not allow, which confuses screen readers.

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children. (5 elements).

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

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

Elements with role="dialog" or role="alertdialog" do not have accessible names. (1 element).

Elements use prohibited ARIA attributes (1 element).

1 form field has no label, so screen readers announce an empty box and autofill guesses.

1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

The homepage links to 281 pages on smartthings.com and 21 external pages.

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.

https://www.samsung.com/us/shop/all-deals and https://www.samsung.com/us/shop all use the title “Limited-Time Offers & Everyday Savings on Essentials | Samsung US”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.samsung.com/us/shop/all-deals and https://www.samsung.com/us/shop use the same meta description. A description written for each page earns more clicks.

Your homepage links to 10 pages by a URL that isn't their canonical one, for example https://www.samsung.com/us/shop/all-deals, whose canonical is https://www.samsung.com/us//offer. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://www.samsung.com/us/smartphones/galaxy-s26-ultra/buy, https://www.samsung.com/us/smartphones/galaxy-z-fold8/buy, https://www.samsung.com/us/smartphones/galaxy-z-fold8-ultra/buy, https://www.samsung.com/us/smartphones/galaxy-z-flip8/buy, https://www.samsung.com/us/tablets/galaxy-tab-s12/buy and https://www.samsung.com/us/watches/galaxy-watch-ultra2/buy and 4 others 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.

https://www.samsung.com/us/tablets/galaxy-tab-s12/buy, https://www.samsung.com/us/watches/galaxy-watch-ultra2/buy, https://www.samsung.com/us/tvs/micro-rgb/85-inch-micro-rgb-4k-tv-r95h-sku-mrn85r95hafxza, https://www.samsung.com/us/lifestyle-tvs/the-frame/85-inch-the-frame-pro-neo-qled-4k-tv-ls03hw-sku-qn85ls03hwfxza, https://www.samsung.com/us/audio-devices/wireless-speaker/music-studio-7-dolby-atmos-speaker-sku-hw-ls70h-za and https://www.samsung.com/us/monitors/gaming/27-inch-odyssey-oled-g8-g80sh-4k-gaming-monitor-sku-ls27hg802snxza and 2 others took over 3 s to send their HTML from our server.

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

4 images failed to load on a phone, for example https://www.samsung.com/us/smartthings/.

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

3 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

The page uses 2 deprecated browser APIs that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

1 error was logged to the browser console while the page loaded, for example “Cannot read properties of undefined (reading 'ECID')”.

1 image is served at too low a resolution for sharp phone screens.

Chrome logged issues while loading the page (“Cookie”).

Large scripts ship without source maps.

Social proof on the homepage: 138 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

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

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

Before a visitor clicks anything, the page loads Google Ads, Google Tag Manager, The Trade Desk and X (Twitter) Ads (measured from a US location before any click). A consent tool (TrustArc) is installed; check it blocks these until visitors agree where the law requires it.

Opening the homepage sets 23 cookies (measured from a US location before any click).

Loading the homepage contacts 15 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.