Website review, no card needed
maniko-nails.de website review
Visit site (opens in a new tab)Reviewed 5 November 202642 issues · 93 checks
This review found 42 issues worth fixing on maniko-nails.de, 16 of them high impact, across 93 checks. The most urgent: mobile performance score: 27. 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
74C- #86,566 of 123,879 reviewed websitesbeats 26%
- #54,439 of 69,702 online storesbeats 18%
- #51,149 of 63,406 Shopify storesbeats 16%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 1.8 s |
| May 23, 2026 | 1.8 s |
| May 30, 2026 | 1.8 s |
| Jun 6, 2026 | 1.7 s |
| Jun 13, 2026 | 1.7 s |
| Jun 20, 2026 | 1.7 s |
| Jun 27, 2026 | 1.7 s |
| Jul 4, 2026 | 1.7 s |
| Jul 11, 2026 | 1.8 s |
| Jul 18, 2026 | 1.8 s |
| Jul 25, 2026 | 1.7 s |
| Aug 1, 2026 | 1.7 s |
| Aug 8, 2026 | 1.7 s |
| Aug 15, 2026 | 1.7 s |
| Aug 22, 2026 | 1.8 s |
| Aug 29, 2026 | 1.8 s |
| Sep 5, 2026 | 1.8 s |
| Sep 12, 2026 | 1.8 s |
| Sep 19, 2026 | 1.8 s |
| Sep 26, 2026 | 1.8 s |
| Oct 3, 2026 | 1.8 s |
| Oct 10, 2026 | 1.7 s |
| Oct 17, 2026 | 1.7 s |
| Oct 24, 2026 | 1.7 s |
| Oct 31, 2026 | 1.7 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 111 ms |
| May 23, 2026 | 113 ms |
| May 30, 2026 | 115 ms |
| Jun 6, 2026 | 118 ms |
| Jun 13, 2026 | 121 ms |
| Jun 20, 2026 | 122 ms |
| Jun 27, 2026 | 125 ms |
| Jul 4, 2026 | 127 ms |
| Jul 11, 2026 | 127 ms |
| Jul 18, 2026 | 126 ms |
| Jul 25, 2026 | 123 ms |
| Aug 1, 2026 | 124 ms |
| Aug 8, 2026 | 125 ms |
| Aug 15, 2026 | 127 ms |
| Aug 22, 2026 | 128 ms |
| Aug 29, 2026 | 131 ms |
| Sep 5, 2026 | 136 ms |
| Sep 12, 2026 | 140 ms |
| Sep 19, 2026 | 145 ms |
| Sep 26, 2026 | 144 ms |
| Oct 3, 2026 | 143 ms |
| Oct 10, 2026 | 141 ms |
| Oct 17, 2026 | 138 ms |
| Oct 24, 2026 | 139 ms |
| Oct 31, 2026 | 142 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.9 s
1.9 s
2.8 s
3.8 s
4.7 s
5.7 s
6.6 s
7.6 s
Speed
Mobile performance score: 27
27/100Your mobile performance score is 27. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 6.9 s
A phone's processor spends 6.9 s on main-thread work while loading, 3.3 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
3,585 HTML elements
The page has 3,585 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
8 third-party services on the page
8 third-party services load with your homepage (ContentSquare, Shopify and Klaviyo and others), adding 1.5 MB and 1.2 s of main-thread time.
Reduce unused JavaScript
450 ms · 710 KiBAbout 710 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 450 ms faster on a phone.
Improve image delivery
150 ms · 437 KiB11 images could be 437 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 150 ms faster on a phone.
ContentSquare adds 328 ms
328 msContentSquare costs a phone 328 ms of main-thread work and 213 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.
18 long tasks on the main thread
18 long tasks block the main thread while loading, the longest for 287 ms. During a long task the page ignores taps.
Shopify adds 232 ms
232 msShopify costs a phone 232 ms of main-thread work and 338 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.
Klaviyo adds 183 ms
183 msKlaviyo costs a phone 183 ms of main-thread work and 368 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.
LoyaltyLion adds 58 ms
58 msLoyaltyLion costs a phone 58 ms of main-thread work and 377 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.
Render-blocking requests
250 ms4 files block the first paint until they finish downloading. Deferring or inlining them could save about 250 ms.
Reduce unused CSS
150 ms · 56 KiBAbout 56 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
169 KiB37 files are served with short cache lifetimes, so returning visitors download them again (169 KiB).
Legacy JavaScript
80 KiBPolyfills for old browsers add 80 KiB JavaScript that modern phones do not need.
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 JavaScript
4 KiB4 KiB could be saved by minifying JavaScript.
1 checks passed
Server response: 104 ms
104 msYour server sent the HTML in 104 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Fails Core Web Vitals for real visitors
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.
Real-user CLS: 0.30
0.30For real visitors the layout shifts by 0.30 (75th percentile). Good is under 0.1.
Largest Contentful Paint: 9.1 s
9.1 sYour largest element takes 9.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Time to Interactive: 23.0 s
23.0 sThe page becomes fully interactive after 23.0 s. Good is under 3.8 s.
Speed Index: 10.5 s
10.5 sVisually, the page fills in at 10.5 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 1.2 s
1.2 sScripts block taps and scrolling for 1.2 s in total while the page loads. Good is under 200 ms.
Tap response (INP) got 25% slower for real visitors
+25%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 111 ms to 142 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0.239
0.239The layout shifts by 0.239 while loading, so content jumps under the reader's thumb. Good is under 0.1.
First Contentful Paint: 2.6 s
2.6 sThe first text or image appears after 2.6 s on a phone. Good is under 1.8 s.
Largest content (LCP) held steady for real visitors
-4%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).
4 checks passed
Real-user LCP: 2.0 s
2.0 sReal visitors wait 2.0 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 131 ms
131 msReal visitors wait 131 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user FCP: 0.9 s
0.9 sReal visitors see the first content after 0.9 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 314 ms
314 msReal visitors wait 314 ms for your server to start answering (75th percentile). Good is under 800 ms.
Images and page weight
Page weight: 6.7 MB in 380 requests
6.7 MBYour homepage downloads 6.7 MB in 380 requests on a phone: scripts 2.2 MB (156), images 2.0 MB (45) and other files 1.7 MB (136). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
ID-119590_Website_Halloween_Homepage_Banner_550x.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).
4 images in older formats
4 images (800 KiB) are 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.
About 1.9 g of CO₂ per visit
1.90 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.90 g of CO₂e: 228.1 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
Images must have alternative text (23 elements)
Images must have alternative text: 23 elements on the page fail this check, rated critical by axe-core.
3 buttons without a name
3 buttons have no accessible name, so screen readers announce just “button”.
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.
3 tap targets too small
3 tap targets are too small or too close together to hit reliably with a finger.
Elements must only use permitted ARIA attributes (2 elements)
Elements must only use permitted ARIA attributes: 2 elements on the page fail this check, rated serious by axe-core.
All page content should be contained by landmarks (111 elements)
All page content should be contained by landmarks: 111 elements on the page fail this check, rated moderate by axe-core.
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.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
8 links without text
8 visible links have no text or label, so screen readers cannot say where they go.
ARIA role should be appropriate for the element (9 elements)
ARIA role should be appropriate for the element: 9 elements on the page fail this check, rated minor by axe-core.
Headings skip levels
Headings skip levels (h1 → h3, h3 → h5 and h3 → h5), which makes the page harder to scan with a screen reader.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (1 element).
1 checks passed
51 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 62 WCAG 2.2 A/AA and best-practice rules on the phone render: 51 passed and 11 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 (“Gratis Beauty Bag zu jedem Set!” and “Das limitierte Halloween-Design ist da. 🌑”). One clear main headline is easier for people and search engines.
Open Graph partly set
Open Graph is missing og:title and og:description, so shared links fall back to guesses.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
130 internal links, 25 external
The homepage links to 130 pages on maniko-nails.de and 25 external pages.
6 checks passed
Meta description: 148 characters
Your meta description is 148 characters: “Nie wieder Absplittern, kein Trocknen, keine Kompromisse. Entdecke Maniko – die neue Art der Maniküre für echte Ergebni…”.
Title: 47 characters
Your title is a healthy 47 characters: “Maniko Nails – Die einfachste Maniküre der Welt”.
Canonical URL set
The canonical URL is https://www.maniko-nails.de/.
Structured data in place
Structured data found: Organization and WebSite.
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.maniko-nails.de/sitemap.xml.
AI search readiness
robots.txt blocks 3 AI answer engine crawlers
3 of 6Your robots.txt shuts out ChatGPT search (OAI-SearchBot), Claude search (Claude-SearchBot) and Perplexity (PerplexityBot). These fetch pages to answer people's questions and cite the source, so your site can't be quoted or linked in those answers.
Opted out of AI training for 5 crawlers
robots.txt blocks GPTBot, ClaudeBot, Google-Extended, Applebot-Extended and CCBot, which collect pages to train models. That's a legitimate choice and doesn't by itself stop the site appearing in AI answers.
3 checks passed
Organization data: 6 of 6 facts
Your Organization JSON-LD gives name, url, logo, sameAs (social profiles), description and contact details.
Text is in the HTML
Your server sends the page's text in the HTML (1,877 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.maniko-nails.de/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
7 pages without a meta description
https://www.maniko-nails.de/pages/anwendung-hub, https://www.maniko-nails.de/collections/zubehor, https://www.maniko-nails.de/collections/soft-gel-press-ons, https://www.maniko-nails.de/collections/zubehoer-sgpo, https://www.maniko-nails.de/collections/sets and https://www.maniko-nails.de/collections/zubehor-nagelpflege and 1 other have no meta description, so Google writes the search snippet from whatever text it finds.
2 pages share a meta description
https://www.maniko-nails.de/products/soft-gel-press-on-starter-set and https://www.maniko-nails.de/products/soft-gel-press-on-nachfull-set use the same meta description. A description written for each page earns more clicks.
11 pages without an H1
https://www.maniko-nails.de/pages/einzelhandel, https://www.maniko-nails.de/collections/uvgel, https://www.maniko-nails.de/collections/zubehor, https://www.maniko-nails.de/collections/pedikure, https://www.maniko-nails.de/products/uvg-starter-set and https://www.maniko-nails.de/products/refill-set and 5 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 42 found) and read each the way a search engine does.
5 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.
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
3 third-party cookies
3 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.
6 JavaScript errors while loading
6 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 ()”.
Missing source maps
Large scripts ship without source maps.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
2 checks passed
Tap targets are thumb-sized
74 of 92 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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 form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
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,931 words of copy
The homepage carries about 1,931 words of visible text.
4 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Starter Set Ideal für den Start”.
3 calls to action
The homepage has 3 calls to action, for example “Shop” and “Starter Set Ideal für den Start”.
Social proof on the page
Social proof on the homepage: 102 testimonial or review blocks, a star rating and 4 trust badges.
Analytics in place
Analytics detected: Google Tag Manager, Google Analytics, Microsoft Clarity and Hotjar.
Privacy and tracking
4 trackers load before any consent
4Before a visitor clicks anything, the page loads Google Analytics, Hotjar, Klaviyo and Snap 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.
19 cookies set on arrival
19Opening the homepage sets 19 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.
44 other companies contacted
Loading the homepage contacts 44 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 maniko-nails.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 20 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Pandectes Gdpr · Mable · Loyalty Rewards And Referrals · Gempages Builder · Kameleoon A B Testing · Uppromote Affiliate · Seowill Redirects · Powerful Form Builder · Djp Rich Snippets Seo Schema · Se Wishlist Engine · Klaviyo Email Marketing Sms · Eg Auto Add To Cart · Gsc Instagram Feed · Contentsquare Analytics · Gdpr Cookie Consent · Affliate By Secomapp · Shoplab Boostly · snapchat.com · linkster.co · cloudfront.net
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
- The footer still says © 2018.
Stack
- Framework
- Tailwind CSS
- E-commerce
- Shopify
- Analytics
- Google Analytics | Google Tag Manager | Hotjar | Microsoft Clarity
- Hosting
- Shopify
Hiring
- Hiring
- 8 open roles
- Teams
- Marketing (5), Operations (3)
- Job board
- recruitee
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 42 issues on maniko-nails.de, including 20 speed issues, 1 SEO issue and 1 conversion gap. 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.