komsa.com website review

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

Your mobile performance score is 88 (desktop: 82). Pages that score under 90 lose visitors before the first paint.

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

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

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

5 images could be 138 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 50 ms faster on a phone.

2 third-party services load with your homepage (piwik.pro and cookieinformation.com), adding 159 KiB and 127 ms of main-thread time.

About 112 KiB of JavaScript is downloaded but never used on this page.

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

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

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.

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

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

Your largest element takes 3.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Wir verwenden Cookies und ähnliche Technologien, um unsere …”. Most of its time is element render delay (1.9 s).

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

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

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

Your homepage downloads 5.1 MB in 24 requests on a phone: media 4.1 MB (1), fonts 337 KiB (6) and scripts 323 KiB (5). Under 2 MB keeps phones on slow connections fast.

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

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 2 elements on the page fail this check, rated moderate by axe-core.

Document should not have more than one banner landmark: 1 element on the page fails this check, rated moderate by axe-core.

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

Your meta description is 187 characters; Google truncates after about 160, so the end of your pitch is cut.

The homepage links to 63 pages on komsa.com and 20 external pages.

There is no https://komsa.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://komsa.com/komon-reseller-club, https://komsa.com/suche and https://komsa.com/device-as-a-service/daas-team are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

https://komsa.com/suche and https://komsa.com/device-as-a-service/daas-team have no meta description, so Google writes the search snippet from whatever text it finds.

Your homepage links to 1 page by a URL that isn't its canonical one, for example https://komsa.com/device-as-a-service, whose canonical is https://komsa.com/device-as-a-service?gad_campaignid=22567579165&gad_source=1&gbraid=0AAAAACL0vCs2e3pPJb7aphNjgMsN-MaSK&gclid=CjwKCAjw9PvWBhAxEiwAddzYyQ-G4gOKv3LtSnRGB8_UYgG1aR6822h0fLGxbKSEwwwUOjYwh7P1HhoC6KkQAvD_BwE&hsa_acc=2230178854&hsa_ad=&hsa_cam=22564000226&hsa_grp=&hsa_kw=&hsa_mt=&hsa_net=adwords&hsa_src=&hsa_tgt=&hsa_ver=3&utm_campaign=PMax_DaaS_Neu&utm_medium=ppc&utm_source=adwords&utm_term=. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://komsa.com/suche has no <h1> headline, so visitors and search engines get no clear main topic.

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

8 of 34 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”.

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

Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

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

The homepage shows no opening hours. If customers visit or call, show when.

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

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 1,006 words of visible text.

Opening the homepage sets 1 cookie (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 2 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.