Website review, no card needed

saltsteam.com logo

saltsteam.com website review

Visit site (opens in a new tab)Reviewed 7 November 202626 issues · 71 checks

This review found 26 issues worth fixing on saltsteam.com, 10 of them high impact, across 71 checks. The most urgent: improve image delivery. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
3.7 s3.1 sMay 16Jul 43.5 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20263.1 s
May 23, 20263.3 s
May 30, 20263.4 s
Jun 6, 20263.6 s
Jun 13, 20263.6 s
Jun 20, 20263.6 s
Jun 27, 20263.6 s
Jul 4, 20263.5 s
Real-visitor tap response (INP)75th percentile, phones
286 ms225 msMay 16Jul 4232 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026279 ms
May 23, 2026272 ms
May 30, 2026274 ms
Jun 6, 2026265 ms
Jun 13, 2026265 ms
Jun 20, 2026265 ms
Jun 27, 2026244 ms
Jul 4, 2026232 ms

Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.

One score from every part of this review. How it works

Full-page screenshot of saltsteam.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. saltsteam.com at 0.6 s0.6 s
  2. saltsteam.com at 1.3 s1.3 s
  3. saltsteam.com at 1.9 s1.9 s
  4. saltsteam.com at 2.5 s2.5 s
  5. saltsteam.com at 3.1 s3.1 s
  6. saltsteam.com at 3.8 s3.8 s
  7. saltsteam.com at 4.4 s4.4 s
  8. saltsteam.com at 5.0 s5.0 s

Speed

3 to fix68
  • Improve image delivery

    3.5 s · 1.7 MB

    7 images could be 1.7 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 3.5 s faster on a phone.

  • Mobile performance score: 68

    68/100

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

  • Render-blocking requests

    800 ms

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

  • 1 long task on the main thread

    1 long task block the main thread while loading, the longest for 75 ms. During a long task the page ignores taps.

  • 2 third-party services on the page

    2 third-party services load with your homepage (Shopify and shop.app), adding 77 KiB and 29 ms of main-thread time.

  • Reduce unused CSS

    10 KiB

    About 10 KiB of CSS is downloaded but never applied on this page.

  • Chained critical requests

    Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

  • Forced reflow

    Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

  • Minify JavaScript

    4 KiB

    4 KiB could be saved by minifying JavaScript.

  • Duplicated JavaScript

    3 KiB

    3 KiB JavaScript is shipped twice across bundles.

  • Use efficient cache lifetimes

    1 KiB

    1 file is served with short cache lifetimes, so returning visitors download them again (1 KiB).

2 checks passed
  • Main-thread work: 1.8 s

    A phone's processor spends 1.8 s on main-thread work while loading, 437 ms of it running JavaScript. That is comfortably low.

  • Server response: 4 ms

    4 ms

    Your server sent the HTML in 4 ms, well inside Google's 600 ms guideline.

Core Web Vitals

4 to fix67
  • Largest Contentful Paint: 8.1 s

    8.1 s

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

  • Speed Index: 6.3 s

    6.3 s

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

  • Time to Interactive: 8.1 s

    8.1 s

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

  • First Contentful Paint: 2.0 s

    2.0 s

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

  • Largest content (LCP) got 11% slower for real visitors

    +11%

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

  • Not enough real-visitor data yet

    Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

3 checks passed
  • Tap response (INP) got 14% faster for real visitors

    -14%

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

  • Cumulative Layout Shift: 0

    0

    The layout barely moves while loading (CLS 0, good is under 0.1).

  • Total Blocking Time: 13 ms

    13 ms

    Scripts block the page for only 13 ms while loading. Good is under 200 ms.

Images and page weight

2 to fix70
  • 2 images over 500 KB

    2 images weigh 1.5 MB together. On a phone connection a single image that size takes seconds.

  • Page weight: 3.0 MB in 140 requests

    3.0 MB

    Your homepage downloads 3.0 MB in 140 requests on a phone: images 2.0 MB (30), other files 594 KiB (45) and scripts 251 KiB (43). Under 2 MB keeps phones on slow connections fast.

  • About 0.9 g of CO₂ per visit

    0.85 g

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

3 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

