pierrebelvedere.com website review

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

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

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

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

8 images could be 155 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.

4 third-party services load with your homepage (Google Tag Manager, Klaviyo and Shopify and others), adding 560 KiB and 236 ms of main-thread time.

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

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

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

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.

Your largest element takes 7.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 6.4 s (Speed Index). Good is under 3.4 s.

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

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

Your homepage downloads 2.3 MB in 202 requests on a phone: other files 786 KiB (102), scripts 780 KiB (65) and images 525 KiB (15). Under 2 MB keeps phones on slow connections fast.

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

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

Summary elements must have discernible text: 2 elements on the page fail this check, rated serious by axe-core.

All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

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

1 form field has no label, so screen readers announce an empty box and autofill guesses.

Headings skip levels (h2 → h4), which makes the page harder to scan with a screen reader.

Elements with visible text labels do not have matching accessible names. (2 elements).

Your title is 67 characters, so Google will cut it off around 60: “Pierre Belvédère | Educational Toys, Board Games, Puzzles, and More”.

There are 3 <h1> headlines (“”, “” and “Faites place aux soirées jeux !||Let the game nig…”). One clear main headline is easier for people and search engines.

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

1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

The homepage links to 215 pages on pierrebelvedere.com and 7 external pages.

A phone browser shows 2,444 words, but the HTML your server sends has only 571. GPTBot, ClaudeBot and PerplexityBot read that HTML without running JavaScript, so they see an almost empty page. Server-side rendering or pre-rendering fixes it.

https://pierrebelvedere.com/en/pages/devenir-dtaillant, https://pierrebelvedere.com/en/pages/nos-produits, https://pierrebelvedere.com/en/collections/casse-tetes-casse-tete-adulte, https://pierrebelvedere.com/en/collections/casse-tetes-casse-tete-adulte-accessoires, https://pierrebelvedere.com/en/collections/jouets and https://pierrebelvedere.com/en/collections/jouets-bricolage-et-arts and 7 others have no meta description, so Google writes the search snippet from whatever text it finds.

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

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

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

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

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

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