lapperre.be website review

44 files are served with short cache lifetimes, so returning visitors download them again (1,012 KiB).

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

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

10 images could be 615 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 450 ms faster on a phone.

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

8 third-party services load with your homepage (Google Tag Manager, Optanon and Clarity and others), adding 1.5 MB and 584 ms of main-thread time.

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

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

contentstack.com costs a phone 0 ms of main-thread work and 759 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.

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

Polyfills for old browsers add 21 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.

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

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 15.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “M_Headerbeeld_HP_485x800_FRx2.webp”.

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

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

Real visitors wait 920 ms for your server to start answering (75th percentile). Good is under 800 ms.

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

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

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

Your homepage downloads 2.5 MB in 105 requests on a phone: scripts 1.4 MB (41), images 770 KiB (14) and other files 154 KiB (40). Under 2 MB keeps phones on slow connections fast.

Phonak_EON_Main_Menu.webp 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).

1 image is downloaded at several times the size a phone draws it, for example IMG-600x600.webp at 1,200 px wide, shown at 260 px. Resized copies would save about 60 KiB.

3 images (290 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 0.70 g of CO₂e: 84.0 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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

1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

ARIA role should be appropriate for the element: 96 elements on the page fail this check, rated minor by axe-core.

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

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

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

Elements with visible text labels do not have matching accessible names. (1 element).

Structured data found (untyped) but with 1 problem, for example “ld+json block 1 is not valid JSON (Unexpected non-whitespace character after JSON at position 4)”.

No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

The homepage links to 82 pages on lapperre.be and 8 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://www.lapperre.be/fr/centre-auditif/trouver, https://www.lapperre.be/fr/test-auditif-en-ligne, https://www.lapperre.be/fr/assistance, https://www.lapperre.be/fr/onlinebookingBEFR, https://www.lapperre.be/fr/appareils-auditifs/assurances and https://www.lapperre.be/fr/appareils-auditifs/plan-supportaudition have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.lapperre.be/fr/centre-auditif/trouver has no <h1> headline, so visitors and search engines get no clear main topic.

https://www.lapperre.be/fr/onlinebookingBEFR has under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

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

1 image failed to load on a phone, for example https://bat.bing.net/action/0?ti=5599680&tm=gtm002&Ver=2&mid=776e86d8-8c66-4d9d-bb90-153325bc6ad0&bo=2&page_path=%2Ffr%2F&tpp=1&spa=Y&r=&lt=645&p=https%3A%2F%2Fwww.lapperre.be%2Ffr%2F&pi=918639831&lg=.

Large scripts ship without source maps.

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

There is no form on the homepage, so every lead has to click through to another page first.

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

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

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

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