ringspann.de website review

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

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

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

4 third-party services load with your homepage (Google Tag Manager, ringspann.com and Google Analytics and others), adding 17.0 MB and 605 ms of main-thread time.

ringspann.com costs a phone 105 ms of main-thread work and 16.5 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.

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

7 images could be 985 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

Google Tag Manager costs a phone 500 ms of main-thread work and 515 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.

62 KiB could be saved by minifying JavaScript.

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

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

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.

The page becomes fully interactive after 9.0 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 883 ms for your server to start answering (75th percentile). Good is under 800 ms.

Your largest element takes 3.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Verwendung von Cookies auf dieser Website Auf unserer Webse…”. Most of its time is element render delay (1.6 s).

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

11 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 145 ms to 151 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 17.0 MB in 62 requests on a phone: media 14.5 MB (2), images 1.7 MB (32) and scripts 762 KiB (11). Under 2 MB keeps phones on slow connections fast.

2 images are downloaded at several times the size a phone draws them, for example 26-01-26-slider-1920x480-1769425998-7265.jpg at 8,000 px wide, shown at 585 px. Resized copies would save about 607 KiB.

9 images (1.5 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.

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

1 dropdown has no label.

Some lists contain elements other than list items, which screen readers announce wrongly.

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

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

14 links inside paragraphs rely on colour alone to stand out.

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

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

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

1 visible link has no text or label, so screen readers cannot say where it goes.

Alternative text of images should not be repeated as text: 2 elements on the page fail this check, rated minor by axe-core.

Your title is 70 characters, so Google will cut it off around 60: “RINGSPANN | Premium-Hersteller von Antriebskomponenten und Spannzeugen”.

No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

Your meta description is 161 characters; Google truncates after about 160, so the end of your pitch is cut.

Structured data found (Organization) but with 1 problem, for example “Organization: url is not an absolute URL ("https://www.ringspann.de/de")”.

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

Your hreflang tags are invalid, so Google may show the wrong language version.

Your <h1> is empty.

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

The homepage links to 120 pages on ringspann.de and 7 external pages.

Your Organization JSON-LD is missing logo, sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

There is no https://www.ringspann.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.ringspann.de/de/branchen/uebersicht has no meta description, so Google writes the search snippet from whatever text it finds.

https://www.ringspann.de/de/produkte/freilaeufe, https://www.ringspann.de/de/produkte/industriekupplungen, https://www.ringspann.de/de/produkte/praezisions-spannzeuge, https://www.ringspann.de/de/branchen/uebersicht, https://www.ringspann.de/de/service and https://www.ringspann.de/de/service/downloads and 1 other took over 3 s to send their HTML from our server.

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

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

3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

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.

Social proof on the homepage: 1 testimonial or review block. Pairing it with named testimonials or customer logos makes it far more convincing.

Your longest form asks for 10 fields (4 required). Every extra field lowers completion.

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

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

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