wust.be website review

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

3 images could be 532 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 2.5 s faster on a phone.

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

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

8 third-party services load with your homepage (Google Tag Manager, Optanon and LinkedIn Ads and others), adding 1.6 MB and 343 ms of main-thread time.

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

cloudfront.net costs a phone 0 ms of main-thread work and 535 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.

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

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

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

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

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

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

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

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

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

The first text or image appears after 1.8 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 100 ms to 107 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

Your homepage downloads 2.3 MB in 53 requests on a phone: scripts 1.1 MB (27), images 911 KiB (12) and HTML 178 KiB (1). Under 2 MB keeps phones on slow connections fast.

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

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

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

Some lists contain elements other than list items, which screen readers announce wrongly.

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

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

1 form field has no label, so screen readers announce an empty box and autofill guesses.

Structured data found (BreadcrumbList and Organization) but with 1 problem, for example “Organization: url is not an absolute URL ("www.wust.be")”.

The homepage links to 29 pages on wust.be and 13 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.

https://www.wust.be/fr/projets/commissariat-de-police-de-la-louviere is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

https://www.wust.be/fr/projets, https://www.wust.be/fr/promotions-immobilieres, https://www.wust.be/fr/careers, https://www.wust.be/fr/contact, https://www.wust.be/fr/projets/grand-theatre-verviers and https://www.wust.be/fr/projets/les-heures-claires-spa have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.wust.be/fr/about-us/rapport-activites has no <h1> headline, so visitors and search engines get no clear main topic.

https://www.wust.be/fr/Activit%C3%A9s, https://www.wust.be/fr/projets, https://www.wust.be/fr/careers, https://www.wust.be/fr/about-us/plaquette-secteur-industriel and https://www.wust.be/fr/about-us/rapport-activites have 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 20 found) and read each the way a search engine does.

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

2 errors were logged to the browser console while the page loaded, for example “Failed to execute 'appendChild' on 'Node': Unexpected end of input”.

Chrome logged issues while loading the page (“Content security policy”).

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.

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

Before a visitor clicks anything, the page loads Google Tag Manager (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.

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