qontroler.com website review

The page goes through 2 redirects before it starts loading, costing about 2.0 s. Link and advertise the final URL directly.

Your mobile performance score is 42. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

8 third-party services load with your homepage (Google Tag Manager, Clarity and Facebook and others), adding 2.4 MB and 760 ms of main-thread time.

1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 700 ms.

29 images could be 325 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.

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

About 306 KiB of JavaScript is downloaded but never used on this page.

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

Shopify costs a phone 0 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.

The HTML itself could arrive about 250 ms sooner: redirects, a slow server response or missing compression delay everything after it.

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

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

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

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

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.

5 KiB could be saved by minifying JavaScript.

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

The layout shifts by 0.737 while loading, so content jumps under the reader's thumb. Good is under 0.1.

Your largest element takes 6.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Z3 Pro, the #1 CPAP alternative — no mask and no hose, no m…”.

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

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

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

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

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

Your homepage downloads 3.2 MB in 167 requests on a phone: images 1.6 MB (85), scripts 1.2 MB (54) and HTML 191 KiB (2). Under 2 MB keeps phones on slow connections fast.

z3v6-15-avant-apres.jpg 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).

2 images are downloaded at several times the size a phone draws them, for example z3v7-avis1.jpg at 1,100 px wide, shown at 342 px. Resized copies would save about 19 KiB.

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

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

Scrollable region must have keyboard access: 4 elements on the page fail this check, rated serious by axe-core.

1 element hidden from screen readers can still receive keyboard focus.

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

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

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

ARIA role should be appropriate for the element: 1 element on the page fails this check, rated minor by axe-core.

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

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

Google's crawler is blocked from indexing this page.

Your meta description is only 59 characters: “Qontroler Z3 Pro, New-generation device with EMS technology”. 70 to 160 characters is enough to sell the click.

Your <h1> is empty.

The homepage links to 58 pages on qontroler.com and 6 external pages.

https://qontroler.com/products/elastic-strap, https://qontroler.com/products/sleeping-patches, https://qontroler.com/products/z3-pro%C2%AE-aloe-vera-confort-gel, https://qontroler.com/pages/reviews, https://qontroler.com/pages/warning-fraudulent-sites and https://qontroler.com/pages/help-center have no meta description, so Google writes the search snippet from whatever text it finds.

Your homepage links to 1 page by a URL that isn't its canonical one, for example https://qontroler.com/products/z3-pro%C2%AE-aloe-vera-confort-gel, whose canonical is https://qontroler.com/products/z3-pro%c2%ae-aloe-vera-confort-gel. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://qontroler.com/pages/reviews, https://qontroler.com/pages/contact, https://qontroler.com/apps/track123, https://qontroler.com/pages/faqs, https://qontroler.com/pages/our-story and https://qontroler.com/pages/warning-fraudulent-sites have no <h1> headline, so visitors and search engines get no clear main topic.

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

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

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 phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

The homepage carries about 2,391 words of visible text.

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

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