lascal.lu website review

The page goes through 4 redirects before it starts loading, costing about 64.8 s. Link and advertise the final URL directly.

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

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

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

8 third-party services load with your homepage (lascal.net, Google Tag Manager and OptiMonk and others), adding 7.9 MB and 1.4 s of main-thread time.

lascal.net costs a phone 642 ms of main-thread work and 6.3 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.

Google Tag Manager costs a phone 378 ms of main-thread work and 558 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 2,365 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

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

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

The HTML itself could arrive about 200 ms sooner: redirects, a slow server response or missing compression delay everything after it.

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

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

3 KiB could be saved by minifying JavaScript.

Your largest element takes 54.4 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 20.7 s (Speed Index). Good is under 3.4 s.

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

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

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

4 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' tap response (inp) went from 108 ms to 98 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 17.5 MB in 835 requests on a phone: images 10.2 MB (379), scripts 5.1 MB (198) and other files 991 KiB (143). Under 2 MB keeps phones on slow connections fast.

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

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

Some list items are not inside a list.

Links must have discernible text: 1 element on the page fails this check, rated serious by axe-core.

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

The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

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

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

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

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

button, link, and menuitem elements do not have accessible names. (12 elements).

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

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

There is no <h1>, so neither visitors nor Google get a clear main headline.

Your title is 69 characters, so Google will cut it off around 60: “Lascal® - Home of BuggyBoard®, KiddyGuard®, m1 Carrier™ and m1 Buggy™”.

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

Open Graph is missing og:title and og:description, so shared links fall back to guesses.

No twitter:card tag. X falls back to Open Graph, which is incomplete here.

The homepage links to 109 pages on lascal.lu and 35 external pages.

There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

https://lascal.net/collections/buggyboard, https://lascal.net/products/buggyboard-maxi, https://lascal.net/products/buggyboard-maxi-plus, https://lascal.net/products/buggyboard-mini, https://lascal.net/products/buggyboard-mini-3d and https://lascal.net/products/buggyboard-saddle and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://lascal.net/collections/buggyboard, https://lascal.net/products/buggyboard-maxi, https://lascal.net/products/buggyboard-maxi-plus and https://lascal.net/products/buggyboard-mini took over 3 s to send their HTML from our server.

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

Large scripts ship without source maps.

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

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

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