sailfish.com website review

Shopify costs a phone 1.5 s of main-thread work and 321 KiB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

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

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

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

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

8 third-party services load with your homepage (Shopify, Google Tag Manager and Clarity and others), adding 1.4 MB and 2.4 s of main-thread time.

About 432 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 150 ms faster on a phone.

Google Tag Manager costs a phone 493 ms of main-thread work and 535 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 84 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 450 ms faster on a phone.

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

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

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

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

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

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

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.

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

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

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

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

Real visitors wait 3.0 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-31, real Chrome visitors' tap response (inp) went from 121 ms to 163 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Real visitors see the first content after 1.8 s (75th percentile). Good is under 1.8 s.

The first text or image appears after 2.0 s on a phone. Good is under 1.8 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' largest content (lcp) went from 1.5 s to 1.7 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 7.4 MB in 250 requests on a phone: fonts 3.6 MB (7), scripts 1.5 MB (78) and images 1.2 MB (35). Under 2 MB keeps phones on slow connections fast.

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

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

Some lists contain elements other than list items, which screen readers announce wrongly.

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

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

The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

1 form field has no label, so screen readers announce an empty box and autofill guesses.

ARIA role should be appropriate for the element: 8 elements on the page fail this check, rated minor by axe-core.

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

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

Your title is only 8 characters: “sailfish”. Between 30 and 65 characters leaves room to say what you do and for whom.

1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

The homepage links to 199 pages on sailfish.com and 10 external pages.

https://www.sailfish.com/en and https://www.sailfish.com/en/collections all use the title “sailfish”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.sailfish.com/en/pages/service has no meta description, so Google writes the search snippet from whatever text it finds.

https://www.sailfish.com/en/pages/sailfish-swim-tour-2027, https://www.sailfish.com/en/collections, https://www.sailfish.com/en/pages/service, https://www.sailfish.com/en/pages/sailfish-x-challenge-roth-kollektion, https://www.sailfish.com/en/pages/accessoires and https://www.sailfish.com/en/pages/sailfish-refurbished-wetsuits have no <h1> headline, so visitors and search engines get no clear main topic.

We fetched 15 pages linked from your homepage (of 69 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”.

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

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

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel and 1 more (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 21 cookies, 17 of them by other companies (measured from a US location before any click).

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