perlesandco.com website review

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

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

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

Your mobile performance score is 21 (desktop: 58). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

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

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

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

Google CDN costs a phone 172 ms of main-thread work and 295 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 (Google CDN, Optanon and Hotjar and others), adding 743 KiB and 419 ms of main-thread time.

About 54 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 200 ms faster on a phone.

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

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

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

Desktop scores 58 but mobile only 21. A gap that wide usually means heavy scripts and images that hit phones hardest.

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.

3 KiB could be saved by minifying JavaScript.

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.

For real visitors the layout shifts by 0.28 (75th percentile). Good is under 0.1.

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

The layout shifts by 0.856 while loading, so content jumps under the reader's thumb. Good is under 0.1.

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

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

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

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

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

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

Your homepage downloads 6.6 MB in 206 requests on a phone: images 4.1 MB (111), fonts 1.1 MB (8) and scripts 1.1 MB (41). Under 2 MB keeps phones on slow connections fast.

2 images weigh 1.9 MB together. On a phone connection a single image that size takes seconds.

Slide_mobile_promos_oct26_fr.png 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).

3 images (608 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.

9 images are downloaded at several times the size a phone draws them, for example Slide_mobile_promos_oct26_fr.png at 1,127 px wide, shown at 360 px. Resized copies would save about 394 KiB.

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

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

2 dropdowns have no label.

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

1 frame has no title, so screen-reader users cannot tell what it contains.

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

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

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

Alternative text of images should not be repeated as text: 28 elements on the page fail this check, rated minor by axe-core.

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

Your title is 70 characters, so Google will cut it off around 60: “Perles&Co Tout le matériel pour créer vos bijoux fantaisie & Tutos DIY”.

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

The homepage links to 536 pages on perlesandco.com and 11 external pages.

There is no https://www.perlesandco.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://www.perlesandco.com/nouveautes and https://www.perlesandco.com/specials.php all use the title “Perles&Co Tout le matériel pour créer vos bijoux fantaisie & Tutos DIY”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.perlesandco.com/nouveautes and https://www.perlesandco.com/specials.php use the same meta description. A description written for each page earns more clicks.

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

47 of 156 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: the server responded with a status of 404 ()”.

2 images are served at too low a resolution for sharp phone screens.

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.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

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

Before a visitor clicks anything, the page loads Google Ads, Google Tag Manager and Hotjar (measured from a US location before any click). A consent tool (OneTrust) is installed; check it blocks these until visitors agree where the law requires it.

Opening the homepage sets 8 cookies (measured from a US location before any click).

Loading the homepage contacts 19 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.