laguildeculinaire.com website review

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

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

8 third-party services load with your homepage (Shopify, Google Tag Manager and TikTok and others), adding 2.1 MB and 1.0 s of main-thread time.

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

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

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

Shopify costs a phone 340 ms of main-thread work and 925 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 298 ms of main-thread work and 684 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.

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

About 43 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 150 ms).

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

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

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

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

2 KiB could be saved by minifying CSS.

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.

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

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

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

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

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

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

Your homepage downloads 4.9 MB in 366 requests on a phone: scripts 1.9 MB (129), images 1.3 MB (69) and other files 1.0 MB (140). Under 2 MB keeps phones on slow connections fast.

8 images (395 KiB) 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.

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

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

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

Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious 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.

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

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

Your title is 89 characters, so Google will cut it off around 60: “Cours de cuisine et magasin d'accessoires pour passionnés gourmands – La Guilde Culinaire”.

28 links have no real href, so search engines can't follow them.

The homepage links to 1,292 pages on laguildeculinaire.com and 14 external pages.

https://www.laguildeculinaire.com/customer_authentication/redirect has no <title>, so Google invents the link text in results.

https://www.laguildeculinaire.com/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

https://www.laguildeculinaire.com/policies/shipping-policy, https://www.laguildeculinaire.com/pages/nos-magasins, https://www.laguildeculinaire.com/customer_authentication/redirect and https://www.laguildeculinaire.com/collections/all have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.laguildeculinaire.com/customer_authentication/redirect, https://www.laguildeculinaire.com/collections/all, https://www.laguildeculinaire.com/collections/nouveautes, https://www.laguildeculinaire.com/collections/coups-de-coeur, https://www.laguildeculinaire.com/collections/les-essentiels-en-cuisine and https://www.laguildeculinaire.com/collections/idees-cadeaux have no <h1> headline, so visitors and search engines get no clear main topic.

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

3 images failed to load on a phone, for example https://bat.bing.net/action/0?ti=56382557&Ver=2&mid=9f88bd4f-bdcd-4cd8-99c6-4929a9ced0a4&bo=3&pi=918639831&lg=en-US&sw=390&sh=844&sc=24&nwd=1&tl=Cours%20de%20cuisine%20et%20magasin%20d%27accessoires%2.

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

1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.

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

Chrome logged issues while loading the page (“Cookie”).

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 phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

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

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