dreaver.com website review

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

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

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

8 third-party services load with your homepage (Google Tag Manager, Clarity and alia-prod.com and others), adding 991 KiB and 708 ms of main-thread time.

About 330 KiB of JavaScript is downloaded but never used on this page.

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

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

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

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

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

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

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

2 KiB could be saved by minifying JavaScript.

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

Your largest element takes 5.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Lachende vrouw wandelt op een Dreaver in haar woonkamer”.

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 223 ms in total while the page loads. Good is under 200 ms.

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.6 MB in 325 requests on a phone: images 1.1 MB (37), other files 1.1 MB (181) and scripts 1.1 MB (88). Under 2 MB keeps phones on slow connections fast.

1 image is downloaded at several times the size a phone draws it, for example 2026-10-15_Dreaver12159_1.jpg at 1,100 px wide, shown at 358 px. Resized copies would save about 5 KiB.

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

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

Scrollable region must have keyboard access: 2 elements on the page fail this check, rated serious by axe-core.

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.

23 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. (3 elements).

Your canonical URL points to dreaver.nl, not dreaver.com, so Google may credit that host instead.

Structured data found (BreadcrumbList, Organization and WebSite) but with 1 problem, for example “Organization: url points at a different host (https://dreaver.nl)”.

The homepage links to 67 pages on dreaver.com and 27 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://dreaver.com/products/dreaver-motion-pro, https://dreaver.com/pages/dreaver-app, https://dreaver.com/pages/over-ons, https://dreaver.com/pages/contact-page and https://dreaver.com/pages/handleidingen-overzicht-dreaver-loopbanden have no meta description, so Google writes the search snippet from whatever text it finds.

https://dreaver.com/pages/handleidingen-overzicht-dreaver-loopbanden has no <h1> headline, so visitors and search engines get no clear main topic.

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

3 errors were logged to the browser console while the page loaded, for example “[Alia launcher] Target not found for campaign 45405”.

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 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 1,218 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel and 5 mores (measured from a US location before any click). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.

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