trywellbe.de website review

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

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

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

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

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

8 third-party services load with your homepage (Shopify, Google Fonts and JSDelivr CDN and others), adding 418 KiB and 8 ms of main-thread time.

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

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

The layout shifts by 0.167 while loading, so content jumps under the reader's thumb. Good is under 0.1.

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

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

Your homepage downloads 2.1 MB in 134 requests on a phone: images 1.5 MB (80), scripts 323 KiB (36) and fonts 108 KiB (4). Under 2 MB keeps phones on slow connections fast.

2 images are downloaded at several times the size a phone draws them, for example Rectangle_1.png at 2,160 px wide, shown at 370 px. Resized copies would save about 208 KiB.

By the Sustainable Web Design model, a visit to your homepage emits about 0.59 g of CO₂e: 70.4 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”.

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

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

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

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

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

2 form fields have no label, so screen readers announce an empty box and autofill guesses.

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

Your title is 69 characters, so Google will cut it off around 60: “wellbe health & beauty UG | Beauty Kollagen mit Rejuva Complex®️ Form”.

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

1 link has no real href, so search engines can't follow it.

The homepage links to 45 pages on trywellbe.de and 4 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.

/collections/produkte, /collections/bundles, /pages/about-us, /pages/wiederruf and /products/gelenk-kollagen have no meta description, so Google writes the search snippet from whatever text it finds.

/products/beauty-kollagen and /products/beauty-kollagen-mit-pfirsich-geschmack use the same meta description. A description written for each page earns more clicks.

/products/beauty-kollagen, /collections/produkte, /collections/bundles, /pages/about-us, /pages/impressum and /pages/datenschutzerklarung and 7 others have no <h1> headline, so visitors and search engines get no clear main topic.

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

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

2 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://reorder-master.hulkapps.com/css/re-order.css?v=2025-10-06%2009:59:41' from origin …”.

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

1 link from your homepage to your own site is broken, for example https://trywellbe.de/products/beauty-gummies-mit-biotin-vitaminen-und-zink (404).

HSTS is set, but max-age is 91 days; one year is the recommended minimum.

1 link go through two or more redirects, for example https://trywellbe.de/checkout.

No Referrer-Policy header, so full URLs can leak to the sites you link to.

No Permissions-Policy header to switch off camera, microphone and location for embedded content.

X-XSS-Protection is set to “1; mode=block”; the header is deprecated and can introduce bugs. Use 0 or remove it.

There is no /.well-known/security.txt telling researchers how to report a security problem to you.

trywellbe.de has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

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

We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

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

DMARC is set to p=none, so mail pretending to be trywellbe.de is still delivered. Add a report address, check the reports, then move to quarantine.

We found no DKIM key on the selectors the big email providers use. If you send through one of them, turning on DKIM signing improves delivery.

Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

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