ncc-systems.com website review

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

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

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

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

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

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

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

40 KiB could be saved by minifying CSS.

The HTML itself could arrive sooner: redirects, a slow server response or missing compression delay everything after it.

7 KiB could be saved by minifying JavaScript.

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

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

The first text or image appears after 3.1 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.

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.

Your homepage downloads 2.9 MB in 34 requests on a phone: images 2.3 MB (22), scripts 266 KiB (6) and stylesheets 243 KiB (1). Under 2 MB keeps phones on slow connections fast.

17 images (2.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 IHK_20_jahre_am_markt.png at 1,560 px wide, shown at 357 px. Resized copies would save about 95 KiB.

2 images further down the page (260 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.83 g of CO₂e: 99.9 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

Certain ARIA roles must be contained by particular parents: 1 element on the page fails this check, rated critical by axe-core.

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

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

Headings should not be empty: 2 elements on the page fail this check, rated minor by axe-core.

Your title is only 29 characters: “Startseite - NCC systems GmbH”. Between 30 and 65 characters leaves room to say what you do and for whom.

Your meta description is only 55 characters: “Wir sind Ihr Partner, wenn es um das herz Ihrer IT geht”. 70 to 160 characters is enough to sell the click.

Structured data found (ImageObject, Page and WebPage) but with 3 problems, for example “ImageObject: contentUrl is not an absolute URL ("https://www.ncc-systems.de/files/ncc-systemes/Layout/Logos/IHK_20_jahre_am_m…”.

No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

Your <h1> is empty.

No twitter:card tag. X falls back to Open Graph, which is incomplete here.

The homepage links to 16 pages on ncc-systems.com and 25 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 https://www.ncc-systems.de/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://www.ncc-systems.de/impressum and https://www.ncc-systems.de/datenschutz have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.ncc-systems.de/impressum and https://www.ncc-systems.de/datenschutz 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 2 pages linked from your homepage and read each the way a search engine does.

5 of 15 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: the server responded with a status of 404 ()”.

Social proof on the homepage: 3 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.

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

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

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.