yncoris.com website review

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

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

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

5 files block the first paint until they finish downloading. Deferring or inlining them could save about 900 ms.

About 112 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.

74 KiB could be saved by minifying JavaScript.

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

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

1 third-party service load with your homepage (ccm19.de), adding 50 KiB and 94 ms of main-thread time.

About 62 KiB of CSS is downloaded but never applied on this page.

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

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

4 KiB could be saved by minifying CSS.

Your largest element takes 6.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Diese Website nutzt Cookies und vergleichbare Funktionen zu…”.

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

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

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

5 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 97 ms to 105 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 2.1 s to 1.7 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

7 images (1.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.

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

2 images are downloaded at several times the size a phone draws them, for example logo.jpg at 1,890 px wide, shown at 152 px. Resized copies would save about 269 KiB.

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

1 button has no accessible name, so screen readers announce just “button”.

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

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

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

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

Document should not have more than one contentinfo landmark: 1 element on the page fails this check, rated moderate by axe-core.

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.

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

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

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

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

There are 6 <h1> headlines (“Welche Leistung suchen Sie?”, “Unsere Leistungen” and “Produkt im Fokus”). One clear main headline is easier for people and search engines.

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

1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

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

The homepage links to 177 pages on yncoris.com and 12 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.yncoris.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.

https://www.yncoris.com/suche and https://www.yncoris.com/leistungen/planen/projektengineering are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

/ and https://www.yncoris.com/en all use the title “YNCORIS - Industrial Services | YNCORIS”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.yncoris.com/kontakt, https://www.yncoris.com/servicewissen, https://www.yncoris.com/suche, https://www.yncoris.com/leistungen, https://www.yncoris.com/leistungskatalog and https://www.yncoris.com/leistungen/planen and 4 others use the same meta description. A description written for each page earns more clicks.

https://www.yncoris.com/kontakt has no <h1> headline, so visitors and search engines get no clear main topic.

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

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

Large scripts ship without source maps.

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.

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

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