yuma.de website review

Not measured in this review.

• Tap response (INP) held steady for real visitors

  -8%

  Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 203 ms to 177 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

• Largest content (LCP) got 13% slower for real visitors

  +13%

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

• Page weight: 3.0 MB

  3.0 MB

  Your homepage downloads 3.0 MB on a phone, 1.0 MB of it images (34%). Under 2 MB keeps phones on slow connections fast.

• An image on the first screen is lazy-loaded

  vorbereitung.png is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

  Elements (3)

• 5 images far larger than shown

  433 KiB

  5 images are downloaded at several times the size a phone draws them, for example vorbereitung.png at 2,970 px wide, shown at 342 px. Resized copies would save about 433 KiB.

  Elements (5)

• About 0.8 g of CO₂ per visit

  0.85 g

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

• ARIA attributes must conform to valid values (2 elements)

  ARIA attributes must conform to valid values: 2 elements on the page fail this check, rated critical by axe-core.

  Elements (2)

• 28 text elements with low contrast

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

  Elements (3)

• Frames without titles

  1 frame has no title, so screen-reader users cannot tell what it contains.

  Elements (1)

• Scrollable region must have keyboard access (1 element)

  Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

  Elements (1)

• 62 images without alt text

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

  View source

• 7 links without text

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

• Headings skip levels

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

  View source

• 2 H1 headlines

  There are 2 <h1> headlines (“” and “Mini-Solaranlagen in Premium-Qualität”). One clear main headline is easier for people and search engines.

  View source

• 167 internal links, 26 external

  The homepage links to 167 pages on yuma.de and 26 external pages.

• No llms.txt

  There is no https://yuma.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.

• 1 page without a title

  https://yuma.de/customer_authentication/redirect has no <title>, so Google invents the link text in results.

  Elements (1)

• 1 linked page hidden from search

  https://yuma.de/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

  Elements (1)

• 1 page without a meta description

  https://yuma.de/customer_authentication/redirect has no meta description, so Google writes the search snippet from whatever text it finds.

  Elements (1)

• 1 link to non-canonical URLs

  Your homepage links to 1 page by a URL that isn't its canonical one, for example https://yuma.de/pages/balkonkraftwerk-speicher, whose canonical is https://yuma.de/collections/balkonkraftwerk-mit-speicher. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  Elements (1)

• 2 pages without an H1

  https://yuma.de/customer_authentication/redirect and https://yuma.de/pages/black-weeks have no <h1> headline, so visitors and search engines get no clear main topic.

• 15 internal pages checked

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

• 1 broken image

  1 image failed to load on a phone, for example https://yuma.de/.

• 5 JavaScript errors while loading

  5 errors were logged to the browser console while the page loaded, for example “Refused to apply style from 'https://yuma.de/cdn/shop/t/67/assets/section-hero-slider.css?v=105998' because its MIME ty…”.

• No call to action on the first screen

  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 calls to action

  We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

• No map or directions link

  There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

• No risk reducer

  No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

• About 1,005 words of copy

  The homepage carries about 1,005 words of visible text.

• Urgency cues

  The page uses urgency cues (a countdown or limited-time wording).

• 6 trackers load before any consent

  6

  Before a visitor clicks anything, the page loads Criteo, Google Ads, Google Tag Manager, Klaviyo and Meta Pixel and 1 more (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.

• 26 cookies set on arrival

  26

  Opening the homepage sets 26 cookies (measured from a US location before any click).

• No consent tool detected

  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.

• 34 other companies contacted

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