Website review, no card needed
naduvi.nl website review
Visit site (opens in a new tab)Reviewed 9 November 202633 issues · 82 checks
This review found 33 issues worth fixing on naduvi.nl, 10 of them high impact, across 82 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
78C- #62,115 of 123,924 reviewed websitesbeats 44%
- #40,543 of 69,719 online storesbeats 36%
- #38,716 of 63,424 Shopify storesbeats 33%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 23, 2026 | 1.3 s |
| May 30, 2026 | 1.3 s |
| Jun 6, 2026 | 1.3 s |
| Jun 13, 2026 | 1.2 s |
| Jun 20, 2026 | 1.2 s |
| Jun 27, 2026 | 1.3 s |
| Jul 4, 2026 | 1.3 s |
| Jul 11, 2026 | 1.3 s |
| Jul 18, 2026 | 1.3 s |
| Jul 25, 2026 | 1.2 s |
| Aug 1, 2026 | 1.2 s |
| Aug 8, 2026 | 1.2 s |
| Aug 15, 2026 | 1.1 s |
| Aug 22, 2026 | 1.1 s |
| Aug 29, 2026 | 1.1 s |
| Sep 5, 2026 | 1.1 s |
| Sep 19, 2026 | 1.1 s |
| Sep 26, 2026 | 1.1 s |
| Oct 3, 2026 | 1.0 s |
| Oct 10, 2026 | 1.0 s |
| Oct 17, 2026 | 1.0 s |
| Oct 24, 2026 | 1.0 s |
| Oct 31, 2026 | 1.0 s |
| Nov 7, 2026 | 1.0 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 23, 2026 | 138 ms |
| May 30, 2026 | 141 ms |
| Jun 6, 2026 | 139 ms |
| Jun 13, 2026 | 145 ms |
| Jun 20, 2026 | 145 ms |
| Jun 27, 2026 | 146 ms |
| Jul 4, 2026 | 153 ms |
| Jul 11, 2026 | 151 ms |
| Jul 18, 2026 | 147 ms |
| Jul 25, 2026 | 142 ms |
| Aug 1, 2026 | 128 ms |
| Aug 8, 2026 | 121 ms |
| Aug 15, 2026 | 120 ms |
| Aug 22, 2026 | 119 ms |
| Aug 29, 2026 | 120 ms |
| Sep 5, 2026 | 117 ms |
| Sep 19, 2026 | 117 ms |
| Sep 26, 2026 | 118 ms |
| Oct 3, 2026 | 117 ms |
| Oct 10, 2026 | 123 ms |
| Oct 17, 2026 | 122 ms |
| Oct 24, 2026 | 121 ms |
| Oct 31, 2026 | 129 ms |
| Nov 7, 2026 | 127 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
1.6 s · 359 KiBAbout 359 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.6 s faster on a phone.
Use efficient cache lifetimes
1.4 s · 243 KiB21 files are served with short cache lifetimes, so returning visitors download them again (243 KiB).
Render-blocking requests
1.2 s1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 1.2 s.
Mobile performance score: 65
65/100Your mobile performance score is 65. Pages that score under 90 lose visitors before the first paint.
7 third-party services on the page
7 third-party services load with your homepage (Google Tag Manager, etrias.nl and Cookie-Script.com and others), adding 1.0 MB and 503 ms of main-thread time.
Google Tag Manager adds 414 ms
414 msGoogle Tag Manager costs a phone 414 ms of main-thread work and 671 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.
etrias.nl adds 32 ms
32 msetrias.nl costs a phone 32 ms of main-thread work and 308 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.
Reduce unused CSS
150 ms · 51 KiBAbout 51 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.
6 long tasks on the main thread
6 long tasks block the main thread while loading, the longest for 124 ms. During a long task the page ignores taps.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
Legacy JavaScript
15 KiBPolyfills for old browsers add 15 KiB JavaScript that modern phones do not need.
Improve image delivery
13 KiB1 image could be 13 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
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.
2 checks passed
Main-thread work: 1.1 s
A phone's processor spends 1.1 s on main-thread work while loading, 687 ms of it running JavaScript. That is comfortably low.
Server response: 171 ms
171 msYour server sent the HTML in 171 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 10.4 s
10.4 sYour largest element takes 10.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “We gebruiken cookies om onze website te laten functioneren …”. Most of its time is element render delay (4.2 s).
Time to Interactive: 10.4 s
10.4 sThe page becomes fully interactive after 10.4 s. Good is under 3.8 s.
Speed Index: 5.5 s
5.5 sVisually, the page fills in at 5.5 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 2.0 s
2.0 sThe first text or image appears after 2.0 s on a phone. Good is under 1.8 s.
Total Blocking Time: 233 ms
233 msScripts block taps and scrolling for 233 ms in total while the page loads. Good is under 200 ms.
6 images without width and height
6 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
-8%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 138 ms to 127 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
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: 0.8 s
0.8 sReal visitors wait 0.8 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 136 ms
136 msReal visitors wait 136 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 FCP: 0.6 s
0.6 sReal visitors see the first content after 0.6 s (75th percentile). Good is under 1.8 s.
Largest content (LCP) got 24% faster for real visitors
-24%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 1.3 s to 1.0 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
About 0.3 g of CO₂ per visit
0.31 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.31 g of CO₂e: 36.9 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
4 checks passed
Page weight: 1.1 MB in 40 requests
1.1 MBYour homepage downloads 1.1 MB in 40 requests on a phone: scripts 932 KiB (14), images 69 KiB (10) and stylesheets 44 KiB (1). That is a lean page.
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
1 button without a name
1 button has no accessible name, so screen readers announce just “button”.
Elements must only use permitted ARIA attributes (2 elements)
Elements must only use permitted ARIA attributes: 2 elements on the page fail this check, rated serious by axe-core.
Links must have discernible text (1 element)
Links must have discernible text: 1 element on the page fails this check, rated serious by axe-core.
All page content should be contained by landmarks (10 elements)
All page content should be contained by landmarks: 10 elements on the page fail this check, rated moderate by axe-core.
No main landmark
The page has no <main> landmark, so screen-reader users cannot jump straight to the content.
Page should contain a level-one heading (1 element)
Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.
2 text elements with low contrast
2 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
button, link, and menuitem elements do not have accessible names.
button, link, and menuitem elements do not have accessible names. (1 element).
1 form field without a label
1 form field has no label, so screen readers announce an empty box and autofill guesses.
Alternative text of images should not be repeated as text (7 elements)
Alternative text of images should not be repeated as text: 7 elements on the page fail this check, rated minor by axe-core.
2 checks passed
Every image has alt text
All 11 images in the HTML carry an alt attribute.
24 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 31 WCAG 2.2 A/AA and best-practice rules on the phone render: 24 passed and 7 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
Title is short (15 characters)
Your title is only 15 characters: “NADUVI | NADUVI”. Between 30 and 65 characters leaves room to say what you do and for whom.
45 internal links, 208 external
The homepage links to 45 pages on naduvi.nl and 208 external pages.
6 checks passed
Meta description: 101 characters
Your meta description is 101 characters: “NADUVI vindt u bij NADUVI ✓ Gratis verzending vanaf € 50,00 ✓ Achteraf betalen | Een Etrias webwinkel”.
Canonical URL set
The canonical URL is https://www.naduvi.nl/.
Structured data in place
Structured data found: BreadcrumbList and 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://www.naduvi.nl/sitemap/naduvi_nl/sitemap.xml.
AI search readiness
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: 4 of 6 facts
Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.
llms.txt published
The site publishes https://www.naduvi.nl/llms.txt (1 KiB, 0 links), a plain-text guide to the site for AI tools.
Other pages
12 pages share 2 titles
https://www.naduvi.nl/veelgesteldevragen/wat-zijn-de-verzendkosten, https://www.naduvi.nl/veelgesteldevragen/hoe-kan-ik-betalen, https://www.naduvi.nl/veelgesteldevragen, https://www.naduvi.nl/veelgesteldevragen/contact, https://www.naduvi.nl/veelgesteldevragen/hoe-kan-ik-retourneren and https://www.naduvi.nl/veelgesteldevragen/hoe-zit-het-met-de-garantie all use the title “Klantenservice | NADUVI”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.
13 pages without a meta description
https://www.naduvi.nl/veelgesteldevragen/wat-zijn-de-verzendkosten, https://www.naduvi.nl/veelgesteldevragen/hoe-kan-ik-betalen, https://www.naduvi.nl/veelgesteldevragen, https://www.naduvi.nl/veelgesteldevragen/contact, https://www.naduvi.nl/veelgesteldevragen/hoe-kan-ik-retourneren and https://www.naduvi.nl/veelgesteldevragen/hoe-zit-het-met-de-garantie and 7 others have no meta description, so Google writes the search snippet from whatever text it finds.
2 links to non-canonical URLs
Your homepage links to 2 pages by a URL that isn't their canonical one, for example https://www.naduvi.nl/veelgesteldevragen, whose canonical is https://www.naduvi.nl/veelgesteldevragen/hoe-kan-ik-inloggen. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
12 pages without an H1
https://www.naduvi.nl/veelgesteldevragen/wat-zijn-de-verzendkosten, https://www.naduvi.nl/veelgesteldevragen/hoe-kan-ik-betalen, https://www.naduvi.nl/veelgesteldevragen, https://www.naduvi.nl/veelgesteldevragen/contact, https://www.naduvi.nl/veelgesteldevragen/hoe-kan-ik-retourneren and https://www.naduvi.nl/veelgesteldevragen/hoe-zit-het-met-de-garantie and 6 others have no <h1> headline, so visitors and search engines get no clear main topic.
3 pages with very little text
https://www.naduvi.nl/veelgesteldevragen, https://www.naduvi.nl/veelgesteldevragen/hoe-zit-het-met-de-garantie and https://www.naduvi.nl/over-ons/giftcard have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.
13 internal pages checked
We fetched 13 pages linked from your homepage and read each the way a search engine does.
3 checks passed
Linked pages load
All 13 pages we checked loaded without an error.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 13 pages that loaded have a <title>.
Best practices
3 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Tap targets are thumb-sized
27 of 31 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.
No direct contact details
No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.
Only about 51 words
The homepage has only about 51 words of visible text; thin pages give Google and first-time buyers little to go on.
No form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
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.
3 checks passed
2 calls to action
The homepage has 2 calls to action, for example “Contact”.
Social proof on the page
Social proof on the homepage: 8 testimonial or review blocks and a star rating.
Analytics in place
Analytics detected: Cloudflare Web Analytics.
Privacy and tracking
3 trackers load before any consent
3Before a visitor clicks anything, the page loads Google Ads, Google Analytics and Google Tag Manager (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.
2 cookies set on arrival
2Opening the homepage sets 2 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.
9 other companies contacted
Loading the homepage contacts 9 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 naduvi.nl, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- E-commerce
- Shopify;Shopify Plus
- Hosting
- Cloudflare
Company
- Headquarters
- Amsterdam
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 33 issues on naduvi.nl, including 13 speed issues, 2 SEO issues and 3 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.