Website review, no card needed

kotschi-consulting.com logo

kotschi-consulting.com website review

Visit site (opens in a new tab)Reviewed 11 November 202629 issues · 71 checks

This review found 29 issues worth fixing on kotschi-consulting.com, 11 of them high impact, across 71 checks. The most urgent: improve image delivery. 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

Full-page screenshot of kotschi-consulting.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. kotschi-consulting.com at 2.4 s2.4 s
  2. kotschi-consulting.com at 4.9 s4.9 s
  3. kotschi-consulting.com at 7.3 s7.3 s
  4. kotschi-consulting.com at 9.8 s9.8 s
  5. kotschi-consulting.com at 12.2 s12.2 s
  6. kotschi-consulting.com at 14.7 s14.7 s
  7. kotschi-consulting.com at 17.1 s17.1 s
  8. kotschi-consulting.com at 19.6 s19.6 s

Speed

7 to fix55
  • Improve image delivery

    72.2 s · 15.2 MB

    1 image could be 15.2 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 72.2 s faster on a phone.

  • 5 third-party services on the page

    5 third-party services load with your homepage (Wix, Cloudflare and Sentry and others), adding 16.5 MB and 105 ms of main-thread time.

  • Wix adds 90 ms

    90 ms

    Wix costs a phone 90 ms of main-thread work and 16.5 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.

  • Mobile performance score: 55

    55/100

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

  • Render-blocking requests

    800 ms

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

  • 1 long task on the main thread

    1 long task block the main thread while loading, the longest for 529 ms. During a long task the page ignores taps.

  • Reduce unused JavaScript

    330 ms · 165 KiB

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

  • Legacy JavaScript

    10 KiB

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

  • Use efficient cache lifetimes

    5 KiB

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

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

  • Duplicated JavaScript

    2 KiB

    2 KiB JavaScript is shipped twice across bundles.

2 checks passed
  • Main-thread work: 1.2 s

    A phone's processor spends 1.2 s on main-thread work while loading, 766 ms of it running JavaScript. That is comfortably low.

  • Server response: 257 ms

    257 ms

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

Core Web Vitals

5 to fix53
  • Largest Contentful Paint: 75.5 s

    75.5 s

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

  • Time to Interactive: 75.5 s

    75.5 s

    The page becomes fully interactive after 75.5 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.

  • Total Blocking Time: 479 ms

    479 ms

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

  • First Contentful Paint: 2.2 s

    2.2 s

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

  • Not enough real-visitor data yet

    Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

1 checks passed
  • Cumulative Layout Shift: 0

    0

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

Images and page weight

4 to fix36
  • Page weight: 16.6 MB in 101 requests

    16.6 MB

    Your homepage downloads 16.6 MB in 101 requests on a phone: images 14.3 MB (38), other files 1.7 MB (21) and scripts 459 KiB (38). Under 2 MB keeps phones on slow connections fast.

  • 1 image over 500 KB

    44d3a5_11cca5cbdc434197a2c41321341f4f99~mv2.gif weighs 14.1 MB. On a phone connection a single image that size takes seconds.

  • 1 image in older formats

    1 image (14.1 MB) 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.

  • An image on the first screen is lazy-loaded

    44d3a5_11cca5cbdc434197a2c41321341f4f99~mv2.gif 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 4.7 g of CO₂ per visit

    4.72 g

    By the Sustainable Web Design model, a visit to your homepage emits about 4.72 g of CO₂e: 566.1 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

2 to fixGoogle 9497
  • 1 tap target too small

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

  • 2 links without text

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

  • Headings skip levels

    Headings skip levels (h2 → h6), which makes the page harder to scan with a screen reader.

2 checks passed
  • Every image has alt text

    All 20 images in the HTML carry an alt attribute.

  • 41 automated accessibility rules passed

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

SEO

3 to fixGoogle 10088
  • Meta description is short (52 characters)

    Your meta description is only 52 characters: “Digital Business, Home Energy Management, Smart Home”. 70 to 160 characters is enough to sell the click.

  • No social preview image

    No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • No XML sitemap

    No XML sitemap at https://www.kotschi-consulting.com/sitemap.xml, so Google discovers your pages only by following links.

  • 25 internal links, 2 external

    The homepage links to 25 pages on kotschi-consulting.com and 2 external pages.

5 checks passed
  • One H1 headline

    Your main headline reads: “Digital Business nachhaltig, profitabel”.

  • Title: 51 characters

    Your title is a healthy 51 characters: “KOTSCHI CONSULTING - Strategie & Interim Management”.

  • Canonical URL set

    The canonical URL is https://kotschi-consulting.com/.

  • Structured data in place

    Structured data found: LocalBusiness and WebSite.

  • robots.txt in place

    robots.txt is in place.

AI search readiness

1 to fix83
  • Organization data is thin (3 of 6 facts)

    Your Organization JSON-LD is missing logo, sameAs (social profiles) and description. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

  • No llms.txt

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

  • Opted out of AI training for 5 crawlers

    robots.txt blocks GPTBot, ClaudeBot, Google-Extended, Applebot-Extended and CCBot, which collect pages to train models. That's a legitimate choice and doesn't by itself stop the site appearing in AI answers, which the crawlers above handle.

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

2 to fix70
  • 10 linked pages are broken

    Your homepage links to https://www.kotschi-consulting.com/erfolgsstories, https://www.kotschi-consulting.com/news, https://www.kotschi-consulting.com/bernd-kotschi, https://www.kotschi-consulting.com/kontakt, https://www.kotschi-consulting.com/leistungen/home-energy-management-systems and https://www.kotschi-consulting.com/leistungen/smart-home-platforms and 4 others, which answer with an error. Visitors hit a dead end and search engines drop them.

  • 2 pages without a meta description

    https://www.kotschi-consulting.com/leistungen and https://www.kotschi-consulting.com/leistungen/digital-business-innovation have no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 page with very little text

    https://www.kotschi-consulting.com/leistungen has under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

  • 12 internal pages checked

    We fetched 12 pages linked from your homepage and read each the way a search engine does.

5 checks passed
  • Canonical URLs point to themselves

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

  • 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 2 pages that loaded have a <title>.

Best practices

1 to fixGoogle 9693
  • 4 JavaScript errors while loading

    4 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 400 ()”.

2 checks passed
  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix56
  • 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.

  • Only about 149 words

    The homepage has only about 149 words of visible text; thin pages give Google and first-time buyers little to go on.

  • No opening hours

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

  • No form on the homepage

    There is no form on the homepage, so every lead has to click through to another page first.

  • No map or directions link

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

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

4 checks passed
  • Analytics in place

    Analytics detected: Cloudflare Web Analytics.

  • Direct contact links

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

  • Phone number on the homepage

    Your phone number is on the homepage as a tap-to-call link.

  • LocalBusiness structured data

    Your homepage describes the business with LocalBusiness JSON-LD, so search engines and AI assistants can read its address, hours and phone reliably.

Privacy and tracking

  • No consent tool detected

    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.

  • 8 other companies contacted

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

1 checks passed
  • 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 kotschi-consulting.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

CMS
Wix
Framework
React
Hosting
Cloudflare

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 29 issues on kotschi-consulting.com, including 12 speed issues, 3 SEO issues and 4 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