saltt.com website review

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

8 third-party services load with your homepage (Shopify, Clarity and reamaze.com and others), adding 1.4 MB and 898 ms of main-thread time.

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

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

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

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

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

3 images could be 96 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 150 ms faster on a phone.

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

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

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

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

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

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

Your largest element takes 6.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Purple SALTT Radical Grape Hydration Packet with ocean spla…”.

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

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

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

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

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

Your homepage downloads 4.2 MB in 478 requests on a phone: images 1.3 MB (44), scripts 1.1 MB (197) and other files 1,023 KiB (198). Under 2 MB keeps phones on slow connections fast.

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

Delayed refresh under 20 hours must not be used: 1 element on the page fails this check, rated critical by axe-core.

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

All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

ARIA input fields do not have accessible names (1 element).

Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

Elements with visible text labels do not have matching accessible names. (1 element).

Your title is 70 characters, so Google will cut it off around 60: “SALTT | Zero Sugar Electrolyte Powder | Keto & POTS Friendly Hydration”.

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

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

No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

The homepage links to 64 pages on saltt.com and 8 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.

Your homepage links to https://saltt.com/collections/vendors, which answers with an error. Visitors hit a dead end and search engines drop it.

https://saltt.com/products/ultra-variety-pack-electrolyte-mix and https://saltt.com/products/all-the-things-variety-saltt-electrolyte-powder-drink-mix all use the title “Ultra Variety Pack SALTT Electrolyte Drink Mix | Sugar-Free Hydration”. Search engines can't tell which page to show for a search, so each competes with the others.

https://saltt.com/policies/shipping-policy has no meta description, so Google writes the search snippet from whatever text it finds.

https://saltt.com/products/ultra-variety-pack-electrolyte-mix and https://saltt.com/products/all-the-things-variety-saltt-electrolyte-powder-drink-mix use the same meta description. A description written for each page earns more clicks.

Your homepage links to 1 page by a URL that isn't its canonical one, for example https://saltt.com/products/all-the-things-variety-saltt-electrolyte-powder-drink-mix, whose canonical is https://saltt.com/products/ultra-variety-pack-electrolyte-mix. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://saltt.com/collections/all and https://saltt.com/collections/new-releases have no <h1> headline, so visitors and search engines get no clear main topic.

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

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 429 ()”.

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: 12 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

The homepage has only about 10 words of visible text; thin pages give Google and first-time buyers little to go on.

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 2 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.