petitspasdegeant.com website review

15 images could be 632 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.1 s faster on a phone.

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

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

About 118 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 300 ms faster on a phone.

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

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

Klaviyo costs a phone 152 ms of main-thread work and 350 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 third-party services load with your homepage (Klaviyo, JSDelivr CDN and Shopify and others), adding 699 KiB and 350 ms of main-thread time.

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

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

5 KiB could be saved by minifying JavaScript.

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

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

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

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

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

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

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

Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 1.6 s to 1.5 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 3.5 MB in 236 requests on a phone: images 1.8 MB (54), scripts 691 KiB (76) and other files 662 KiB (62). Under 2 MB keeps phones on slow connections fast.

8 images (1.2 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.

image-best-seller.webp 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).

4 images are downloaded at several times the size a phone draws them, for example photo-page-niveau-motricite-3.webp at 390 px wide, shown at 45 px. Resized copies would save about 355 KiB.

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

1 button has no accessible name, so screen readers announce just “button”.

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

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

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 2 elements on the page fail this check, rated moderate by axe-core.

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

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

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

ARIA role should be appropriate for the element: 14 elements on the page fail this check, rated minor by axe-core.

button, link, and menuitem elements do not have accessible names. (2 elements).

There is no <h1>, so neither visitors nor Google get a clear main headline.

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

Structured data found (FAQPage, Organization and WebSite) but with 1 problem, for example “WebSite: potentialAction.target is not an absolute URL ("{search_term_string}")”.

The homepage links to 243 pages on petitspasdegeant.com and 10 external pages.

https://www.petitspasdegeant.com/collections/baskets, https://www.petitspasdegeant.com/collections/babies, https://www.petitspasdegeant.com/collections/bottines, https://www.petitspasdegeant.com/collections/bottes-de-pluie, https://www.petitspasdegeant.com/collections/chaussons and https://www.petitspasdegeant.com/collections/chaussures-fourrees and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.petitspasdegeant.com/collections/tex, https://www.petitspasdegeant.com/collections/sport, https://www.petitspasdegeant.com/collections/randonnee, https://www.petitspasdegeant.com/collections/ceremonie, https://www.petitspasdegeant.com/collections/adultes and https://www.petitspasdegeant.com/collections/sandales took over 3 s to send their HTML from our server.

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

9 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

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.

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

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