Programmable

Website review, no card needed

beautyhacker.de logo

beautyhacker.de website review

Visit site (opens in a new tab)Reviewed 10 November 202631 issues · 68 checks

This review found 31 issues worth fixing on beautyhacker.de, 8 of them high impact, across 68 checks. The most urgent: main-thread work: 6.0 s. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Site score

84B

Closest competitors among Shopify stores

Compare side by side

One score from every part of this review. How it works

www.beautyhacker.de (opens in a new tab)
Full-page screenshot of beautyhacker.de (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. beautyhacker.de at 1.0 s1.0 s
  2. beautyhacker.de at 2.1 s2.1 s
  3. beautyhacker.de at 3.1 s3.1 s
  4. beautyhacker.de at 4.2 s4.2 s
  5. beautyhacker.de at 5.2 s5.2 s
  6. beautyhacker.de at 6.3 s6.3 s
  7. beautyhacker.de at 7.3 s7.3 s
  8. beautyhacker.de at 8.3 s8.3 s

Speed

6 to fix91

  • Main-thread work: 6.0 s

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

  • Render-blocking requests

    950 ms

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

  • Reduce unused JavaScript

    531 KiB

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

  • 3 third-party services on the page

    3 third-party services load with your homepage (Shopify, shop.app and Judge.me), adding 1.2 MB and 347 ms of main-thread time.

  • Shopify adds 339 ms

    339 ms

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

  • 1,575 HTML elements

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

  • Reduce unused CSS

    40 ms · 55 KiB

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

  • 2 long tasks on the main thread

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

  • Improve image delivery

    58 KiB

    1 image could be 58 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Use efficient cache lifetimes

    42 KiB

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

  • Chained critical requests

    Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

  • Forced reflow

    Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

2 checks passed

  • Mobile performance score: 91

    91/100

    Your mobile performance score is 91. That is in Google's “good” band (90 and up).

  • Server response: 5 ms

    5 ms

    Your server sent the HTML in 5 ms, well inside Google's 600 ms guideline.

Core Web Vitals

4 to fix97

  • Time to Interactive: 8.6 s

    8.6 s

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

  • Speed Index: 5.0 s

    5.0 s

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

  • First Contentful Paint: 2.5 s

    2.5 s

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

  • 2 images without width and height

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

  • Not enough real-visitor data yet

    Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

3 checks passed

  • Largest Contentful Paint: 2.5 s

    2.5 s

    Your largest element renders in 2.5 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the text “Kein unangenehmer Nachgeschmack, keine Überwindung. Stattde…”.

  • Cumulative Layout Shift: 0

    0

    The layout barely moves while loading (CLS 0, good is under 0.1).

  • Total Blocking Time: 5 ms

    5 ms

    Scripts block the page for only 5 ms while loading. Good is under 200 ms.

Images and page weight

2 to fix60

  • Page weight: 5.3 MB in 335 requests

    5.3 MB

    Your homepage downloads 5.3 MB in 335 requests on a phone: media 2.7 MB (2), other files 1.1 MB (158) and scripts 968 KiB (131). Under 2 MB keeps phones on slow connections fast.

  • 1 image far larger than shown

    58 KiB

    1 image is downloaded at several times the size a phone draws it, for example BeautyHacker_Logo-01_262b1719-38bd-43a1-8506-df21498b5670.pn at 6,379 px wide, shown at 250 px. Resized copies would save about 58 KiB.

  • 2 images below the first screen load straight away

    2 images further down the page (98 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 1.5 g of CO₂ per visit

    1.50 g

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

1 checks passed

  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

Accessibility

4 to fixGoogle 9594

  • Interactive controls must not be nested (1 element)

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

  • 1 image without alt text

    1 image has no alt text, which hurts accessibility and image search.

  • Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (2 elements)

    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.

  • 4 links without text

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

1 checks passed

  • 49 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 52 WCAG 2.2 A/AA and best-practice rules on the phone render: 49 passed and 3 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

4 to fixGoogle 9279

  • Title is long (70 characters)

    Your title is 70 characters, so Google will cut it off around 60: “Beautyhacker Wildberry Collagen: Kollagen Drink für Haut, Haare, Nägel”.

  • No structured data

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

  • Meta description is long (170 characters)

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

  • One H1 headline

    Your <h1> is empty.

  • 32 internal links, 14 external

    The homepage links to 32 pages on beautyhacker.de and 14 external pages.

4 checks passed

  • Canonical URL set

    The canonical URL is https://www.beautyhacker.de/.

  • Open Graph tags complete

    Open Graph tags are complete, so shared links show a title, description and image.

  • robots.txt in place

    robots.txt is in place and points crawlers to your sitemap.

  • XML sitemap found

    Your XML sitemap is reachable at https://www.beautyhacker.de/sitemap.xml.

AI search readiness

1 to fix88

  • No Organization structured data

    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.

3 checks passed

  • AI answer engines may read the site

    Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.

  • Text is in the HTML

    Your server sends the page's text in the HTML (855 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

    The site publishes https://www.beautyhacker.de/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.

Other pages

3 to fix65

  • 2 linked pages are broken

    Your homepage links to https://www.beautyhacker.de/pages/collagen-calculator and https://www.beautyhacker.de/pages/reviews, which answer with an error. Visitors hit a dead end and search engines drop them.

  • 4 pages without a meta description

    https://www.beautyhacker.de/policies/refund-policy, https://www.beautyhacker.de/policies/shipping-policy, https://www.beautyhacker.de/policies/privacy-policy and https://www.beautyhacker.de/collections/all have no meta description, so Google writes the search snippet from whatever text it finds.

  • 6 pages without an H1

    https://www.beautyhacker.de/products/wildberry-collagen, https://www.beautyhacker.de/pages/collagen-rechner, https://www.beautyhacker.de/pages/gruendungsstory-inner-beauty, https://www.beautyhacker.de/blogs/magazin, https://www.beautyhacker.de/pages/kontakt and https://www.beautyhacker.de/collections/all have no <h1> headline, so visitors and search engines get no clear main topic.

  • 11 internal pages checked

    We fetched 11 pages linked from your homepage and read each the way a search engine does.

4 checks passed

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • Titles are unique

    Every page we checked has its own title.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 9 pages that loaded have a <title>.

Best practices

2 to fixGoogle 9687

  • 5 small tap targets

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

  • 1 JavaScript error while loading

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

1 checks passed

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix50

  • No call to action on the first screen

    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 calls to action

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

  • No analytics detected

    No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

  • No direct contact details

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

  • No risk reducer

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

  • About 910 words of copy

    The homepage carries about 910 words of visible text.

2 checks passed

  • 5 short forms

    5 short forms (1 field at most) are right on the homepage, asking for an email.

  • Social proof on the page

    Social proof on the homepage: 7 testimonial or review blocks and a star rating.

Privacy and tracking

1 to fix

  • 5 trackers load before any consent

    5

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and TikTok Pixel (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.

  • 14 cookies set on arrival

    14

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

  • No consent tool detected

    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.

  • 18 other companies contacted

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

Security, domain, email and software versions

The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at beautyhacker.de, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Apps on your store

Your storefront loads 2 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Judge Me Reviews · Forms

Apps found in the homepage's code. Apps that only run in checkout or the admin aren't seen, and a headless storefront shows none. App data from programmable.info

Upkeep, stack and company

Stack

E-commerce
Shopify
Hosting
Shopify

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 31 issues on beautyhacker.de, including 10 speed issues, 4 SEO issues and 4 conversion gaps. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.

  • 28 research agents read your site, reviews, competitors, communities and public filings
  • Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
  • Competitor intelligence with battlecards for your closest rivals
  • Ideal customer profile, buyer segments and buying-stage funnel
  • Ranked channels, outreach sequences and content angles
  • Live Reddit threads where buyers ask for what you sell, with draft replies
  • Earned media and PR openings
  • At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
  • PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
  • Refresh the playbook later to see what changed

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25