didierlab.it website review

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

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

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

8 third-party services load with your homepage (ContentSquare, omnisnippet1.com and PayPal and others), adding 2.8 MB and 2.1 s of main-thread time.

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

40 files are served with short cache lifetimes, so returning visitors download them again (1.6 MB).

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

ContentSquare costs a phone 625 ms of main-thread work and 185 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.

omnisnippet1.com costs a phone 580 ms of main-thread work and 128 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.

PayPal costs a phone 316 ms of main-thread work and 678 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 222 ms of main-thread work and 501 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.

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

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

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

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

22 KiB JavaScript is shipped twice across bundles.

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

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

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.

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

Your largest element takes 7.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

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

Real visitors wait 270 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

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

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

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

Your homepage downloads 6.7 MB in 600 requests on a phone: scripts 2.1 MB (134), images 1.8 MB (50) and other files 1.6 MB (351). Under 2 MB keeps phones on slow connections fast.

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

Delayed refresh under 20 hours must not be used: 1 element on the page fails this check, rated critical by axe-core.

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

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

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

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

Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

Elements with visible text labels do not have matching accessible names. (5 elements).

No meta description, so Google writes its own snippet from whatever text it finds.

Your title is only 15 characters: “DidierLab Italy”. Between 30 and 65 characters leaves room to say what you do and for whom.

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

Your <h1> is empty.

The homepage links to 214 pages on didierlab.it and 9 external pages.

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

https://didierlab.it/policies/shipping-policy, https://didierlab.it/collections/prodotti-senza-hema, https://didierlab.it/collections/rinforzo, https://didierlab.it/collections/allungamento-unghie, https://didierlab.it/collections/manicure-veloce and https://didierlab.it/collections/effetto-naturale and 3 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://didierlab.it/collections/all, https://didierlab.it/collections/prodotti-senza-hema, https://didierlab.it/collections/rinforzo, https://didierlab.it/collections/allungamento-unghie, https://didierlab.it/collections/manicure-veloce and https://didierlab.it/collections/effetto-naturale and 3 others have no <h1> headline, so visitors and search engines get no clear main topic.

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

3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 429 ()”.

Requests the notification permission on page load.

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.

The homepage has only about 10 words of visible text; thin pages give Google and first-time buyers little to go on.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

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