Website review, no card needed

nolte-kuechen.com logo

nolte-kuechen.com website review

Visit site (opens in a new tab)Reviewed 26 October 202637 issues · 79 checks

This review found 37 issues worth fixing on nolte-kuechen.com, 18 of them high impact, across 79 checks. The most urgent: page weight: 26.0 MB in 142 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.4 s1.3 sMay 9Oct 242.5 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20261.5 s
May 16, 20261.6 s
May 23, 20261.6 s
May 30, 20261.7 s
Jun 6, 20261.7 s
Jun 13, 20261.8 s
Jun 20, 20261.8 s
Jun 27, 20262.1 s
Jul 4, 20262.3 s
Jul 11, 20262.5 s
Jul 18, 20262.6 s
Jul 25, 20262.6 s
Aug 1, 20262.6 s
Aug 8, 20262.6 s
Aug 15, 20262.5 s
Aug 22, 20262.6 s
Aug 29, 20263.1 s
Sep 5, 20263.1 s
Sep 12, 20263.1 s
Sep 19, 20263.1 s
Sep 26, 20262.5 s
Oct 3, 20262.5 s
Oct 10, 20262.6 s
Oct 17, 20262.5 s
Oct 24, 20262.5 s
Real-visitor tap response (INP)75th percentile, phones
177 ms142 msMay 9Oct 24170 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026146 ms
May 16, 2026146 ms
May 23, 2026151 ms
May 30, 2026155 ms
Jun 6, 2026162 ms
Jun 13, 2026167 ms
Jun 20, 2026169 ms
Jun 27, 2026171 ms
Jul 4, 2026171 ms
Jul 11, 2026173 ms
Jul 18, 2026173 ms
Jul 25, 2026171 ms
Aug 1, 2026170 ms
Aug 8, 2026169 ms
Aug 15, 2026167 ms
Aug 22, 2026163 ms
Aug 29, 2026161 ms
Sep 5, 2026160 ms
Sep 12, 2026160 ms
Sep 19, 2026162 ms
Sep 26, 2026166 ms
Oct 3, 2026169 ms
Oct 10, 2026170 ms
Oct 17, 2026170 ms
Oct 24, 2026170 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 nolte-kuechen.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. nolte-kuechen.com at 2.1 s2.1 s
  2. nolte-kuechen.com at 4.2 s4.2 s
  3. nolte-kuechen.com at 6.3 s6.3 s
  4. nolte-kuechen.com at 8.4 s8.4 s
  5. nolte-kuechen.com at 10.4 s10.4 s
  6. nolte-kuechen.com at 12.5 s12.5 s
  7. nolte-kuechen.com at 14.6 s14.6 s
  8. nolte-kuechen.com at 16.7 s16.7 s

Speed

14 to fix47
  • Reduce initial server response time

    2.2 s

    Reduce initial server response time. Google estimates savings of 2.2 s on a phone.

  • Document request latency

    2.2 s

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

  • Reduce unused JavaScript

    1.1 s · 200 KiB

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

  • Mobile performance score: 47

    47/100

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

  • Main-thread work: 4.6 s

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

  • Server response: 2.3 s

    2.3 s

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

  • Use efficient cache lifetimes

    13.4 MB

    11 files are served with short cache lifetimes, so returning visitors download them again (13.4 MB).

  • Improve image delivery

    650 ms · 3.1 MB

    36 images could be 3.1 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 650 ms faster on a phone.

  • 3 third-party services on the page

    3 third-party services load with your homepage (Usercentrics CMP, nootiz.com and flbx.io), adding 8.4 MB and 182 ms of main-thread time.

  • flbx.io adds 0 ms

    0 ms

    flbx.io costs a phone 0 ms of main-thread work and 8.1 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.

  • Render-blocking requests

    750 ms

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

  • Font display

    600 ms

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

  • Reduce unused CSS

    300 ms · 21 KiB

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

  • 8 long tasks on the main thread

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

  • Legacy JavaScript

    22 KiB

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

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: 14.8 s

    14.8 s

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

  • Speed Index: 16.4 s

    16.4 s

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

  • Time to Interactive: 15.3 s

    15.3 s

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

  • Total Blocking Time: 686 ms

    686 ms

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

  • Real-user LCP: 3.0 s

    3.0 s

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

  • Largest content (LCP) got 59% slower for real visitors

    +59%

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

  • Real-user TTFB: 1.1 s

    1.1 s

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

  • 2 images without width and height

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

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

    +16%

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

