Website review, no card needed

vorwerk.at logo

vorwerk.at website review

Visit site (opens in a new tab)Reviewed 5 November 202626 issues · 68 checks

This review found 26 issues worth fixing on vorwerk.at, 10 of them high impact, across 68 checks. The most urgent: reduce unused JavaScript. 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.6 s1.3 sMay 16Oct 311.4 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20261.4 s
May 23, 20261.4 s
May 30, 20261.4 s
Jun 6, 20261.4 s
Jun 13, 20261.4 s
Jun 20, 20261.4 s
Jun 27, 20261.4 s
Jul 4, 20261.5 s
Jul 11, 20261.4 s
Jul 18, 20261.4 s
Jul 25, 20261.4 s
Aug 1, 20261.4 s
Aug 8, 20261.5 s
Aug 15, 20261.5 s
Aug 22, 20261.5 s
Aug 29, 20261.6 s
Sep 5, 20261.6 s
Sep 12, 20261.6 s
Sep 19, 20261.6 s
Sep 26, 20261.5 s
Oct 3, 20261.4 s
Oct 10, 20261.3 s
Oct 17, 20261.3 s
Oct 24, 20261.4 s
Oct 31, 20261.4 s
Real-visitor tap response (INP)75th percentile, phones
220 ms184 msMay 16Oct 31214 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026188 ms
May 23, 2026188 ms
May 30, 2026190 ms
Jun 6, 2026192 ms
Jun 13, 2026194 ms
Jun 20, 2026196 ms
Jun 27, 2026198 ms
Jul 4, 2026203 ms
Jul 11, 2026204 ms
Jul 18, 2026204 ms
Jul 25, 2026204 ms
Aug 1, 2026204 ms
Aug 8, 2026209 ms
Aug 15, 2026212 ms
Aug 22, 2026215 ms
Aug 29, 2026216 ms
Sep 5, 2026215 ms
Sep 12, 2026213 ms
Sep 19, 2026212 ms
Sep 26, 2026210 ms
Oct 3, 2026209 ms
Oct 10, 2026209 ms
Oct 17, 2026211 ms
Oct 24, 2026213 ms
Oct 31, 2026214 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 vorwerk.at (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. vorwerk.at at 0.5 s0.5 s
  2. vorwerk.at at 1.1 s1.1 s
  3. vorwerk.at at 1.6 s1.6 s
  4. vorwerk.at at 2.1 s2.1 s
  5. vorwerk.at at 2.7 s2.7 s
  6. vorwerk.at at 3.2 s3.2 s
  7. vorwerk.at at 3.7 s3.7 s
  8. vorwerk.at at 4.3 s4.3 s

Speed

5 to fix38
  • Reduce unused JavaScript

    3.6 s · 691 KiB

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

  • Mobile performance score: 38

    38/100

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

  • Use efficient cache lifetimes

    300 ms · 171 KiB

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

  • Render-blocking requests

    300 ms

    1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 300 ms.

  • Main-thread work: 2.3 s

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

  • 10 long tasks on the main thread

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

  • Document request latency

    203 KiB

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

  • Improve image delivery

    188 KiB

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

  • Reduce unused CSS

    150 ms · 29 KiB

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

  • 3 third-party services on the page

    3 third-party services load with your homepage (Optanon, hlx.page and Google Tag Manager), adding 217 KiB and 135 ms of main-thread time.

  • Legacy JavaScript

    9 KiB

    Polyfills for old browsers add 9 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: 14 ms

    14 ms

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

Core Web Vitals

9 to fix67
  • Fails Core Web Vitals for real visitors

    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.

  • Largest Contentful Paint: 13.0 s

    13.0 s

    Your largest element takes 13.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Dekorative Herbstillustration mit fallenden Blättern, Eiche…”.

  • First Contentful Paint: 5.7 s

    5.7 s

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

  • Time to Interactive: 13.5 s

    13.5 s

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

  • Speed Index: 8.6 s

    8.6 s

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

  • Real-user INP: 236 ms

    236 ms

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

  • Total Blocking Time: 533 ms

    533 ms

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

  • Cumulative Layout Shift: 0.148

    0.148

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

  • 6 images without width and height

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

  • Tap response (INP) got 14% slower for real visitors

    +14%

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

  • Largest content (LCP) held steady for real visitors

    -1%

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

4 checks passed
  • Real-user LCP: 1.3 s

    1.3 s

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

  • Real-user CLS: 0.00

    0.00

    For real visitors the layout shifts by 0.00 (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: 336 ms

    336 ms

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

Images and page weight

1 to fix50
  • Page weight: 2.5 MB in 47 requests

    2.5 MB

    Your homepage downloads 2.5 MB in 47 requests on a phone: scripts 1.1 MB (16), images 759 KiB (20) and HTML 303 KiB (1). Under 2 MB keeps phones on slow connections fast.

  • About 0.7 g of CO₂ per visit

    0.70 g

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

Accessibility

2 to fix90
  • 3 buttons without a name

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

  • 18 text elements with low contrast

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

  • Headings skip levels

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

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

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

1 checks passed
  • Every image has alt text

    All 24 images in the HTML carry an alt attribute.

SEO

1 to fixGoogle 10099
  • No favicon declared

    No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

  • No X (Twitter) card tag

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

  • 47 internal links, 13 external

    The homepage links to 47 pages on vorwerk.at and 13 external pages.

8 checks passed
  • Meta description: 108 characters

    Your meta description is 108 characters: “Entdecke die innovativen Produkte von Vorwerk online ►Thermomix® TM7 & Zubehör ►Kobold Staubsauger & Zubehör”.

  • One H1 headline

    Your main headline reads: “Vorwerk Herbst Sale”.

  • Title: 56 characters

    Your title is a healthy 56 characters: “Vorwerk Österreich | Alle Thermomix® und Kobold Produkte”.

  • Canonical URL set

    The canonical URL is https://www.vorwerk.com/at/de.

  • Structured data in place

    Structured data found: Organization.

  • Open Graph tags complete

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

  • robots.txt in place

    robots.txt is in place and points crawlers to your sitemap.

  • XML sitemap found

    Your XML sitemap is reachable at https://www.vorwerk.com/de/de/c/sitemap.xml.

AI search readiness

100
  • No llms.txt

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

2 checks passed
  • AI answer engines may read the site

    Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.

  • Organization data: 5 of 6 facts

    Your Organization JSON-LD gives name, url, logo, sameAs (social profiles) and description; contact details would complete it.

Other pages

5 to fix76
  • 5 pages share 2 titles

    https://www.vorwerk.com/at/de, https://www.vorwerk.com/at/de/c/home/service and https://www.vorwerk.com/at/de/c/home/karriere all use the title “Vorwerk Österreich | Alle Thermomix® und Kobold Produkte”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

  • 2 pages without a meta description

    https://www.vorwerk.com/at/de/shop/kategorien/herbstangebote and https://www.vorwerk.com/at/de/shop/kategorien/thermomix/thermomix-tm6-renewed have no meta description, so Google writes the search snippet from whatever text it finds.

  • 4 pages share a meta description

    https://www.vorwerk.com/at/de/produkte/thermomix and https://www.vorwerk.com/at/de/c/home/produkte/thermomix use the same meta description. A description written for each page earns more clicks.

  • 4 links to non-canonical URLs

    Your homepage links to 4 pages by a URL that isn't their canonical one, for example https://www.vorwerk.com/at/de/c/home/produkte/kobold, whose canonical is https://www.vorwerk.com/at/de/produkte/kobold. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 3 pages without an H1

    https://www.vorwerk.com/at/de/campaigns/thermomix/tm6/tm6-renewed, https://www.vorwerk.com/at/de/campaigns/kobold/vk7/titanium and https://www.vorwerk.com/at/de/c/home/angebote/kobold-angebote 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 36 found) and read each the way a search engine does.

3 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • 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

Google 100100
  • Missing source maps

    Large scripts ship without source maps.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix38
  • 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 social proof

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

  • No direct contact details

    No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

  • No form on the homepage

    There is no form on the homepage, so every lead has to click through to another page first.

  • 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 939 words of copy

    The homepage carries about 939 words of visible text.

1 checks passed
  • Analytics in place

    Analytics detected: Google Tag Manager.

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

Upkeep, stack and company

Stack

Analytics
Google Tag Manager
Hosting
Hetzner

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 26 issues on vorwerk.at, including 14 speed issues, 1 SEO issue 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