ipowerqueen.fr website review

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

Clarity costs a phone 2.9 s of main-thread work and 31 KiB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

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

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

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

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

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

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

Shopify costs a phone 218 ms of main-thread work and 836 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 160 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.

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

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

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

Polyfills for old browsers add 28 KiB JavaScript that modern phones do not need.

21 KiB JavaScript is shipped twice across bundles.

13 KiB could be saved by minifying CSS.

10 KiB could be saved by minifying JavaScript.

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.

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

Your largest element takes 5.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Jusqu'à 50 % d'économies”.

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

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

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

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

Your homepage downloads 6.4 MB in 488 requests on a phone: images 2.4 MB (42), scripts 2.0 MB (136) and other files 1.3 MB (256). Under 2 MB keeps phones on slow connections fast.

Batterie_Power_Queen_12_V_140_Ah_190_H_LiFePO4_avec_Bluetoot 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).

4 images (658 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.

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

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

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

Interactive controls must not be nested: 1 element on the page fails this check, rated serious by axe-core.

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

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

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

14 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.

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

Your title is 85 characters, so Google will cut it off around 60: “Power Queen FR - Marque Leader Mondiale de Batterie Lithium LiFePO4 – Power Queen® FR”.

Structured data found (Organization) but with 2 problems, for example “Organization: logo is not an absolute URL ("//ipowerqueen.fr/cdn/shop/files/logo_1.webp?v=174529369…”.

The homepage links to 197 pages on ipowerqueen.fr and 16 external pages.

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

4 errors were logged to the browser console while the page loaded, for example “PushEngage: Cannot read properties of undefined (reading 'addEventListener')”.

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

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

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