4 to fixGoogle 9494
  • ARIA dialog and alertdialog nodes should have an accessible name (1 element)

    ARIA dialog and alertdialog nodes should have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

  • Summary elements must have discernible text (1 element)

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

  • All page content should be contained by landmarks (15 elements)

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

  • 4 links without text

    4 visible links have no text or label, so screen readers cannot say where they go.

2 checks passed
  • Every image has alt text

    All 24 images in the HTML carry an alt attribute.

  • 48 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 52 WCAG 2.2 A/AA and best-practice rules on the phone render: 48 passed and 4 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

3 to fixGoogle 9286
  • Title is short (12 characters)

    Your title is only 12 characters: “Salt & Steam”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • Meta description is short (41 characters)

    Your meta description is only 41 characters: “The only men's swimwear you'll ever need.”. 70 to 160 characters is enough to sell the click.

  • 2 links with vague text

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

  • 73 internal links, 2 external

    The homepage links to 73 pages on saltsteam.com and 2 external pages.

6 checks passed
  • One H1 headline

    Your main headline reads: “The only men's swimwear you'll every need.”.

  • Canonical URL set

    The canonical URL is https://saltsteam.com/en.

  • Structured data in place

    Structured data found: Organization and WebSite.

  • Open Graph tags complete

    Open Graph tags are complete, so shared links show a title, description and image.

  • robots.txt in place

    robots.txt is in place and points crawlers to your sitemap.

  • XML sitemap found

    Your XML sitemap is reachable at https://saltsteam.com/sitemap.xml.

AI search readiness

100
4 checks passed
  • AI answer engines may read the site

    Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.

  • Organization data: 4 of 6 facts

    Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.

  • Text is in the HTML

    Your server sends the page's text in the HTML (428 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

    The site publishes https://saltsteam.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.

Other pages

5 to fix43
  • 1 linked page is broken

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

  • 1 page without a title

    https://saltsteam.com/customer_authentication/redirect has no <title>, so Google invents the link text in results.

  • 1 linked page hidden from search

    https://saltsteam.com/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

  • 9 pages without a meta description

    https://saltsteam.com/en/collections/all, https://saltsteam.com/en/collections/best-sellers, https://saltsteam.com/en/collections/classics-collection, https://saltsteam.com/en/collections/tulum-collection, https://saltsteam.com/en/collections/compression-layer and https://saltsteam.com/en/collections/mesh-briefs and 3 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 pages without an H1

    https://saltsteam.com/en/pages/contact and https://saltsteam.com/customer_authentication/redirect have no <h1> headline, so visitors and search engines get no clear main topic.

  • 15 internal pages checked

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

2 checks passed
  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • Titles are unique

    Every page we checked has its own title.

Best practices

1 to fixGoogle 9693
  • 15 small tap targets

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

2 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix67
  • No social proof

    No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

  • No analytics detected

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

  • No direct contact details

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

  • No risk reducer

    No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

  • About 332 words of copy

    The homepage carries about 332 words of visible text.

3 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “SHOP NOW” and “START SHOPPING”.

  • 15 calls to action

    The homepage has 15 calls to action, for example “SHOP ALL”, “CONTACT” and “Shop Now”.

  • 5 short forms

    5 short forms (1 field at most) are right on the homepage.

Privacy and tracking

1 to fix
  • 2 trackers load before any consent

    2

    Before a visitor clicks anything, the page loads Google Ads and Google Tag Manager (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.

  • 8 cookies set on arrival

    8

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

  • No consent tool detected

    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.

  • 8 other companies contacted

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

Security, domain, email and software versions

The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at saltsteam.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Apps on your store

Your storefront loads 1 app. It is code from another company running for your shoppers.

Apps your storefront loads

Accessez

Apps found in the homepage's code. Apps that only run in checkout or the admin aren't seen, and a headless storefront shows none. App data from programmable.info

Upkeep, stack and company

Stack

E-commerce
Shopify
Hosting
Shopify

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 26 issues on saltsteam.com, including 7 speed issues, 3 SEO issues and 3 conversion gaps. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.

  • 28 research agents read your site, reviews, competitors, communities and public filings
  • Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
  • Competitor intelligence with battlecards for your closest rivals
  • Ideal customer profile, buyer segments and buying-stage funnel
  • Ranked channels, outreach sequences and content angles
  • Live Reddit threads where buyers ask for what you sell, with draft replies
  • Earned media and PR openings
  • At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
  • PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
  • Refresh the playbook later to see what changed

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25