westfalen.com website review

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

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

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

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

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

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

21 KiB could be saved by minifying CSS.

9 KiB could be saved by minifying JavaScript.

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

1 third-party service load with your homepage (Cookiebot), adding 163 KiB and 65 ms of main-thread time.

1 file is served with short cache lifetimes, so returning visitors download them again (33 KiB).

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

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

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

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

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

3 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-31, real Chrome visitors' largest content (lcp) went from 1.6 s to 1.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 3.2 MB in 101 requests on a phone: images 1.9 MB (53), scripts 764 KiB (26) and fonts 317 KiB (6). Under 2 MB keeps phones on slow connections fast.

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

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

1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

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

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

Your title is 110 characters, so Google will cut it off around 60: “Westfalen-Gruppe: Experte für Gase, Wärme und Kälte sowie für zukunftsfähige Mobilität - …”.

Structured data found (BreadcrumbList, Organization and WebSite) but with 1 problem, for example “Organization: missing name”.

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

The homepage links to 258 pages on westfalen.com and 24 external pages.

Your Organization JSON-LD is missing name, sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

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

https://westfalen.com/de/de and / all use the title “Westfalen-Gruppe: Experte für Gase, Wärme und Kälte sowie für zukunft…”. Search engines can't tell which page to show for a search, so each competes with the others.

/ and https://westfalen.com/at/de use the same meta description. A description written for each page earns more clicks.

Your homepage links to 1 page by a URL that isn't its canonical one, for example /, whose canonical is https://westfalen.com/de/de. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

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

2 errors were logged to the browser console while the page loaded, for example “Connecting to 'https://analytics.google.com/g/collect?a=adblocker_check' violates the following Content Security Policy…”.

Chrome logged issues while loading the page (“Content security policy”).

Large scripts ship without source maps.

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

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

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,119 words of visible text.

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

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