redodopower.de website review

18 images could be 987 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.9 s faster on a phone.

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

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

8 third-party services load with your homepage (Clarity, Shopify and loox.io and others), adding 2.9 MB and 1.6 s of main-thread time.

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

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

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

Clarity costs a phone 445 ms of main-thread work and 28 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.

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

Shopify costs a phone 252 ms of main-thread work and 602 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.

askstarry.com costs a phone 117 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.

PayPal costs a phone 172 ms of main-thread work and 389 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.

Klaviyo costs a phone 104 ms of main-thread work and 306 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.

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

18 KiB could be saved by minifying CSS.

3 KiB could be saved by minifying JavaScript.

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

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

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 see the first content after 3.0 s (75th percentile). Good is under 1.8 s.

Your largest element takes 15.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Redodo Black Friday Angebote 2026 für LiFePO4 Batterien”.

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

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

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

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

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

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

Your homepage downloads 6.5 MB in 354 requests on a phone: images 2.7 MB (74), scripts 2.3 MB (140) and other files 755 KiB (108). Under 2 MB keeps phones on slow connections fast.

12 images (1.3 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.

redodo-12v-100ah-h168-kompakte-bauhoehe-m.webp 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).

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

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

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

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

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

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

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

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

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

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

Elements with visible text labels do not have matching accessible names. (1 element).

Your title is 68 characters, so Google will cut it off around 60: “Redodos offizielles Geschäft - Die besten LiFePO4 & Lithium Batterie”.

Your meta description is 243 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: logo is not an absolute URL ("//www.redodopower.de/cdn/shop/files/RO_logo.png?v=17485…”.

2 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

The homepage links to 367 pages on redodopower.de and 29 external pages.

/pages/redodo-batterie-kaufen and /pages/redodo-black-friday-angebote all use the title “Redodo Black Friday Sale 2026 – Jetzt LiFePO4 Deals sichern!”. Search engines can't tell which page to show for a search, so each competes with the others.

/pages/widerrufsrecht has no meta description, so Google writes the search snippet from whatever text it finds.

/pages/redodo-batterie-kaufen and /pages/redodo-black-friday-angebote use the same meta description. A description written for each page earns more clicks.

/pages/redodo-batterie-kaufen, /pages/redodo-black-friday-angebote, /pages/redodo-geschichte, /blogs/blogs, /blogs/kundengeschichten and /pages/garantie-registrieren and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

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

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

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

2 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

HSTS is set, but max-age is 91 days; one year is the recommended minimum.

No Referrer-Policy header, so full URLs can leak to the sites you link to.

No Permissions-Policy header to switch off camera, microphone and location for embedded content.

X-XSS-Protection is set to “1; mode=block”; the header is deprecated and can introduce bugs. Use 0 or remove it.

There is no /.well-known/security.txt telling researchers how to report a security problem to you.

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

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust 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 1,543 words of visible text.

DMARC is set to p=none, so mail pretending to be redodopower.de is still delivered. Add a report address, check the reports, then move to quarantine.

We found no DKIM key on the selectors the big email providers use. If you send through one of them, turning on DKIM signing improves delivery.

Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

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

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