Independent technical audit

wlw.de

Overall AI readiness score

A combined result across all audit signals.

Average

AI readiness audit: 10/19/2026Public technical data

About the site

wer liefert was (wlw) is a German B2B marketplace where suppliers list their products and services and buyers search for partners and send quote requests. The site covers more than 100 industries, including a packaging category, and combines a product catalogue, supplier profiles and a request portal.

Category:: Online stores
Platform:: Nuxt

Written by AI from the site’s llms.txt and homepage.

Overall AI readiness assessment

How ready wlw.de is for AI systems

44/100

llms.txt for wlw.de was independently audited by llmsmap. wlw.de currently scores 44/100 for AI readiness. The result combines AI-specific files, crawler policy, sitemap discovery, structured homepage data, and—when available—the mobile Google Lighthouse technical profile.

Audit context

llms.txt is accessible and contains 99 tokens. No accessible llms-full.txt was detected, so deeper context still has to be assembled from regular pages. No separate ai.txt policy was detected; it is optional, but can clarify training, retrieval, and attribution preferences.

robots.txt is available. 6 of 11 tracked AI bots are not blocked, while 5 receive a prohibition. Declared sitemaps: 0. No Schema.org type was detected on the homepage. 0 OpenGraph tags were found and markup completeness is 0%, leaving more entity interpretation to crawlers.

The mobile Lighthouse profile adds Performance 29/100, Accessibility 92/100, Best Practices 96/100, SEO 92/100, and experimental Agentic Browsing 48/100. These signals have a limited weight: they complement rather than replace llms.txt, robots.txt, and structured-data checks.

Confirmed strengths

Accessible llms.txt

Priority improvements

1Add llms-full.txt for richer first-party context.
2Review the 5 explicit AI-bot blocks and keep only intentional restrictions.
3Declare the current sitemap.xml in robots.txt.
4Add JSON-LD for the organisation, website, and core entities.

llms.txt tokens99

llms-full.txt tokens—

ai.txt

sitemap.xml

Google Lighthouse technical profile

A mobile Lighthouse measurement. Google’s experimental Agentic Browsing category is explained separately and does not replace the broader llmsmap AI-readiness score.

Mobile · Lighthouse

Performance

Accessibility

Best Practices

Technical SEO

Agentic Browsing

What these results mean

Mobile performance is 29/100, with the largest visible content block appearing in 36.9 s and the browser main thread blocked for 1,860 ms. Layout shift was 0. The main thread is where the browser runs JavaScript, calculates layout, and paints the page; long work there delays both user input and browser-agent actions.

Accessibility scored 92/100, Best Practices 96/100, and technical SEO 92/100. The experimental Agentic Browsing category scored 48/100. It measures signals Google currently tests for software agents and is shown separately from the llmsmap AI-readiness score.

Free the main thread and accelerate the first view

Split long JavaScript tasks, defer non-critical scripts and styles, and shorten blocking request chains. This helps the primary content appear sooner and makes controls usable earlier.

Reduce code that loads without helping the page

Remove unused CSS and JavaScript, load heavy widgets on demand, and limit third-party scripts. Less code means less parsing and background work on the device.

Optimise images and their loading order

Serve correctly sized modern formats, prioritise the primary visual, and lazy-load content below the first viewport.

Reduce network delay

Improve server response time, remove unnecessary redirects and repeat downloads, and use compression, caching, and selective preconnect hints.

FCP5.5 s

First content

LCP36.9 s

Main content

CLS0

Layout stability

TBT1,860 ms

Blocking time

SI9.7 s

Visual speed

Metric glossary

FCP · First content: When the first text or image appeared on screen.
LCP · Main content: When the largest visible element in the first viewport rendered.
CLS · Layout stability: How much content shifted unexpectedly while loading; lower is better.
TBT · Blocking time: How long the browser main thread could not respond quickly to input.
SI · Visual speed: How quickly the visible viewport filled with content.

10/19/2026Lighthouse 13.5.0Mobile profile

AI readiness checks

Machine-readable files, crawler policy, discovery, and homepage markup.

llms.txt

File found and accessible

https://www.wlw.de/llms.txt

llms-full.txt

Full version was not found

ai.txt

ai.txt file was not found

robots.txt

File found

https://wlw.de/robots.txt

Sitemap in robots.txt

Sitemap is not declared in robots.txt

Schema.org (JSON-LD)

Schema.org markup was not found on the homepage

OpenGraph

OpenGraph tags were not found on the homepage

AI bot access

Based on robots.txt analysis

GPTBotAllowed

OAI-SearchBotAllowed

ChatGPT-UserAllowed

Google-ExtendedAllowed

ClaudeBotBlocked

Claude-SearchBotBlocked

Claude-UserBlocked

BytespiderBlocked

CCBotBlocked

PerplexityBotAllowed

Perplexity-UserAllowed

# llms.txt for wlw.de
# This file directs Large Language Models to the primary content source for the "Verpackung" (Packaging) category.
# Following best practices, we specify the parent directory to include all current and future sub-pages.

User-agent: *

# Allow crawling of the entire packaging category and all its sub-pages.
Allow: /de/showroom/verpackung
Allow: /de/showroom/verpackung/*

Share or continue the analysis

Share this audit