gualap.com website review

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

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

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

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

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

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

16 long tasks block the main thread while loading, the longest for 1.2 s. During a long task the page ignores taps.

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

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

7 third-party services load with your homepage (Facebook, Klaviyo and Google Tag Manager and others), adding 862 KiB and 551 ms of main-thread time.

Klaviyo costs a phone 169 ms of main-thread work and 324 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.

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

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.

Your largest element takes 11.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “La veste Cécilia”. Most of its time is resource load delay (10.6 s).

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

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

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

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

Real visitors wait 3.1 s for the largest content to appear (75th percentile). Good is under 2.5 s.

Real visitors see the first content after 1.9 s (75th percentile). Good is under 1.8 s.

Real visitors wait 1.3 s for your server to start answering (75th percentile). Good is under 800 ms.

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

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

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

Your homepage downloads 2.4 MB in 76 requests on a phone: scripts 1.1 MB (36), images 658 KiB (16) and fonts 338 KiB (7). Under 2 MB keeps phones on slow connections fast.

8 images are downloaded at several times the size a phone draws them, for example le-top-clara-noir.jpg at 540 px wide, shown at 178 px. Resized copies would save about 12 KiB.

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

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

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

1 tap target is too small or too close together to hit reliably with a finger.

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

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.

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

1 visible link has no text or label, so screen readers cannot say where it goes.

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

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

Your title is only 10 characters: “Nouveautés”. Between 30 and 65 characters leaves room to say what you do and for whom.

No XML sitemap at https://gualap.com/sitemap.xml, so Google discovers your pages only by following links.

The homepage links to 526 pages on gualap.com and 12 external pages.

Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

There is no https://gualap.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.

Your homepage links to https://gualap.com/fr/39-pulls-t-shirts-oversize and https://gualap.com/fr/42-tenue-de-ceremonie, which answer with an error. Visitors hit a dead end and search engines drop them.

https://gualap.com/fr/16-nos-bestsellers and https://gualap.com/fr/31-tous-les-vetements use the same meta description. A description written for each page earns more clicks.

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

1 image failed to load on a phone, for example https://gualap.com/img/cms/gualap-fashion-family-logo.png.

2 errors were logged to the browser console while the page loaded, for example “$(...).masonry is not a function”.

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.

Social proof on the homepage: a star rating. Pairing it with named testimonials or customer logos makes it far more convincing.

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

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