Website review, no card needed

sandsberg.de logo

sandsberg.de website review

Visit site (opens in a new tab)Reviewed 10 November 202613 issues · 67 checks

This review found 13 issues worth fixing on sandsberg.de, 3 of them high impact, across 67 checks. The most urgent: no call to action on the first screen. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
1.4 s508 msMay 23Nov 7614 ms
Show as table
DateReal-visitor load time (LCP)
May 23, 2026857 ms
May 30, 2026939 ms
Jun 6, 20261.1 s
Jun 13, 20261.3 s
Jun 20, 20261.3 s
Jun 27, 2026939 ms
Jul 4, 2026786 ms
Jul 11, 2026765 ms
Jul 18, 2026760 ms
Jul 25, 2026762 ms
Aug 1, 2026766 ms
Aug 8, 2026768 ms
Aug 15, 2026768 ms
Aug 22, 2026774 ms
Aug 29, 2026775 ms
Sep 5, 2026775 ms
Sep 12, 2026776 ms
Sep 19, 2026759 ms
Sep 26, 2026734 ms
Oct 3, 2026704 ms
Oct 10, 2026669 ms
Oct 17, 2026654 ms
Oct 24, 2026644 ms
Oct 31, 2026629 ms
Nov 7, 2026614 ms
Real-visitor tap response (INP)75th percentile, phones
120 ms83 msMay 23Nov 7113 ms
Show as table
DateReal-visitor tap response (INP)
May 23, 202698 ms
May 30, 202696 ms
Jun 6, 202695 ms
Jun 13, 202690 ms
Jun 20, 202687 ms
Jun 27, 2026104 ms
Jul 4, 2026109 ms
Jul 11, 2026109 ms
Jul 18, 2026108 ms
Jul 25, 2026106 ms
Aug 1, 2026104 ms
Aug 8, 2026103 ms
Aug 15, 2026104 ms
Aug 22, 2026104 ms
Aug 29, 2026105 ms
Sep 5, 2026110 ms
Sep 12, 2026112 ms
Sep 19, 2026114 ms
Sep 26, 2026116 ms
Oct 3, 2026115 ms
Oct 10, 2026114 ms
Oct 17, 2026113 ms
Oct 24, 2026113 ms
Oct 31, 2026113 ms
Nov 7, 2026113 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

