kappa.fr website review

Google Tag Manager costs a phone 1.2 s of main-thread work and 875 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.

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

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 9.5 s on main-thread work while loading, 4.9 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

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

8 third-party services load with your homepage (Google Tag Manager, Klaviyo and Clarity and others), adding 5.7 MB and 2.6 s of main-thread time.

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

About 843 KiB of JavaScript is downloaded but never used on this page.

114 KiB could be saved by minifying CSS.

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

Shopify costs a phone 129 ms of main-thread work and 3.7 MB 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.

Clarity costs a phone 466 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.

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

azurefd.net costs a phone 51 ms of main-thread work and 320 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.

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

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

Polyfills for old browsers add 19 KiB JavaScript that modern phones do not need.

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

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 12.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “SKI COLLECTION”.

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

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

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

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

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

1 image 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 209 ms to 249 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 11.2 MB in 512 requests on a phone: images 4.2 MB (116), media 2.8 MB (1) and scripts 2.3 MB (127). Under 2 MB keeps phones on slow connections fast.

1080x1350_-_2026-10-22T124954.031.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).

By the Sustainable Web Design model, a visit to your homepage emits about 3.18 g of CO₂e: 381.9 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”.

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

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

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

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

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

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

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

Structured data found (Organization and WebSite) but with 1 problem, for example “Organization: logo is not an absolute URL ("//www.kappa.com/cdn/shop/files/logo-kappa-png.png?heigh…”.

1 link has no real href, so search engines can't follow it.

The homepage links to 965 pages on kappa.fr and 6 external pages.

https://www.kappa.com/en-us and / all use the title “Kappa: Casual and sports clothing, shoes, accessories”. Search engines can't tell which page to show for a search, so each competes with the others.

Your homepage links to 1 page by a URL that isn't its canonical one, for example /, whose canonical is https://www.kappa.com/en-us. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://www.kappa.com/en-us/pages/black-friday, https://www.kappa.com/en-us/collections/special-team-days, https://www.kappa.com/en-us/pages/kappa-welcome, https://www.kappa.com/en-us/pages/authentic, https://www.kappa.com/en-us/pages/robe-di-kappa and https://www.kappa.com/en-us/pages/men and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

We fetched 15 pages linked from your homepage (of 197 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=295009998&tm=gtm002&Ver=2&mid=23dff347-014d-40c4-b712-8b84aecc1ab9&bo=1&sid=a5a502e0d7bf11f19ed807c264b2633c&vid=a5a4eb40d7bf11f19376130aab7107c4&vids=1&msclkid=N&pi=9.

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

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

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.

The homepage carries about 674 words of visible text.

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

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

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