surfari.ch website review

About 351 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.1 s faster on a phone.

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

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

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

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

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

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

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

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

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

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

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

7 KiB could be saved by minifying CSS.

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

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

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

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

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

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

Your homepage downloads 3.0 MB in 221 requests on a phone: scripts 1.2 MB (81), images 857 KiB (24) and other files 695 KiB (99). Under 2 MB keeps phones on slow connections fast.

1 image (151 KiB) is 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.86 g of CO₂e: 102.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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

2 elements hidden from screen readers can still receive keyboard focus.

Documents must have <title> element to aid in navigation: 1 element on the page fails this check, rated serious by axe-core.

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

1 visible link has no text or label, so screen readers cannot say where it goes.

Alternative text of images should not be repeated as text: 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).

No meta description, so Google writes its own snippet from whatever text it finds.

Your title is only 6 characters: “icon-X”. Between 30 and 65 characters leaves room to say what you do and for whom.

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

The homepage links to 262 pages on surfari.ch 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://surfari.ch/pages/retouren, which answers with an error. Visitors hit a dead end and search engines drop it.

/, https://surfari.ch/collections/boards, https://surfari.ch/collections/wellenreitboards, https://surfari.ch/collections/poolboards, https://surfari.ch/collections/bodyboards and https://surfari.ch/collections/surfboard-sale and 9 others all use the title “icon-X”. Search engines can't tell which page to show for a search, so each competes with the others.

https://surfari.ch/collections/boards, https://surfari.ch/collections/wellenreitboards, https://surfari.ch/collections/poolboards, https://surfari.ch/collections/bodyboards, https://surfari.ch/collections/surfboard-sale and https://surfari.ch/collections/custom-order-surfboard and 8 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://surfari.ch/collections/custom-order-surfboard has no <h1> headline, so visitors and search engines get no clear main topic.

https://surfari.ch/collections/boards, https://surfari.ch/collections/wellenreitboards and https://surfari.ch/collections/bodyboards took over 3 s to send their HTML from our server.

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

1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=187004419&Ver=2&mid=ae9593eb-7fc3-4e04-b9d1-ab70a27f9f10&bo=1&sid=3ff81b20da7f11f19db2df40c7613862&vid=3ff86260da7f11f1ac5cfd0b10d73649&vids=1&msclkid=N&pi=918639831&l.

1 error was logged to the browser console while the page loaded, for example “Uncaught (in promise) TypeError: Cannot read properties of undefined (reading 'register')”.

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

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

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

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

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

Opening the homepage sets 19 cookies, 2 of them by other companies (measured from a US location before any click).

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