Full-page screenshot of sandsberg.de (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. sandsberg.de at 0.4 s0.4 s
  2. sandsberg.de at 0.8 s0.8 s
  3. sandsberg.de at 1.1 s1.1 s
  4. sandsberg.de at 1.5 s1.5 s
  5. sandsberg.de at 1.9 s1.9 s
  6. sandsberg.de at 2.3 s2.3 s
  7. sandsberg.de at 2.6 s2.6 s
  8. sandsberg.de at 3.0 s3.0 s

Speed

100
  • Improve image delivery

    129 KiB

    3 images could be 129 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Reduce unused CSS

    41 KiB

    About 41 KiB of CSS is downloaded but never applied on this page.

  • 3 third-party services on the page

    3 third-party services load with your homepage (myshopify.com, Shopify and Klaviyo), adding 204 KiB and 2 ms of main-thread time.

  • Use efficient cache lifetimes

    8 KiB

    3 files are served with short cache lifetimes, so returning visitors download them again (8 KiB).

  • 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.

3 checks passed
  • Mobile performance score: 100

    100/100

    Your mobile performance score is 100. That is in Google's “good” band (90 and up).

  • Main-thread work: 0.2 s

    A phone's processor spends 0.2 s on main-thread work while loading, 26 ms of it running JavaScript. That is comfortably low.

  • Server response: 6 ms

    6 ms

    Your server sent the HTML in 6 ms, well inside Google's 600 ms guideline.

Core Web Vitals

100
  • Tap response (INP) got 16% slower for real visitors

    +16%

    Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 98 ms to 113 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

13 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: 0.6 s

    0.6 s

    Real visitors wait 0.6 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Real-user INP: 96 ms

    96 ms

    Real visitors wait 96 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Real-user CLS: 0.00

    0.00

    For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.

  • Real-user FCP: 0.6 s

    0.6 s

    Real visitors see the first content after 0.6 s (75th percentile). Good is under 1.8 s.

  • Real-user TTFB: 518 ms

    518 ms

    Real visitors wait 518 ms for your server to start answering (75th percentile). Good is under 800 ms.

  • Largest content (LCP) got 31% faster for real visitors

    -31%

    Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 0.9 s to 0.6 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Cumulative Layout Shift: 0

    0

    The layout barely moves while loading (CLS 0, good is under 0.1).

  • First Contentful Paint: 1.1 s

    1.1 s

    The first text or image appears after 1.1 s, inside the 1.8 s “good” threshold.

  • Largest Contentful Paint: 1.1 s

    1.1 s

    Your largest element renders in 1.1 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the text “Γ”.

  • Speed Index: 1.3 s

    1.3 s

    Visually, the page fills in at 1.3 s (Speed Index), inside the 3.4 s “good” threshold.

  • Total Blocking Time: 0 ms

    0 ms

    Scripts block the page for only 0 ms while loading. Good is under 200 ms.

  • Time to Interactive: 1.1 s

    1.1 s

    The page is fully interactive after 1.1 s.

Images and page weight

1 to fix97
  • An image on the first screen is lazy-loaded

    Bowlift_Black_Friday_DE_Mobile_Banner.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).

  • 2 images in older formats

    2 images (149 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 0.3 g of CO₂ per visit

    0.29 g

    By the Sustainable Web Design model, a visit to your homepage emits about 0.29 g of CO₂e: 34.3 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: 1.0 MB in 39 requests

    1.0 MB

    Your homepage downloads 1.0 MB in 39 requests on a phone: images 532 KiB (15), scripts 313 KiB (13) and stylesheets 67 KiB (7). That is a lean page.

  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

2 to fixGoogle 9698
  • 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.

  • 5 links without text

    5 visible links have no text or label, so screen readers cannot say where they go.

2 checks passed
  • Every image has alt text

    All 27 images in the HTML carry an alt attribute.

  • 44 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 46 WCAG 2.2 A/AA and best-practice rules on the phone render: 44 passed and 2 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

3 to fixGoogle 10084
  • Title is short (5 characters)

    Your title is only 5 characters: “Karnz”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • No structured data

    No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

  • Meta description is short (36 characters)

    Your meta description is only 36 characters: “TRENDIG, ERSCHWINGLICH & EINZIGARTIG”. 70 to 160 characters is enough to sell the click.

  • 91 internal links, 4 external

    The homepage links to 91 pages on sandsberg.de and 4 external pages.

5 checks passed
  • One H1 headline

    Your main headline reads: “Karnz”.

  • Canonical URL set

    The canonical URL is https://karnz.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://karnz.de/sitemap.xml.

AI search readiness

1 to fix88
  • No Organization structured data

    There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

  • No llms.txt

    There is no https://karnz.de/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.

  • Text is in the HTML

    Your server sends the page's text in the HTML (421 words), so crawlers that don't run JavaScript still read it.

Other pages

1 to fix95
  • 8 pages without a meta description

    https://karnz.de/collections/wohnaccessoires, https://karnz.de/collections/organisation, https://karnz.de/collections/kuche-1, https://karnz.de/collections/schlafzimmer, https://karnz.de/collections/badezimmer-3 and https://karnz.de/collections/ornament and 2 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 42 found) and read each the way a search engine does.

6 checks passed
  • Linked pages load

    8 pages of 15 loaded without an error (the rest turned automated requests away).

  • 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.

  • 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 8 pages that loaded have a <title>.

Best practices

Google 100100
3 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Tap targets are thumb-sized

    11 of 12 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix42
  • 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 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 265 words of copy

    The homepage carries about 265 words of visible text.

2 checks passed
  • 2 short forms

    2 short forms (1 field at most) are right on the homepage.

  • Direct contact links

    Visitors can reach you directly: 1 phone link and 1 email link.

Privacy and tracking

1 to fix
  • 1 tracker load before any consent

    1

    Before a visitor clicks anything, the page loads 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

    6

    Opening 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.

  • 3 other companies contacted

    Loading the homepage contacts 3 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 sandsberg.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 5 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Simprosys Google Shopping Feed · Klaviyo Email Marketing Sms · Corner · Upcart · wetracked.io

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

E-commerce
Shopify
Hosting
Shopify

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 13 issues on sandsberg.de, including 3 SEO issues and 4 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

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25