luxeol.com website review

35 images could be 2.5 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 3.5 s faster on a phone.

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

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

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

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

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

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

8 third-party services load with your homepage (join-stories.com, Klaviyo and Didomi and others), adding 1.4 MB and 931 ms of main-thread time.

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

Shopify costs a phone 115 ms of main-thread work and 386 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 174 ms. During a long task the page ignores taps.

14 KiB could be saved by minifying CSS.

23 KiB could be saved by minifying JavaScript.

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

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 31.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “We and our partners store and access non-sensitive informat…”.

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

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

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

Real visitors wait 3.1 s for the largest content to appear (75th percentile). Good is under 2.5 s.

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

Real visitors see the first content after 1.9 s (75th percentile). Good is under 1.8 s.

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

Your homepage downloads 14.0 MB in 310 requests on a phone: media 6.1 MB (1), images 4.4 MB (56) and scripts 1.8 MB (95). Under 2 MB keeps phones on slow connections fast.

4 images (500 KiB) 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.

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

21 buttons have no accessible name, so screen readers announce just “button”.

Certain ARIA roles must contain particular children: 1 element on the page fails this check, rated critical by axe-core.

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

Some lists contain elements other than list items, which screen readers announce wrongly.

ARIA dialog and alertdialog nodes should have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

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

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.

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

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

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

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

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

The homepage links to 176 pages on luxeol.com and 12 external pages.

The HTML your server sends has 639 of the 1,311 words a browser shows. AI crawlers don't run JavaScript, so they miss the rest.

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

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

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

https://luxeol.com/pages/notre-marque, https://luxeol.com/pages/fidelite and https://luxeol.com/collections/offres use the same meta description. A description written for each page earns more clicks.

https://luxeol.com/collections/meilleures-ventes, https://luxeol.com/pages/notre-marque, https://luxeol.com/pages/fidelite, https://luxeol.com/customer_authentication/redirect, https://luxeol.com/collections/routines and https://luxeol.com/collections/produits-primes and 4 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://luxeol.com/customer_authentication/redirect took over 3 s to send its HTML from our server.

We fetched 15 pages linked from your homepage (of 71 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: net::ERR_FAILED”.

Large scripts ship without source maps.

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: a star rating. Pairing it with named testimonials or customer logos makes it far more convincing.

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

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

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

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