schuetz.net website review

19 images could be 6.9 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 2.4 s faster on a phone.

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

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

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

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

6 third-party services load with your homepage (Unpkg, Other Google APIs/SDKs and getmdl.io and others), adding 2.0 MB and 19 ms of main-thread time.

schuetz-packaging.net costs a phone 0 ms of main-thread work and 1.2 MB 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.

schuetz-composites.net costs a phone 0 ms of main-thread work and 632 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.

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

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

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

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

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.

Real visitors wait 4.3 s for the largest content to appear (75th percentile). Good is under 2.5 s.

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

Your largest element takes 9.2 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 9.3 s. Good is under 3.8 s.

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

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

Visually, the page fills in at 5.2 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-10-24, real Chrome visitors' tap response (inp) went from 85 ms to 87 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

Your homepage downloads 9.0 MB in 90 requests on a phone: images 7.4 MB (22), fonts 712 KiB (28) and scripts 700 KiB (28). Under 2 MB keeps phones on slow connections fast.

12 images are downloaded at several times the size a phone draws them, for example co-header-slider-newsletter-05-2026-en-web.jpg at 2,000 px wide, shown at 390 px. Resized copies would save about 2.4 MB.

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

16 images (3.8 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.

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

1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

2 buttons have no accessible name, so screen readers announce just “button”.

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

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

1 tap target is too small or too close together to hit reliably with a finger.

The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

No meta description, so Google writes its own snippet from whatever text it finds.

Your title is only 12 characters: “en | COMPANY”. Between 30 and 65 characters leaves room to say what you do and for whom.

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

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

There is no robots.txt at schuetz.net/robots.txt, the first file search crawlers ask for.

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 62 pages on schuetz.net and 37 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.schuetz.net/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.schuetz.net/en/downloads, https://www.schuetz.net/en/contact, https://www.schuetz.net/en/imprint, https://www.schuetz.net/en/terms-and-conditions, https://www.schuetz.net/de and https://www.schuetz.net/en/company and 8 others have no meta description, so Google writes the search snippet from whatever text it finds.

Your homepage links to 1 page by a URL that isn't its canonical one, for example https://www.schuetz.net/en/downloads, whose canonical is https://www.schuetz.net/en/downloads/brochures. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://www.schuetz.net/en/contact and https://www.schuetz.net/en/company/locations-worldwide have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.schuetz.net/en/contact and https://www.schuetz.net/en/company/locations-worldwide 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.

https://www.schuetz.net/en/company/divisions/packaging-systems, https://www.schuetz.net/en/company/divisions/industrial-services, https://www.schuetz.net/en/company/divisions/composites and https://www.schuetz.net/en/company/divisions/energy-systems took over 3 s to send their HTML from our server.

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

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

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

Chrome logged issues while loading the page (“Content security policy”).

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

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

Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

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