Website review, no card needed
lockenkopf.com website review
Visit site (opens in a new tab)Reviewed 11 November 202628 issues · 80 checks
This review found 28 issues worth fixing on lockenkopf.com, 6 of them high impact, across 80 checks. The most urgent: 9,450 HTML elements. 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
89B- #3,343 of 106,317 reviewed websitesbeats 95%
- #1,745 of 59,911 online storesbeats 95%
- #1,696 of 54,621 Shopify storesbeats 95%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 23, 2026 | 1.7 s |
| May 30, 2026 | 1.7 s |
| Jun 6, 2026 | 1.7 s |
| Jun 13, 2026 | 1.7 s |
| Jun 20, 2026 | 1.7 s |
| Jun 27, 2026 | 1.6 s |
| Jul 4, 2026 | 1.6 s |
| Jul 11, 2026 | 1.4 s |
| Jul 18, 2026 | 1.4 s |
| Jul 25, 2026 | 1.5 s |
| Aug 1, 2026 | 1.5 s |
| Aug 8, 2026 | 1.6 s |
| Aug 15, 2026 | 1.7 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.7 s |
| Oct 10, 2026 | 1.7 s |
| Oct 17, 2026 | 1.6 s |
| Oct 24, 2026 | 1.6 s |
| Oct 31, 2026 | 1.5 s |
| Nov 7, 2026 | 1.6 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 23, 2026 | 160 ms |
| May 30, 2026 | 162 ms |
| Jun 6, 2026 | 164 ms |
| Jun 13, 2026 | 176 ms |
| Jun 20, 2026 | 192 ms |
| Jun 27, 2026 | 200 ms |
| Jul 4, 2026 | 208 ms |
| Jul 11, 2026 | 208 ms |
| Jul 18, 2026 | 194 ms |
| Jul 25, 2026 | 195 ms |
| Aug 1, 2026 | 200 ms |
| Aug 8, 2026 | 216 ms |
| Aug 15, 2026 | 222 ms |
| Aug 22, 2026 | 228 ms |
| Aug 29, 2026 | 228 ms |
| Sep 5, 2026 | 219 ms |
| Sep 12, 2026 | 216 ms |
| Sep 19, 2026 | 215 ms |
| Sep 26, 2026 | 216 ms |
| Oct 3, 2026 | 220 ms |
| Oct 10, 2026 | 220 ms |
| Oct 17, 2026 | 214 ms |
| Oct 24, 2026 | 213 ms |
| Oct 31, 2026 | 201 ms |
| Nov 7, 2026 | 195 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
Speed
9,450 HTML elements
The page has 9,450 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Mobile performance score: 72
72/100Your mobile performance score is 72. Pages that score under 90 lose visitors before the first paint.
Render-blocking requests
750 ms4 files block the first paint until they finish downloading. Deferring or inlining them could save about 750 ms.
Reduce unused CSS
150 ms · 35 KiBAbout 35 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 150 ms faster on a phone.
Use efficient cache lifetimes
100 ms · 37 KiB8 files are served with short cache lifetimes, so returning visitors download them again (37 KiB).
Improve image delivery
96 KiB10 images could be 96 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
3 long tasks on the main thread
3 long tasks block the main thread while loading, the longest for 92 ms. During a long task the page ignores taps.
6 third-party services on the page
6 third-party services load with your homepage (Shopify, Klaviyo and shop.app and others), adding 532 KiB and 2 ms of main-thread time.
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
Main-thread work: 0.9 s
A phone's processor spends 0.9 s on main-thread work while loading, 194 ms of it running JavaScript. That is comfortably low.
Server response: 32 ms
32 msYour server sent the HTML in 32 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 7.7 s
7.7 sYour largest element takes 7.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Time to Interactive: 7.7 s
7.7 sThe page becomes fully interactive after 7.7 s. Good is under 3.8 s.
Tap response (INP) got 23% slower for real visitors
+23%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 160 ms to 195 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Speed Index: 4.4 s
4.4 sVisually, the page fills in at 4.4 s (Speed Index). Good is under 3.4 s.
3 images without width and height
3 images have no width and height attributes, so the layout jumps as each one loads.
10 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: 195 ms
195 msReal visitors wait 195 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user FCP: 1.2 s
1.2 sReal visitors see the first content after 1.2 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 585 ms
585 msReal visitors wait 585 ms for your server to start answering (75th percentile). Good is under 800 ms.
Largest content (LCP) got 10% faster for real visitors
-10%Over the last 25 four-week periods to 2026-11-07, 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).
First Contentful Paint: 1.7 s
1.7 sThe first text or image appears after 1.7 s, inside the 1.8 s “good” threshold.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Total Blocking Time: 57 ms
57 msScripts block the page for only 57 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 2.2 MB in 79 requests
2.2 MBYour homepage downloads 2.2 MB in 79 requests on a phone: images 1.2 MB (41), scripts 593 KiB (27) and HTML 190 KiB (1). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
lockenkopf-Deutschland-curly-boutique-slider3.jpg is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).
1 image in older formats
1 image (30 KiB) is JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.
1 image below the first screen load straight away
1 image further down the page (24 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.
About 0.6 g of CO₂ per visit
0.63 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.63 g of CO₂e: 75.9 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
17 text elements with low contrast
17 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
4 tap targets too small
4 tap targets are too small or too close together to hit reliably with a finger.
All page content should be contained by landmarks (12 elements)
All page content should be contained by landmarks: 12 elements on the page fail this check, rated moderate by axe-core.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
Alternative text of images should not be repeated as text (1 element)
Alternative text of images should not be repeated as text: 1 element on the page fails this check, rated minor by axe-core.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (1 element).
2 checks passed
Every image has alt text
All 189 images in the HTML carry an alt attribute.
51 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 56 WCAG 2.2 A/AA and best-practice rules on the phone render: 51 passed and 5 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Meta description is long (175 characters)
Your meta description is 175 characters; Google truncates after about 160, so the end of your pitch is cut.
8 links with vague text
8 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
689 internal links, 0 external
The homepage links to 689 pages on lockenkopf.com and 0 external pages.
7 checks passed
One H1 headline
Your main headline reads: “lockenkopf Deutschland”.
Title: 58 characters
Your title is a healthy 58 characters: “Natürliche Lockenpflege & Curly Girl Produkte | lockenkopf”.
Canonical URL set
The canonical URL is https://lockenkopf.com/en.
Structured data in place
Structured data found: 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://lockenkopf.com/sitemap.xml.
AI search readiness
Organization data is thin (3 of 6 facts)
Your Organization JSON-LD is missing sameAs (social profiles), 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 (3,244 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://lockenkopf.com/llms.txt (37 KiB, 169 links), a plain-text guide to the site for AI tools.
Other pages
1 page without a title
https://lockenkopf.com/customer_authentication/redirect has no <title>, so Google invents the link text in results.
1 linked page hidden from search
https://lockenkopf.com/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.
2 pages share a title
https://lockenkopf.com/en and https://lockenkopf.com/ena/wishlist all use the title “Natürliche Lockenpflege & Curly Girl Produkte | lockenkopf”. Search engines can't tell which page to show for a search, so each competes with the others.
1 page without a meta description
https://lockenkopf.com/customer_authentication/redirect has no meta description, so Google writes the search snippet from whatever text it finds.
2 pages share a meta description
https://lockenkopf.com/ena/wishlist and https://lockenkopf.com/en/collections use the same meta description. A description written for each page earns more clicks.
1 link to non-canonical URLs
Your homepage links to 1 page by a URL that isn't its canonical one, for example https://lockenkopf.com/ena/wishlist, whose canonical is https://lockenkopf.com/en. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
1 page without an H1
https://lockenkopf.com/customer_authentication/redirect has 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 191 found) and read each the way a search engine does.
1 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
Best practices
54 small tap targets
54 of 150 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
5 JavaScript errors while loading
5 errors were logged to the browser console while the page loaded, for example “Cannot redefine property: src Object.defineProperties (<anonymous>)”.
1 low-resolution image
1 image is served at too low a resolution for sharp phone screens.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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 2,686 words of copy
The homepage carries about 2,686 words of visible text.
6 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “SHOP NOW”.
7 calls to action
The homepage has 7 calls to action, for example “Travel & Get Started & Kits”, “Contact” and “Start shopping”.
59 short forms
59 short forms (1 field at most) are right on the homepage.
Social proof on the page
Social proof on the homepage: 112 testimonial or review blocks and a star rating.
Analytics in place
Analytics detected: Microsoft Clarity.
Direct contact links
Visitors can reach you directly: 0 phone links and 1 email link.
Privacy and tracking
2 trackers load before any consent
2Before a visitor clicks anything, the page loads Google Tag Manager and 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.
6 cookies set on arrival
6Opening the homepage sets 6 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.
10 other companies contacted
Loading the homepage contacts 10 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 lockenkopf.com, 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 16 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Pandectes Gdpr · Tinyseo Ai Seo Speed · Fbp Fast Bundle · Fd Combined Listings · Klaviyo Email Marketing Sms · Multifeeds · Langify · Seowill Redirects · Judge Me Reviews · Gdpr Cookie Consent · Fd Product Groups · Revoq Eu Withdrawal Button · Freegifts · webmarked.net · bogos.io · trustedshops.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
- Framework
- jQuery
- E-commerce
- Shopify
- Analytics
- Google Analytics
- Hosting
- Shopify
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 28 issues on lockenkopf.com, including 8 speed issues and 2 SEO issues. 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.