sonxplusvaldessources.com website review

About 595 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 4.3 s faster on a phone.

hcaptcha.com costs a phone 1.0 s of main-thread work and 1.2 MB 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.

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

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

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

7 third-party services load with your homepage (hcaptcha.com, Shopify and qikify.com and others), adding 2.5 MB and 1.4 s of main-thread time.

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

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

Polyfills for old browsers add 78 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 350 ms faster on a phone.

Shopify costs a phone 310 ms of main-thread work and 1.1 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 page has 1,818 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

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

2 images could be 34 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 100 ms faster on a phone.

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.

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

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

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

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

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

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

Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

Your homepage downloads 4.1 MB in 321 requests on a phone: scripts 2.1 MB (160), other files 839 KiB (122) and HTML 529 KiB (5). Under 2 MB keeps phones on slow connections fast.

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

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

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

Elements must only use permitted ARIA attributes: 1 element on the page fails this check, rated serious by axe-core.

18 elements use ARIA attributes their role does not allow, which confuses screen readers.

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

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

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

Elements with role="dialog" or role="alertdialog" do not have accessible names. (1 element).

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

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

Your title is 76 characters, so Google will cut it off around 60: “SONXPLUS Val-des-Sources | Magasin d’Électronique — Sonxplus Val-des-sources”.

There are 2 <h1> headlines (“Découvrez tous nos téléviseurs” and “VENDREDI FOU : on monte le volume!Profitez de rab…”). One clear main headline is easier for people and search engines.

4 links have no real href, so search engines can't follow them.

The homepage links to 122 pages on sonxplusvaldessources.com and 8 external pages.

There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

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

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

https://www.sonxplusvaldessources.com/customer_authentication/redirect, https://www.sonxplusvaldessources.com/collections/all, https://www.sonxplusvaldessources.com/collections/bravia-7-ii, https://www.sonxplusvaldessources.com/collections/bravia-9-ii, https://www.sonxplusvaldessources.com/collections/bravia-6 and https://www.sonxplusvaldessources.com/collections/bravia-3-ii and 1 other 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://www.sonxplusvaldessources.com/collections/r85h/products/samsung-mrn85r85hafxzc-televiseur-85-micro-rgb-anti-reflet-4k-144hz-serie-r85h, whose canonical is https://www.sonxplusvaldessources.com/products/samsung-mrn85r85hafxzc-televiseur-85-micro-rgb-anti-reflet-4k-144hz-serie-r85h. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://www.sonxplusvaldessources.com/customer_authentication/redirect and https://www.sonxplusvaldessources.com/collections/r85h/products/samsung-mrn85r85hafxzc-televiseur-85-micro-rgb-anti-reflet-4k-144hz-serie-r85h have no <h1> headline, so visitors and search engines get no clear main topic.

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

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

3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 403 ()”.

Requests the geolocation permission on page load.

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 testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

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

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

Before a visitor clicks anything, the page loads Google Analytics and Google Tag Manager (measured from a US location before any click). A consent tool (CookieYes) is installed; check it blocks these until visitors agree where the law requires it.

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

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