tobit.com website review

chayns-static.space costs a phone 3.6 s of main-thread work and 1.4 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

6 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.5 s.

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

3 third-party services load with your homepage (chayns-static.space, tobit.cloud and tsimg.cloud), adding 1.8 MB and 3.6 s of main-thread time.

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

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

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

About 62 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 400 ms faster on a phone.

tsimg.cloud costs a phone 0 ms of main-thread work and 313 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.

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

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

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

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

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.

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

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

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

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

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

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

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

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

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

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

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

Your homepage downloads 2.0 MB in 77 requests on a phone: scripts 1.0 MB (25), fonts 464 KiB (6) and images 314 KiB (18). Under 2 MB keeps phones on slow connections fast.

1 image further down the page (126 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

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

11 images have no alt text, which hurts accessibility and image search.

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

There is no <h1>, so neither visitors nor Google get a clear main headline.

No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

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

The homepage links to 47 pages on tobit.com and 2 external pages.

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

/sidekick/agent-store is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

/ and /software all use the title “Tobit.Software | Software für Digitalisierung”. Search engines can't tell which page to show for a search, so each competes with the others.

/software, /teamdavid, /teamdavid/leistungs%C3%BCbersicht, /teamdavid/support, /teamdavid/kaufen and /teamdavid/downloads and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

/teamdavid, /teamdavid/leistungs%C3%BCbersicht, /teamdavid/support, /teamdavid/kaufen, /teamdavid/downloads and /sidekick and 7 others have 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.

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

4 errors were logged to the browser console while the page loaded, for example “[object Object]”.

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 phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

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

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 333 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 4 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.