maison-caffet.com website review

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

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

About 199 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.1 s faster on a phone.

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

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

13 files are served with short cache lifetimes, so returning visitors download them again (14.0 MB).

Your mobile performance score is 56 (desktop: 76). Pages that score under 90 lose visitors before the first paint.

8 third-party services load with your homepage (api-and-you.com, Google Tag Manager and Clarity and others), adding 1.2 MB and 768 ms of main-thread time.

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

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

api-and-you.com costs a phone 298 ms of main-thread work and 498 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.

Google Tag Manager costs a phone 248 ms of main-thread work and 341 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.

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

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

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.

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

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

Your largest element takes 21.9 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 29.0 s. Good is under 3.8 s.

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

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

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

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

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

1 image have no width and height attributes, so the layout jumps as each one loads.

Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 148 ms to 162 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 24.9 MB in 188 requests on a phone: media 14.0 MB (9), images 7.4 MB (80) and scripts 2.8 MB (27). Under 2 MB keeps phones on slow connections fast.

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

3 images are downloaded at several times the size a phone draws them, for example ptit_nomade_-_ambiance_pralin_noisette_-_940x840_2025.webp at 940 px wide, shown at 60 px. Resized copies would save about 245 KiB.

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

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

Certain ARIA roles must contain particular children: 1 element on the page fails this check, rated critical by axe-core.

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

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

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

Some list items are not inside a list.

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

ARIA dialog and alertdialog nodes should have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

1 link inside paragraphs relies on colour alone to stand out.

3 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.

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

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

Your title is 91 characters, so Google will cut it off around 60: “Maison Caffet - Chocolaterie en Ligne Artisanale | Vente de Chocolats, Pralinés et Macaro…”.

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

No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

No twitter:card tag. X falls back to Open Graph, which is incomplete here.

The homepage links to 193 pages on maison-caffet.com and 16 external pages.

There is no https://maison-caffet.com/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.

https://maison-caffet.com/en and https://maison-caffet.com/us all use the title “Maison Caffet - Chocolates & Macarons - French Artisan Maker - Online…”. Search engines can't tell which page to show for a search, so each competes with the others.

https://maison-caffet.com/en and https://maison-caffet.com/us use the same meta description. A description written for each page earns more clicks.

https://maison-caffet.com/cadeaux_entreprises has no <h1> headline, so visitors and search engines get no clear main topic.

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

1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=97148860&tm=gtm002&Ver=2&mid=7997ce53-4884-4821-994d-012fd9b6a830&bo=1&sid=7ede0b50d07411f197801fc2a23b6cd1&vid=7ede0ef0d07411f1a5086de2beb644ac&vids=1&msclkid=N&gtm_t.

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

The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

Chrome logged issues while loading the page (“Content security policy”).

Large scripts ship without source maps.

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.

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

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