joyeuxliens.com website review

39 images could be 1.8 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 2.5 s faster on a phone.

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

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

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

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

8 third-party services load with your homepage (Shopify, Google Tag Manager and cloudfront.net and others), adding 3.3 MB and 698 ms of main-thread time.

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

5 files block the first paint until they finish downloading. Deferring or inlining them could save about 600 ms.

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

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

cloudfront.net costs a phone 90 ms of main-thread work and 1.5 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.

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

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

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 37.5 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 38.6 s. Good is under 3.8 s.

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

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

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

Real visitors wait 219 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

Real visitors see the first content after 1.9 s (75th percentile). 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 2.7 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 8.4 MB in 362 requests on a phone: images 5.0 MB (65), other files 1.5 MB (174) and scripts 1.4 MB (104). Under 2 MB keeps phones on slow connections fast.

2 images weigh 1.9 MB together. On a phone connection a single image that size takes seconds.

1 image is downloaded at several times the size a phone draws it, for example 29be5da44cf2ea1f4314f12a2893074a.png at 1,035 px wide, shown at 270 px. Resized copies would save about 505 KiB.

4 images (2.1 MB) are JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.

2.gif 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).

11 images further down the page (309 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 2.39 g of CO₂e: 286.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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

6 elements hidden from screen readers can still receive keyboard focus.

autocomplete attribute must be used correctly: 1 element on the page fails this check, rated serious by axe-core.

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

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

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

Alternative text of images should not be repeated as text: 7 elements on the page fail this check, rated minor by axe-core.

Your title is 84 characters, so Google will cut it off around 60: “JoyeuxLiens - Créez des souvenirs uniques avec nos cadeaux personnalis – joyeuxliens”.

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

The homepage links to 289 pages on joyeuxliens.com and 35 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.joyeuxliens.com/pages/track-order, https://www.joyeuxliens.com/collections/sweat-shirt-de-noel, https://www.joyeuxliens.com/collections/sweat-de-noel-pour-animaux, https://www.joyeuxliens.com/collections/puzzle, https://www.joyeuxliens.com/collections/sac and https://www.joyeuxliens.com/collections/ornements-noel and 8 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.joyeuxliens.com/pages/track-order, https://www.joyeuxliens.com/collections/sweat-shirt-de-noel, https://www.joyeuxliens.com/collections/sweat-de-noel-pour-animaux, https://www.joyeuxliens.com/collections/puzzle, https://www.joyeuxliens.com/collections/sac and https://www.joyeuxliens.com/collections/ornements-noel and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

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

2 images failed to load on a phone, for example https://www.joyeuxliens.com/.

2 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://dkov91l6wait7.cloudfront.net/intl-tel-input/intlTelInput.css' from origin 'https:/…”.

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.

Social proof on the homepage: 87 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

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

Before a visitor clicks anything, the page loads Google Ads, Google Analytics and Google Tag Manager (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 9 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 24 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.