Website review, no card needed

wilulu.de logo

wilulu.de website review

Visit site (opens in a new tab)Reviewed 20 November 202646 issues · 87 checks

This review found 46 issues worth fixing on wilulu.de, 22 of them high impact, across 87 checks. The most urgent: improve image delivery. 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.1 s850 msMay 30Nov 141.0 s
Show as table
DateReal-visitor load time (LCP)
May 30, 2026966 ms
Jun 6, 2026979 ms
Jun 13, 2026976 ms
Jun 20, 2026949 ms
Jun 27, 2026938 ms
Jul 4, 2026919 ms
Jul 11, 2026918 ms
Jul 18, 2026952 ms
Jul 25, 2026934 ms
Aug 1, 2026937 ms
Aug 15, 2026888 ms
Aug 22, 2026894 ms
Aug 29, 2026902 ms
Sep 5, 2026990 ms
Sep 12, 2026982 ms
Sep 19, 2026957 ms
Sep 26, 2026935 ms
Oct 3, 2026874 ms
Oct 10, 2026891 ms
Oct 17, 2026949 ms
Oct 24, 2026970 ms
Oct 31, 2026995 ms
Nov 7, 20261.0 s
Nov 14, 20261.0 s
Real-visitor tap response (INP)75th percentile, phones
122 ms87 msMay 30Nov 14108 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 202696 ms
Jun 6, 2026102 ms
Jun 20, 2026118 ms
Jun 27, 2026116 ms
Jul 4, 2026114 ms
Jul 11, 2026109 ms
Jul 18, 2026108 ms
Aug 15, 202694 ms
Aug 22, 202693 ms
Aug 29, 202691 ms
Sep 5, 2026103 ms
Sep 12, 2026105 ms
Sep 19, 2026109 ms
Sep 26, 2026107 ms
Oct 3, 2026100 ms
Oct 10, 202696 ms
Oct 17, 2026102 ms
Oct 24, 2026104 ms
Oct 31, 2026107 ms
Nov 7, 2026106 ms
Nov 14, 2026108 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 wilulu.de (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. wilulu.de at 0.4 s0.4 s
  2. wilulu.de at 0.9 s0.9 s
  3. wilulu.de at 1.3 s1.3 s
  4. wilulu.de at 1.8 s1.8 s
  5. wilulu.de at 2.2 s2.2 s
  6. wilulu.de at 2.7 s2.7 s
  7. wilulu.de at 3.1 s3.1 s
  8. wilulu.de at 3.6 s3.6 s

Speed

12 to fix43
  • Improve image delivery

    10.2 s · 4.1 MB

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

  • Render-blocking requests

    1.1 s

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

  • Mobile performance score: 43

    43/100

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

  • 5,382 HTML elements

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

  • Main-thread work: 5.4 s

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

  • 5 third-party services on the page

    5 third-party services load with your homepage (Clerk.io ApS, PayPal and Doofinder and others), adding 614 KiB and 794 ms of main-thread time.

  • Use efficient cache lifetimes

    250 ms · 508 KiB

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

  • Reduce unused CSS

    460 ms · 128 KiB

    About 128 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 460 ms faster on a phone.

  • Reduce unused JavaScript

    160 ms · 345 KiB

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

  • Clerk.io ApS adds 396 ms

    396 ms

    Clerk.io ApS costs a phone 396 ms of main-thread work and 191 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.

  • PayPal adds 330 ms

    330 ms

    PayPal costs a phone 330 ms of main-thread work and 275 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.

  • 15 long tasks on the main thread

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

  • Legacy JavaScript

    38 KiB

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

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

    157 ms

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

Core Web Vitals

6 to fix100
  • Largest Contentful Paint: 28.4 s

    28.4 s

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

  • Time to Interactive: 37.9 s

    37.9 s

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

  • Total Blocking Time: 826 ms

    826 ms

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

  • Speed Index: 5.9 s

    5.9 s

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

  • Cumulative Layout Shift: 0.145

    0.145

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

  • First Contentful Paint: 1.8 s

    1.8 s

    The first text or image appears after 1.8 s on a phone. Good is under 1.8 s.

  • Tap response (INP) held steady for real visitors

    +8%

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

  • Largest content (LCP) held steady for real visitors

    +5%

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

6 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.0 s

    1.0 s

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

  • Real-user INP: 105 ms

    105 ms

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

  • Real-user CLS: 0.04

    0.04

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

  • Real-user FCP: 0.8 s

    0.8 s

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

  • Real-user TTFB: 487 ms

    487 ms

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

Images and page weight

6 to fix19
  • Page weight: 11.9 MB in 131 requests

    11.9 MB

    Your homepage downloads 11.9 MB in 131 requests on a phone: images 10.8 MB (65), scripts 784 KiB (51) and stylesheets 148 KiB (4). Under 2 MB keeps phones on slow connections fast.

  • 2 images over 500 KB

    2 images weigh 1.2 MB together. On a phone connection a single image that size takes seconds.

  • 13 images far larger than shown

    921 KiB

    13 images are downloaded at several times the size a phone draws them, for example kiddo-mega-booster-pads_4213.png at 1,000 px wide, shown at 282 px. Resized copies would save about 921 KiB.

  • 40 images in older formats

    40 images (5.9 MB) 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.

  • 13 images below the first screen load straight away

    13 images further down the page (2.2 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • An image on the first screen is lazy-loaded

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

  • About 3.4 g of CO₂ per visit

    3.37 g

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

Accessibility

11 to fixGoogle 6484
  • 8 buttons without a name

    8 buttons have no accessible name, so screen readers announce just “button”.

  • Invalid ARIA attributes

    2 elements use ARIA attributes their role does not allow, which confuses screen readers.

  • Certain ARIA roles must contain particular children (1 element)

    Certain ARIA roles must contain particular children: 1 element on the page fails this check, rated critical by axe-core.

  • 20 text elements with low contrast

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

  • Links look like plain text

    16 links inside paragraphs rely on colour alone to stand out.

  • Hidden but focusable

    8 elements hidden from screen readers can still receive keyboard focus.

  • Elements must only use permitted ARIA attributes (4 elements)

    Elements must only use permitted ARIA attributes: 4 elements on the page fail this check, rated serious by axe-core.

  • 7 images without alt text

    7 images have no alt text, which hurts accessibility and image search.

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

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

  • 3 links without text

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

  • 2 form fields without a label

    2 form fields have no label, so screen readers announce an empty box and autofill guesses.

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

    Elements with visible text labels do not have matching accessible names. (1 element).

1 checks passed
  • 48 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 58 WCAG 2.2 A/AA and best-practice rules on the phone render: 48 passed and 10 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 8390
  • No structured data

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

  • No robots.txt

    There is no robots.txt at wilulu.de/robots.txt, the first file search crawlers ask for.

  • 1 link crawlers can't follow

    1 link has no real href, so search engines can't follow it.

  • 189 internal links, 1 external

    The homepage links to 189 pages on wilulu.de and 1 external page.

6 checks passed
  • Meta description: 135 characters

    Your meta description is 135 characters: “Wenn du Windeln liebst bist du bei wilulu genau richtig. Bei uns findest du eine große Auswahl an tollen Windeln für fa…”.

  • One H1 headline

    Your main headline reads: “wilulu - Der Windelshop für Adult Babys und Windelliebhaber”.

  • Title: 55 characters

    Your title is a healthy 55 characters: “Windeln für Windelliebhaber und Adult Babys | wilulu.de”.

  • Canonical URL set

    The canonical URL is https://wilulu.de/.

  • Open Graph tags complete

    Open Graph tags are complete, so shared links show a title, description and image.

  • XML sitemap found

    Your XML sitemap is reachable at https://wilulu.de/sitemap.xml.

AI search readiness

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

  • Some text only appears after JavaScript runs

    53%

    The HTML your server sends has 5,984 of the 11,333 words a browser shows. AI crawlers don't run JavaScript, so they miss the rest.

  • No llms.txt

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

1 checks passed
  • AI answer engines may read the site

    There is no robots.txt, so nothing stops the crawlers behind ChatGPT search, Claude and Perplexity from reading the site and cite it in answers.

Other pages

2 to fix90
  • 3 pages without a meta description

    https://wilulu.de/wishlist, https://wilulu.de/revocation and https://wilulu.de/wilulu-Blog have no meta description, so Google writes the search snippet from whatever text it finds.

  • 8 pages without an H1

    https://wilulu.de/Windeln-fuer-AB-DL, https://wilulu.de/wishlist, https://wilulu.de/Hilfreich-fuer-Windeltraeger, https://wilulu.de/Bodys-und-mehr, https://wilulu.de/wilulu-Blog and https://wilulu.de/Windeln-fuer-AB-DL/fuer-den-Windelpopo and 2 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 15 internal pages checked

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

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

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

Best practices

1 to fixGoogle 10093
  • 3 JavaScript errors while loading

    3 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://cdn.doofinder.com/livelayer/1.8.213/css/2/mobile.css?v=1.8.213' from origin 'https…”.

2 checks passed
  • Tap targets are thumb-sized

    143 of 144 tappable elements near the top are at least 24 px.

  • 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 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 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 11,333 words of copy

    The homepage carries about 11,333 words of visible text.

3 checks passed
  • 51 short forms

    51 short forms (7 fields at most) are right on the homepage.

  • Social proof on the page

    Social proof on the homepage: 24 testimonial or review blocks and 3 customer or partner logos.

  • Direct contact links

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

Privacy and tracking

  • 2 cookies set on arrival

    2

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

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

Upkeep, stack and company

Stack

Framework
Tailwind CSS
Hosting
Hetzner

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 46 issues on wilulu.de, including 18 speed issues, 3 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