decoinparis.be website review

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

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

8 third-party services load with your homepage (Shopify, Cookiebot and Clarity and others), adding 1.7 MB and 1.6 s of main-thread time.

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

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

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

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

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

Cookiebot costs a phone 455 ms of main-thread work and 41 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.

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

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

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

Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).

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

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

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

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

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

13 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 23.0 MB in 472 requests on a phone: media 17.4 MB (4), images 1.7 MB (49) and scripts 1.7 MB (120). Under 2 MB keeps phones on slow connections fast.

1 image further down the page (27 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

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

2 buttons have no accessible name, so screen readers announce just “button”.

1 element use ARIA attributes their role does not allow, which confuses screen readers.

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

Some lists contain elements other than list items, which screen readers announce wrongly.

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

1 tap target is too small or too close together to hit reliably with a finger.

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

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.

button, link, and menuitem elements do not have accessible names. (2 elements).

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

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

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

Structured data found (FurnitureStore, Organization and WebSite) but with 1 problem, for example “Organization: url points at a different host (https://decoinparis.com)”.

The homepage links to 283 pages on decoinparis.be and 13 external pages.

https://decoinparis.be/collections/black-november has no meta description, so Google writes the search snippet from whatever text it finds.

We fetched 15 pages linked from your homepage (of 120 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 load resource: net::ERR_FAILED”.

Requests the notification 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.

Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

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

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

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

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