lwl.org website review

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

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

Your mobile performance score is 67 (desktop: 81). Pages that score under 90 lose visitors before the first paint.

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

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

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

2 images could be 438 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

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

1 third-party service load with your homepage (ReadSpeaker), adding 69 KiB and 13 ms of main-thread time.

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

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

Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.

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

Your largest element takes 4.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Karte Westfalen-Lippes mit Story-Orten”.

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

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

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

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

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

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

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

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

Your homepage downloads 118.7 MB in 44 requests on a phone: media 117.2 MB (14), images 730 KiB (8) and scripts 361 KiB (7). Under 2 MB keeps phones on slow connections fast.

5 images further down the page (455 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

5 images (455 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.

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

ARIA dialog and alertdialog nodes should have an accessible name: 6 elements on the page fail this check, rated serious by axe-core.

Some lists contain elements other than list items, which screen readers announce wrongly.

1 tap target is too small or too close together to hit reliably with a finger.

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

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

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

ARIA role should be appropriate for the element: 14 elements on the page fail this check, rated minor by axe-core.

Elements use prohibited ARIA attributes (4 elements).

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

1 form field has no label, so screen readers announce an empty box and autofill guesses.

Elements marked as presentational should be consistently ignored: 1 element on the page fails this check, rated minor by axe-core.

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

No meta description, so Google writes its own snippet from whatever text it finds.

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

No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

No Open Graph image (also missing: og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

9 links have no real href, so search engines can't follow them.

The homepage links to 79 pages on lwl.org and 62 external pages.

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.

There is no https://www2.lwl.org/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.

Your homepage links to /, which answers with an error. Visitors hit a dead end and search engines drop it.

https://www2.lwl.org/de/LWL/portal/lwl-storys/2026/elternassistenz is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

https://www2.lwl.org/de/LWL/portal/lwl-storys/2026/goldledertapeten, https://www2.lwl.org/de/LWL/portal/lwl-storys/2026/waldtherapie, https://www2.lwl.org/de/LWL/portal/lwl-storys/2026/elternassistenz, https://www2.lwl.org/de/LWL/portal/lwl-storys/2025/intensiv-ambulant-betreutes-wohnen, https://www2.lwl.org/de/LWL/portal/lwl-storys/2025/Gastfamilien and https://www2.lwl.org/de/LWL/portal/lwl-storys/2025/einsamkeit and 6 others have no meta description, so Google writes the search snippet from whatever text it finds.

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

On a 390 px-wide phone the page scrolls sideways, a sign that something is wider than the screen.

2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_TUNNEL_CONNECTION_FAILED”.

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

The homepage carries about 1,783 words of visible text.

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

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.

Loading the homepage contacts 1 host run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.