obi.ch website review

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

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

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

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

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

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

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

5 third-party services load with your homepage (Google Tag Manager, baqend.com and Kameleoon and others), adding 1.8 MB and 453 ms of main-thread time.

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

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

obi.de costs a phone 26 ms of main-thread work and 1.4 MB 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.

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.

The first text or image appears after 9.4 s on a phone. Good is under 1.8 s.

Your largest element takes 16.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Auch wir verwenden Cookies und ähnliche Technologien, damit…”.

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

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

Real visitors wait 256 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

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

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

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

27 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 139 ms to 158 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 3.9 MB in 572 requests on a phone: images 1.9 MB (161), scripts 1.3 MB (192) and other files 401 KiB (136). Under 2 MB keeps phones on slow connections fast.

1 image further down the page (25 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

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

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

Links must have discernible text: 1 element on the page fails this check, rated serious by axe-core.

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

Elements with visible text labels do not have matching accessible names. (2 elements).

There are 13 <h1> headlines (“Hol dir deinen Biber Bonus!”, “Neue OBI Kinderwerkbank: DIY-Spielspass aus Holz” and “Varifit: Ein System. Viele Möglichkeiten.”). One clear main headline is easier for people and search engines.

Structured data found (Organization and WebPage) but with 1 problem, for example “Organization: logo is not an absolute URL ("https://www.obi.ch/assets/icons/logos/obi-logo-orange.svg")”.

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

The homepage links to 187 pages on obi.ch and 9 external pages.

There is no https://www.obi.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.obi.ch/marken/obi-reinigung and https://www.obi.ch/beratung-und-planung/waermepumpe-anfragen are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

https://www.obi.ch/oele-additive/castrol-motorenoel-edge-5w-30-ll-h-5-1-l/p/6061261, https://www.obi.ch/werkbaenke/cosco-mobile-werkbank-klappbar-stahl-mdf-hxbxt-86-x-132-x-67-cm/p/5877618, https://www.obi.ch/waeschekoerbe/waeschesammler-corno-beige-43-l/p/1668128, https://www.obi.ch/beratung-und-planung/waermepumpe-anfragen, https://www.obi.ch/beratung-und-planung/photovoltaik and https://www.obi.ch/beratung-und-planung/dachfenster and 1 other took over 3 s to send their HTML from our server.

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

4 errors were logged to the browser console while the page loaded, for example “Cannot read properties of undefined (reading 'controller')”.

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: 2 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.

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

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 1,787 words of visible text.

Before a visitor clicks anything, the page loads Google Tag Manager (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 9 cookies (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 10 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.