Website review, no card needed
dreaver.nl website review
Visit site (opens in a new tab)Reviewed 6 November 202630 issues · 83 checks
This review found 30 issues worth fixing on dreaver.nl, 10 of them high impact, across 83 checks. The most urgent: reduce unused JavaScript. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
85B- #16,318 of 120,970 reviewed websitesbeats 82%
- #10,337 of 68,463 online storesbeats 79%
- #10,041 of 62,386 Shopify storesbeats 78%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 1.7 s |
| May 23, 2026 | 1.8 s |
| May 30, 2026 | 1.9 s |
| Jun 6, 2026 | 2.2 s |
| Jun 13, 2026 | 2.4 s |
| Jun 20, 2026 | 2.6 s |
| Jun 27, 2026 | 2.6 s |
| Jul 4, 2026 | 2.7 s |
| Jul 11, 2026 | 2.6 s |
| Jul 18, 2026 | 2.6 s |
| Jul 25, 2026 | 2.5 s |
| Aug 1, 2026 | 2.3 s |
| Aug 8, 2026 | 2.3 s |
| Aug 15, 2026 | 2.3 s |
| Aug 22, 2026 | 2.4 s |
| Aug 29, 2026 | 2.4 s |
| Sep 5, 2026 | 2.4 s |
| Sep 12, 2026 | 2.3 s |
| Sep 19, 2026 | 2.2 s |
| Sep 26, 2026 | 2.1 s |
| Oct 3, 2026 | 2.0 s |
| Oct 10, 2026 | 2.0 s |
| Oct 17, 2026 | 2.0 s |
| Oct 24, 2026 | 2.0 s |
| Oct 31, 2026 | 2.0 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 160 ms |
| May 23, 2026 | 163 ms |
| May 30, 2026 | 165 ms |
| Jun 6, 2026 | 169 ms |
| Jun 13, 2026 | 177 ms |
| Jun 20, 2026 | 178 ms |
| Jun 27, 2026 | 179 ms |
| Jul 4, 2026 | 182 ms |
| Jul 11, 2026 | 179 ms |
| Jul 18, 2026 | 179 ms |
| Jul 25, 2026 | 178 ms |
| Aug 1, 2026 | 178 ms |
| Aug 8, 2026 | 177 ms |
| Aug 15, 2026 | 177 ms |
| Aug 22, 2026 | 171 ms |
| Aug 29, 2026 | 168 ms |
| Sep 5, 2026 | 168 ms |
| Sep 12, 2026 | 170 ms |
| Sep 19, 2026 | 171 ms |
| Sep 26, 2026 | 179 ms |
| Oct 3, 2026 | 181 ms |
| Oct 10, 2026 | 187 ms |
| Oct 17, 2026 | 187 ms |
| Oct 24, 2026 | 186 ms |
| Oct 31, 2026 | 185 ms |
Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.
One score from every part of this review. How it works
Speed
Reduce unused JavaScript
3.9 s · 721 KiBAbout 721 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 3.9 s faster on a phone.
Use efficient cache lifetimes
1.1 s · 275 KiB25 files are served with short cache lifetimes, so returning visitors download them again (275 KiB).
Main-thread work: 5.1 s
A phone's processor spends 5.1 s on main-thread work while loading, 3.1 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
8 third-party services on the page
8 third-party services load with your homepage (loox.io, Google Tag Manager and alia-prod.com and others), adding 1.3 MB and 1.2 s of main-thread time.
Mobile performance score: 58
58/100Your mobile performance score is 58. Pages that score under 90 lose visitors before the first paint.
Render-blocking requests
550 ms13 files block the first paint until they finish downloading. Deferring or inlining them could save about 550 ms.
loox.io adds 379 ms
379 msloox.io costs a phone 379 ms of main-thread work and 17 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.
Google Tag Manager adds 244 ms
244 msGoogle Tag Manager costs a phone 244 ms of main-thread work and 333 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.
alia-prod.com adds 202 ms
202 msalia-prod.com costs a phone 202 ms of main-thread work and 502 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.
Minify JavaScript
160 ms · 94 KiB94 KiB could be saved by minifying JavaScript.
Improve image delivery
50 ms · 131 KiB5 images could be 131 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 50 ms faster on a phone.
Reduce unused CSS
150 ms · 23 KiBAbout 23 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.
8 long tasks on the main thread
8 long tasks block the main thread while loading, the longest for 157 ms. During a long task the page ignores taps.
Legacy JavaScript
37 KiBPolyfills for old browsers add 37 KiB JavaScript that modern phones do not need.
Chained critical requests
Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.
Forced reflow
Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.
1 checks passed
Server response: 32 ms
32 msYour server sent the HTML in 32 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Fails Core Web Vitals for real visitors
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.
Largest Contentful Paint: 18.3 s
18.3 sYour largest element takes 18.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Time to Interactive: 20.4 s
20.4 sThe page becomes fully interactive after 20.4 s. Good is under 3.8 s.
Speed Index: 10.0 s
10.0 sVisually, the page fills in at 10.0 s (Speed Index). Good is under 3.4 s.
Real-user FCP: 1.8 s
1.8 sReal visitors see the first content after 1.8 s (75th percentile). Good is under 1.8 s.
First Contentful Paint: 2.7 s
2.7 sThe first text or image appears after 2.7 s on a phone. Good is under 1.8 s.
Total Blocking Time: 237 ms
237 msScripts block taps and scrolling for 237 ms in total while the page loads. Good is under 200 ms.
Tap response (INP) got 15% slower for real visitors
+15%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 160 ms to 185 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 13% slower for real visitors
+13%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 1.7 s to 2.0 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
5 checks passed
Real-user LCP: 1.8 s
1.8 sReal visitors wait 1.8 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 172 ms
172 msReal visitors wait 172 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user TTFB: 318 ms
318 msReal visitors wait 318 ms for your server to start answering (75th percentile). Good is under 800 ms.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 3.7 MB in 268 requests
3.7 MBYour homepage downloads 3.7 MB in 268 requests on a phone: scripts 1.9 MB (100), other files 717 KiB (88) and fonts 647 KiB (16). Under 2 MB keeps phones on slow connections fast.
About 1.1 g of CO₂ per visit
1.06 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.06 g of CO₂e: 127.1 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
3 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
8 text elements with low contrast
8 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
2 tap targets too small
2 tap targets are too small or too close together to hit reliably with a finger.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
59 form fields without a label
59 form fields have no label, so screen readers announce an empty box and autofill guesses.
24 links without text
24 visible links have no text or label, so screen readers cannot say where they go.
Headings should not be empty (1 element)
Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.
Headings skip levels
Headings skip levels (h2 → h4 and h2 → h5), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 54 images in the HTML carry an alt attribute.
45 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 51 WCAG 2.2 A/AA and best-practice rules on the phone render: 45 passed and 6 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
88 internal links, 9 external
The homepage links to 88 pages on dreaver.nl and 9 external pages.
8 checks passed
Meta description: 147 characters
Your meta description is 147 characters: “Je sportschool mist je misschien, je woonkamer niet. Stille, inklapbare loopbanden met eigen app. 75.000+ mensen gingen…”.
One H1 headline
Your main headline reads: “Dreaver”.
Title: 55 characters
Your title is a healthy 55 characters: “Dreaver | Beweeg thuis op de loopband, ook in je pyjama”.
Canonical URL set
The canonical URL is https://dreaver.nl/.
Structured data in place
Structured data found: BreadcrumbList, Organization and WebSite.
Open Graph tags complete
Open Graph tags are complete, so shared links show a title, description and image.
robots.txt in place
robots.txt is in place and points crawlers to your sitemap.
XML sitemap found
Your XML sitemap is reachable at https://dreaver.nl/sitemap.xml.
AI search readiness
Organization data is thin (2 of 6 facts)
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.
3 checks passed
AI answer engines may read the site
Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.
Text is in the HTML
Your server sends the page's text in the HTML (1,282 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://dreaver.nl/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
4 pages without a meta description
https://dreaver.nl/products/dreaver-assist, https://dreaver.nl/pages/dreaver-app, https://dreaver.nl/pages/over-ons and https://dreaver.nl/products/dreaver-motion-pro have no meta description, so Google writes the search snippet from whatever text it finds.
1 page without an H1
https://dreaver.nl/blogs/kennisbank has no <h1> headline, so visitors and search engines get no clear main topic.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 31 found) and read each the way a search engine does.
5 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
Titles are unique
Every page we checked has its own title.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 15 pages that loaded have a <title>.
Best practices
6 small tap targets
6 of 18 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
5 JavaScript errors while loading
5 errors were logged to the browser console while the page loaded, for example “Applying inline style violates the following Content Security Policy directive 'style-src 'self''. Either the 'unsafe-i…”.
Browser-reported issues
Chrome logged issues while loading the page (“Content security policy”).
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No call to action on the first screen
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 risk reducer
No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.
About 694 words of copy
The homepage carries about 694 words of visible text.
Urgency cues
The page uses urgency cues (a countdown or limited-time wording).
5 checks passed
4 calls to action
The homepage has 4 calls to action, for example “Contact”.
5 short forms
5 short forms (1 field at most) are right on the homepage.
Social proof on the page
Social proof on the homepage: 12 testimonial or review blocks, 1 customer or partner logo and 8 trust badges.
Analytics in place
Analytics detected: Google Tag Manager, Microsoft Clarity and TikTok Pixel.
Direct contact links
Visitors can reach you directly: 2 phone links and 2 email links.
Privacy and tracking
10 trackers load before any consent
10Before 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.
29 cookies set on arrival
29Opening the homepage sets 29 cookies (measured from a US location before any click).
No consent tool detected
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.
45 other companies contacted
Loading the homepage contacts 45 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
Security, domain, email and software versions
The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at dreaver.nl, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Apps on your store
Your storefront loads 16 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Intelligems A B Testing · T Lab Ai Translate · Microsoft Clarity · Elevate Ab Testing · Caliber Dreaver · Gorgias Live Chat Helpdesk · Triplewhale · Klaviyo Email Marketing Sms · Multifeeds · Simprosys Google Shopping Feed · loox.io · trustpilot.com · getsitecontrol.com · 9gtb.com · cloudfront.net · zigpoll.com
Apps found in the homepage's code. Apps that only run in checkout or the admin aren't seen, and a headless storefront shows none. App data from programmable.info
Upkeep, stack and company
Stack
- Framework
- Bootstrap
- E-commerce
- Shopify
- Analytics
- Google Tag Manager | Microsoft Clarity
- Hosting
- Shopify
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 30 issues on dreaver.nl, including 16 speed issues and 1 conversion gap. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.
- 28 research agents read your site, reviews, competitors, communities and public filings
- Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
- Competitor intelligence with battlecards for your closest rivals
- Ideal customer profile, buyer segments and buying-stage funnel
- Ranked channels, outreach sequences and content angles
- Live Reddit threads where buyers ask for what you sell, with draft replies
- Earned media and PR openings
- At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
- PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
- Refresh the playbook later to see what changed
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.