xouxouberlin.com website review

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

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

8 third-party services load with your homepage (rebuyengine.com, Facebook and Cookiebot and others), adding 1.3 MB and 705 ms of main-thread time.

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

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

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

rebuyengine.com costs a phone 148 ms of main-thread work and 312 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.

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

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

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

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

17 KiB could be saved by minifying JavaScript.

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

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

13 KiB could be saved by minifying CSS.

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 18.3 s. Good is under 3.8 s.

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

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

Visually, the page fills in at 5.9 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 102 ms to 97 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

Your homepage downloads 6.0 MB in 256 requests on a phone: media 2.6 MB (2), scripts 1.7 MB (89) and other files 783 KiB (120). Under 2 MB keeps phones on slow connections fast.

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

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

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

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

Interactive controls must not be nested: 2 elements on the page fail this check, rated serious by axe-core.

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

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

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

Headings skip levels (h1 → h3), which makes the page harder to scan with a screen reader.

Elements with visible text labels do not have matching accessible names. (1 element).

Your title is 67 characters, so Google will cut it off around 60: “Phone Cases with Strap for your iPhone & Tech Accessories | XOUXOU®”.

The homepage links to 199 pages on xouxouberlin.com and 16 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.

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

2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

Large scripts ship without source maps.

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

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

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

Before a visitor clicks anything, the page loads Google Ads, Google Tag Manager, Klaviyo, Meta Pixel and Microsoft Clarity and 1 more (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 30 cookies (measured from a US location before any click).

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