Website review, no card needed
van-hees.com website review
Visit site (opens in a new tab)Reviewed 19 November 202630 issues · 69 checks
This review found 30 issues worth fixing on van-hees.com, 9 of them high impact, across 69 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
69DClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| Aug 22, 2026 | 1.0 s |
| Oct 31, 2026 | 1.2 s |
| Nov 7, 2026 | 1.2 s |
| Nov 14, 2026 | 1.2 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| Aug 22, 2026 | 92 ms |
| Oct 31, 2026 | 90 ms |
| Nov 7, 2026 | 91 ms |
| Nov 14, 2026 | 92 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
How it loaded on a phone
0.4 s
0.8 s
1.1 s
1.5 s
1.9 s
2.3 s
2.6 s
3.0 s
Speed
Reduce unused JavaScript
2.8 s · 392 KiBAbout 392 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.8 s faster on a phone.
Mobile performance score: 67
67/100Your mobile performance score is 67. Pages that score under 90 lose visitors before the first paint.
Improve image delivery
750 ms · 166 KiB2 images could be 166 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 750 ms faster on a phone.
Font display
850 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 850 ms).
Render-blocking requests
800 ms2 files block the first paint until they finish downloading. Deferring or inlining them could save about 800 ms.
Reduce unused CSS
450 ms · 72 KiBAbout 72 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 450 ms faster on a phone.
Minify JavaScript
450 ms · 58 KiB58 KiB could be saved by minifying JavaScript.
4 third-party services on the page
4 third-party services load with your homepage (Google Tag Manager, Cookiebot and MyFonts and others), adding 448 KiB and 261 ms of main-thread time.
Use efficient cache lifetimes
150 ms · 33 KiB2 files are served with short cache lifetimes, so returning visitors download them again (33 KiB).
2 long tasks on the main thread
2 long tasks block the main thread while loading, the longest for 134 ms. During a long task the page ignores taps.
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: 0.6 s
A phone's processor spends 0.6 s on main-thread work while loading, 289 ms of it running JavaScript. That is comfortably low.
Server response: 2 ms
2 msYour server sent the HTML in 2 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 8.8 s
8.8 sYour largest element takes 8.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Welcome to VAN HEES”.
Time to Interactive: 8.8 s
8.8 sThe page becomes fully interactive after 8.8 s. Good is under 3.8 s.
Speed Index: 5.6 s
5.6 sVisually, the page fills in at 5.6 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 2.4 s
2.4 sThe first text or image appears after 2.4 s on a phone. Good is under 1.8 s.
1 image without width and height
1 image have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
+1%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 92 ms to 92 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
+8%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 1.0 s to 1.2 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Not enough real-visitor data yet
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.
2 checks passed
Total Blocking Time: 105 ms
105 msScripts block the page for only 105 ms while loading. Good is under 200 ms.
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.33 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.33 g of CO₂e: 40.0 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.2 MB in 19 requests
1.2 MBYour homepage downloads 1.2 MB in 19 requests on a phone: scripts 705 KiB (7), images 294 KiB (2) and fonts 140 KiB (4). 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 image without alt text
1 image has no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (4 elements)
All page content should be contained by landmarks: 4 elements on the page fail this check, rated moderate by axe-core.
1 link without text
1 visible link has no text or label, so screen readers cannot say where it goes.
1 checks passed
42 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 45 WCAG 2.2 A/AA and best-practice rules on the phone render: 42 passed and 3 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Page is set to noindex
The robots meta tag says “noindex,follow”: Google is told not to list this page at all.
Blocked from indexing
Google's crawler is blocked from indexing this page.
Title is short (22 characters)
Your title is only 22 characters: “VAN HEES - we know how”. Between 30 and 65 characters leaves room to say what you do and for whom.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
No canonical URL
No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.
No social preview image
No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.
No XML sitemap
No XML sitemap at https://www.van-hees.com/sitemap.xml, so Google discovers your pages only by following links.
7 internal links, 0 external
The homepage links to 7 pages on van-hees.com and 0 external pages.
3 checks passed
Meta description: 151 characters
Your meta description is 151 characters: “VAN HEES ist einer der führenden Hersteller von Gewürzen, Gewürzmischungen, Gütezusätzen und Marinaden für vielfältige …”.
One H1 headline
Your main headline reads: “Welcome to VAN HEES”.
robots.txt in place
robots.txt is in place and points crawlers to your sitemap.
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.
1 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.
Other pages
6 pages without an H1
https://www.van-hees.com/fr/fr, https://www.van-hees.com/ch/de, https://www.van-hees.com/de/de, https://www.van-hees.com/us/en, https://www.van-hees.com/bx/nl and https://www.van-hees.com/de/en have no <h1> headline, so visitors and search engines get no clear main topic.
6 internal pages checked
We fetched 6 pages linked from your homepage and read each the way a search engine does.
6 checks passed
Linked pages load
All 6 pages we checked loaded without an error.
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
Every page has a meta description
All 6 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 6 pages that loaded have a <title>.
Best practices
7 small tap targets
7 of 10 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
Missing source maps
Large scripts ship without source maps.
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 calls to action
We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.
No social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
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 96 words
The homepage has only about 96 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.
1 checks passed
Analytics in place
Analytics detected: Google Tag Manager.
Privacy and tracking
2 trackers load before any consent
2Before a visitor clicks anything, the page loads Google Analytics and Google Tag Manager (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.
3 cookies set on arrival
3Opening the homepage sets 3 cookies, 1 of them by other companies (measured from a US location before any click).
5 other companies contacted
Loading the homepage contacts 5 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 van-hees.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- CMS
- TYPO3 CMS
- Analytics
- Google Tag Manager
- Hosting
- netcup GmbH
Company
- Founded
- 1947
- Headquarters
- Walluf
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 van-hees.com, including 12 speed issues, 7 SEO issues and 5 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.