denaive.com website review

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

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

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

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

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

8 third-party services load with your homepage (Shopify, Clarity and Klaviyo and others), adding 3.0 MB and 747 ms of main-thread time.

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

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

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

16 KiB could be saved by minifying JavaScript.

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

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

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

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

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 22.4 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 33.8 s. Good is under 3.8 s.

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

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

Real visitors wait 262 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-10-31, real Chrome visitors' tap response (inp) went from 160 ms to 263 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

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

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

Your homepage downloads 9.5 MB in 1,237 requests on a phone: images 4.4 MB (509), other files 2.4 MB (401) and scripts 1.7 MB (276). Under 2 MB keeps phones on slow connections fast.

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

ARIA attributes must conform to valid values: 1 element on the page fails this check, rated critical by axe-core.

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

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

All page content should be contained by landmarks: 3 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.

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. (2 elements).

Your title is 84 characters, so Google will cut it off around 60: “Dominique Denaive • Créateur de bijoux fantaisie en résine – Dominique Denaive Paris”.

There are 6 <h1> headlines (“”, “Galerie” and “Boucles Rochelle”). One clear main headline is easier for people and search engines.

Your meta description is 207 characters; Google truncates after about 160, so the end of your pitch is cut.

The homepage links to 238 pages on denaive.com and 3 external pages.

/pages/shop-instagram has no meta description, so Google writes the search snippet from whatever text it finds.

/pages/nos-collections, /pages/nos-bijoux, /pages/devenir-revendeur, /collections/ss25-valse-des-fleurs and /pages/vente-privee-denaive use the same meta description. A description written for each page earns more clicks.

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

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

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

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 longest form asks for 16 fields (0 required). Every extra field lowers completion.

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,764 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 2 mores (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 18 cookies, 1 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 37 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.