lab9.be website review

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

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

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

8 third-party services load with your homepage (Klaviyo, Facebook and Adobe Tag Manager and others), adding 2.6 MB and 732 ms of main-thread time.

17 files block the first paint until they finish downloading. Deferring or inlining them could save about 550 ms.

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

About 406 KiB of JavaScript is downloaded but never used on this page.

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

Klaviyo costs a phone 196 ms of main-thread work and 508 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 49 ms of main-thread work and 1.5 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.

About 82 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.

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

Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).

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

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

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

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

Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 1.5 s to 1.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

The layout shifts by 0.21 while loading, so content jumps under the reader's thumb. Good is under 0.1.

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

3 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 187 ms to 213 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 5.2 MB in 368 requests on a phone: images 1.8 MB (26), scripts 1.6 MB (131) and other files 986 KiB (152). Under 2 MB keeps phones on slow connections fast.

5 images are downloaded at several times the size a phone draws them, for example IMG-21451512_m_jpeg_1.jpg at 4,000 px wide, shown at 246 px. Resized copies would save about 1.4 MB.

IMG-21451512_m_jpeg_1.jpg weighs 964 KiB. On a phone connection a single image that size takes seconds.

Energy_Label_iPad_mini_A20_Pro_Wi-Fi_A3595.png is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

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

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

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

Some list items are not inside a list.

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

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

Elements marked as presentational should be consistently ignored: 1 element on the page fails this check, rated minor by axe-core.

Your title is only 28 characters: “Lab9 - Apple Premium Partner”. Between 30 and 65 characters leaves room to say what you do and for whom.

9 links have no real href, so search engines can't follow them.

The homepage links to 52 pages on lab9.be and 5 external pages.

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

https://www.lab9.be/pages/winkels-store-locator and https://www.lab9.be/pages/winkels-overzicht all use the title “Vind een winkel | Lab9 - Apple Premium Partner”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.lab9.be/collections/macbook-pro-proled-xdr-display has no meta description, so Google writes the search snippet from whatever text it finds.

https://www.lab9.be/pages/winkels-store-locator and https://www.lab9.be/pages/winkels-overzicht use the same meta description. A description written for each page earns more clicks.

Your homepage links to 1 page by a URL that isn't its canonical one, for example https://www.lab9.be/pages/winkels-overzicht, whose canonical is https://www.lab9.be/pages/winkels-store-locator. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://www.lab9.be/pages/winkels-store-locator and https://www.lab9.be/pages/winkels-overzicht have no <h1> headline, so visitors and search engines get no clear main topic.

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

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

3 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

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

3 errors were logged to the browser console while the page loaded, for example “pandectes-rules: could not find pandectesRulesSettings TypeError: Cannot read properties of undefined (reading 'length')”.

Requests the geolocation permission on page load.

Chrome logged issues while loading the page (“Cookie”).

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

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

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