softub.com website review

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

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

Your mobile performance score is 72 (desktop: 89). Pages that score under 90 lose visitors before the first paint.

About 164 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 750 ms faster on a phone.

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

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

1 third-party service load with your homepage (Google Fonts), adding 40 KiB and 0 ms of main-thread time.

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 see the first content after 3.1 s (75th percentile). Good is under 1.8 s.

Real visitors wait 2.9 s for your server to start answering (75th percentile). Good is under 800 ms.

Your largest element takes 5.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “PoseidonX™ sets a new standard for hydrotherapy– combining …”.

The first text or image appears after 3.2 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.

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

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

15 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-10, real Chrome visitors' tap response (inp) went from 72 ms to 71 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

6 images are downloaded at several times the size a phone draws them, for example home-day.jpg at 1,920 px wide, shown at 390 px. Resized copies would save about 885 KiB.

Your homepage downloads 3.1 MB in 55 requests on a phone: images 2.8 MB (32), stylesheets 198 KiB (16) and fonts 115 KiB (4). Under 2 MB keeps phones on slow connections fast.

13 images further down the page (2.4 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

11 images (2.1 MB) are JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.

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

Certain ARIA roles must contain particular children: 1 element on the page fails this check, rated critical by axe-core.

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

4 frames have no title, so screen-reader users cannot tell what they contain.

3 tap targets are too small or too close together to hit reliably with a finger.

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

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

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

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

Headings should not be empty: 5 elements on the page fail this check, rated minor by axe-core.

Elements marked as presentational should be consistently ignored: 3 elements on the page fail this check, rated minor by axe-core.

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

<td> elements in a large <table> do not have table headers. (1 element).

There is no <h1>, so neither visitors nor Google get a clear main headline.

Your title is only 17 characters: “Softub® | Hot Tub”. Between 30 and 65 characters leaves room to say what you do and for whom.

Structured data found (BreadcrumbList, Organization, Product and WebPage) but with 1 problem, for example “Product: no offers (price) block”.

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

1 link has no real href, so search engines can't follow it.

The homepage links to 141 pages on softub.com and 6 external pages.

There is no https://softub.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://softub.com/syntex-gallery and https://softub.com/syntex-gallery-2 all use the title “SynTex® Colors & Textures | Softub®”. Search engines can't tell which page to show for a search, so each competes with the others.

https://softub.com/product/sportster-140 has no meta description, so Google writes the search snippet from whatever text it finds.

https://softub.com/product/poseidonx and https://softub.com/product/portico 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://softub.com/product/poseidonx, whose canonical is https://softub.com/product/portico. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

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: net::ERR_FAILED”.

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

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.

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

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

Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

There is no form on the homepage, so every lead has to click through to another page first.

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.

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.