ipowerqueen.de website review

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

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

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

8 third-party services load with your homepage (Clarity, Shopify and askstarry.com and others), adding 2.0 MB and 766 ms of main-thread time.

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

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

About 476 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.

Clarity costs a phone 294 ms of main-thread work and 29 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 115 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.

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

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

About 157 KiB of CSS is downloaded but never applied on this page.

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

20 KiB JavaScript is shipped twice across bundles.

13 KiB could be saved by minifying CSS.

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

3 KiB could be saved by minifying JavaScript.

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.

Your largest element takes 9.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “VIP Early Access”.

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

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

Real visitors wait 238 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 198 ms to 320 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.0 s to 1.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 5.1 MB in 332 requests on a phone: images 2.5 MB (52), scripts 1.5 MB (141) and other files 669 KiB (83). Under 2 MB keeps phones on slow connections fast.

10 images (1.1 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.

Power_Queen-Wohnmobil_Camping_320Ah_LiFePO4_Tragbar-768x1280 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.45 g of CO₂e: 174.1 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

1 button has no accessible name, so screen readers announce just “button”.

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

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

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

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

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

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

1 form field has no label, so screen readers announce an empty box and autofill guesses.

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

There is no <h1>, so neither visitors nor Google get a clear main headline.

Your title is 74 characters, so Google will cut it off around 60: “Power Queen DE | LiFePO4 Akku Marktführer ▷ EU-Lieferung – Power Queen® DE”.

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

Structured data found (Organization) but with 2 problems, for example “Organization: logo is not an absolute URL ("//www.ipowerqueen.de/cdn/shop/files/500_120.png?v=17528…”.

The homepage links to 270 pages on ipowerqueen.de and 14 external pages.

/pages/black-friday-mega-sale has no meta description, so Google writes the search snippet from whatever text it finds.

/pages/black-friday-mega-sale, /collections/power-queen-12v-lifepo4-batterien, /products/power-queen-12v-50ah-lifepo4-batterie-eingebautes-50a-bms, /products/power-queen-12-v-100-ah-lifepo4-deep-cycle-batterie, /products/power-queen-12v-100ah-selbstheizende-lifepo4-batterie and /products/power-queen-12v-100ah-niedertemperatur-smart-trolling-motor-lifepo4-batterie and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

/collections/power-queen-12v-lifepo4-batterien, /products/power-queen-12-v-100-ah-lifepo4-deep-cycle-batterie and /products/power-queen-12v-100ah-selbstheizende-lifepo4-batterie took over 3 s to send their HTML from our server.

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

1 error was logged to the browser console while the page loaded, for example “Failed to fetch”.

1 link from your homepage to your own site is broken, for example https://www.ipowerqueen.de/products/power-queen-24v-125ah-smart-lifepo4-bootsbatterie-mit-selbstheizung (network).

1 link to other sites is dead, for example https://support.google.com/analytics/answer/2700409 (404).

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.

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.

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 1,614 words of visible text.

ipowerqueen.de has no SPF record, so mail servers can't tell which servers may send email as you. Your mail lands in spam more often, and anyone can send mail pretending to be you.

DMARC is set to p=none, so mail pretending to be ipowerqueen.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.

ipowerqueen.de has no MX record, so it receives no email. SPF -all and DMARC reject still matter: they stop others sending mail as you.

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 Criteo, Google Ads, Google Analytics, Google Tag Manager and Meta Pixel and 2 mores (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 33 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.