hellotushy.com website review

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

About 167 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.1 s faster on a phone.

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

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

8 third-party services load with your homepage (alia-prod.com, Klaviyo and Google Tag Manager and others), adding 1.9 MB and 1.6 s of main-thread time.

About 1.2 MB of JavaScript is downloaded but never used on this page.

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

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

alia-prod.com costs a phone 387 ms of main-thread work and 397 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 269 ms of main-thread work and 609 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.

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

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

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

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

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

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.

2 KiB could be saved by minifying JavaScript.

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 visitors wait 4.1 s for the largest content to appear (75th percentile). Good is under 2.5 s.

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

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

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

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

1 image 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 187 ms to 199 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.4 s to 2.6 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 19.8 MB in 473 requests on a phone: media 13.7 MB (2), scripts 3.1 MB (181) and images 1.4 MB (51). Under 2 MB keeps phones on slow connections fast.

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

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

1 image has no alt text, which hurts accessibility and image search.

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

Alternative text of images should not be repeated as text: 5 elements on the page fail this check, rated minor by axe-core.

Headings skip levels (h2 → h4), which makes the page harder to scan with a screen reader.

There are 2 <h1> headlines (“” and “”). One clear main headline is easier for people and search engines.

Structured data found (Organization and WebSite) but with 1 problem, for example “WebSite: missing name”.

The homepage links to 248 pages on hellotushy.com and 23 external pages.

/collections/sale, /collections/whole-bidet-catalog, /collections/tushy-bidet-attachments/best-seller, /collections/tushy-bidet-attachments, /collections/tushy-bidet-attachments/warm-water and /collections/parts-and-accessories and 3 others are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

/blogs/all has no meta description, so Google writes the search snippet from whatever text it finds.

/collections/tushy-bidet-attachments/best-seller, /collections/tushy-bidet-attachments and /collections/tushy-bidet-attachments/warm-water use the same meta description. A description written for each page earns more clicks.

/pages/hsa-fsa, /collections/sale, /collections/whole-bidet-catalog, /pages/about-us, /blogs/all and /collections/tushy-bidet-attachments/best-seller and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

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

2 images failed to load on a phone, for example https://hellotushy.com/.

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

The page uses 1 deprecated browser API that will stop working in future browsers (“CSS appearance value `slider-vertical` is not standardized and will be removed.”).

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

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

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

Large scripts ship without source maps.

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

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.

hellotushy.com has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

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

Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

The homepage shows no opening hours. If customers visit or call, show when.

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

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

DMARC is set to p=none, so mail pretending to be hellotushy.com is still delivered. Reports are on, so moving to quarantine is the next step.

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 Amazon Ads, Google Ads, Google Analytics, Google Tag Manager and Klaviyo and 4 mores (measured from a US location before any click). A consent tool (Cookiebot) is installed; check it blocks these until visitors agree where the law requires it.

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

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