Website review, no card needed

vitkonwood.de logo

vitkonwood.de website review

Visit site (opens in a new tab)Reviewed 11 November 202635 issues · 84 checks

This review found 35 issues worth fixing on vitkonwood.de, 16 of them high impact, across 84 checks. The most urgent: render-blocking requests. 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
3.2 s2.3 sMay 23Nov 72.5 s
Show as table
DateReal-visitor load time (LCP)
May 23, 20262.8 s
May 30, 20262.8 s
Jun 6, 20262.8 s
Jun 13, 20262.8 s
Jun 20, 20262.9 s
Jun 27, 20263.0 s
Jul 4, 20263.1 s
Jul 11, 20263.1 s
Jul 18, 20263.0 s
Jul 25, 20262.8 s
Aug 1, 20262.6 s
Aug 8, 20262.4 s
Aug 15, 20262.4 s
Aug 22, 20262.5 s
Aug 29, 20262.5 s
Sep 5, 20262.5 s
Sep 12, 20262.6 s
Sep 19, 20262.6 s
Sep 26, 20262.6 s
Oct 3, 20262.7 s
Oct 10, 20262.7 s
Oct 17, 20262.7 s
Oct 24, 20262.6 s
Oct 31, 20262.5 s
Nov 7, 20262.5 s
Real-visitor tap response (INP)75th percentile, phones
175 ms140 msMay 23Nov 7158 ms
Show as table
DateReal-visitor tap response (INP)
May 23, 2026147 ms
May 30, 2026144 ms
Jun 6, 2026145 ms
Jun 13, 2026146 ms
Jun 20, 2026147 ms
Jun 27, 2026153 ms
Jul 4, 2026153 ms
Jul 11, 2026154 ms
Jul 18, 2026152 ms
Jul 25, 2026147 ms
Aug 1, 2026146 ms
Aug 8, 2026144 ms
Aug 15, 2026147 ms
Aug 22, 2026152 ms
Aug 29, 2026155 ms
Sep 5, 2026157 ms
Sep 12, 2026159 ms
Sep 19, 2026163 ms
Sep 26, 2026167 ms
Oct 3, 2026170 ms
Oct 10, 2026171 ms
Oct 17, 2026171 ms
Oct 24, 2026163 ms
Oct 31, 2026161 ms
Nov 7, 2026158 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 vitkonwood.de (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. vitkonwood.de at 0.8 s0.8 s
  2. vitkonwood.de at 1.7 s1.7 s
  3. vitkonwood.de at 2.5 s2.5 s
  4. vitkonwood.de at 3.4 s3.4 s
  5. vitkonwood.de at 4.2 s4.2 s
  6. vitkonwood.de at 5.0 s5.0 s
  7. vitkonwood.de at 5.9 s5.9 s
  8. vitkonwood.de at 6.7 s6.7 s

Speed

11 to fix59
  • Render-blocking requests

    2.0 s

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

  • Improve image delivery

    1.1 s · 849 KiB

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

  • Main-thread work: 4.5 s

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (iubenda, Shopify and Google Tag Manager and others), adding 2.1 MB and 1.6 s of main-thread time.

  • Reduce unused JavaScript

    150 ms · 984 KiB

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

  • Mobile performance score: 59

    59/100

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

  • iubenda adds 472 ms

    472 ms

    iubenda costs a phone 472 ms of main-thread work and 119 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.

  • Shopify adds 396 ms

    396 ms

    Shopify costs a phone 396 ms of main-thread work and 624 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.

  • Google Tag Manager adds 395 ms

    395 ms

    Google Tag Manager costs a phone 395 ms of main-thread work and 528 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.

  • Use efficient cache lifetimes

    283 KiB

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

  • 2,309 HTML elements

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

  • Minify JavaScript

    150 ms · 139 KiB

    139 KiB could be saved by minifying JavaScript.

  • Reduce unused CSS

    150 ms · 84 KiB

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

  • 14 long tasks on the main thread

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

  • Legacy JavaScript

    42 KiB

    Polyfills for old browsers add 42 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.

  • Minify CSS

    3 KiB

    3 KiB could be saved by minifying CSS.

1 checks passed
  • Server response: 108 ms

    108 ms

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

Core Web Vitals

6 to fix100
  • Largest Contentful Paint: 11.6 s

    11.6 s

    Your largest element takes 11.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Hochwertige Hot Tubs für den Garten kaufen”.

  • Time to Interactive: 28.0 s

    28.0 s

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

  • Speed Index: 6.6 s

    6.6 s

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

  • First Contentful Paint: 3.3 s

    3.3 s

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

  • 33 images without width and height

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

  • Total Blocking Time: 217 ms

    217 ms

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

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

    +10%

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

8 checks passed
  • Passes Core Web Vitals for real visitors

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

  • Real-user LCP: 1.5 s

    1.5 s

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

  • Real-user INP: 136 ms

    136 ms

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

  • 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: 1.2 s

    1.2 s

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

  • Real-user TTFB: 288 ms

    288 ms

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

  • Largest content (LCP) got 11% faster for real visitors

    -11%

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

  • Cumulative Layout Shift: 0

    0

    The layout barely moves while loading (CLS 0, good is under 0.1).

Images and page weight

3 to fix53
  • Page weight: 6.5 MB in 399 requests

    6.5 MB

    Your homepage downloads 6.5 MB in 399 requests on a phone: images 2.6 MB (100), scripts 2.3 MB (88) and other files 1.1 MB (181). Under 2 MB keeps phones on slow connections fast.

  • 34 images below the first screen load straight away

    34 images further down the page (1.6 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • 6 images in older formats

    6 images (1.2 MB) 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.

  • About 1.8 g of CO₂ per visit

    1.84 g

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

1 checks passed
  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

6 to fixGoogle 7789
  • Images must have alternative text (97 elements)

    Images must have alternative text: 97 elements on the page fail this check, rated critical by axe-core.

  • 2 buttons without a name

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

  • ARIA attributes must conform to valid values (1 element)

    ARIA attributes must conform to valid values: 1 element on the page fails this check, rated critical by axe-core.

  • 6 text elements with low contrast

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

  • All page content should be contained by landmarks (1 element)

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

  • 1 tap target too small

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

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

    Elements with visible text labels do not have matching accessible names. (1 element).

1 checks passed
  • 41 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 46 WCAG 2.2 A/AA and best-practice rules on the phone render: 41 passed and 5 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

1 to fixGoogle 9296
  • No structured data

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

  • 64 internal links, 5 external

    The homepage links to 64 pages on vitkonwood.de and 5 external pages.

7 checks passed
  • Meta description: 142 characters

    Your meta description is 142 characters: “Egal ob Fasssauna, Iglusauna, klassische Gartensauna oder ein Hot Tub mit Holzofen. Jetzt in 3D Ihre Wohlfühloase im ei…”.

  • One H1 headline

    Your main headline reads: “HOT TUB, GARTENSAUNA ODER GRILLKOTA - JEDEN TAG.”.

  • Title: 65 characters

    Your title is a healthy 65 characters: “VITKONWOOD - Gartensaunen, Hot Tubs & Grillkotas für Ihren Garten”.

  • Canonical URL set

    The canonical URL is https://vitkonwood.de/.

  • 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://vitkonwood.de/sitemap.xml.

AI search readiness

2 to fix63
  • Most text only appears after JavaScript runs

    7%

    A phone browser shows 3,434 words, but the HTML your server sends has only 233. GPTBot, ClaudeBot and PerplexityBot read that HTML without running JavaScript, so they see an almost empty page. Server-side rendering or pre-rendering fixes it.

  • No Organization structured data

    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.

  • No llms.txt

    There is no https://vitkonwood.de/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.

1 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.

Other pages

1 to fix95
  • 1 page without an H1

    https://vitkonwood.de/collections/gartensauna-kaufen has 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 25 found) and read each the way a search engine does.

6 checks passed
  • Linked pages load

    1 page of 15 loaded without an error (the rest turned automated requests away).

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • Every page has a meta description

    All 1 page that loaded have a meta description.

  • Titles are unique

    Every page we checked has its own title.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 1 page that loaded have a <title>.

Best practices

2 to fixGoogle 9687
  • 35 small tap targets

    35 of 47 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “Cannot read properties of undefined (reading 'on')”.

  • 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 fix50
  • No call to action on the first screen

    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 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 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 3,434 words of copy

    The homepage carries about 3,434 words of visible text.

3 checks passed
  • 1 short form

    A short form (1 field at most) is right on the homepage.

  • Analytics in place

    Analytics detected: Google Tag Manager.

  • Direct contact links

    Visitors can reach you directly: 3 phone links and 0 email links.

Privacy and tracking

  • 6 trackers load before any consent

    6

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and Microsoft Clarity and 1 more (measured from a US location before any click). A consent tool (iubenda) is installed; check it blocks these until visitors agree where the law requires it.

  • 14 cookies set on arrival

    14

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

  • 31 other companies contacted

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

1 checks passed
  • Consent tool: iubenda

    A consent management tool (iubenda) loads with the page.

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

Apps on your store

Your storefront loads 9 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Complianz Consent · Contact Form Ultimate · Aris Product Options · Propel Replays · optimonk.com · reputon.com · hextom.com · trustedshops.com · vercel.app

Apps found in the homepage's code. Apps that only run in checkout or the admin aren't seen, and a headless storefront shows none. App data from programmable.info

Upkeep, stack and company

Stack

Framework
jQuery
E-commerce
Shopify
Analytics
Google Tag Manager
Hosting
Shopify

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 35 issues on vitkonwood.de, including 17 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