Website review, no card needed

zusss.de logo

zusss.de website review

Visit site (opens in a new tab)Reviewed 5 November 202638 issues · 84 checks

This review found 38 issues worth fixing on zusss.de, 16 of them high impact, across 84 checks. The most urgent: zusss.nl adds 1.2 s. 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
2.8 s2.1 sMay 16Oct 312.2 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20262.7 s
May 23, 20262.5 s
May 30, 20262.3 s
Jun 6, 20262.2 s
Jun 27, 20262.5 s
Jul 4, 20262.5 s
Jul 11, 20262.5 s
Jul 18, 20262.5 s
Jul 25, 20262.3 s
Aug 1, 20262.3 s
Aug 8, 20262.2 s
Aug 15, 20262.3 s
Aug 22, 20262.3 s
Sep 12, 20262.6 s
Sep 26, 20262.6 s
Oct 3, 20262.5 s
Oct 10, 20262.2 s
Oct 17, 20262.2 s
Oct 24, 20262.2 s
Oct 31, 20262.2 s
Real-visitor tap response (INP)75th percentile, phones
236 ms106 msMay 23Oct 31149 ms
Show as table
DateReal-visitor tap response (INP)
May 23, 2026121 ms
May 30, 2026127 ms
Jun 6, 2026148 ms
Jun 27, 2026221 ms
Jul 4, 2026202 ms
Jul 11, 2026178 ms
Jul 18, 2026191 ms
Jul 25, 2026180 ms
Aug 1, 2026190 ms
Aug 8, 2026191 ms
Aug 15, 2026189 ms
Aug 22, 2026153 ms
Sep 12, 2026173 ms
Sep 26, 2026173 ms
Oct 3, 2026159 ms
Oct 10, 2026145 ms
Oct 17, 2026145 ms
Oct 24, 2026154 ms
Oct 31, 2026149 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 zusss.de (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. zusss.de at 1.6 s1.6 s
  2. zusss.de at 3.1 s3.1 s
  3. zusss.de at 4.7 s4.7 s
  4. zusss.de at 6.2 s6.2 s
  5. zusss.de at 7.8 s7.8 s
  6. zusss.de at 9.4 s9.4 s
  7. zusss.de at 10.9 s10.9 s
  8. zusss.de at 12.5 s12.5 s

Speed

13 to fix34
  • zusss.nl adds 1.2 s

    1.2 s

    zusss.nl costs a phone 1.2 s of main-thread work and 2.0 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

  • Main-thread work: 12.1 s

    A phone's processor spends 12.1 s on main-thread work while loading, 6.7 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

  • Mobile performance score: 34

    34/100

    Your mobile performance score is 34. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

  • 6,841 HTML elements

    The page has 6,841 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 (zusss.nl, cloudfront.net and weglot.com and others), adding 4.2 MB and 3.6 s of main-thread time.

  • Reduce unused JavaScript

    150 ms · 811 KiB

    About 811 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.

  • Use efficient cache lifetimes

    779 KiB

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

  • cloudfront.net adds 570 ms

    570 ms

    cloudfront.net costs a phone 570 ms of main-thread work and 59 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

    450 ms

    5 files block the first paint until they finish downloading. Deferring or inlining them could save about 450 ms.

  • weglot.com adds 428 ms

    428 ms

    weglot.com costs a phone 428 ms of main-thread work and 156 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.

  • Google Tag Manager adds 401 ms

    401 ms

    Google Tag Manager costs a phone 401 ms of main-thread work and 362 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.

  • Clarity adds 398 ms

    398 ms

    Clarity costs a phone 398 ms of main-thread work and 30 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 395 ms. During a long task the page ignores taps.

  • Improve image delivery

    150 ms · 72 KiB

    4 images could be 72 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.

  • Legacy JavaScript

    61 KiB

    Polyfills for old browsers add 61 KiB JavaScript that modern phones do not need.

  • Font display

    50 ms

    Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).

  • Duplicated JavaScript

    35 KiB

    35 KiB JavaScript is shipped twice across bundles.

  • Reduce unused CSS

    15 KiB

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

  • 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: 19 ms

    19 ms

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

Core Web Vitals

6 to fix31
  • Speed Index: 18.8 s

    18.8 s

    Visually, the page fills in at 18.8 s (Speed Index). Good is under 3.4 s.

  • Time to Interactive: 34.7 s

    34.7 s

    The page becomes fully interactive after 34.7 s. Good is under 3.8 s.

  • Largest Contentful Paint: 8.9 s

    8.9 s

    Your largest element takes 8.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

  • Total Blocking Time: 1.1 s

    1.1 s

    Scripts block taps and scrolling for 1.1 s in total while the page loads. Good is under 200 ms.

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

    +22%

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

  • Cumulative Layout Shift: 0.171

    0.171

    The layout shifts by 0.171 while loading, so content jumps under the reader's thumb. Good is under 0.1.

  • Not enough real-visitor data yet

    Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

