sudscrub.com website review

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

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

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

8 third-party services load with your homepage (Hotjar, Clarity and rebuyengine.com and others), adding 2.2 MB and 1.9 s of main-thread time.

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

About 695 KiB of JavaScript is downloaded but never used on this page.

Hotjar costs a phone 513 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.

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

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

Clarity costs a phone 433 ms of main-thread work and 29 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.

rebuyengine.com costs a phone 269 ms of main-thread work and 692 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.

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

Shopify costs a phone 118 ms of main-thread work and 766 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 51 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 150 ms faster on a phone.

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

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

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

7 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.

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

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

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

Your largest element takes 4.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “HELPING YOU FEEL CLEAN AND CONFIDENT GENTLE ANTIMICROBIAL S…”.

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

Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 195 ms to 207 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 1.9 s to 1.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 5.4 MB in 533 requests on a phone: scripts 1.8 MB (104), other files 1.6 MB (340) and images 1.4 MB (54). Under 2 MB keeps phones on slow connections fast.

1 image further down the page (20 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 1.54 g of CO₂e: 184.4 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

2 buttons have no accessible name, so screen readers announce just “button”.

ARIA attributes must conform to valid values: 1 element on the page fails this check, rated critical by axe-core.

Links must have discernible text: 1 element on the page fails this check, rated serious by axe-core.

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

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

The homepage links to 80 pages on sudscrub.com and 11 external pages.

There is no https://www.sudscrub.com/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.

https://www.sudscrub.com/policies/shipping-policy and https://www.sudscrub.com/collections/bundles-sets have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.sudscrub.com/products/sud-scrub-2-0, https://www.sudscrub.com/collections/accessories, https://www.sudscrub.com/collections/bundles-sets, https://www.sudscrub.com/pages/faq, https://www.sudscrub.com/pages/contact-us and https://www.sudscrub.com/collections/body-scrubbers-2-0 have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.sudscrub.com/products/sud-scrub-2-0 and https://www.sudscrub.com/products/face-scrubber-1 took over 3 s to send their HTML from our server.

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

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

1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.

6 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 403 ()”.

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

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

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

The homepage carries about 1,465 words of visible text.

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