quipu.de website review

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

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

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

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

7 third-party services load with your homepage (Google CDN, Google Tag Manager and Other Google APIs/SDKs and others), adding 1.7 MB and 765 ms of main-thread time.

Google CDN costs a phone 427 ms of main-thread work and 1.1 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.

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

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

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

A phone's processor spends 2.2 s on main-thread work while loading, 1.4 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

The page has 1,605 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

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

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

12 KiB could be saved by minifying JavaScript.

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

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

4 KiB could be saved by minifying CSS.

Your largest element takes 14.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Empowering every customer to do more with IT We empower all…”. Most of its time is resource load delay (10.7 s).

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

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

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

Scripts block taps and scrolling for 274 ms in total while the page loads. Good is under 200 ms.

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

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 4.1 MB in 82 requests on a phone: images 1.7 MB (14), scripts 1.7 MB (35) and other files 360 KiB (9). Under 2 MB keeps phones on slow connections fast.

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

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

Documents must have <title> element to aid in navigation: 1 element on the page fails this check, rated serious by axe-core.

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

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

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

Elements with visible text labels do not have matching accessible names. (2 elements).

Your page has no <title>, so Google has to invent the blue link in search results.

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

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

The homepage links to 47 pages on quipu.de and 8 external pages.

There is no https://quipu.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://quipu.de/company-info, https://quipu.de/company/mission, https://quipu.de/company/our-clients, https://quipu.de/company/management_team, https://quipu.de/company/shareholders and https://quipu.de/company/certification and 3 others have no <title>, so Google invents the link text in results.

https://quipu.de/company-info, https://quipu.de/company/mission, https://quipu.de/company/our-clients, https://quipu.de/company/management_team and https://quipu.de/company/certification have no meta description, so Google writes the search snippet from whatever text it finds.

https://quipu.de/news has no <h1> headline, so visitors and search engines get no clear main topic.

https://quipu.de/company-info, https://quipu.de/company/mission, https://quipu.de/company/our-clients, https://quipu.de/company/management_team, https://quipu.de/company/shareholders and https://quipu.de/company/certification and 3 others took over 3 s to send their HTML from our server.

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

1 image failed to load on a phone, for example https://www.quipu.de/wp-content/uploads/2024/07/20240619_071350897_iOS.heic.

6 errors were logged to the browser console while the page loaded, for example “[CookieFirst] WARNING: Loading CookieFirst banner via banner.js has been deprecated and will be removed soon. Please us…”.

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.

Your longest form asks for 26 fields (12 required). Every extra field lowers completion.

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

Before a visitor clicks anything, the page loads 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 9 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 9 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.