Website review, no card needed
zoevacosmetics.de website review
Visit site (opens in a new tab)Reviewed 10 November 202645 issues · 90 checks
This review found 45 issues worth fixing on zoevacosmetics.de, 15 of them high impact, across 90 checks. The most urgent: reduce unused JavaScript. 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
76C- #62,754 of 102,353 reviewed websitesbeats 34%
- #39,488 of 56,833 online storesbeats 26%
- #37,402 of 51,696 Shopify storesbeats 23%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 23, 2026 | 2.2 s |
| May 30, 2026 | 2.2 s |
| Jun 6, 2026 | 2.2 s |
| Jun 13, 2026 | 2.2 s |
| Jun 20, 2026 | 2.3 s |
| Jun 27, 2026 | 2.4 s |
| Jul 4, 2026 | 2.5 s |
| Jul 11, 2026 | 2.5 s |
| Jul 18, 2026 | 2.4 s |
| Jul 25, 2026 | 2.4 s |
| Aug 1, 2026 | 2.3 s |
| Aug 8, 2026 | 2.3 s |
| Aug 15, 2026 | 2.3 s |
| Aug 22, 2026 | 2.3 s |
| Aug 29, 2026 | 2.3 s |
| Sep 5, 2026 | 2.3 s |
| Sep 12, 2026 | 2.3 s |
| Sep 19, 2026 | 2.2 s |
| Sep 26, 2026 | 2.2 s |
| Oct 3, 2026 | 2.2 s |
| Oct 10, 2026 | 2.3 s |
| Oct 17, 2026 | 2.3 s |
| Oct 24, 2026 | 2.3 s |
| Oct 31, 2026 | 2.2 s |
| Nov 7, 2026 | 2.2 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 23, 2026 | 222 ms |
| May 30, 2026 | 226 ms |
| Jun 6, 2026 | 233 ms |
| Jun 13, 2026 | 240 ms |
| Jun 20, 2026 | 247 ms |
| Jun 27, 2026 | 252 ms |
| Jul 4, 2026 | 255 ms |
| Jul 11, 2026 | 260 ms |
| Jul 18, 2026 | 262 ms |
| Jul 25, 2026 | 257 ms |
| Aug 1, 2026 | 255 ms |
| Aug 8, 2026 | 257 ms |
| Aug 15, 2026 | 260 ms |
| Aug 22, 2026 | 259 ms |
| Aug 29, 2026 | 253 ms |
| Sep 5, 2026 | 245 ms |
| Sep 12, 2026 | 237 ms |
| Sep 19, 2026 | 238 ms |
| Sep 26, 2026 | 262 ms |
| Oct 3, 2026 | 313 ms |
| Oct 10, 2026 | 368 ms |
| Oct 17, 2026 | 397 ms |
| Oct 24, 2026 | 403 ms |
| Oct 31, 2026 | 409 ms |
| Nov 7, 2026 | 405 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
2.9 s
5.8 s
8.7 s
11.6 s
14.6 s
17.5 s
20.4 s
23.3 s
Speed
Reduce unused JavaScript
1.7 s · 1.1 MBAbout 1.1 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.7 s faster on a phone.
Main-thread work: 11.3 s
A phone's processor spends 11.3 s on main-thread work while loading, 2.9 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Render-blocking requests
1.0 s6 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.0 s.
3,507 HTML elements
The page has 3,507 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 (Google Tag Manager, Clarity and Klaviyo and others), adding 2.9 MB and 1.6 s of main-thread time.
Mobile performance score: 55
55/100Your mobile performance score is 55. Pages that score under 90 lose visitors before the first paint.
Improve image delivery
845 KiB10 images could be 845 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Google Tag Manager adds 519 ms
519 msGoogle Tag Manager costs a phone 519 ms of main-thread work and 685 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.
Use efficient cache lifetimes
450 KiB19 files are served with short cache lifetimes, so returning visitors download them again (450 KiB).
Shopify adds 186 ms
186 msShopify costs a phone 186 ms of main-thread work and 929 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 202 ms
202 msKlaviyo costs a phone 202 ms of main-thread work and 337 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.
rebuyengine.com adds 114 ms
114 msrebuyengine.com costs a phone 114 ms of main-thread work and 298 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
150 ms · 86 KiBAbout 86 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.
15 long tasks on the main thread
15 long tasks block the main thread while loading, the longest for 184 ms. During a long task the page ignores taps.
Legacy JavaScript
66 KiBPolyfills for old browsers add 66 KiB JavaScript that modern phones do not need.
Minify JavaScript
9 KiB9 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.
1 checks passed
Server response: 13 ms
13 msYour server sent the HTML in 13 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.
Largest Contentful Paint: 10.7 s
10.7 sYour largest element takes 10.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.
Time to Interactive: 30.2 s
30.2 sThe page becomes fully interactive after 30.2 s. Good is under 3.8 s.
Speed Index: 6.4 s
6.4 sVisually, the page fills in at 6.4 s (Speed Index). Good is under 3.4 s.
Real-user INP: 403 ms
403 msReal visitors wait 403 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Tap response (INP) got 82% slower for real visitors
+82%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 222 ms to 405 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Total Blocking Time: 434 ms
434 msScripts block taps and scrolling for 434 ms in total while the page loads. Good is under 200 ms.
Cumulative Layout Shift: 0.104
0.104The layout shifts by 0.104 while loading, so content jumps under the reader's thumb. Good is under 0.1.
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
0%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 2.2 s to 2.2 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
5 checks passed
Real-user LCP: 2.2 s
2.2 sReal visitors wait 2.2 s for the largest content to appear (75th percentile). Good is under 2.5 s.
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.4 s
1.4 sReal visitors see the first content after 1.4 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 683 ms
683 msReal visitors wait 683 ms for your server to start answering (75th percentile). Good is under 800 ms.
First Contentful Paint: 1.5 s
1.5 sThe first text or image appears after 1.5 s, inside the 1.8 s “good” threshold.
Images and page weight
Page weight: 20.3 MB in 449 requests
20.3 MBYour homepage downloads 20.3 MB in 449 requests on a phone: media 14.2 MB (4), scripts 2.7 MB (108) and images 1.4 MB (37). Under 2 MB keeps phones on slow connections fast.
1 image over 500 KB
HP26_CRYSTAL-LIPSTICK_MULTI_TILE_01.gif weighs 535 KiB. On a phone connection a single image that size takes seconds.
1 image in older formats
1 image (535 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.
2 images below the first screen load straight away
2 images further down the page (555 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 5.8 g of CO₂ per visit
5.76 gBy the Sustainable Web Design model, a visit to your homepage emits about 5.76 g of CO₂e: 691.8 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
10 tap targets too small
10 tap targets are too small or too close together to hit reliably with a finger.
ARIA tooltip nodes must have an accessible name (1 element)
ARIA tooltip nodes must have an accessible name: 1 element on the page fails this check, rated serious by axe-core.
Malformed lists
Some lists contain elements other than list items, which screen readers announce wrongly.
4 images without alt text
4 images have no alt text, which hurts accessibility and image search.
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.
All page content should be contained by landmarks (1 element)
All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.
23 links without text
23 visible links have no text or label, so screen readers cannot say where they go.
2 form fields without a label
2 form fields have no label, so screen readers announce an empty box and autofill guesses.
ARIA role should be appropriate for the element (2 elements)
ARIA role should be appropriate for the element: 2 elements on the page fail this check, rated minor by axe-core.
Headings skip levels
Headings skip levels (h2 → h4), which makes the page harder to scan with a screen reader.
1 checks passed
55 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 63 WCAG 2.2 A/AA and best-practice rules on the phone render: 55 passed and 8 failed. 4 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
100 links crawlers can't follow
100 links have no real href, so search engines can't follow them.
197 internal links, 13 external
The homepage links to 197 pages on zoevacosmetics.de and 13 external pages.
8 checks passed
Meta description: 125 characters
Your meta description is 125 characters: “Beauty, makeup & brushes by ZOEVA 💖 Discover new beauty trends! 💖 Brushes, eyeshadow, foundation & more! ➤ Shop onlin…”.
One H1 headline
Your main headline reads: “ZOEVA Cosmetics”.
Title: 44 characters
Your title is a healthy 44 characters: “ZOEVA | Beauty, Makeup & Brushes | Shop now!”.
Canonical URL set
The canonical URL is https://zoevacosmetics.com/en-us.
Structured data in place
Structured data found: BreadcrumbList, Organization and WebSite.
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://zoevacosmetics.com/sitemap.xml.
AI search readiness
Organization data is thin (2 of 6 facts)
Your Organization JSON-LD is missing logo, 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 (1,083 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://zoevacosmetics.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
2 pages share a title
https://zoevacosmetics.com/en/products/fsb-xmas2026 and https://zoevacosmetics.com/en-us/products/fsb-xmas2026 all use the title “La Célébration Christmas Set - Build your Christmas Kit”. Search engines can't tell which page to show for a search, so each competes with the others.
9 pages without a meta description
https://zoevacosmetics.com/en/products/fsb-xmas2026, https://zoevacosmetics.com/en-us/collections/christmas-collection-2026, https://zoevacosmetics.com/en-us/collections/christmas-augen, https://zoevacosmetics.com/en-us/collections/christmas-lippen, https://zoevacosmetics.com/en-us/collections/christmas-geschenksets and https://zoevacosmetics.com/en-us/products/fsb-xmas2026 and 3 others have no meta description, so Google writes the search snippet from whatever text it finds.
2 links to non-canonical URLs
Your homepage links to 2 pages by a URL that isn't their canonical one, for example https://zoevacosmetics.com/en/products/fsb-xmas2026, whose canonical is https://zoevacosmetics.com/en-us/products/fsb-xmas2026. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
15 pages without an H1
https://zoevacosmetics.com/en/products/fsb-xmas2026, https://zoevacosmetics.com/en/pages/shipping-delivery-1, https://zoevacosmetics.com/en-us/collections/christmas-collection-2026, https://zoevacosmetics.com/en-us/collections/christmas-augen, https://zoevacosmetics.com/en-us/collections/christmas-lippen and https://zoevacosmetics.com/en-us/collections/christmas-geschenksets 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 86 found) and read each the way a search engine does.
3 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
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
1 broken image
1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=134422823&tm=gtm002&Ver=2&mid=1957c43d-4391-425c-bebe-fcd4ea0c3ad2&bo=1&sid=e9ae6da0dd2311f1ba8c2f355fc412f4&vid=e9ae8f50dd2311f187bfd710885e7fca&vids=1&msclkid=N&pi=9.
17 small tap targets
17 of 35 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
6 JavaScript errors while loading
6 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.
Missing source maps
Large scripts ship without source maps.
1 checks passed
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 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 581 words of copy
The homepage carries about 581 words of visible text.
5 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Learn more”.
9 calls to action
The homepage has 9 calls to action, for example “Shop All”, “Register” and “Trace my order”.
6 short forms
6 short forms (1 field at most) are right on the homepage.
Social proof on the page
Social proof on the homepage: 1 testimonial or review block and 1 trust badge.
Analytics in place
Analytics detected: Microsoft Clarity.
Privacy and tracking
8 trackers load before any consent
8Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel and 3 mores (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.
31 cookies set on arrival
31Opening the homepage sets 31 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.
43 other companies contacted
Loading the homepage contacts 43 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 zoevacosmetics.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 · Yotpo Product Reviews · Oxify Cart Drawer · Microsoft Clarity · Rebuy Personalization Engine · Gorgias Live Chat Helpdesk · Elevar Conversion Tracking · Zoeva Discounts · Klaviyo Email Marketing Sms · Hulk Form Builder · Gdpr Cookie Consent · Forms · Polar Analytics · web.app · rebuyengine.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
- Bootstrap
- E-commerce
- Shopify
- Analytics
- Microsoft Clarity
- Hosting
- Shopify
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 45 issues on zoevacosmetics.de, including 21 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.