Website review, no card needed
trekhaken.nl website review
Visit site (opens in a new tab)Reviewed 8 November 202631 issues · 79 checks
This review found 31 issues worth fixing on trekhaken.nl, 15 of them high impact, across 79 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
63D- #111,651 of 117,441 reviewed websitesbeats 4%
- #65,432 of 66,904 online storesbeats 2%
- #59,933 of 61,009 Shopify storesbeats 1%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 1.8 s |
| May 23, 2026 | 1.9 s |
| May 30, 2026 | 2.0 s |
| Jun 6, 2026 | 2.0 s |
| Jun 13, 2026 | 1.8 s |
| Jun 20, 2026 | 1.9 s |
| Jun 27, 2026 | 1.8 s |
| Jul 4, 2026 | 1.9 s |
| Jul 11, 2026 | 2.1 s |
| Jul 18, 2026 | 2.2 s |
| Jul 25, 2026 | 2.0 s |
| Aug 1, 2026 | 2.0 s |
| Aug 8, 2026 | 1.9 s |
| Aug 15, 2026 | 2.0 s |
| Aug 22, 2026 | 2.0 s |
| Aug 29, 2026 | 1.9 s |
| Sep 5, 2026 | 2.0 s |
| Sep 12, 2026 | 1.8 s |
| Sep 19, 2026 | 2.0 s |
| Sep 26, 2026 | 2.2 s |
| Oct 3, 2026 | 2.2 s |
| Oct 10, 2026 | 2.2 s |
| Oct 17, 2026 | 2.0 s |
| Oct 24, 2026 | 1.9 s |
| Oct 31, 2026 | 1.9 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 790 ms |
| May 23, 2026 | 1.4 s |
| May 30, 2026 | 1.1 s |
| Jun 6, 2026 | 732 ms |
| Jun 13, 2026 | 446 ms |
| Jun 20, 2026 | 252 ms |
| Jun 27, 2026 | 258 ms |
| Jul 4, 2026 | 271 ms |
| Jul 11, 2026 | 298 ms |
| Jul 18, 2026 | 297 ms |
| Jul 25, 2026 | 269 ms |
| Aug 1, 2026 | 242 ms |
| Aug 8, 2026 | 221 ms |
| Aug 15, 2026 | 219 ms |
| Aug 22, 2026 | 232 ms |
| Aug 29, 2026 | 242 ms |
| Sep 5, 2026 | 245 ms |
| Sep 12, 2026 | 217 ms |
| Sep 19, 2026 | 196 ms |
| Sep 26, 2026 | 201 ms |
| Oct 3, 2026 | 216 ms |
| Oct 10, 2026 | 235 ms |
| Oct 17, 2026 | 250 ms |
| Oct 24, 2026 | 238 ms |
| Oct 31, 2026 | 221 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.1 s · 677 KiBAbout 677 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 3.1 s faster on a phone.
Mobile performance score: 29
29/100Your mobile performance score is 29. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 7.1 s
A phone's processor spends 7.1 s on main-thread work while loading, 5.3 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Render-blocking requests
750 ms3 files block the first paint until they finish downloading. Deferring or inlining them could save about 750 ms.
19 long tasks on the main thread
19 long tasks block the main thread while loading, the longest for 506 ms. During a long task the page ignores taps.
Shopify adds 182 ms
182 msShopify costs a phone 182 ms of main-thread work and 385 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,188 HTML elements
The page has 2,188 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
8 third-party services on the page
8 third-party services load with your homepage (Shopify, Clarity and Klaviyo and others), adding 814 KiB and 486 ms of main-thread time.
Legacy JavaScript
250 ms · 60 KiBPolyfills for old browsers add 60 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 250 ms faster on a phone.
Minify JavaScript
250 ms · 21 KiB21 KiB could be saved by minifying JavaScript.
Reduce unused CSS
150 ms · 41 KiBAbout 41 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.
Improve image delivery
50 ms · 30 KiB3 images could be 30 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.
Use efficient cache lifetimes
58 KiB6 files are served with short cache lifetimes, so returning visitors download them again (58 KiB).
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.
1 checks passed
Server response: 82 ms
82 msYour server sent the HTML in 82 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: 11.9 s
11.9 sYour largest element takes 11.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.
Time to Interactive: 16.6 s
16.6 sThe page becomes fully interactive after 16.6 s. Good is under 3.8 s.
Total Blocking Time: 1.5 s
1.5 sScripts block taps and scrolling for 1.5 s in total while the page loads. Good is under 200 ms.
Speed Index: 7.7 s
7.7 sVisually, the page fills in at 7.7 s (Speed Index). Good is under 3.4 s.
Real-user CLS: 0.19
0.19For real visitors the layout shifts by 0.19 (75th percentile). Good is under 0.1.
Cumulative Layout Shift: 0.21
0.21The layout shifts by 0.21 while loading, so content jumps under the reader's thumb. Good is under 0.1.
First Contentful Paint: 2.3 s
2.3 sThe first text or image appears after 2.3 s on a phone. Good is under 1.8 s.
Largest content (LCP) held steady for real visitors
+3%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 1.8 s to 1.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
2 checks passed
Real-user FCP: 0.8 s
0.8 sReal visitors see the first content after 0.8 s (75th percentile). Good is under 1.8 s.
Tap response (INP) got 79% faster for real visitors
-79%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 790 ms to 221 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Images and page weight
Page weight: 4.3 MB in 263 requests
4.3 MBYour homepage downloads 4.3 MB in 263 requests on a phone: other files 2.2 MB (157), scripts 1.6 MB (79) and images 167 KiB (12). Under 2 MB keeps phones on slow connections fast.
About 1.2 g of CO₂ per visit
1.21 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.21 g of CO₂e: 144.6 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
Unlabelled dropdowns
3 dropdowns have no label.
Invalid ARIA attributes
1 element use ARIA attributes their role does not allow, which confuses screen readers.
4 text elements with low contrast
4 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Scrollable region must have keyboard access (1 element)
Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.
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.
3 form fields without a label
3 form fields have no label, so screen readers announce an empty box and autofill guesses.
Alternative text of images should not be repeated as text (1 element)
Alternative text of images should not be repeated as text: 1 element on the page fails this check, rated minor by axe-core.
2 checks passed
Every image has alt text
All 7 images in the HTML carry an alt attribute.
47 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: 47 passed and 7 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
132 internal links, 0 external
The homepage links to 132 pages on trekhaken.nl and 0 external pages.
7 checks passed
Meta description: 144 characters
Your meta description is 144 characters: “Trekhaak Kopen? Bestel bij dé Auto Trekhaak Specialist van Nederland! ➔ ✓Trekhaken Kopen op Kenteken ✓Fietsendragers & …”.
One H1 headline
Your main headline reads: “Trekhaken”.
Title: 58 characters
Your title is a healthy 58 characters: “Trekhaak Kopen? Trekhaken.nl: dé Auto Trekhaak Specialist!”.
Canonical URL set
The canonical URL is https://trekhaken.nl/.
Structured data in place
Structured data found: BreadcrumbList.
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://trekhaken.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.
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 (468 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://trekhaken.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://trekhaken.nl/collections/transport-op-trekhaak, https://trekhaken.nl/collections/transport-op-dakdrager, https://trekhaken.nl/collections/trekhaakaccessoires-universeel and https://trekhaken.nl/collections/bescherming-kogels-behuizingen have no meta description, so Google writes the search snippet from whatever text it finds.
5 pages without an H1
https://trekhaken.nl/collections/trekhaken-kabelsets, https://trekhaken.nl/collections/transport-op-trekhaak, https://trekhaken.nl/collections/transport-op-dakdrager, https://trekhaken.nl/collections/trekhaakaccessoires-universeel and https://trekhaken.nl/collections/bescherming-kogels-behuizingen have no <h1> headline, so visitors and search engines get no clear main topic.
1 page with very little text
https://trekhaken.nl/collections/bescherming-kogels-behuizingen has 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.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 66 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 5 pages that loaded have a <title>.
Best practices
Missing source maps
Large scripts ship without source maps.
3 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Tap targets are thumb-sized
37 of 43 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 social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
No analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
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 397 words of copy
The homepage carries about 397 words of visible text.
3 checks passed
4 calls to action
The homepage has 4 calls to action, for example “Contact” and “Shop onze producten”.
10 short forms
10 short forms (4 fields at most) are right on the homepage.
Direct contact links
Visitors can reach you directly: 2 phone links and 1 email link.
Privacy and tracking
5 trackers load before any consent
5Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Microsoft Clarity (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.
20 cookies set on arrival
20Opening the homepage sets 20 cookies (measured from a US location before any click).
28 other companies contacted
Loading the homepage contacts 28 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 trekhaken.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 4 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Bss B2b Quotes · Bss B2b Solution · Klaviyo Email Marketing Sms · bsscommerce.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
- jQuery
- E-commerce
- Shopify
- Hosting
- Shopify
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 trekhaken.nl, including 15 speed issues, 1 SEO issue 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.