Website review, no card needed
fincut.nl website review
Visit site (opens in a new tab)Reviewed 11 November 202625 issues · 62 checks
This review found 25 issues worth fixing on fincut.nl, 9 of them high impact, across 62 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
76C- #66,762 of 108,844 reviewed websitesbeats 34%
- #42,925 of 61,763 online storesbeats 26%
- #40,746 of 56,363 Shopify storesbeats 23%
Closest competitors among Shopify stores
Compare side by sideOne score from every part of this review. How it works
Speed
Reduce unused JavaScript
1.2 s · 311 KiBAbout 311 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.2 s faster on a phone.
Mobile performance score: 70
70/100Your mobile performance score is 70. Pages that score under 90 lose visitors before the first paint.
Use efficient cache lifetimes
450 ms · 112 KiB5 files are served with short cache lifetimes, so returning visitors download them again (112 KiB).
Render-blocking requests
250 ms3 files block the first paint until they finish downloading. Deferring or inlining them could save about 250 ms.
Reduce unused CSS
150 ms · 47 KiBAbout 47 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.
5 third-party services on the page
5 third-party services load with your homepage (Shopify, kiwisizing.com and loox.io and others), adding 330 KiB and 153 ms of main-thread time.
1 long task on the main thread
1 long task block the main thread while loading, the longest for 65 ms. During a long task the page ignores taps.
Minify CSS
8 KiB8 KiB could be saved by minifying CSS.
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.9 s
A phone's processor spends 0.9 s on main-thread work while loading, 368 ms of it running JavaScript. That is comfortably low.
Server response: 4 ms
4 msYour server sent the HTML in 4 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 8.7 s
8.7 sYour largest element takes 8.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Time to Interactive: 8.7 s
8.7 sThe page becomes fully interactive after 8.7 s. Good is under 3.8 s.
Speed Index: 5.2 s
5.2 sVisually, the page fills in at 5.2 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.
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
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Total Blocking Time: 15 ms
15 msScripts block the page for only 15 ms while loading. Good is under 200 ms.
Images and page weight
About 0.5 g of CO₂ per visit
0.46 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.46 g of CO₂e: 54.7 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Page weight: 1.6 MB in 153 requests
1.6 MBYour homepage downloads 1.6 MB in 153 requests on a phone: other files 784 KiB (100), scripts 500 KiB (35) and images 189 KiB (10). That is a lean page.
Accessibility
Delayed refresh under 20 hours must not be used (1 element)
Delayed refresh under 20 hours must not be used: 1 element on the page fails this check, rated critical by axe-core.
2 buttons without a name
2 buttons have no accessible name, so screen readers announce just “button”.
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.
1 tap target too small
1 tap target is too small or too close together to hit reliably with a finger.
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.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (1 element).
2 checks passed
Every image has alt text
All 39 images in the HTML carry an alt attribute.
20 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 23 WCAG 2.2 A/AA and best-practice rules on the phone render: 20 passed and 3 failed. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No meta description
No meta description, so Google writes its own snippet from whatever text it finds.
Title is short (18 characters)
Your title is only 18 characters: “Fincut Netherlands”. Between 30 and 65 characters leaves room to say what you do and for whom.
No social preview image
No Open Graph image (also missing: og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.
83 internal links, 2 external
The homepage links to 83 pages on fincut.nl and 2 external pages.
5 checks passed
One H1 headline
Your main headline reads: “Fincut Netherlands”.
Canonical URL set
The canonical URL is https://fincut.nl/.
Structured data in place
Structured data found: BreadcrumbList, Organization and WebSite.
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://fincut.nl/sitemap.xml.
AI search readiness
Organization data is thin (3 of 6 facts)
Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.
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.
llms.txt published
The site publishes https://fincut.nl/llms.txt (5 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
2 pages share a title
/ and https://fincut.nl/apps/track123 all use the title “Fincut Netherlands”. Search engines can't tell which page to show for a search, so each competes with the others.
12 pages without a meta description
https://fincut.nl/collections/cols-r-all, https://fincut.nl/collections/pakket-van-9, https://fincut.nl/collections/pakket-van-6, https://fincut.nl/collections/pakket-van-4, https://fincut.nl/collections/pakket-van-3 and https://fincut.nl/collections/pakket-van-2 and 6 others have no meta description, so Google writes the search snippet from whatever text it finds.
10 pages without an H1
https://fincut.nl/collections/cols-r-all, https://fincut.nl/collections/pakket-van-9, https://fincut.nl/collections/pakket-van-6, https://fincut.nl/collections/pakket-van-4, https://fincut.nl/collections/pakket-van-3 and https://fincut.nl/collections/pakket-van-2 and 4 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 32 found) and read each the way a search engine does.
4 checks passed
Linked pages load
14 pages of 15 loaded without an error (the rest turned automated requests away).
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 14 pages that loaded have a <title>.
Best practices
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 429 ()”.
1 checks passed
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.
Only about 10 words
The homepage has only about 10 words of visible text; thin pages give Google and first-time buyers little to go on.
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
4 calls to action
The homepage has 4 calls to action, for example “Contact” and “[email protected]”.
2 short forms
2 short forms (1 field at most) are right on the homepage.
Direct contact links
Visitors can reach you directly: 0 phone links and 1 email link.
Privacy and tracking
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.
2 other companies contacted
Loading the homepage contacts 2 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
No known trackers before consent
No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).
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 fincut.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 3 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Wair Size Fit Recommendation · loox.io · kiwisizing.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
- 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 25 issues on fincut.nl, including 7 speed issues, 3 SEO issues 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.