uinfootwear.de website review

The page goes through 2 redirects before it starts loading, costing about 34.4 s. Link and advertise the final URL directly.

About 1.1 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 8.1 s faster on a phone.

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

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

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

8 third-party services load with your homepage (cloudfront.net, Shopify and Clarity and others), adding 2.6 MB and 813 ms of main-thread time.

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

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

cloudfront.net costs a phone 335 ms of main-thread work and 523 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.

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

gelacy.app costs a phone 0 ms of main-thread work and 1.5 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.

The HTML itself could arrive about 250 ms sooner: redirects, a slow server response or missing compression delay everything after it.

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

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

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

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

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

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

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

Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 128 ms to 130 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.8 s to 1.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 10.0 MB in 972 requests on a phone: images 5.3 MB (517), scripts 2.4 MB (134) and other files 1.6 MB (292). Under 2 MB keeps phones on slow connections fast.

01_-W10210337_-_KV.jpg 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).

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

1 button has no accessible name, so screen readers announce just “button”.

10 elements hidden from screen readers can still receive keyboard focus.

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: 6 elements on the page fail this check, rated moderate by axe-core.

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

Headings should not be empty: 5 elements on the page fail this check, rated minor by axe-core.

Your title is 73 characters, so Google will cut it off around 60: “UIN FOOTWEAR Deutschland | Spanische Kunst-Reiseschuhe. – DE UIN Footwear”.

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

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

The homepage links to 227 pages on uinfootwear.de and 11 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.

There is no https://www.uinfootwear.de/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.uinfootwear.de/collections/best-seller, https://www.uinfootwear.de/collections/new-arrival, https://www.uinfootwear.de/collections/womens-shoes, https://www.uinfootwear.de/collections/uin-signatures-women-shoes, https://www.uinfootwear.de/collections/slip-on-women and https://www.uinfootwear.de/collections/espadrilles-women and 1 other have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.uinfootwear.de/collections/best-seller, https://www.uinfootwear.de/collections/new-arrival, https://www.uinfootwear.de/collections/womens-shoes, https://www.uinfootwear.de/collections/uin-signatures-women-shoes, https://www.uinfootwear.de/collections/slip-on-women and https://www.uinfootwear.de/collections/espadrilles-women and 1 other have no <h1> headline, so visitors and search engines get no clear main topic.

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

The page uses 2 deprecated browser APIs that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.

4 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://d2zz0xvz7ly6wf.cloudfront.net/static/css/arco.22224e35.chunk.css' from origin 'htt…”.

Chrome logged issues while loading the page (“Cookie”).

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

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and Microsoft Clarity (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 21 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 36 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.