decathlon.cd website review

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

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

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

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

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

Shopify costs a phone 102 ms of main-thread work and 352 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 files block the first paint until they finish downloading. Deferring or inlining them could save about 200 ms.

5 third-party services load with your homepage (Shopify, Google CDN and Cloudflare CDN and others), adding 400 KiB and 133 ms of main-thread time.

1 long task block the main thread while loading, the longest for 73 ms. During a long task the page ignores taps.

8 KiB could be saved by minifying CSS.

7 KiB JavaScript is shipped twice across bundles.

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.

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

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.2 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 9.3 s. Good is under 3.8 s.

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

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

Real visitors wait 282 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-11-07, real Chrome visitors' tap response (inp) went from 167 ms to 227 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Real visitors see the first content after 2.0 s (75th percentile). Good is under 1.8 s.

Real visitors wait 1.3 s for your server to start answering (75th percentile). Good is under 800 ms.

The first text or image appears after 2.0 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 1.9 s to 1.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 3.0 MB in 221 requests on a phone: images 1.4 MB (43), other files 876 KiB (130) and scripts 509 KiB (39). Under 2 MB keeps phones on slow connections fast.

BANNIERE_ROLLER_MO.png 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).

1 image is downloaded at several times the size a phone draws it, for example logo.png at 3,524 px wide, shown at 351 px. Resized copies would save about 54 KiB.

2 images further down the page (172 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

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

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

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

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

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

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

1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

Headings should not be empty: 9 elements on the page fail this check, rated minor by axe-core.

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

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

Your title is 73 characters, so Google will cut it off around 60: “DECATHLON I Magasin de Sport – Decathlon Democratic Republic of the Congo”.

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

The homepage links to 474 pages on decathlon.cd and 5 external pages.

Your Organization JSON-LD is missing logo, sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

https://decathlon.cd/pages/stores has no meta description, so Google writes the search snippet from whatever text it finds.

https://decathlon.cd/pages/stores has no <h1> headline, so visitors and search engines get no clear main topic.

https://decathlon.cd/collections/football took over 3 s to send its HTML from our server.

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

13 of 45 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 “Cannot read properties of undefined (reading 'register')”.

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 analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

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

Before a visitor clicks anything, the page loads Meta Pixel (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 6 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 8 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.