Website review, no card needed

black-white-grey.de logo

black-white-grey.de website review

Visit site (opens in a new tab)Reviewed 9 November 202623 issues · 78 checks

This review found 23 issues worth fixing on black-white-grey.de, 5 of them high impact, across 78 checks. The most urgent: 7 text elements with low contrast. 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.8 s1.5 sMay 23Sep 261.5 s
Show as table
DateReal-visitor load time (LCP)
May 23, 20261.5 s
May 30, 20261.6 s
Jun 6, 20261.7 s
Jun 13, 20261.6 s
Jun 20, 20261.6 s
Jun 27, 20261.6 s
Jul 4, 20261.6 s
Jul 11, 20261.8 s
Jul 18, 20261.7 s
Jul 25, 20261.8 s
Sep 26, 20261.5 s
Real-visitor tap response (INP)75th percentile, phones
103 ms77 msMay 23Sep 26100 ms
Show as table
DateReal-visitor tap response (INP)
May 23, 202681 ms
May 30, 202680 ms
Jun 6, 202689 ms
Jun 13, 202691 ms
Jun 20, 202690 ms
Jun 27, 202690 ms
Jul 4, 202689 ms
Jul 11, 202690 ms
Sep 26, 2026100 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 black-white-grey.de (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. black-white-grey.de at 0.6 s0.6 s
  2. black-white-grey.de at 1.3 s1.3 s
  3. black-white-grey.de at 1.9 s1.9 s
  4. black-white-grey.de at 2.6 s2.6 s
  5. black-white-grey.de at 3.2 s3.2 s
  6. black-white-grey.de at 3.9 s3.9 s
  7. black-white-grey.de at 4.5 s4.5 s
  8. black-white-grey.de at 5.1 s5.1 s

Speed

4 to fix80
  • Mobile performance score: 80

    80/100

    Your mobile performance score is 80. Pages that score under 90 lose visitors before the first paint.

  • Render-blocking requests

    800 ms

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

  • Improve image delivery

    350 ms · 292 KiB

    22 images could be 292 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 350 ms faster on a phone.

  • 1,573 HTML elements

    The page has 1,573 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

  • Reduce unused CSS

    150 ms · 33 KiB

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

  • Reduce unused JavaScript

    150 ms · 28 KiB

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

  • 2 third-party services on the page

    2 third-party services load with your homepage (Shopify and nfcube.com), adding 109 KiB and 143 ms of main-thread time.

  • Legacy JavaScript

    100 ms · 7 KiB

    Polyfills for old browsers add 7 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 100 ms faster on a phone.

  • 2 long tasks on the main thread

    2 long tasks block the main thread while loading, the longest for 62 ms. During a long task the page ignores taps.

  • Font display

    50 ms

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

  • Use efficient cache lifetimes

    5 KiB

    3 files are served with short cache lifetimes, so returning visitors download them again (5 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.

  • Forced reflow

    Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

2 checks passed
  • Main-thread work: 1.7 s

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

  • Server response: 27 ms

    27 ms

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

Core Web Vitals

4 to fix77
  • Largest Contentful Paint: 4.8 s

    4.8 s

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

  • Speed Index: 4.4 s

    4.4 s

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

  • Time to Interactive: 4.8 s

    4.8 s

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

  • 8 images without width and height

    8 images have no width and height attributes, so the layout jumps as each one loads.

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

    +18%

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

  • Largest content (LCP) held steady for real visitors

    +6%

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

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

3 checks passed
  • 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.

  • Cumulative Layout Shift: 0.001

    0.001

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

  • Total Blocking Time: 16 ms

    16 ms

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

Images and page weight

1 to fix85
  • Page weight: 2.4 MB in 202 requests

    2.4 MB

    Your homepage downloads 2.4 MB in 202 requests on a phone: images 1.3 MB (89), other files 664 KiB (67) and scripts 273 KiB (34). Under 2 MB keeps phones on slow connections fast.

  • About 0.7 g of CO₂ per visit

    0.67 g

    By the Sustainable Web Design model, a visit to your homepage emits about 0.67 g of CO₂e: 80.7 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

3 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

  • 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 8893
  • 7 text elements with low contrast

    7 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

  • [role="img"] and [role="image"] elements must have alternative text (4 elements)

    [role="img"] and [role="image"] elements must have alternative text: 4 elements on the page fail this check, rated serious by axe-core.

  • Hidden but focusable

    1 element hidden from screen readers can still receive keyboard focus.

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

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

  • 8 links without text

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

  • Headings skip levels

    Headings skip levels (h1 → h6 and h2 → h6), which makes the page harder to scan with a screen reader.

  • Elements with visible text labels do not have matching accessible names.

    Elements with visible text labels do not have matching accessible names. (2 elements).

2 checks passed
  • Every image has alt text

    All 50 images in the HTML carry an alt attribute.

  • 48 automated accessibility rules passed

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

SEO

1 to fixGoogle 10095
  • 13 H1 headlines

    There are 13 <h1> headlines (“ELISA KLINKENBERG X BLACKWHITEGREY”, “ELISA KLINKENBERG X BLACKWHITEGREY” and “ELISA KLINKENBERG X BLACKWHITEGREY”). One clear main headline is easier for people and search engines.

  • 112 internal links, 14 external

    The homepage links to 112 pages on black-white-grey.de and 14 external pages.

7 checks passed
  • Meta description: 98 characters

    Your meta description is 98 characters: “Bekleidung, Accessoires und Deko-Artikel mit Feel-Good-Garantie ☆ Fair und nachhaltig produziert ☆”.

  • Title: 43 characters

    Your title is a healthy 43 characters: “BlackWhiteGrey Shop – Black White Grey Shop”.

  • Canonical URL set

    The canonical URL is https://black-white-grey.de/.

  • Structured data in place

    Structured data found: 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://black-white-grey.de/sitemap.xml.

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

  • llms.txt published

    The site publishes https://black-white-grey.de/llms.txt (5 KiB, 8 links), a plain-text guide to the site for AI tools.

Other pages

3 to fix88
  • 3 pages without a meta description

    https://black-white-grey.de/collections/frauen, https://black-white-grey.de/collections/accessoire and https://black-white-grey.de/collections/home have no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 pages share a meta description

    https://black-white-grey.de/products/elisa-klinkenberg-x-blackwhitegrey-master-peace-longsleeve and https://black-white-grey.de/products/elisa-klinkenberg-x-blackwhitegrey-master-peace-hoodie use the same meta description. A description written for each page earns more clicks.

  • 1 page without an H1

    https://black-white-grey.de/collections has no <h1> headline, so visitors and search engines get no clear main topic.

  • 1 page with very little text

    https://black-white-grey.de/collections has under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

  • 15 internal pages checked

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

5 checks passed
  • Linked pages load

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

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 11 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

    75 of 77 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix58
  • 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.

  • Thin social proof

    Social proof on the homepage: 8 customer or partner logos. Pairing it with named testimonials or customer logos makes it far more convincing.

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

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

    The homepage carries about 627 words of visible text.

  • Urgency cues

    The page uses urgency cues (a countdown or limited-time wording).

2 checks passed
  • 1 call to action

    The homepage has 1 call to action, for example “Black White Grey Shop”.

  • 6 short forms

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

Privacy and tracking

1 to fix
  • 1 tracker load before any consent

    1

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

  • 7 cookies set on arrival

    7

    Opening the homepage sets 7 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.

  • 6 other companies contacted

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

Apps your storefront loads

Eu Warranty Label · Eu Widerruf Button · nfcube.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

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 23 issues on black-white-grey.de, including 8 speed issues, 1 SEO issue 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