zapaka.fr website review

About 1.1 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 3.7 s faster on a phone.

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

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

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

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

17 images could be 1.4 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 450 ms faster on a phone.

8 third-party services load with your homepage (YouTube, cloudfront.net and growave.io and others), adding 2.7 MB and 1.2 s of main-thread time.

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

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

YouTube costs a phone 436 ms of main-thread work and 1,019 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.

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

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

17 long tasks block the main thread while loading, the longest for 184 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).

15 KiB could be saved by minifying CSS.

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 30.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “ZAPAKA FR”.

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

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

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

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

6 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' largest content (lcp) went from 2.2 s to 2.4 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 128.4 MB in 344 requests on a phone: media 117.7 MB (36), images 6.9 MB (103) and scripts 2.5 MB (82). Under 2 MB keeps phones on slow connections fast.

23 images are downloaded at several times the size a phone draws them, for example 85c42c87b9473e9b6fce8713fa9bbb54.jpg at 1,296 px wide, shown at 390 px. Resized copies would save about 2.3 MB.

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

4 elements use ARIA attributes their role does not allow, which confuses screen readers.

Certain ARIA roles must contain particular children: 4 elements on the page fail this check, rated critical by axe-core.

ARIA attributes must conform to valid values: 4 elements on the page fail this check, rated critical by axe-core.

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

1 dropdown has no label.

34 elements hidden from screen readers can still receive keyboard focus.

Interactive controls must not be nested: 5 elements on the page fail this check, rated serious by axe-core.

ARIA input fields must have an accessible name: 4 elements on the page fail this check, rated serious by axe-core.

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

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

<html> element must have a lang attribute: 1 element on the page fails this check, rated serious by axe-core.

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

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

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

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

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

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

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

The <html> element has no lang attribute, so screen readers may read the page in the wrong voice and accent.

Elements marked as presentational should be consistently ignored: 4 elements on the page fail this check, rated minor by axe-core.

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

Your title is 69 characters, so Google will cut it off around 60: “Robes Vintages Pour Femme et accessoires rétro rockabilly | ZAPAKA FR”.

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

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

No twitter:card tag. X falls back to Open Graph, which is incomplete here.

The homepage links to 356 pages on zapaka.fr and 28 external pages.

There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

https://zapaka.fr/collections/nouveau-produit, https://zapaka.fr/collections/robes-en-vedette, https://zapaka.fr/collections/robes-de-soiree-en-stock, https://zapaka.fr/collections/toutes-les-robes and https://zapaka.fr/collections/robes-de-bureau have no meta description, so Google writes the search snippet from whatever text it finds.

https://zapaka.fr/collections/nouveau-produit, https://zapaka.fr/collections/robe-de-soiree, https://zapaka.fr/collections/robes-blanches, https://zapaka.fr/collections/robes-de-mariee, https://zapaka.fr/collections/robes-en-vedette and https://zapaka.fr/collections/robes-demoiselle-dhonneur and 6 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://zapaka.fr/collections/robes-de-mariee and https://zapaka.fr/collections/robe-de-cocktail 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.

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

6 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

Chrome logged issues while loading the page (“Cookie”).

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.

Social proof on the homepage: 1 trust badge. Pairing it with named testimonials or customer logos makes it far more convincing.

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

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