jockey.de website review

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

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

8 third-party services load with your homepage (vitals.app, ZenDesk and Optanon and others), adding 1.7 MB and 941 ms of main-thread time.

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

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

vitals.app costs a phone 269 ms of main-thread work and 519 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.

ZenDesk costs a phone 260 ms of main-thread work and 395 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,727 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

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

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

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

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

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

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

6 KiB could be saved by minifying JavaScript.

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 11.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.

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

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

Scripts block taps and scrolling for 379 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' largest content (lcp) went from 1.9 s to 1.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 5.2 MB in 256 requests on a phone: media 1.9 MB (1), scripts 1.8 MB (69) and other files 1,020 KiB (164). Under 2 MB keeps phones on slow connections fast.

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

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

Interactive controls must not be nested: 1 element on the page fails this check, rated serious by axe-core.

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 2 elements on the page fail this check, rated moderate by axe-core.

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

Banner landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.

Document should not have more than one banner landmark: 1 element on the page fails this check, rated moderate by axe-core.

2 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. (1 element).

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

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

Your <h1> is empty.

The homepage links to 238 pages on jockey.de and 8 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://jockey.eu/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://jockey.eu/collections/jockey-holiday-gifting-herren and https://jockey.eu/collections/jockey-festlicher-pyjama-fur-herren have no meta description, so Google writes the search snippet from whatever text it finds.

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

8 of 31 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”.

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.

The homepage has only about 243 words of visible text; thin pages give Google and first-time buyers little to go on.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

Opening the homepage sets 7 cookies (measured from a US location before any click).

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