kinnls.co website review

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

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

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

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

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

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

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

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

5 third-party services load with your homepage (Shopify, Facebook and shop.app and others), adding 899 KiB and 352 ms of main-thread time.

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

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

Polyfills for old browsers add 13 KiB JavaScript that modern phones do not need.

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

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

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

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

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

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

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

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

Your homepage downloads 2.7 MB in 383 requests on a phone: other files 959 KiB (168), scripts 898 KiB (169) and images 566 KiB (22). Under 2 MB keeps phones on slow connections fast.

kinnls_banner_1.png 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).

1 image (35 KiB) is 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.

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

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

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

1 image has no alt text, which hurts accessibility and image search.

All page content should be contained by landmarks: 2 elements on the page fail this check, rated moderate by axe-core.

2 visible links have no text or label, so screen readers cannot say where they go.

Your title is 91 characters, so Google will cut it off around 60: “KINNLS Germany – High-Quality Office Chairs with Massage Function – KINNLS OFFICE FURNITU…”.

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

1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

The homepage links to 98 pages on kinnls.co and 20 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.

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

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

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

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

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

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

The page uses urgency cues (a countdown or limited-time wording).

Before a visitor clicks anything, the page loads Meta Pixel (measured from a US location before any click). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.

Opening the homepage sets 10 cookies, 1 of them by other companies (measured from a US location before any click).

No known cookie consent tool loads with the page. Some sites build their own banner, and some only show one to visitors from the EU.

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