add.be website review

Your mobile performance score is 66 (desktop: 87). Pages that score under 90 lose visitors before the first paint.

About 162 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 780 ms faster on a phone.

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

6 images could be 135 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.

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

1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 300 ms.

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

3 third-party services load with your homepage (Google Tag Manager, cookiebot.eu and Google Analytics), adding 429 KiB and 268 ms of main-thread time.

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

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

Your largest element takes 6.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Elke ondernemer is graag goed verzekerd, weinigen willen er…”.

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

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

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

Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

Your homepage downloads 3.7 MB in 38 requests on a phone: images 1.7 MB (16), fonts 1.4 MB (7) and scripts 517 KiB (9). Under 2 MB keeps phones on slow connections fast.

9 images further down the page (372 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

1 image (122 KiB) is 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 1.06 g of CO₂e: 127.4 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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

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.

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

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

No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

No Open Graph image (also missing: og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

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

The homepage links to 36 pages on add.be and 7 external pages.

Your Organization JSON-LD is missing logo, sameAs (social profiles), 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.

There is no https://www.add.be/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.

https://www.add.be/nl/solutions and https://www.add.be/nl/contact have no meta description, so Google writes the search snippet from whatever text it finds.

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

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

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

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

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

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