sidas.ch website review

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

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

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

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

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

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

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

ZenDesk costs a phone 264 ms of main-thread work and 473 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.

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

Klaviyo costs a phone 224 ms of main-thread work and 330 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.

10 images could be 226 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

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

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.

3 KiB could be saved by minifying CSS.

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

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

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

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

Your homepage downloads 3.9 MB in 280 requests on a phone: scripts 1.9 MB (95), images 912 KiB (32) and other files 811 KiB (110). Under 2 MB keeps phones on slow connections fast.

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

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

All page content should be contained by landmarks: 17 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.

Alternative text of images should not be repeated as text: 7 elements on the page fail this check, rated minor by axe-core.

Your title is 73 characters, so Google will cut it off around 60: “Sidas - Expert in Foot Comfort: Insoles, Socks and Protectors. – Sidas CH”.

Your meta description is 191 characters; Google truncates after about 160, so the end of your pitch is cut.

3 links have no real href, so search engines can't follow them.

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

The homepage links to 282 pages on sidas.ch and 16 external pages.

https://www.sidas.ch/en/pages/delivery-and-tracking and https://www.sidas.ch/en/pages/contact have no meta description, so Google writes the search snippet from whatever text it finds.

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

The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

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.

A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

Social proof on the homepage: 1 trust badge. Pairing it with named testimonials or customer logos makes it far more convincing.

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

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

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

The homepage carries about 882 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel (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 14 cookies, 1 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 22 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.