w1nnas.com website review

Your mobile performance score is 49. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

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

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

8 third-party services load with your homepage (Shopify, Google Tag Manager and Reviews.io and others), adding 2.8 MB and 1.6 s of main-thread time.

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

About 1.1 MB of JavaScript is downloaded but never used on this page.

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

15 images could be 552 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 300 ms faster on a phone.

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

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

Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 200 ms).

20 KiB could be saved by minifying CSS.

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

108 KiB could be saved by minifying JavaScript.

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

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

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

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

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

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

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

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

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

Your homepage downloads 14.5 MB in 295 requests on a phone: media 9.0 MB (1), scripts 1.9 MB (90) and images 1.6 MB (58). Under 2 MB keeps phones on slow connections fast.

5 images are downloaded at several times the size a phone draws them, for example 4_2.png at 1,080 px wide, shown at 90 px. Resized copies would save about 431 KiB.

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

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

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

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

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

3 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. (2 elements).

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

The homepage links to 47 pages on w1nnas.com and 12 external pages.

https://w1nnas.com/customer_authentication/redirect has no <title>, so Google invents the link text in results.

https://w1nnas.com/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

https://w1nnas.com/products/starter-set and https://w1nnas.com/products/energy-starter-set all use the title “W1NNAS | Energy Starter Set - Performance Pouches | limitiert”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

https://w1nnas.com/customer_authentication/redirect has no meta description, so Google writes the search snippet from whatever text it finds.

https://w1nnas.com/blogs/news, https://w1nnas.com/collections/all, https://w1nnas.com/policies/legal-notice, https://w1nnas.com/policies/contact-information and https://w1nnas.com/policies/privacy-policy use the same meta description. A description written for each page earns more clicks.

Your homepage links to 2 pages by a URL that isn't their canonical one, for example https://w1nnas.com/products/energy-starter-set, whose canonical is https://w1nnas.com/products/starter-set. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://w1nnas.com/pages/vereine, https://w1nnas.com/pages/runclub, https://w1nnas.com/pages/entwicklung, https://w1nnas.com/customer_authentication/redirect and https://w1nnas.com/collections/all have no <h1> headline, so visitors and search engines get no clear main topic.

https://w1nnas.com/pages/runclub took over 3 s to send its HTML from our server.

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

1 image failed to load on a phone, for example https://w1nnas.com/.

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

5 errors were 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.

Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

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

The homepage shows no opening hours. If customers visit or call, show when.

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

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

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