Website review, no card needed
yepposoonsoo.de website review
Visit site (opens in a new tab)Reviewed 12 November 202625 issues · 76 checks
This review found 25 issues worth fixing on yepposoonsoo.de, 7 of them high impact, across 76 checks. The most urgent: 5,186 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
84B- #18,899 of 104,033 reviewed websitesbeats 77%
- #12,142 of 58,116 online storesbeats 73%
- #11,783 of 52,916 Shopify storesbeats 71%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 23, 2026 | 2.7 s |
| May 30, 2026 | 2.9 s |
| Jun 6, 2026 | 3.0 s |
| Jun 13, 2026 | 2.9 s |
| Jun 20, 2026 | 2.9 s |
| Jun 27, 2026 | 2.8 s |
| Jul 4, 2026 | 3.0 s |
| Jul 11, 2026 | 3.1 s |
| Jul 18, 2026 | 3.1 s |
| Jul 25, 2026 | 3.2 s |
| Aug 1, 2026 | 3.0 s |
| Aug 8, 2026 | 2.9 s |
| Aug 15, 2026 | 2.6 s |
| Aug 22, 2026 | 2.5 s |
| Aug 29, 2026 | 2.4 s |
| Sep 5, 2026 | 2.5 s |
| Sep 12, 2026 | 2.5 s |
| Sep 19, 2026 | 2.5 s |
| Sep 26, 2026 | 2.3 s |
| Oct 3, 2026 | 1.9 s |
| Oct 10, 2026 | 1.8 s |
| Oct 17, 2026 | 1.7 s |
| Oct 24, 2026 | 1.6 s |
| Oct 31, 2026 | 1.5 s |
| Nov 7, 2026 | 1.4 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 23, 2026 | 153 ms |
| May 30, 2026 | 223 ms |
| Jun 6, 2026 | 282 ms |
| Jun 13, 2026 | 381 ms |
| Jun 20, 2026 | 460 ms |
| Jun 27, 2026 | 690 ms |
| Jul 4, 2026 | 887 ms |
| Jul 11, 2026 | 909 ms |
| Jul 18, 2026 | 820 ms |
| Jul 25, 2026 | 641 ms |
| Aug 1, 2026 | 396 ms |
| Aug 8, 2026 | 347 ms |
| Aug 15, 2026 | 290 ms |
| Aug 22, 2026 | 254 ms |
| Aug 29, 2026 | 245 ms |
| Sep 5, 2026 | 269 ms |
| Sep 12, 2026 | 249 ms |
| Sep 19, 2026 | 227 ms |
| Sep 26, 2026 | 198 ms |
| Oct 3, 2026 | 139 ms |
| Oct 10, 2026 | 132 ms |
| Oct 17, 2026 | 129 ms |
| Oct 24, 2026 | 123 ms |
| Oct 31, 2026 | 129 ms |
| Nov 7, 2026 | 139 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.4 s
0.8 s
1.1 s
1.5 s
1.9 s
2.3 s
2.6 s
3.0 s
Speed
5,186 HTML elements
The page has 5,186 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Main-thread work: 4.7 s
A phone's processor spends 4.7 s on main-thread work while loading, 1.9 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Mobile performance score: 79
79/100Your mobile performance score is 79. Pages that score under 90 lose visitors before the first paint.
Render-blocking requests
550 ms5 files block the first paint until they finish downloading. Deferring or inlining them could save about 550 ms.
Shopify adds 101 ms
101 msShopify costs a phone 101 ms of main-thread work and 389 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.
8 third-party services on the page
8 third-party services load with your homepage (Clarity, Shopify and JSDelivr CDN and others), adding 713 KiB and 308 ms of main-thread time.
Use efficient cache lifetimes
150 ms · 204 KiB19 files are served with short cache lifetimes, so returning visitors download them again (204 KiB).
Reduce unused JavaScript
150 ms · 194 KiBAbout 194 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 150 ms faster on a phone.
Duplicated JavaScript
150 ms · 44 KiB44 KiB JavaScript is shipped twice across bundles. Google estimates it would make the page about 150 ms faster on a phone.
Reduce unused CSS
150 ms · 29 KiBAbout 29 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.
Improve image delivery
126 KiB7 images could be 126 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
12 long tasks on the main thread
12 long tasks block the main thread while loading, the longest for 104 ms. During a long task the page ignores taps.
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: 28 ms
28 msYour server sent the HTML in 28 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 4.4 s
4.4 sYour largest element takes 4.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “[Some By Mi] Retinol Intense Daily Mask”.
Time to Interactive: 8.0 s
8.0 sThe page becomes fully interactive after 8.0 s. Good is under 3.8 s.
Speed Index: 4.1 s
4.1 sVisually, the page fills in at 4.1 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 211 ms
211 msScripts block taps and scrolling for 211 ms in total while the page loads. Good is under 200 ms.
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.8 s
1.8 sReal visitors wait 1.8 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 143 ms
143 msReal visitors wait 143 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.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: 511 ms
511 msReal visitors wait 511 ms for your server to start answering (75th percentile). Good is under 800 ms.
Tap response (INP) got 29% faster for real visitors
-29%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 153 ms to 139 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 49% faster for real visitors
-49%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 2.7 s to 1.4 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
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
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 2.6 MB in 275 requests
2.6 MBYour homepage downloads 2.6 MB in 275 requests on a phone: other files 1,001 KiB (131), images 720 KiB (43) and scripts 676 KiB (75). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
VTCosmeticsRetinalPeptideCapsuleCream1.png 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).
About 0.7 g of CO₂ per visit
0.74 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.74 g of CO₂e: 88.9 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
46 text elements with low contrast
46 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
All page content should be contained by landmarks (3 elements)
All page content should be contained by landmarks: 3 elements on the page fail this check, rated moderate by axe-core.
30 links without text
30 visible links have no text or label, so screen readers cannot say where they go.
2 checks passed
Every image has alt text
All 307 images in the HTML carry an alt attribute.
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. 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 (276 characters)
Your meta description is 276 characters; Google truncates after about 160, so the end of your pitch is cut.
Structured data has 1 problem
Structured data found (Organization and WebSite) but with 1 problem, for example “Organization: url points at a different host (https://www.yeppo.fi)”.
308 internal links, 16 external
The homepage links to 308 pages on yepposoonsoo.de and 16 external pages.
6 checks passed
One H1 headline
Your main headline reads: “Hautpflege -25%”.
Title: 47 characters
Your title is a healthy 47 characters: “Yeppo&Soonsoo | Koreanische Kosmetik | K-Beauty”.
Canonical URL set
The canonical URL is https://www.yepposoonsoo.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.yepposoonsoo.de/sitemap.xml.
AI search readiness
4 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.
Organization data: 4 of 6 facts
Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (2,055 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.yepposoonsoo.de/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
2 pages share a title
https://www.yepposoonsoo.de/collections/korealainen-ihonhoito and https://www.yepposoonsoo.de/collections/hautpflege all use the title “Koreanische Hautpflege | K Beauty Hautpflegeprodukte für das Gesicht …”. Search engines can't tell which page to show for a search, so each competes with the others.
2 pages share a meta description
https://www.yepposoonsoo.de/collections/korealainen-ihonhoito and https://www.yepposoonsoo.de/collections/hautpflege 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://www.yepposoonsoo.de/collections/korealainen-ihonhoito, whose canonical is https://www.yepposoonsoo.de/collections/hautpflege. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
1 page without an H1
https://www.yepposoonsoo.de/pages/black-friday 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 182 found) and read each the way a search engine does.
4 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
Every page has a meta description
All 15 pages that loaded have a meta description.
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 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “safeCall failure TypeError: Cannot read properties of undefined (reading 'variants')”.
2 checks passed
Tap targets are thumb-sized
63 of 67 tappable elements near the top are at least 24 px.
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.
A 31-field form
Your longest form asks for 31 fields (0 required). Every extra field lowers completion.
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 982 words of copy
The homepage carries about 982 words of visible text.
3 checks passed
Social proof on the page
Social proof on the homepage: 47 testimonial or review blocks and 3 trust badges.
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
7 trackers load before any consent
7Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and Microsoft Clarity and 2 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.
18 cookies set on arrival
18Opening the homepage sets 18 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.
33 other companies contacted
Loading the homepage contacts 33 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 yepposoonsoo.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 8 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
T Lab Ai Translate · Multifeeds · Uppush Order Limit · Judge Me Reviews · Multi Location Inv · apprl.com · cloudfront.net · custobar.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
- Tailwind CSS
- 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 25 issues on yepposoonsoo.de, including 9 speed issues, 2 SEO issues and 3 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.