Website review, no card needed
asambeauty.com website review
Visit site (opens in a new tab)Reviewed 28 October 202618 issues · 70 checks
This review found 18 issues worth fixing on asambeauty.com, 5 of them high impact, across 70 checks. The most urgent: 1 button without a name. 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
85BClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 1.9 s |
| May 16, 2026 | 1.9 s |
| May 23, 2026 | 1.9 s |
| May 30, 2026 | 1.9 s |
| Jun 6, 2026 | 1.9 s |
| Jun 13, 2026 | 1.9 s |
| Jun 20, 2026 | 1.9 s |
| Jun 27, 2026 | 1.9 s |
| Jul 4, 2026 | 2.0 s |
| Jul 11, 2026 | 2.0 s |
| Jul 18, 2026 | 2.0 s |
| Jul 25, 2026 | 2.0 s |
| Aug 1, 2026 | 2.0 s |
| Aug 8, 2026 | 2.1 s |
| Aug 15, 2026 | 2.1 s |
| Aug 22, 2026 | 2.1 s |
| Aug 29, 2026 | 2.1 s |
| Sep 5, 2026 | 2.1 s |
| Sep 12, 2026 | 2.1 s |
| Sep 19, 2026 | 2.0 s |
| Sep 26, 2026 | 2.0 s |
| Oct 3, 2026 | 2.0 s |
| Oct 10, 2026 | 2.0 s |
| Oct 17, 2026 | 2.1 s |
| Oct 24, 2026 | 2.1 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 160 ms |
| May 16, 2026 | 159 ms |
| May 23, 2026 | 159 ms |
| May 30, 2026 | 158 ms |
| Jun 6, 2026 | 160 ms |
| Jun 13, 2026 | 160 ms |
| Jun 20, 2026 | 161 ms |
| Jun 27, 2026 | 162 ms |
| Jul 4, 2026 | 166 ms |
| Jul 11, 2026 | 169 ms |
| Jul 18, 2026 | 170 ms |
| Jul 25, 2026 | 170 ms |
| Aug 1, 2026 | 169 ms |
| Aug 8, 2026 | 169 ms |
| Aug 15, 2026 | 170 ms |
| Aug 22, 2026 | 170 ms |
| Aug 29, 2026 | 168 ms |
| Sep 5, 2026 | 166 ms |
| Sep 12, 2026 | 163 ms |
| Sep 19, 2026 | 163 ms |
| Sep 26, 2026 | 163 ms |
| Oct 3, 2026 | 165 ms |
| Oct 10, 2026 | 166 ms |
| Oct 17, 2026 | 168 ms |
| Oct 24, 2026 | 171 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
Mobile performance score: 86
86/100Your mobile performance score is 86 (desktop: 100). Pages that score under 90 lose visitors before the first paint.
Improve image delivery
150 ms · 43 KiB1 image could be 43 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.
Reduce unused CSS
22 KiBAbout 22 KiB of CSS is downloaded but never applied on this page.
1 third-party service on the page
1 third-party service load with your homepage (Cloudinary), adding 64 KiB and 0 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.
2 checks passed
Server response: 315 ms
315 msYour server sent the HTML in 315 ms, well inside Google's 600 ms guideline.
Main-thread work: 0.1 s
A phone's processor spends 0.1 s on main-thread work while loading, 4 ms of it running JavaScript. That is comfortably low.
Core Web Vitals
Cumulative Layout Shift: 0.261
0.261The layout shifts by 0.261 while loading, so content jumps under the reader's thumb. Good is under 0.1.
2 images without width and height
2 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
+6%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 160 ms to 171 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 11% slower for real visitors
+11%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 1.9 s to 2.1 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
11 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.2 s
1.2 sReal visitors wait 1.2 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 26 ms
26 msReal visitors wait 26 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: 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: 650 ms
650 msReal visitors wait 650 ms for your server to start answering (75th percentile). Good is under 800 ms.
Largest Contentful Paint: 2.0 s
2.0 sYour largest element renders in 2.0 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the image.
Time to Interactive: 2.0 s
2.0 sThe page is fully interactive after 2.0 s.
First Contentful Paint: 1.0 s
1.0 sThe first text or image appears after 1.0 s, inside the 1.8 s “good” threshold.
Speed Index: 1.6 s
1.6 sVisually, the page fills in at 1.6 s (Speed Index), inside the 3.4 s “good” threshold.
Total Blocking Time: 0 ms
0 msScripts block the page for only 0 ms while loading. Good is under 200 ms.
Images and page weight
An image on the first screen is lazy-loaded
MA__MF__0__MU__MG__make-up__OTH__0__plp-header.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).
1 image far larger than shown
13 KiB1 image is downloaded at several times the size a phone draws it, for example MA__MF__0__MU__MG__make-up__OTH__0__plp-header.png at 1,280 px wide, shown at 390 px. Resized copies would save about 13 KiB.
About 0.05 g of CO₂ per visit
0.05 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.05 g of CO₂e: 6.0 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 checks passed
Page weight: 180 KiB in 5 requests
180 KiBYour homepage downloads 180 KiB in 5 requests on a phone: fonts 78 KiB (2), images 74 KiB (2) and HTML 27 KiB (1). That is a lean page.
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Accessibility
1 button without a name
1 button has no accessible name, so screen readers announce just “button”.
All page content should be contained by landmarks (8 elements)
All page content should be contained by landmarks: 8 elements on the page fail this check, rated moderate by axe-core.
No main landmark
The page has no <main> landmark, so screen-reader users cannot jump straight to the content.
2 checks passed
Every image has alt text
All 2 images in the HTML carry an alt attribute.
22 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 25 WCAG 2.2 A/AA and best-practice rules on the phone render: 22 passed and 3 failed. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No social preview image
No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
14 internal links, 0 external
The homepage links to 14 pages on asambeauty.com and 0 external pages.
7 checks passed
Meta description: 156 characters
Your meta description is 156 characters: “Entdecke hochwertige Kosmetik & Hautpflege - wirksame Pflegeprodukte für Gesicht, Haare & Körper. ✓ Für jeden Hauttyp &…”.
One H1 headline
Your main headline reads: “Choose your shop”.
Title: 54 characters
Your title is a healthy 54 characters: “asambeauty Online Shop | M. Asam Kosmetik & Hautpflege”.
Canonical URL set
The canonical URL is https://www.asambeauty.com/.
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.asambeauty.com/de-de/sitemap.xml.
AI search readiness
No llms.txt
There is no https://www.asambeauty.com/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.
2 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: 5 of 6 facts
Your Organization JSON-LD gives name, url, logo, sameAs (social profiles) and contact details; description would complete it.
Other pages
5 pages share a meta description
https://www.asambeauty.com/de-de, https://www.asambeauty.com/de-at and https://www.asambeauty.com/de-ch use the same meta description. A description written for each page earns more clicks.
2 pages slow to respond
https://www.asambeauty.com/fr-ch and https://www.asambeauty.com/de-de/service/agb took over 3 s to send their HTML from our server.
9 internal pages checked
We fetched 9 pages linked from your homepage and read each the way a search engine does.
7 checks passed
Linked pages load
All 9 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 9 pages that loaded have a meta description.
Titles are unique
Every page we checked has its own title.
Every page has an H1
Each page we checked has a main headline.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 9 pages that loaded have a <title>.
Best practices
4 small tap targets
4 of 10 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
No HTML doctype
The page has no <!DOCTYPE html>, so browsers render it in quirks mode.
2 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
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.
No social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
No analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
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.
Only about 47 words
The homepage has only about 47 words of visible text; thin pages give Google and first-time buyers little to go on.
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.
Privacy and tracking
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.
1 other company contacted
Loading the homepage contacts 1 host run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
No known trackers before consent
No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).
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 asambeauty.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Framework
- Nuxt
- Hosting
- AWS
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 18 issues on asambeauty.com, including 3 speed issues, 1 SEO issue and 6 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.