pepperfield.fr website review

ContentSquare costs a phone 1.6 s of main-thread work and 197 KiB of downloads while your page loads. That alone is enough to make taps feel slow. 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 14.4 s on main-thread work while loading, 8.3 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

8 third-party services load with your homepage (ContentSquare, Clarity and Shopify and others), adding 2.3 MB and 3.6 s of main-thread time.

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

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

Clarity costs a phone 611 ms of main-thread work and 29 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 files are served with short cache lifetimes, so returning visitors download them again (605 KiB).

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

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

stape.net costs a phone 326 ms of main-thread work and 327 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.

appstle.com costs a phone 339 ms of main-thread work and 89 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.

6 images could be 252 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

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

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

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

1 KiB JavaScript is shipped twice across bundles.

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

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

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

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

Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

Your homepage downloads 4.8 MB in 379 requests on a phone: scripts 2.3 MB (148), other files 1.4 MB (184) and images 785 KiB (30). Under 2 MB keeps phones on slow connections fast.

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

1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

9 images have no alt text, which hurts accessibility and image search.

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

4 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 page has no <title>, so Google has to invent the blue link in search results.

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

The homepage links to 172 pages on pepperfield.fr and 7 external pages.

https://pepperfield.fr/apps/wishlist, https://pepperfield.fr/pages/inscription, https://pepperfield.fr/pages/recommandez-a-un-ami, https://pepperfield.fr/collections/tous-les-produits, https://pepperfield.fr/collections/sel-de-kampot and https://pepperfield.fr/collections/cadeau-emballage and 8 others have no <title>, so Google invents the link text in results.

https://pepperfield.fr/apps/wishlist and https://pepperfield.fr/pages/inscription have no meta description, so Google writes the search snippet from whatever text it finds.

https://pepperfield.fr/pages/recommandez-a-un-ami, https://pepperfield.fr/collections/tous-les-produits, https://pepperfield.fr/collections/sel-de-kampot, https://pepperfield.fr/collections/cadeau-emballage, https://pepperfield.fr/collections/tous-les-produits-1 and https://pepperfield.fr/collections/poivre-de-kampot have no <h1> headline, so visitors and search engines get no clear main topic.

https://pepperfield.fr/pages/recommandez-a-un-ami, https://pepperfield.fr/collections/tous-les-produits and https://pepperfield.fr/collections/tous-les-produits-1 have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

https://pepperfield.fr/apps/wishlist took over 3 s to send its HTML from our server.

We fetched 15 pages linked from your homepage (of 66 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=355051548&Ver=2&mid=2384f3c6-e637-479a-9e58-86a0991f6c4b&bo=3&sid=078516e0ddc711f180560fc763455719&vid=07853330ddc711f1989d976faa4419b5&vids=1&msclkid=N&pagetype=home&.

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

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

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.

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

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