rensa.nl website review

10 images could be 9.9 MB 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.

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

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

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

About 180 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 750 ms faster on a phone.

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

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

6 third-party services load with your homepage (Usercentrics CMP, Google Tag Manager and LinkedIn Ads and others), adding 620 KiB and 532 ms of main-thread time.

Usercentrics CMP costs a phone 301 ms of main-thread work and 269 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 2.4 s on main-thread work while loading, 1.4 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

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

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

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.

For real visitors the layout shifts by 0.34 (75th percentile). Good is under 0.1.

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

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

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

Real visitors wait 203 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

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

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

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

11 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' tap response (inp) went from 178 ms to 185 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 12.5 MB in 116 requests on a phone: images 10.7 MB (36), scripts 1.2 MB (25) and fonts 319 KiB (9). Under 2 MB keeps phones on slow connections fast.

2 images weigh 8.9 MB together. On a phone connection a single image that size takes seconds.

3 images are downloaded at several times the size a phone draws them, for example Atag_1026.jpg at 8,059 px wide, shown at 225 px. Resized copies would save about 8.1 MB.

7 images (9.4 MB) 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.

4 images further down the page (9.0 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

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

ARIA roles used must conform to valid values: 1 element on the page fails this check, rated critical by axe-core.

1 button has no accessible name, so screen readers announce just “button”.

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

7 images have no alt text, which hurts accessibility and image search.

Heading levels should only increase by one: 1 element on the page fails this check, rated moderate by axe-core.

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

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

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

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

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

There are 3 <h1> headlines (“De duurzaamstegroothandel”, “Leveringen” and “Webselectie”). One clear main headline is easier for people and search engines.

Your meta description is 176 characters; Google truncates after about 160, so the end of your pitch is cut.

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 51 pages on rensa.nl and 7 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 /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.

Your homepage links to /%7B%7Bpage.url%7D%7D, which answers with an error. Visitors hit a dead end and search engines drop it.

/veelgestelde-vragen, /help, /feedback, /nieuws/onderhoudscontracten-van-bijzaak-naar-serieus-specialisme, /ketelpakketweken and /nieuws/nieuwe-generatie-ducoflex-fast-flexible-future-proof and 5 others have no meta description, so Google writes the search snippet from whatever text it finds.

Your homepage links to 1 page by a URL that isn't its canonical one, for example /feedback, whose canonical is /Feedback. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

/nieuws/onderhoudscontracten-van-bijzaak-naar-serieus-specialisme, /ketelpakketweken, /nieuws/nieuwe-generatie-ducoflex-fast-flexible-future-proof, /nieuws/vsh-powerpress-nu-ook-in-xl-maten-beschikbaar, /nieuws/warmte-waar-en-wanneer-je-het-nodig-hebt and /nieuws/albrand-vloerverwarmingspakket and 2 others have no <h1> headline, so visitors and search engines get no clear main topic.

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

On a 390 px-wide phone the page scrolls sideways, a sign that something is wider than the screen.

4 of 15 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 load resource: the server responded with a status of 401 (Unauthorized)”.

2 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

1 image is served at too low a resolution for sharp phone screens.

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.

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

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

Opening the homepage sets 9 cookies, 1 of them by other companies (measured from a US location before any click).

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