artsdelices.com website review

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

8 third-party services load with your homepage (PayPal, POWr and Shopify and others), adding 1.1 MB and 893 ms of main-thread time.

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

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

PayPal costs a phone 321 ms of main-thread work and 395 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.

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

About 329 KiB of JavaScript is downloaded but never used on this page.

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

POWr costs a phone 291 ms of main-thread work and 13 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.

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

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

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

About 25 KiB of CSS is downloaded but never applied on this page.

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

6 KiB could be saved by minifying CSS.

6 KiB could be saved by minifying JavaScript.

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.

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

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

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

Your homepage downloads 2.6 MB in 317 requests on a phone: scripts 898 KiB (135), other files 791 KiB (119) and images 359 KiB (18). Under 2 MB keeps phones on slow connections fast.

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

Form elements must have labels: 1 element on the page fails this check, rated critical by axe-core.

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

Main landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.

Document should not have more than one main landmark: 1 element on the page fails 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.

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

Your title is 66 characters, so Google will cut it off around 60: “Arts'Délices | Vanille Bourbon, épices de Madagascar et d'ailleurs”.

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

No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

Your <h1> is empty.

The homepage links to 65 pages on artsdelices.com and 1 external page.

https://www.artsdelices.com/blogs/infos and https://www.artsdelices.com/pages/points-de-vente have no meta description, so Google writes the search snippet from whatever text it finds.

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

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

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.

A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

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.

The homepage shows no opening hours. If customers visit or call, show when.

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 454 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 22 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.