snapconsult.com website review

11 images could be 710 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 3.2 s faster on a phone.

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

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

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

Your mobile performance score is 44 (desktop: 65). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

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.

Wistia costs a phone 184 ms of main-thread work and 434 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 third-party services load with your homepage (Wistia, Google Tag Manager and LinkedIn Ads), adding 577 KiB and 269 ms of main-thread time.

7 KiB could be saved by minifying CSS.

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

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

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

Your largest element takes 12.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Titelbild der snap zipped next Veranstaltung”.

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

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

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

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

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

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

10 images (1,021 KiB) are 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.

5 images are downloaded at several times the size a phone draws them, for example csm_Slider_zipped_next_2026_275483102a.jpg at 1,200 px wide, shown at 390 px. Resized copies would save about 41 KiB.

3 images further down the page (136 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

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

15 elements have a tabindex above 0, which scrambles the keyboard order.

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

2 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

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

Main landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.

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

5 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

2 links have no real href, so search engines can't follow them.

Open Graph is missing og:title and og:description, so shared links fall back to guesses.

The homepage links to 197 pages on snapconsult.com and 13 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 /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.

/news/events is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

/snapware-smarte-softwareloesungen-fuer-wertvolle-sap-prozesse and /snapware-smarte-softwareloesungen-fuer-wertvolle-sap-prozesse/snapware-instandhaltung use the same meta description. A description written for each page earns more clicks.

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

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

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

Before a visitor clicks anything, the page loads Google Tag Manager and LinkedIn Insight (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.

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