Website review, no card needed
daan.eu website review
Visit site (opens in a new tab)Reviewed 5 November 202647 issues · 99 checks
This review found 47 issues worth fixing on daan.eu, 17 of them high impact, across 99 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
76CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 2.5 s |
| May 23, 2026 | 2.5 s |
| May 30, 2026 | 2.5 s |
| Jun 6, 2026 | 2.3 s |
| Jun 13, 2026 | 2.2 s |
| Jun 20, 2026 | 2.3 s |
| Jun 27, 2026 | 2.3 s |
| Jul 4, 2026 | 2.3 s |
| Jul 11, 2026 | 2.2 s |
| Jul 18, 2026 | 2.0 s |
| Jul 25, 2026 | 1.8 s |
| Aug 1, 2026 | 1.7 s |
| Aug 8, 2026 | 1.7 s |
| Aug 15, 2026 | 1.7 s |
| Aug 22, 2026 | 1.7 s |
| Aug 29, 2026 | 1.7 s |
| Sep 5, 2026 | 1.7 s |
| Sep 12, 2026 | 1.6 s |
| Sep 19, 2026 | 1.6 s |
| Sep 26, 2026 | 1.6 s |
| Oct 3, 2026 | 1.6 s |
| Oct 10, 2026 | 1.5 s |
| Oct 17, 2026 | 1.5 s |
| Oct 24, 2026 | 1.5 s |
| Oct 31, 2026 | 1.5 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 131 ms |
| May 23, 2026 | 133 ms |
| May 30, 2026 | 136 ms |
| Jun 6, 2026 | 138 ms |
| Jun 13, 2026 | 140 ms |
| Jun 20, 2026 | 143 ms |
| Jun 27, 2026 | 139 ms |
| Jul 4, 2026 | 141 ms |
| Jul 11, 2026 | 141 ms |
| Jul 18, 2026 | 141 ms |
| Jul 25, 2026 | 145 ms |
| Aug 1, 2026 | 146 ms |
| Aug 8, 2026 | 149 ms |
| Aug 15, 2026 | 147 ms |
| Aug 22, 2026 | 146 ms |
| Aug 29, 2026 | 146 ms |
| Sep 5, 2026 | 145 ms |
| Sep 12, 2026 | 146 ms |
| Sep 19, 2026 | 146 ms |
| Sep 26, 2026 | 147 ms |
| Oct 3, 2026 | 153 ms |
| Oct 10, 2026 | 154 ms |
| Oct 17, 2026 | 161 ms |
| Oct 24, 2026 | 164 ms |
| Oct 31, 2026 | 163 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
5.2 s · 1.3 MBAbout 1.3 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 5.2 s faster on a phone.
Render-blocking requests
3.0 s8 files block the first paint until they finish downloading. Deferring or inlining them could save about 3.0 s.
Reduce unused CSS
1.8 s · 291 KiBAbout 291 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.8 s faster on a phone.
Mobile performance score: 34
34/100Your mobile performance score is 34. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 5.0 s
A phone's processor spends 5.0 s on main-thread work while loading, 2.9 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Improve image delivery
700 ms · 3.8 MB17 images could be 3.8 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 700 ms faster on a phone.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, YouTube and Cookiebot and others), adding 2.5 MB and 2.1 s of main-thread time.
Use efficient cache lifetimes
750 ms · 890 KiB59 files are served with short cache lifetimes, so returning visitors download them again (890 KiB).
Google Tag Manager adds 621 ms
621 msGoogle Tag Manager costs a phone 621 ms of main-thread work and 695 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.
YouTube adds 545 ms
545 msYouTube costs a phone 545 ms of main-thread work and 983 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.
Font display
500 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 500 ms).
Cookiebot adds 300 ms
300 msCookiebot costs a phone 300 ms of main-thread work and 40 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.
2,925 HTML elements
The page has 2,925 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
19 long tasks on the main thread
19 long tasks block the main thread while loading, the longest for 273 ms. During a long task the page ignores taps.
Google Maps adds 107 ms
107 msGoogle Maps costs a phone 107 ms of main-thread work and 367 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.
Legacy JavaScript
23 KiBPolyfills for old browsers add 23 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.
Minify JavaScript
3 KiB3 KiB could be saved by minifying JavaScript.
1 checks passed
Server response: 100 ms
100 msYour server sent the HTML in 100 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 33.7 s
33.7 sYour largest element takes 33.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “EEN WERELD VOL LEUKE BANEN search Zoeken”.
Time to Interactive: 40.4 s
40.4 sThe page becomes fully interactive after 40.4 s. Good is under 3.8 s.
Speed Index: 14.5 s
14.5 sVisually, the page fills in at 14.5 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 832 ms
832 msScripts block taps and scrolling for 832 ms in total while the page loads. Good is under 200 ms.
Tap response (INP) got 24% slower for real visitors
+24%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 131 ms to 163 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
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.
Cumulative Layout Shift: 0.171
0.171The layout shifts by 0.171 while loading, so content jumps under the reader's thumb. Good is under 0.1.
11 images without width and height
11 images have no width and height attributes, so the layout jumps as each one loads.
7 checks passed
Passes Core Web Vitals for real visitors
Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).
Real-user LCP: 1.7 s
1.7 sReal visitors wait 1.7 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 166 ms
166 msReal visitors wait 166 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.01
0.01For real visitors the layout shifts by 0.01 (75th percentile). Good is under 0.1.
Real-user FCP: 1.3 s
1.3 sReal visitors see the first content after 1.3 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 511 ms
511 msReal visitors wait 511 ms for your server to start answering (75th percentile). Good is under 800 ms.
Largest content (LCP) got 40% faster for real visitors
-40%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 2.5 s to 1.5 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Images and page weight
Page weight: 8.3 MB in 153 requests
8.3 MBYour homepage downloads 8.3 MB in 153 requests on a phone: images 4.7 MB (43), scripts 2.8 MB (51) and fonts 442 KiB (7). Under 2 MB keeps phones on slow connections fast.
15 images far larger than shown
2.9 MB15 images are downloaded at several times the size a phone draws them, for example 1749021412-Blokkendoos.webp at 1,440 px wide, shown at 220 px. Resized copies would save about 2.9 MB.
15 images below the first screen load straight away
15 images further down the page (4.2 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 2.4 g of CO₂ per visit
2.36 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.36 g of CO₂e: 283.0 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Accessibility
7 buttons without a name
7 buttons have no accessible name, so screen readers announce just “button”.
Unlabelled dropdowns
1 dropdown has no label.
13 text elements with low contrast
13 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Frames without titles
1 frame has no title, so screen-reader users cannot tell what it contains.
All page content should be contained by landmarks (12 elements)
All page content should be contained by landmarks: 12 elements on the page fail this check, rated moderate by axe-core.
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)
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.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
49 form fields without a label
49 form fields have no label, so screen readers announce an empty box and autofill guesses.
6 links without text
6 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 (h3 → h5), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 34 images in the HTML carry an alt attribute.
44 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 54 WCAG 2.2 A/AA and best-practice rules on the phone render: 44 passed and 10 failed. 4 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
1 link crawlers can't follow
1 link has no real href, so search engines can't follow it.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.
356 internal links, 47 external
The homepage links to 356 pages on daan.eu and 47 external pages.
8 checks passed
Meta description: 114 characters
Your meta description is 114 characters: “Daan staat voor een wereld vol leuke banen en gelooft in uitmuntend werkgeverschap. Bekijk onze leukste vacatures.”.
One H1 headline
Your main headline reads: “Een wereld”.
Title: 40 characters
Your title is a healthy 40 characters: “Daan | De leukste vacatures in Nederland”.
Canonical URL set
The canonical URL is https://daan.eu/.
Structured data in place
Structured data found: Organization.
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://daan.eu/sitemap2.xml.
AI search readiness
No llms.txt
There is no https://daan.eu/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.
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.
Organization data: 6 of 6 facts
Your Organization JSON-LD gives name, url, logo, sameAs (social profiles), description and contact details.
Text is in the HTML
Your server sends the page's text in the HTML (1,499 words), so crawlers that don't run JavaScript still read it.
Other pages
1 link to non-canonical URLs
Your homepage links to 1 page by a URL that isn't its canonical one, for example https://daan.eu/vacatures/zzper-in-de-zorg, whose canonical is https://daan.eu/Voorbereid-de-toekomst-in. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
15 pages without an H1
https://daan.eu/vacatures, https://daan.eu/vacatures/zorg, https://daan.eu/vacatures-ouderenzorg, https://daan.eu/vacatures-gehandicaptenzorg, https://daan.eu/vacatures-ggz and https://daan.eu/vacatures-ziekenhuis and 9 others have 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 127 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.
Every page has a meta description
All 15 pages that loaded have a meta description.
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
1 broken image
1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=136026336&tm=gtm002&Ver=2&mid=4d9a42ed-8b2a-4ddc-9fb7-f436ac2824ba&bo=2&sid=b6202460d8d711f1977a2930b6f835de&vid=b6203b30d8d711f1bbe729431d21b647&vids=1&msclkid=N>m_.
5 third-party cookies
5 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.
2 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.
1 distorted image
1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
Missing source maps
Large scripts ship without source maps.
2 checks passed
Tap targets are thumb-sized
21 of 26 tappable elements near the top are at least 24 px.
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.
Local business without LocalBusiness data
Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.
No analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
A 12-field form
Your longest form asks for 12 fields (7 required). Every extra field lowers completion.
No opening hours
The homepage shows no opening hours. If customers visit or call, show when.
No map or directions link
There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.
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 293 words of copy
The homepage carries about 293 words of visible text.
4 checks passed
5 calls to action
The homepage has 5 calls to action, for example “Contact”, “Contact expand_more expand_less” and “Neem contact op”.
Social proof on the page
Social proof on the homepage: 7 testimonial or review blocks, a star rating and 3 trust badges.
Direct contact links
Visitors can reach you directly: 3 phone links and 3 email links.
Phone number on the homepage
Your phone number is on the homepage as a tap-to-call link.
Privacy and tracking
8 trackers load before any consent
8Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, LinkedIn Insight and Meta Pixel and 3 mores (measured from a US location before any click). A consent tool (Cookiebot) is installed; check it blocks these until visitors agree where the law requires it.
19 cookies set on arrival
19Opening the homepage sets 19 cookies, 1 of them by other companies (measured from a US location before any click).
40 other companies contacted
Loading the homepage contacts 40 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: Cookiebot
A consent management tool (Cookiebot) loads with the page.
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 daan.eu, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Hosting
- Signet B.V.
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 47 issues on daan.eu, including 23 speed issues, 1 SEO issue and 4 conversion gaps. 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.