kind.com website review

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

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

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

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

4 third-party services load with your homepage (Google Tag Manager, Google Maps and Usercentrics CMP and others), adding 722 KiB and 280 ms of main-thread time.

Polyfills for old browsers add 13 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 200 ms faster on a phone.

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

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

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

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.

Your largest element takes 6.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Birgit Schrowange auf dunkelblauem Hintergrund zeigt ein kl…”.

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

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

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

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

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

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

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

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

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

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

1 button has no accessible name, so screen readers announce just “button”.

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

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.

Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

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

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

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

The homepage links to 169 pages on kind.com and 5 external pages.

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.

There is no https://www.kind.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://www.kind.com/de-de/beratung/hoerberatung/hoergeraete-beratung and https://www.kind.com/de-de/hoeren/hoergeraete use the same meta description. A description written for each page earns more clicks.

https://www.kind.com/de-de/beratung/service/faq, https://www.kind.com/de-de/beratung/service/terminvereinbarung and https://www.kind.com/de-de/hoeren/hoergeraete-service have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.kind.com/de-de/beratung/vorteile/garantien and https://www.kind.com/de-de/beratung/service/kontakt/kontaktanfrage took over 3 s to send their HTML from our server.

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

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

The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

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.

We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust 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 567 words of visible text.

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

Opening the homepage sets 1 cookie (measured from a US location before any click).

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