lecyclo.com website review

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

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

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

8 third-party services load with your homepage (Google Tag Manager, Yotpo and Kaltura Video Platform and others), adding 2.3 MB and 1.4 s of main-thread time.

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

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

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

Google Tag Manager costs a phone 517 ms of main-thread work and 526 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.

Yotpo costs a phone 375 ms of main-thread work and 548 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.

Kaltura Video Platform costs a phone 236 ms of main-thread work and 581 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.

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

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

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

1 image could be 58 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

21 KiB could be saved by minifying JavaScript.

Polyfills for old browsers add 8 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.

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

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

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

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

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

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

17 images 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' largest content (lcp) went from 1.6 s to 1.6 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 5.8 MB in 227 requests on a phone: images 2.7 MB (19), scripts 2.0 MB (58) and other files 796 KiB (124). Under 2 MB keeps phones on slow connections fast.

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

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

3 elements hidden from screen readers can still receive keyboard focus.

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

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

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

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

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

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

The homepage links to 735 pages on lecyclo.com and 13 external pages.

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

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

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

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

https://www.lecyclo.com/customer_authentication/redirect, https://www.lecyclo.com/collections/sacoches-velo, https://www.lecyclo.com/collections/sacoche-porte-bagages, https://www.lecyclo.com/collections/sacoche-double-velo, https://www.lecyclo.com/collections/sacoche-guidon and https://www.lecyclo.com/collections/sacoche-selle 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 197 found) and read each the way a search engine does.

4 images failed to load on a phone, for example https://www.lecyclo.com/.

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

The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

5 errors were logged to the browser console while the page loaded, for example “An error has been thrown while configuring your widget AbortError: signal is aborted without reason AbortError: signal …”.

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

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