Website review, no card needed
hairgivers.de website review
Visit site (opens in a new tab)Reviewed 16 November 202636 issues · 90 checks
This review found 36 issues worth fixing on hairgivers.de, 13 of them high impact, across 90 checks. The most urgent: page weight: 7.2 MB in 322 requests. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
85B- #16,616 of 123,808 reviewed websitesbeats 82%
- #10,460 of 69,682 online storesbeats 80%
- #10,156 of 63,392 Shopify storesbeats 78%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 30, 2026 | 1.7 s |
| Jun 6, 2026 | 1.6 s |
| Jun 13, 2026 | 1.6 s |
| Jun 20, 2026 | 1.6 s |
| Jun 27, 2026 | 1.6 s |
| Jul 4, 2026 | 1.6 s |
| Jul 11, 2026 | 1.6 s |
| Jul 18, 2026 | 1.6 s |
| Jul 25, 2026 | 1.6 s |
| Aug 1, 2026 | 1.6 s |
| Aug 8, 2026 | 1.6 s |
| Aug 15, 2026 | 1.6 s |
| Aug 22, 2026 | 1.7 s |
| Aug 29, 2026 | 1.7 s |
| Sep 5, 2026 | 1.7 s |
| Sep 12, 2026 | 1.7 s |
| Sep 19, 2026 | 1.7 s |
| Sep 26, 2026 | 1.7 s |
| Oct 3, 2026 | 1.6 s |
| Oct 10, 2026 | 1.6 s |
| Oct 17, 2026 | 1.7 s |
| Oct 24, 2026 | 1.7 s |
| Oct 31, 2026 | 1.8 s |
| Nov 7, 2026 | 1.7 s |
| Nov 14, 2026 | 1.6 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 30, 2026 | 135 ms |
| Jun 6, 2026 | 126 ms |
| Jun 13, 2026 | 124 ms |
| Jun 20, 2026 | 127 ms |
| Jun 27, 2026 | 129 ms |
| Jul 4, 2026 | 129 ms |
| Jul 11, 2026 | 130 ms |
| Jul 18, 2026 | 129 ms |
| Jul 25, 2026 | 127 ms |
| Aug 1, 2026 | 125 ms |
| Aug 8, 2026 | 126 ms |
| Aug 15, 2026 | 126 ms |
| Aug 22, 2026 | 123 ms |
| Aug 29, 2026 | 124 ms |
| Sep 5, 2026 | 122 ms |
| Sep 12, 2026 | 125 ms |
| Sep 19, 2026 | 128 ms |
| Sep 26, 2026 | 129 ms |
| Oct 3, 2026 | 139 ms |
| Oct 10, 2026 | 142 ms |
| Oct 17, 2026 | 146 ms |
| Oct 24, 2026 | 148 ms |
| Oct 31, 2026 | 155 ms |
| Nov 7, 2026 | 164 ms |
| Nov 14, 2026 | 165 ms |
Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.
One score from every part of this review. How it works
How it loaded on a phone
0.6 s
1.2 s
1.8 s
2.4 s
2.9 s
3.5 s
4.1 s
4.7 s
Speed
4,848 HTML elements
The page has 4,848 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Use efficient cache lifetimes
2.6 MB20 files are served with short cache lifetimes, so returning visitors download them again (2.6 MB).
Improve image delivery
400 ms · 1.2 MB47 images could be 1.2 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 400 ms faster on a phone.
Mobile performance score: 69
69/100Your mobile performance score is 69. Pages that score under 90 lose visitors before the first paint.
Render-blocking requests
600 ms5 files block the first paint until they finish downloading. Deferring or inlining them could save about 600 ms.
8 third-party services on the page
8 third-party services load with your homepage (Shopify, LoyaltyLion and 506.io and others), adding 1.1 MB and 376 ms of main-thread time.
Reduce unused JavaScript
50 ms · 397 KiBAbout 397 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 50 ms faster on a phone.
Main-thread work: 3.1 s
A phone's processor spends 3.1 s on main-thread work while loading, 937 ms of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
LoyaltyLion adds 61 ms
61 msLoyaltyLion costs a phone 61 ms of main-thread work and 367 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.
Reduce unused CSS
50 ms · 95 KiBAbout 95 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 50 ms faster on a phone.
1 long task on the main thread
1 long task block the main thread while loading, the longest for 58 ms. During a long task the page ignores taps.
Legacy JavaScript
49 KiBPolyfills for old browsers add 49 KiB JavaScript that modern phones do not need.
Minify JavaScript
26 KiB26 KiB could be saved by minifying JavaScript.
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.
Minify CSS
3 KiB3 KiB could be saved by minifying CSS.
1 checks passed
Server response: 79 ms
79 msYour server sent the HTML in 79 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 7.6 s
7.6 sYour largest element takes 7.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Time to Interactive: 17.3 s
17.3 sThe page becomes fully interactive after 17.3 s. Good is under 3.8 s.
Speed Index: 6.7 s
6.7 sVisually, the page fills in at 6.7 s (Speed Index). Good is under 3.4 s.
Tap response (INP) got 26% slower for real visitors
+26%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 135 ms to 165 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
1 image without width and height
1 image have no width and height attributes, so the layout jumps as each one loads.
Largest content (LCP) held steady for real visitors
+1%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 1.7 s to 1.6 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
9 checks passed
Passes Core Web Vitals for real visitors
Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).
Real-user LCP: 1.6 s
1.6 sReal visitors wait 1.6 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 165 ms
165 msReal visitors wait 165 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.03
0.03For real visitors the layout shifts by 0.03 (75th percentile). Good is under 0.1.
Real-user FCP: 1.5 s
1.5 sReal visitors see the first content after 1.5 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 517 ms
517 msReal visitors wait 517 ms for your server to start answering (75th percentile). Good is under 800 ms.
First Contentful Paint: 1.6 s
1.6 sThe first text or image appears after 1.6 s, inside the 1.8 s “good” threshold.
Cumulative Layout Shift: 0.026
0.026The layout barely moves while loading (CLS 0.026, good is under 0.1).
Total Blocking Time: 4 ms
4 msScripts block the page for only 4 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 7.2 MB in 322 requests
7.2 MBYour homepage downloads 7.2 MB in 322 requests on a phone: images 4.8 MB (74), scripts 1.3 MB (127) and other files 766 KiB (81). Under 2 MB keeps phones on slow connections fast.
About 2.0 g of CO₂ per visit
2.05 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.05 g of CO₂e: 245.9 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
3 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
12 buttons without a name
12 buttons have no accessible name, so screen readers announce just “button”.
<dt> and <dd> elements must be contained by a <dl> (96 elements)
<dt> and <dd> elements must be contained by a <dl>: 96 elements on the page fail this check, rated serious by axe-core.
<dl> elements must only directly contain properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements (24 elements)
<dl> elements must only directly contain properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements: 24 elements on the page fail this check, rated serious by axe-core.
6 text elements with low contrast
6 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
1 tap target too small
1 tap target is too small or too close together to hit reliably with a finger.
1 image without alt text
1 image has no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (7 elements)
All page content should be contained by landmarks: 7 elements on the page fail this check, rated moderate by axe-core.
3 form fields without a label
3 form fields have no label, so screen readers announce an empty box and autofill guesses.
1 link without text
1 visible link has no text or label, so screen readers cannot say where it goes.
Alternative text of images should not be repeated as text (10 elements)
Alternative text of images should not be repeated as text: 10 elements on the page fail this check, rated minor by axe-core.
Headings skip levels
Headings skip levels (h1 → h3, h1 → h3 and h3 → h5), which makes the page harder to scan with a screen reader.
1 checks passed
50 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 60 WCAG 2.2 A/AA and best-practice rules on the phone render: 50 passed and 10 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
2 H1 headlines
There are 2 <h1> headlines (“Volleres, stärkeres Haar, das sich wieder sehen l…” and “Deine persönliche, kostenlose & unverbindliche Ha…”). One clear main headline is easier for people and search engines.
365 internal links, 8 external
The homepage links to 365 pages on hairgivers.de and 8 external pages.
7 checks passed
Meta description: 155 characters
Your meta description is 155 characters: “Hairgivers, der Haarwuchsspezialist mit effektiven Haarwuchsmitteln & persönlicher Beratung ✅Kauf auf Rechnung ✅ Bewähr…”.
Title: 62 characters
Your title is a healthy 62 characters: “Hairgivers® | Für dein Haar, für dich - Haarwuchsmittel kaufen”.
Canonical URL set
The canonical URL is https://www.hairgivers.de/.
Structured data in place
Structured data found: BreadcrumbList, OnlineBusiness and Organization.
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.hairgivers.de/sitemap.xml.
AI search readiness
Organization data is thin (3 of 6 facts)
Your Organization JSON-LD is missing logo, description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.
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 (1,884 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.hairgivers.de/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
4 pages share a meta description
https://www.hairgivers.de/blogs/probleme/haarausfall, https://www.hairgivers.de/blogs/probleme/was-kann-man-gegen-trockenes-und-geschadigtes-haar-machen, https://www.hairgivers.de/blogs/probleme/arten-von-haarausfall and https://www.hairgivers.de/blogs/blog/top-3-der-besten-und-einfachsten-haarwuchsmittel-current-year use the same meta description. A description written for each page earns more clicks.
15 pages without an H1
https://www.hairgivers.de/pages/beratung, https://www.hairgivers.de/blogs/probleme/haarausfall, https://www.hairgivers.de/blogs/probleme/haarausfall-bei-manner, https://www.hairgivers.de/blogs/probleme/haarausfal-bei-frauen, https://www.hairgivers.de/blogs/probleme/haarausfall-nach-der-schwangerschaft and https://www.hairgivers.de/blogs/probleme/menopause-und-haarausfall and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 198 found) and read each the way a search engine does.
6 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
Every page has a meta description
All 15 pages that loaded have a meta description.
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 15 pages that loaded have a <title>.
Best practices
16 small tap targets
16 of 79 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
2 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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.
Local business without LocalBusiness data
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.
No analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
No opening hours
The homepage shows no opening hours. If customers visit or call, show when.
No map or directions link
There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.
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 1,165 words of copy
The homepage carries about 1,165 words of visible text.
4 checks passed
10 short forms
10 short forms (1 field at most) are right on the homepage.
Social proof on the page
Social proof on the homepage: 59 testimonial or review blocks, 3 customer or partner logos, a star rating and 1 trust badge.
Direct contact links
Visitors can reach you directly: 1 phone link and 1 email link.
Phone number on the homepage
Your phone number is on the homepage as a tap-to-call link.
Privacy and tracking
5 trackers load before any consent
5Before a visitor clicks anything, the page loads Google Ads, Google Tag Manager, Meta Pixel, Microsoft Ads and Reddit 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.
21 cookies set on arrival
21Opening the homepage sets 21 cookies, 1 of them by other companies (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.
41 other companies contacted
Loading the homepage contacts 41 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 hairgivers.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 15 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Pandectes Gdpr · Eg Auto Add To Cart · Fontify · Drip Email Marketing Popup · Loyalty Rewards And Referrals · Trusted Shops Reviews And More · Sc Easy 404 Ai Redirects · Wingify · Judge Me Reviews · Gdpr Cookie Consent · Hairgivers · luckyorange.com · revenuehunt.com · sealsubscriptions.com · amazonaws.com
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 36 issues on hairgivers.de, including 14 speed issues, 1 SEO issue 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.