Website review, no card needed

diebine.de logo

diebine.de website review

Visit site (opens in a new tab)Reviewed 20 November 202627 issues · 65 checks

This review found 27 issues worth fixing on diebine.de, 8 of them high impact, across 65 checks. The most urgent: use efficient cache lifetimes. 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

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

How it loaded on a phone

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

Speed

6 to fix76
  • Use efficient cache lifetimes

    3.8 s · 2.7 MB

    11 files are served with short cache lifetimes, so returning visitors download them again (2.7 MB).

  • Improve image delivery

    2.5 s · 2.2 MB

    7 images could be 2.2 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 2.5 s faster on a phone.

  • Render-blocking requests

    1.4 s

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

  • Mobile performance score: 76

    76/100

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

  • Font display

    700 ms

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

  • Reduce unused JavaScript

    450 ms · 65 KiB

    About 65 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 450 ms faster on a phone.

  • Reduce unused CSS

    150 ms · 27 KiB

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

  • Document request latency

    43 KiB

    The HTML itself could arrive sooner: redirects, a slow server response or missing compression delay everything after it.

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

  • Minify JavaScript

    3 KiB

    3 KiB could be saved by minifying JavaScript.

2 checks passed
  • Main-thread work: 0.3 s

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

  • Server response: 129 ms

    129 ms

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

Core Web Vitals

4 to fix72
  • Largest Contentful Paint: 5.4 s

    5.4 s

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

  • Time to Interactive: 5.4 s

    5.4 s

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

  • Speed Index: 3.7 s

    3.7 s

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

  • 6 images without width and height

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

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

    1.8 s

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

  • Cumulative Layout Shift: 0.081

    0.081

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

  • Total Blocking Time: 0 ms

    0 ms

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

Images and page weight

4 to fix58
  • Page weight: 2.8 MB in 17 requests

    2.8 MB

    Your homepage downloads 2.8 MB in 17 requests on a phone: images 2.5 MB (7), scripts 137 KiB (3) and fonts 86 KiB (2). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    G76I5128-scaled.jpg 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 (558 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.

  • 2 images far larger than shown

    309 KiB

    2 images are downloaded at several times the size a phone draws them, for example G76I4974-scaled.jpg at 1,620 px wide, shown at 320 px. Resized copies would save about 309 KiB.

  • About 0.8 g of CO₂ per visit

    0.80 g

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

Accessibility

3 to fixGoogle 9395
  • 8 text elements with low contrast

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

  • 5 tap targets too small

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

  • All page content should be contained by landmarks (1 element)

    All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

2 checks passed
  • Every image has alt text

    All 19 images in the HTML carry an alt attribute.

  • 43 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: 43 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

4 to fixGoogle 10079
  • Title is long (74 characters)

    Your title is 74 characters, so Google will cut it off around 60: “dieBine.de - Maschinenstickerei | Wir machen ihr Kleidungstück einzigartig”.

  • No structured data

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

  • 2 H1 headlines

    There are 2 <h1> headlines (“Home” and “Wir machen Ihr Kleidungsstück einzigartig.”). One clear main headline is easier for people and search engines.

  • Meta description is long (329 characters)

    Your meta description is 329 characters; Google truncates after about 160, so the end of your pitch is cut.

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

  • 36 internal links, 5 external

    The homepage links to 36 pages on diebine.de and 5 external pages.

4 checks passed
  • Canonical URL set

    The canonical URL is https://diebine.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.

  • XML sitemap found

    Your XML sitemap is reachable at https://diebine.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.

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

  • llms.txt published

    The site publishes https://diebine.de/llms.txt (1 KiB, 0 links, though it should open with a “# Title” line), a plain-text guide to the site for AI tools.

Other pages

100
  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 22 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

2 to fixGoogle 9687
  • 14 small tap targets

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

  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “wp is not defined”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

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

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

    The homepage carries about 325 words of visible text.

3 checks passed
  • 3 calls to action

    The homepage has 3 calls to action, for example “Shop” and “Zum Shop”.

  • 1 short form

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

  • Direct contact links

    Visitors can reach you directly: 3 phone links and 0 email links.

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 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 diebine.de, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

CMS
WordPress
Framework
jQuery
Hosting
Strato GmbH

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 27 issues on diebine.de, including 10 speed issues, 4 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

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