ochsner-shoes.ch website review

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

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

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

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

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

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

2 third-party services load with your homepage (consentmanager.net and Google Tag Manager), adding 127 KiB and 97 ms of main-thread time.

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

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

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.

4 KiB could be saved by minifying CSS.

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.

For real visitors the layout shifts by 0.26 (75th percentile). Good is under 0.1.

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

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

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

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 “cdn_main-banner_landscape_2500x1068_NIKIN_10Jahre”.

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

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

Your homepage downloads 2.2 MB in 132 requests on a phone: scripts 1,003 KiB (28), images 600 KiB (75) and fonts 223 KiB (5). Under 2 MB keeps phones on slow connections fast.

genderbild_familie_mobile_hw26 is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

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

All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

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

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

Structured data found (Organization and WebSite) but with 2 problems, for example “ld+json block 3 is not valid JSON (Unexpected end of JSON input)”.

No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

The homepage links to 220 pages on ochsner-shoes.ch and 10 external pages.

Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

There is no https://www.ochsner-shoes.ch/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://www.ochsner-shoes.ch/de-ch/wishlist is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

Your homepage links to 2 pages by a URL that isn't their canonical one, for example https://www.ochsner-shoes.ch/de-ch/s/brandoverview, whose canonical is https://www.ochsner-shoes.ch/de-ch/brandoverview. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://www.ochsner-shoes.ch/de-ch/storefinder, https://www.ochsner-shoes.ch/de-ch/wishlist, https://www.ochsner-shoes.ch/de-ch/s/brandoverview and https://www.ochsner-shoes.ch/de-ch/s/entdecken have no <h1> headline, so visitors and search engines get no clear main topic.

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

2 errors were logged to the browser console while the page loaded, for example “ERROR TypeError: Cannot read properties of undefined (reading 'addEventListener')”.

Large scripts ship without source maps.

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

We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

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

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

Before a visitor clicks anything, the page loads Google Tag Manager (measured from a US location before any click). A consent tool (consentmanager) is installed; check it blocks these until visitors agree where the law requires it.

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

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