ooono.de website review

8 third-party services load with your homepage (Intercom, Google Tag Manager and Cookiebot and others), adding 1.1 MB and 686 ms of main-thread time.

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

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

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

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

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

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

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

1 image could be 13 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

Polyfills for old browsers add 9 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.

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

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

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

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

Your homepage downloads 31.7 MB in 331 requests on a phone: media 28.8 MB (4), other files 1.5 MB (241) and scripts 1.0 MB (53). Under 2 MB keeps phones on slow connections fast.

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

5 buttons have no accessible name, so screen readers announce just “button”.

1 dropdown has no label.

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

1 element has a tabindex above 0, which scrambles the keyboard order.

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

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

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

8 visible links have no text or label, so screen readers cannot say where they go.

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

Headings skip levels (h2 → h4 and h2 → h6), which makes the page harder to scan with a screen reader.

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

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

The homepage links to 60 pages on ooono.de and 4 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.

https://ooono.com/de/collections/blitzerwarner, https://ooono.com/de/products/co-driver-no3, https://ooono.com/de/products/co-driver-no2, https://ooono.com/de/products/co-driver-no1, https://ooono.com/de/collections/elektronische-parkscheibe and https://ooono.com/de/products/de-p-disc-no3-black and 8 others declare the homepage as their canonical URL, which tells Google they are copies of the homepage and keeps them out of search results. A site-wide template setting usually causes this.

https://ooono.com/de/pages/digitales-fahrtenbuch is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

https://ooono.com/de/products/p-disc-no2-dark and https://ooono.com/de/products/p-disc-no2 all use the title “P-DISC NO2”. Search engines can't tell which page to show for a search, so each competes with the others.

https://ooono.com/de/products/de-p-disc-no3-black, https://ooono.com/de/products/p-disc-no2-dark, https://ooono.com/de/collections/accessories, https://ooono.com/de/blogs/news and https://ooono.com/de/products/co-driver-no2-plus have no meta description, so Google writes the search snippet from whatever text it finds.

https://ooono.com/de/collections/blitzerwarner, https://ooono.com/de/products/co-driver-no3, https://ooono.com/de/collections/elektronische-parkscheibe, https://ooono.com/de/pages/digitales-fahrtenbuch and https://ooono.com/de/blogs/news have no <h1> headline, so visitors and search engines get no clear main topic.

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

2 of 10 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

4 errors were 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: 5 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 429 words of visible text.

Before a visitor clicks anything, the page loads Amazon Ads, Google Ads, Google Tag Manager, Hotjar and Meta Pixel and 5 mores (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 19 cookies (measured from a US location before any click).

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