laconicum.fr website review

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

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

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

8 third-party services load with your homepage (Shopify, Klaviyo and Clarity and others), adding 1.0 MB and 536 ms of main-thread time.

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

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

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

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

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

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

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

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

About 19 KiB of CSS is downloaded but never applied on this page.

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.

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

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

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

Your largest element takes 3.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Ultra-Cleanser”. Most of its time is resource load delay (2.6 s).

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 2.4 s to 2.5 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 2.3 MB in 174 requests on a phone: scripts 1.1 MB (82), other files 661 KiB (63) and images 339 KiB (15). Under 2 MB keeps phones on slow connections fast.

1 image further down the page (20 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

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

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

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

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

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

1 form field has no label, so screen readers announce an empty box and autofill guesses.

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

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

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

The homepage links to 245 pages on laconicum.fr and 7 external pages.

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

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

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

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

https://laconicum.com/customer_authentication/redirect and https://laconicum.com/pages/coni have no <h1> headline, so visitors and search engines get no clear main topic.

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

1 image failed to load on a phone, for example https://laconicum.com/.

6 of 20 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

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

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 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 557 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 23 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 34 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.