rexel.nl website review

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

68 files are served with short cache lifetimes, so returning visitors download them again (1.5 MB).

About 368 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.0 s faster on a phone.

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

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

About 3.0 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 600 ms faster on a phone.

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

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

9 images could be 367 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

7 third-party services load with your homepage (Google Tag Manager, Optanon and Unpkg and others), adding 2.3 MB and 109 ms of main-thread time.

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

rexel.com costs a phone 0 ms of main-thread work and 1.2 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 Fonts costs a phone 0 ms of main-thread work and 701 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.

173 KiB could be saved by minifying JavaScript.

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

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.

3 KiB could be saved by minifying CSS.

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 19.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Rexel en zijn digitale partners gebruiken cookies en vergel…”.

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

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

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

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

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

8 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-24, real Chrome visitors' largest content (lcp) went from 1.8 s to 1.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 5.2 MB in 265 requests on a phone: other files 1.7 MB (183), images 1.2 MB (46) and fonts 972 KiB (13). Under 2 MB keeps phones on slow connections fast.

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

2 images are downloaded at several times the size a phone draws them, for example 26-05-13-Word-Klant-hero-1200x960 at 1,200 px wide, shown at 352 px. Resized copies would save about 88 KiB.

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

1 tap target is too small or too close together to hit reliably with a finger.

All page content should be contained by landmarks: 16 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.

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.

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

1 visible link has no text or label, so screen readers cannot say where it goes.

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

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

There are 3 <h1> headlines (“Onze voordelen”, “Keuzekaart e-mobility” and “Keuzehulp WCD”). One clear main headline is easier for people and search engines.

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

No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

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

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

The homepage links to 258 pages on rexel.nl and 12 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.

There is no https://www.rexel.nl/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.rexel.nl/nln/Rexel/Duurzame-keuze/E-mobility/c/0013.0020.0000, https://www.rexel.nl/nln/Rexel/Duurzame-keuze/Zonne-energie-en-energieopslag/c/0013.0010.0000, https://www.rexel.nl/nln/Rexel/Duurzame-keuze/Verwarmen%2C-Koelen-en-Ventileren/c/0013.0030.0000, https://www.rexel.nl/nln/Rexel/Duurzame-keuze/Schakelmateriaal/c/0013.0140.0000, https://www.rexel.nl/nln/Rexel/Duurzame-keuze/Installatiekasten-en-verdeelinrichtingen/c/0013.0130.0000 and https://www.rexel.nl/nln/Rexel/Duurzame-keuze/Kabel/c/0013.0040.0000 and 5 others use the same meta description. A description written for each page earns more clicks.

https://www.rexel.nl/nln/store-finder, https://www.rexel.nl/nln/Rexel/Duurzame-keuze/c/0013.0000.0000, https://www.rexel.nl/nln/Rexel/Duurzame-keuze/E-mobility/c/0013.0020.0000, https://www.rexel.nl/nln/Rexel/Duurzame-keuze/Zonne-energie-en-energieopslag/c/0013.0010.0000, https://www.rexel.nl/nln/Rexel/Duurzame-keuze/Verwarmen%2C-Koelen-en-Ventileren/c/0013.0030.0000 and https://www.rexel.nl/nln/Rexel/Duurzame-keuze/Schakelmateriaal/c/0013.0140.0000 and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

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

The page uses 1 deprecated browser API that will stop working in future browsers (“Synchronous `XMLHttpRequest` on the main thread is deprecated because of its detrimental effects to…”).

1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

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.

Social proof on the homepage: 1 trust badge. Pairing it with named testimonials or customer logos makes it far more convincing.

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

Opening the homepage sets 5 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 3 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.