Website review, no card needed
naaktedruiven.nl website review
Visit site (opens in a new tab)Reviewed 9 November 202631 issues · 79 checks
This review found 31 issues worth fixing on naaktedruiven.nl, 10 of them high impact, across 79 checks. The most urgent: fails Core Web Vitals for real visitors. 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
86B- #12,026 of 124,013 reviewed websitesbeats 87%
- #7,287 of 69,747 online storesbeats 85%
- #148 of 2,903 WooCommerce storesbeats 94%
Closest competitors among WooCommerce stores
Compare side by sideOne score from every part of this review. How it works
How it loaded on a phone
1.0 s
2.0 s
3.0 s
4.1 s
5.1 s
6.1 s
7.1 s
8.1 s
Speed
Mobile performance score: 82
82/100Your mobile performance score is 82. Pages that score under 90 lose visitors before the first paint.
Render-blocking requests
850 ms1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 850 ms.
Reduce unused CSS
600 ms · 118 KiBAbout 118 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 600 ms faster on a phone.
4 third-party services on the page
4 third-party services load with your homepage (Google Tag Manager, Google/Doubleclick Ads and Other Google APIs/SDKs and others), adding 513 KiB and 514 ms of main-thread time.
Google Tag Manager adds 512 ms
512 msGoogle Tag Manager costs a phone 512 ms of main-thread work and 506 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.
3 long tasks on the main thread
3 long tasks block the main thread while loading, the longest for 253 ms. During a long task the page ignores taps.
1,581 HTML elements
The page has 1,581 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Reduce unused JavaScript
225 KiBAbout 225 KiB of JavaScript is downloaded but never used on this page.
Improve image delivery
11 KiB1 image could be 11 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.4 s
A phone's processor spends 1.4 s on main-thread work while loading, 420 ms of it running JavaScript. That is comfortably low.
Server response: 107 ms
107 msYour server sent the HTML in 107 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.
Speed Index: 11.0 s
11.0 sVisually, the page fills in at 11.0 s (Speed Index). Good is under 3.4 s.
Real-user TTFB: 1.0 s
1.0 sReal visitors wait 1.0 s for your server to start answering (75th percentile). Good is under 800 ms.
Time to Interactive: 7.3 s
7.3 sThe page becomes fully interactive after 7.3 s. Good is under 3.8 s.
Total Blocking Time: 240 ms
240 msScripts block taps and scrolling for 240 ms in total while the page loads. Good is under 200 ms.
Largest Contentful Paint: 2.5 s
2.5 sYour largest element takes 2.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Bekijk al onze extra-lang gerijpte wijnen (op hout)”. Most of its time is element render delay (6.7 s).
1 image without width and height
1 image have no width and height attributes, so the layout jumps as each one loads.
5 checks passed
Real-user LCP: 1.6 s
1.6 sReal visitors wait 1.6 s for the largest content to appear (75th percentile). Good is under 2.5 s.
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: 1.3 s
1.3 sReal visitors see the first content after 1.3 s (75th percentile). Good is under 1.8 s.
First Contentful Paint: 1.8 s
1.8 sThe first text or image appears after 1.8 s, inside the 1.8 s “good” threshold.
Cumulative Layout Shift: 0.022
0.022The layout barely moves while loading (CLS 0.022, good is under 0.1).
Images and page weight
2 images in older formats
2 images (108 KiB) 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.
About 0.3 g of CO₂ per visit
0.30 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.30 g of CO₂e: 36.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
3 checks passed
Page weight: 1.1 MB in 18 requests
1.1 MBYour homepage downloads 1.1 MB in 18 requests on a phone: scripts 510 KiB (4), fonts 299 KiB (2) and stylesheets 125 KiB (1). That is a lean page.
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
12 buttons without a name
12 buttons have no accessible name, so screen readers announce just “button”.
Hidden but focusable
97 elements hidden from screen readers can still receive keyboard focus.
39 text elements with low contrast
39 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Orphan list items
Some list items are not inside a list.
Malformed lists
Some lists contain elements other than list items, which screen readers announce wrongly.
4 tap targets too small
4 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.
All page content should be contained by landmarks (1 element)
All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.
20 links without text
20 visible links have no text or label, so screen readers cannot say where they go.
Headings skip levels
Headings skip levels (h2 → h4), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 60 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 54 WCAG 2.2 A/AA and best-practice rules on the phone render: 45 passed and 9 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
2 H1 headlines
There are 2 <h1> headlines (“Allemaal” and “Bubbels”). One clear main headline is easier for people and search engines.
256 internal links, 4 external
The homepage links to 256 pages on naaktedruiven.nl and 4 external pages.
7 checks passed
Meta description: 154 characters
Your meta description is 154 characters: “Bekijk ons uitgebreide assortiment met alcoholvrije wijn: witte wijn, rode wijn, rose en bubbels! Op werkdagen voor 16u…”.
Title: 59 characters
Your title is a healthy 59 characters: “De Naakte Druiven, het beste assortiment alcoholvrije wijn!”.
Canonical URL set
The canonical URL is https://naaktedruiven.nl/.
Structured data in place
Structured data found: BreadcrumbList, WebPage 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.
XML sitemap found
Your XML sitemap is reachable at https://naaktedruiven.nl/sitemap.xml.
AI search readiness
No Organization structured data
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.
No llms.txt
There is no https://naaktedruiven.nl/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.
2 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 (977 words), so crawlers that don't run JavaScript still read it.
Other pages
1 linked page hidden from search
https://naaktedruiven.nl/inhoud/20cl,375cl is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.
4 pages without a meta description
https://naaktedruiven.nl/collections/overig, https://naaktedruiven.nl/inhoud/20cl,375cl, https://naaktedruiven.nl/collections/alcoholvrije-proefpakketten and https://naaktedruiven.nl/aanbiedingen have no meta description, so Google writes the search snippet from whatever text it finds.
12 pages slow to respond
https://naaktedruiven.nl/collections/alcoholvrije-rode-wijn, https://naaktedruiven.nl/collections/alcoholvrije-rose-wijn, https://naaktedruiven.nl/collections/alcoholvrije-bubbels, https://naaktedruiven.nl/collections/overig, https://naaktedruiven.nl/collections/overig/aperitief and https://naaktedruiven.nl/collections/overig/druivensap and 6 others took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 81 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.
Every page has an H1
Each page we checked has a main headline.
Every page has a title
All 14 pages that loaded have a <title>.
Best practices
51 small tap targets
51 of 213 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
1 low-resolution image
1 image is served at too low a resolution for sharp phone screens.
2 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
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 social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
Phone number is not tap-to-call
Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.
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 1,206 words of copy
The homepage carries about 1,206 words of visible text.
3 checks passed
2 calls to action
The homepage has 2 calls to action, for example “Leitz PNR Pinot Noir Reserve” and “Contact”.
2 short forms
2 short forms (1 field at most) are right on the homepage.
Analytics in place
Analytics detected: Google Tag Manager.
Privacy and tracking
4 trackers load before any consent
4Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager and Klaviyo (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.
12 cookies set on arrival
12Opening the homepage sets 12 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.
11 other companies contacted
Loading the homepage contacts 11 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 naaktedruiven.nl, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- CMS
- WordPress
- Framework
- jQuery
- E-commerce
- WooCommerce
- Analytics
- Google Tag Manager
- Hosting
- Duocast B.V.
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 31 issues on naaktedruiven.nl, including 14 speed issues, 1 SEO issue and 2 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.