4cgroup.com website review

34 files are served with short cache lifetimes, so returning visitors download them again (5.0 MB).

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

About 312 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.5 s faster on a phone.

8 images could be 1.3 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 250 ms faster on a phone.

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

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

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

48 KiB could be saved by minifying CSS.

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

1 third-party service load with your homepage (YouTube), adding 65 KiB and 0 ms of main-thread time.

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 39.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.

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

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

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

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

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

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

Your homepage downloads 13.8 MB in 36 requests on a phone: images 8.8 MB (20), media 3.7 MB (1) and scripts 604 KiB (5). Under 2 MB keeps phones on slow connections fast.

3 images weigh 6.0 MB together. On a phone connection a single image that size takes seconds.

4 images (6.1 MB) 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.

1 image is downloaded at several times the size a phone draws it, for example 36_i91721920x500_41_217.jpg at 1,920 px wide, shown at 354 px. Resized copies would save about 43 KiB.

1 image further down the page (62 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 3.90 g of CO₂e: 468.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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

1 frame has no title, so screen-reader users cannot tell what it contains.

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

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

7 form fields have no label, so screen readers announce an empty box and autofill guesses.

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

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

No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

The homepage links to 141 pages on 4cgroup.com and 7 external pages.

/ and /en/home all use the title “Management consulting for CxOs - 4C GROUP AG”. Search engines can't tell which page to show for a search, so each competes with the others.

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

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

Large scripts ship without source maps.

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.

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

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

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