5 checks passed
  • Real-user INP: 193 ms

    193 ms

    Real visitors wait 193 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.6 s

    1.6 s

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

  • First Contentful Paint: 1.7 s

    1.7 s

    The first text or image appears after 1.7 s, inside the 1.8 s “good” threshold.

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

2 to fix64
  • Page weight: 26.0 MB in 142 requests

    26.0 MB

    Your homepage downloads 26.0 MB in 142 requests on a phone: media 21.0 MB (9), images 3.6 MB (76) and scripts 674 KiB (33). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    nolte_Toaster+Wasserkocher_260825_bearb_ns_KI.jpg is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

  • About 7.4 g of CO₂ per visit

    7.36 g

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

2 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images are sized for phones

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

Accessibility

4 to fixGoogle 9694
  • Images must have alternative text (1 element)

    Images must have alternative text: 1 element on the page fails this check, rated critical by axe-core.

  • 5 tap targets too small

    5 tap targets are too small or too close together to hit reliably with a finger.

  • 1 text element with low contrast

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

  • 1 form field without a label

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

1 checks passed
  • 50 automated accessibility rules passed

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

SEO

2 to fixGoogle 10093
  • Structured data has 1 problem

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

  • No social preview image

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

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is incomplete here.

  • 50 internal links, 13 external

    The homepage links to 50 pages on nolte-kuechen.com and 13 external pages.

6 checks passed
  • Meta description: 138 characters

    Your meta description is 138 characters: “Entdecken Sie Küchen von nolte: vielfältige Designs, Farben und Materialien, clevere Planungslösungen und Inspiration f…”.

  • One H1 headline

    Your main headline reads: “nolte Elektrogeräte & Zubehör”.

  • Title: 52 characters

    Your title is a healthy 52 characters: “nolte Küchen: Küchen entdecken, planen & inspirieren”.

  • Canonical URL set

    The canonical URL is https://www.nolte-kuechen.com/de-DE/privatkunden.

  • 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.nolte-kuechen.com/sitemap.xml.

AI search readiness

100
  • No llms.txt

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

3 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: 4 of 6 facts

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

  • Text is in the HTML

    Your server sends the page's text in the HTML (755 words), so crawlers that don't run JavaScript still read it.

Other pages

100
  • 11 pages slow to respond

    https://www.nolte-kuechen.com/de-DE/privatkunden/nolte, https://www.nolte-kuechen.com/de-DE/privatkunden/kuechenneuheiten, https://www.nolte-kuechen.com/de-DE/privatkunden/inspiration/wohnen, https://www.nolte-kuechen.com/de-DE/privatkunden/inspiration/hauswirtschaftsraum, https://www.nolte-kuechen.com/de-DE/privatkunden/inspiration/bad and https://www.nolte-kuechen.com/de-DE/privatkunden/inspiration/trend-kueche and 5 others took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

7 checks passed
  • Linked pages load

    13 pages 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 13 pages that loaded have a meta description.

  • Titles are unique

    Every page we checked has its own title.

  • Every page has an H1

    Each page we checked has a main headline.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 13 pages that loaded have a <title>.

Best practices

1 to fixGoogle 10093
  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

2 checks passed
  • Tap targets are thumb-sized

    20 of 20 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

5 to fix33
  • 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 analytics detected

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

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

    The homepage carries about 651 words of visible text.

1 checks passed
  • 1 short form

    A short form (1 field at most) is right on the homepage, asking for an email.

Privacy and tracking

  • 6 other companies contacted

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

2 checks passed
  • Consent tool: Usercentrics

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

  • No known trackers before consent

    No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).

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

Upkeep, stack and company

Stack

Framework
Next.js

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 37 issues on nolte-kuechen.com, including 23 speed issues, 2 SEO issues and 5 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