reflex-winkelmann.com website review

About 212 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.1 s faster on a phone.

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

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

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

Reduce initial server response time. Google estimates savings of 804 ms on a phone.

6 third-party services load with your homepage (Google Tag Manager, Hotjar and Cookiebot and others), adding 3.4 MB and 198 ms of main-thread time.

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

reflex.de costs a phone 0 ms of main-thread work and 2.6 MB 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.

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

Your server takes 904 ms to send the HTML. Google recommends under 600 ms; everything else waits for it.

storyblok.com costs a phone 0 ms of main-thread work and 484 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.

About 179 KiB of CSS is downloaded but never applied on this page.

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

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

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

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

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.

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

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

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

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

Your largest element takes 14.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Minimalist room with a green glowing Storatherm Aqua+Heat h…”.

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

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

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

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

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

17 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' tap response (inp) went from 141 ms to 139 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

Your homepage downloads 4.9 MB in 159 requests on a phone: other files 2.7 MB (53), HTML 1.2 MB (3) and scripts 591 KiB (52). Under 2 MB keeps phones on slow connections fast.

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

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

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

5 text elements don'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 images have no alt text, which hurts accessibility and image search.

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.

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

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

Alternative text of images should not be repeated as text: 3 elements on the page fail this check, rated minor by axe-core.

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

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

Your meta description is only 66 characters: “Products and holistic solutions for building and supply technology”. 70 to 160 characters is enough to sell the click.

Your hreflang tags are invalid, so Google may show the wrong language version.

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

No XML sitemap at https://reflex-winkelmann.com/sitemap.xml, so Google discovers your pages only by following links.

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

The homepage links to 83 pages on reflex-winkelmann.com and 41 external pages.

Your Organization JSON-LD is missing 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://reflex-winkelmann.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.

Your homepage links to https://reflex-winkelmann.com/en/solutions-and-references/product-solutions, https://reflex-winkelmann.com/en/solutions-and-references/product-solutions/separation-technology, https://reflex-winkelmann.com/en/solutions-and-references/product-solutions/pressure-maintenance-technology and https://reflex-winkelmann.com/en/solutions-and-references/product-solutions/freshwater-stations, which answer with an error. Visitors hit a dead end and search engines drop them.

https://reflex-winkelmann.com/en/solutions-and-references/project-solutions, https://reflex-winkelmann.com/en/solutions-and-references/reference-sites and https://reflex-winkelmann.com/en/solutions-and-references/holistic-solutions took over 3 s to send their HTML from our server.

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

Large scripts ship without source maps.

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 phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

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

Before a visitor clicks anything, the page loads Google Tag Manager and Hotjar (measured from a US location before any click). A consent tool (Cookiebot) is installed; check it blocks these until visitors agree where the law requires it.

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

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