2 checks passed
  • Largest content (LCP) got 16% faster for real visitors

    -16%

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

  • First Contentful Paint: 1.4 s

    1.4 s

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

Images and page weight

1 to fix70
  • Page weight: 7.1 MB in 533 requests

    7.1 MB

    Your homepage downloads 7.1 MB in 533 requests on a phone: scripts 2.7 MB (120), other files 2.5 MB (316) and fonts 1,002 KiB (14). Under 2 MB keeps phones on slow connections fast.

  • 1 image below the first screen load straight away

    1 image further down the page (60 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

  • About 2.0 g of CO₂ per visit

    2.02 g

    By the Sustainable Web Design model, a visit to your homepage emits about 2.02 g of CO₂e: 242.2 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

5 to fixGoogle 9193
  • 9 tap targets too small

    9 tap targets are too small or too close together to hit reliably with a finger.

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

  • Summary elements must have discernible text (1 element)

    Summary elements must have discernible text: 1 element on the page fails this check, rated serious by axe-core.

  • 175 links without text

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

  • All page content should be contained by landmarks (15 elements)

    All page content should be contained by landmarks: 15 elements on the page fail this check, rated moderate by axe-core.

2 checks passed
  • Every image has alt text

    All 243 images in the HTML carry an alt attribute.

  • 52 automated accessibility rules passed

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

SEO

4 to fixGoogle 10076
  • No H1 headline

    There is no <h1>, so neither visitors nor Google get a clear main headline.

  • Title is long (86 characters)

    Your title is 86 characters, so Google will cut it off around 60: “ZUSSS.de |Offizieller Webshop | Kleidung, Geschenke und Wohnaccessoires kaufen – Zusss”.

  • No social preview image

    No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • No XML sitemap

    No XML sitemap at https://www.zusss.nl/sitemap.xml, so Google discovers your pages only by following links.

  • 934 internal links, 8 external

    The homepage links to 934 pages on zusss.de and 8 external pages.

4 checks passed
  • Meta description: 146 characters

    Your meta description is 146 characters: “Kaufen Sie Damenmode, Geschenke und Wohnaccessoires bei Zusss. Verschenken, nutzen, lieben. Jede Saison eine neue Kolle…”.

  • Canonical URL set

    The canonical URL is https://www.zusss.de/.

  • Structured data in place

    Structured data found: OnlineStore, WebPage and WebSite.

  • robots.txt in place

    robots.txt is in place and points crawlers to your sitemap.

AI search readiness

100
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: 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,861 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

    The site publishes https://www.zusss.de/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.

Other pages

100
  • 4 pages slow to respond

    https://www.zusss.de/collections/nieuw, https://www.zusss.de/collections/nieuw-kleding, https://www.zusss.de/collections/nieuw-jasjes and https://www.zusss.de/collections/nieuw-truien took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

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

  • Every page has a meta description

    All 15 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 15 pages that loaded have a <title>.

Best practices

3 to fixGoogle 9671
  • 1 broken image

    1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=56009651&tm=gtm002&Ver=2&mid=d7acd816-57db-4091-bfeb-c4a80c282d62&bo=1&sid=d383a040d8cd11f1b2afa7aa13c525dc&vid=d383e760d8cd11f191e8d18a810e3f65&vids=1&msclkid=N&pi=91.

  • 163 small tap targets

    163 of 276 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

  • 4 JavaScript errors while loading

    4 errors were logged to the browser console while the page loaded, for example “Uncaught TypeError: Cannot read properties of undefined (reading 'filter')”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

6 to fix50
  • 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.

  • Local business without LocalBusiness data

    Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

  • No phone number on the homepage

    A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

  • Thin social proof

    Social proof on the homepage: 1 trust badge. Pairing it with named testimonials or customer logos makes it far more convincing.

  • 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 opening hours

    The homepage shows no opening hours. If customers visit or call, show when.

  • No map or directions link

    There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

  • 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 377 words of copy

    The homepage carries about 377 words of visible text.

2 checks passed
  • 1 short form

    A short form (1 field at most) is right on the homepage.

  • Analytics in place

    Analytics detected: Google Tag Manager.

Privacy and tracking

  • 8 trackers load before any consent

    8

    Before a visitor clicks anything, the page loads Google Ads, Google Tag Manager, Klaviyo, Meta Pixel and Microsoft Ads and 3 mores (measured from a US location before any click). A consent tool (Cookiebot) is installed; check it blocks these until visitors agree where the law requires it.

  • 20 cookies set on arrival

    20

    Opening the homepage sets 20 cookies (measured from a US location before any click).

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

1 checks passed
  • Consent tool: Cookiebot

    A consent management tool (Cookiebot) loads with the page.

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

Weglot Translate Your Store · Eg Auto Add To Cart · Klaviyo Email Marketing Sms · Zepto Product Personalizer · Stape Remix · Wishlist Club · cloudfront.net · trustpilot.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
Google Tag Manager
Hosting
Enflow B.V.

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 38 issues on zusss.de, including 19 speed issues, 4 SEO issues 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

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