ulanzi.de website review

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

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

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

8 third-party services load with your homepage (Google Tag Manager, jQuery CDN and Shopify and others), adding 1.2 MB and 174 ms of main-thread time.

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

xcottons.com costs a phone 0 ms of main-thread work and 323 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 images could be 117 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 150 ms faster on a phone.

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

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

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

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

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 page becomes fully interactive after 12.5 s. Good is under 3.8 s.

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

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

10 images have no width and height attributes, so the layout jumps as each one loads.

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

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

Your homepage downloads 10.7 MB in 208 requests on a phone: media 6.9 MB (2), images 1.9 MB (88) and scripts 1.5 MB (63). Under 2 MB keeps phones on slow connections fast.

20260323-093509.png 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).

3 images are downloaded at several times the size a phone draws them, for example 20260522-153927.webp at 1,600 px wide, shown at 55 px. Resized copies would save about 206 KiB.

8 images (387 KiB) are JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.

1 image further down the page (98 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 3.03 g of CO₂e: 363.1 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

ARIA attributes must conform to valid names: 1 element on the page fails this check, rated critical by axe-core.

Some list items are not inside a list.

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

Scrollable region must have keyboard access: 3 elements on the page fail this check, rated serious by axe-core.

1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

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

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

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

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

Your title is 67 characters, so Google will cut it off around 60: “Ulanzi De - Kameracage | Stative | Beleuchtung und anderes Zubehöre”.

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

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

No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

The homepage links to 254 pages on ulanzi.de and 19 external pages.

robots.txt blocks GPTBot, ClaudeBot and CCBot, which collect pages to train models. That's a legitimate choice and doesn't by itself stop the site appearing in AI answers, which the crawlers above handle.

https://www.ulanzi.de/collections/lagerraumung, https://www.ulanzi.de/collections/magsafe-zubehor, https://www.ulanzi.de/collections/smartphone-leuchten and https://www.ulanzi.de/collections/selfie-stick-1 have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.ulanzi.de/products/treeroot-quick-release-reisestativ-t00a4301, https://www.ulanzi.de/products/tc002-smart-pixel-uhr-i008, https://www.ulanzi.de/products/d200x-creative-deck, https://www.ulanzi.de/products/la30-30w-rgb-air-tube-light, https://www.ulanzi.de/products/jj06-glidego-video-tripod and https://www.ulanzi.de/products/kamera-cage-fur-hasselblad-x2d-x2d-ii have no <h1> headline, so visitors and search engines get no clear main topic.

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

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

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

2 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

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

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

The page uses urgency cues (a countdown or limited-time wording).

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