klipsit.fr website review

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

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

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

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

8 third-party services load with your homepage (Shopify, heatmap.com and Clarity and others), adding 2.8 MB and 1.2 s of main-thread time.

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

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

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

heatmap.com costs a phone 261 ms of main-thread work and 94 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 long tasks block the main thread while loading, the longest for 258 ms. During a long task the page ignores taps.

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

Google CDN costs a phone 116 ms of main-thread work and 298 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.

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

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

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

4 KiB could be saved by minifying CSS.

Your largest element takes 16.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Build My Bear Hero Image”.

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

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

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

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

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

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-11-07, real Chrome visitors' largest content (lcp) went from 1.1 s to 1.1 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 5.7 MB in 379 requests on a phone: images 2.5 MB (37), scripts 1.6 MB (73) and other files 1.1 MB (249). Under 2 MB keeps phones on slow connections fast.

14 images are downloaded at several times the size a phone draws them, for example Publication_Instagram_Lorena_12.webp at 3,375 px wide, shown at 390 px. Resized copies would save about 1.6 MB.

Publication_Instagram_Lorena_12.webp weighs 610 KiB. On a phone connection a single image that size takes seconds.

7 images (1.3 MB) 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.

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

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

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

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.

ARIA role should be appropriate for the element: 1 element on the page fails this check, rated minor by axe-core.

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

Your title is 88 characters, so Google will cut it off around 60: “Klips’it™️ Ours en brique Géant à Assembler – Klips’it™ Ours en brique Géant à Assembler”.

There are 2 <h1> headlines (“” and “Libère ton âme de créateur avec Klipsit”). One clear main headline is easier for people and search engines.

The homepage links to 63 pages on klipsit.fr and 0 external pages.

A phone browser shows 1,603 words, but the HTML your server sends has only 415. GPTBot, ClaudeBot and PerplexityBot read that HTML without running JavaScript, so they see an almost empty page. Server-side rendering or pre-rendering fixes it.

https://klipsit.fr/customer_authentication/redirect has no <title>, so Google invents the link text in results.

https://klipsit.fr/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

https://klipsit.fr/customer_authentication/redirect has no meta description, so Google writes the search snippet from whatever text it finds.

https://klipsit.fr/collections/bestsellers, https://klipsit.fr/pages/a-propos-de-nous-1, https://klipsit.fr/apps/parcelpanel, https://klipsit.fr/pages/contact, https://klipsit.fr/collections/all and https://klipsit.fr/products/original-bear and 8 others use the same meta description. A description written for each page earns more clicks.

https://klipsit.fr/pages/a-propos-de-nous-1, https://klipsit.fr/apps/parcelpanel, https://klipsit.fr/pages/contact and https://klipsit.fr/customer_authentication/redirect have no <h1> headline, so visitors and search engines get no clear main topic.

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

1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.

3 errors were logged to the browser console while the page loaded, for example “Uncaught Error: Goaffpro is already loaded. This message prevents duplicate loading of the script. Kindly ignore.”.

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.

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

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

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