Overall Score
Flatfish remains in a cryogenic state of digital neglect—identical content, zero improvements on any front, and complete disregard for the previous eight-month critique. This is not stagnation; it's willful abandonment of their own digital storefront.
The Roast
Flatfish has achieved something remarkable: they've managed to ignore eight months of brutally specific, actionable feedback and pretend their website doesn't exist. It's like a locksmith whose front door lock is broken—except they've had 240 days to fix it. The audacity to claim 'technical partnership' credentials while refusing to implement a skip-to-content link (literally a 2-minute fix) or add schema markup is genuinely breathtaking. They've built software for clients but apparently view their own site as a problem for future-them. Future-them is never arriving.
🎯 Start Here
Google PageSpeed Insights
(Real metrics from Google)These scores come directly from Google's PageSpeed API. The AI scores above evaluate broader aspects like copy, trust signals, and conversion.
Core Web Vitals
Trust Signals
SEO
Conversion
Copy & Messaging
Design & UX
Accessibility
Mobile
Performance
Trust Signals
Completely neglected since June—client logos remain unlinked decoration with zero testimonials or success metrics, zero credibility signals (no team bios, security badges, or press mentions), and KVK number hidden in unreadable footer text.
Issues Found
- Client logos remain unlinked, unquoted, and unverified—no testimonial snippets ('Flatfish delivered our SaaS MVP in 8 weeks'), no success metrics ('Reduced time-to-market by 60%,' 'Scaled to 100K+ users'), no case study links
- Zero credibility signals visible: no team bios or LinkedIn links, no security badges (SOC2, ISO 27001, GDPR compliance), no press mentions or third-party certifications; KVK number (6527303) hidden in 8pt footer—doesn't inspire confidence in a software partner
- No social proof dashboard or quantified metrics—missing '50+ projects delivered,' 'Founded 2019,' 'Avg project delivery 12 weeks,' '98% client satisfaction,' 'Team of 8 Symfony experts'; prospects cannot benchmark credibility
Recommendations
-
Create quantified trust dashboard high
Add visible metrics above fold: '45+ SaaS Products Delivered,' 'Founded 2019,' 'Average Delivery: 12 Weeks,' '98% Client Retention,' 'Team of 10 Symfony + AI Experts'—use icons and bold typography.
-
Link client logos to testimonials + case studies high
Each logo links to 3-5 line testimonial ('Reduced deployment from 4h to 30m') and full case study with metrics, screenshots, client quote with name/title/LinkedIn.
-
Add security & credibility signals medium
Display GDPR compliance statement, SOC2 Audit readiness, LinkedIn team links (CEO + 3 senior devs), and 2-3 press/award logos if available; move KVK from footer to 'About' section with founding date and team headcount.
SEO
Completely untouched since June—249 words of anemic content, zero schema markup, and generic headings that couldn't rank for a misspelled search term. Google has basically ghosted this site.
Issues Found
- Content volume critically low (249 words vs. 2,000+ required); cannot rank for 'Symfony webapplicatie ontwikkeling,' 'SaaS MVP bouw,' 'AI integraties ChatGPT'
- Zero schema.org markup (Organization, SoftwareApplication, LocalBusiness, FAQSchema); Google cannot auto-index credentials, services, location, or testimonials
- Heading keywords generic ('Onze diensten,' 'Hoe wij werken') with zero high-intent terms like 'Enterprise SaaS Gebouwd op Symfony' or 'AI Integraties voor Bedrijfsautomatie'
Recommendations
-
Expand content to 2,500+ words high
Add service deep-dives (SaaS architecture decisions, API scalability, AI integration frameworks), client success metrics, tech stack details, and location-specific keywords ('Amsterdam SaaS developers,' 'Utrecht Symfony specialists').
-
Implement schema.org markup high
Add Organization schema (KVK, founding date, location), SoftwareApplication schema (services offered), LocalBusiness schema (Amsterdam HQ), and FAQSchema for common questions.
-
Rewrite headings with keyword intent medium
H2: 'SaaS Development Services for Enterprise Scaling' (not 'Onze diensten'); H2: 'Agile Custom Software Development Process' (not 'Hoe wij werken').
Conversion
Completely unchanged: client logos remain unlinked orphans with zero proof metrics, contact form demands blind commitment with no friction-reduction, and zero funnel segmentation for different prospect stages.
Issues Found
- Client logos (Chalet.nl, Portfoliio, Alphacomm, De Valkshag, Lamppoint) remain unlinked and unquoted—no case study links, testimonial snippets, or proof metrics ('Reduced deployment time by 60%'); logos alone don't convert
- Contact form lacks context: no response-time guarantee, no alternative friction-reduction (live chat, Calendly embed, phone scheduling), no reassurance copy about data confidentiality
- Zero funnel segmentation: all prospects forced through identical contact flow; missing lead magnets (SaaS Dev Checklist PDF, tech stack guide), webinar invites, or low-friction exploration resources
Recommendations
-
Link client logos to case studies with metrics high
Create 3-5 one-page case studies (problem → solution → metrics: 'Reduced deployment from 4 hours to 30 mins,' 'Scaled to 500K MAU'); link logos to studies with testimonial snippets.
-
Add friction-reduction to contact form high
Add response-time guarantee ('We reply within 2 hours'), Calendly embed for direct scheduling, or live chat toggle to reduce blind-commitment anxiety.
-
Create segmented funnel for awareness stages medium
Add early-stage resource (SaaS Dev Checklist PDF, '5-Step Enterprise Software Roadmap') as lead magnet; separate high-intent CTA ('Schedule Project Discovery') from exploratory CTA ('Get Free Tech Audit').
Copy & Messaging
Still describing what you do instead of what customers gain—H1 is capability-focused drivel, service copy is generic boilerplate, and CTAs remain passive and indistinguishable across the page.
Issues Found
- Hero H1 ('Uw partner in software ontwikkeling') describes capability, not customer outcome—zero urgency or competitive differentiation
- Service descriptions remain benefit-agnostic ('Wij bouwen schaalbare SaaS producten van scratch') without proof, outcomes, or 'why this matters' statements
- CTA copy ('Start uw project,' 'Bespreken uw project,' 'Bespreek uw project') is passive and identical—missing urgency or scarcity language
Recommendations
-
Rewrite H1 with outcome focus high
Change to customer-facing result: 'Schaalbare SaaS-Producten in 12 Weken—Van Idee naar Miljoen Gebruikers' or 'Enterprise-Grade Software Gebouwd op Symfony voor Nederlands Bedrijven.'
-
Add outcome-driven service descriptions high
Follow each service with proof statement: 'SaaS: Snel schalen naar 100K+ gebruikers zonder performance verlies' + one metric or client result.
-
Differentiate CTA copy by stage medium
Hero CTA: 'Schedule Your Free Technical Audit' (exploratory); footer CTA: 'Start Your Project Today' (commitment); add response-time promise ('We reply within 2 hours').
Design & UX
Still visually competent but strategically lazy—service cards remain undifferentiated boxes, process flow lacks directional indicators, and hero/CTA gradients are still embarrassingly identical copies of each other.
Issues Found
- Service cards (SaaS, Maatwerk, API, AI) remain identical in visual weight with no hierarchy signaling customer pain points or revenue drivers
- Process section still lacks numbered steps, arrows, or flow indicators—four isolated boxes instead of a sequential journey
- Hero and bottom CTA sections use identical blue-to-purple gradients, making CTAs feel repetitive rather than progression
Recommendations
-
Implement visual service hierarchy high
Highlight primary service (likely SaaS) with larger card size, distinct color, or badge ('Most Popular') to guide visitor attention toward revenue service.
-
Add process flow indicators medium
Connect the four process boxes with numbered circles (1→2→3→4) and directional arrows to create perceivable journey momentum.
-
Differentiate CTA section gradient low
Replace bottom CTA gradient with distinct color (complementary accent) to signal progression from hero and create visual separation.
Accessibility
Still missing trivial WCAG Level A fixes—no skip-to-content link (2-minute fix ignored 8 months), unverified heading hierarchy, and ARIA semantic alignment remains unchecked. Genuinely lazy.
Issues Found
- No skip-to-content link: keyboard users must tab through 4 nav items before reaching H1—violates WCAG 2.1 Level A (2.4.1 Bypass Blocks); eight-month-old criticism completely ignored
- Heading hierarchy nesting unverified: h1:1, h2:4, h3:8, h4:2 present but actual nesting order unknown; if h3 appears before h2, screen readers cannot build accurate document outline
- ARIA semantic alignment unchecked: no confirmation that aria-labels match roles or don't redundantly conflict with native HTML semantics
Recommendations
-
Add skip-to-content link (DO THIS TODAY) high
Insert `<a href='#main' class='skip-link'>Skip to content</a>` in header, position off-screen, show on focus; 2-minute fix that should have been done 8 months ago.
-
Audit heading hierarchy structure medium
Verify h1 → h2 → h3 proper nesting (no skips, no h3 before h2); use axe DevTools or WAVE to auto-validate; fix any misalignments.
-
Clean up ARIA usage medium
Remove redundant aria-labels on native buttons/links where label text already exists; ensure aria-labels only enhance, not conflict, with semantics.
Mobile
Still mobile-unfriendly at the funnel level—service cards stack flat without accordion/priority indicators, no sticky CTA or back-to-top affordances, and hamburger menu behavior remains unverified.
Issues Found
- Service card stacking on mobile remains flat—all four cards stack 1-column at identical height/prominence with no accordion collapse or 'Learn more' expansion; fourth card buried below fold
- No sticky mobile CTA or back-to-top button—users must scroll entire page (6,000px+ on mobile) from hero to contact with zero quick-access; 'Start uw project' button vanishes after hero
- Hamburger menu behavior unverified—no indication if nav persists on scroll (sticky), auto-closes after link, or requires manual close; on <375px phones, icons may misalign
Recommendations
-
Prioritize service cards with accordion/tabs high
Replace flat stack with tabbed interface ('SaaS' selected by default) or accordion collapse to reduce scroll friction; highlight primary service at top.
-
Add sticky mobile CTA or back-to-top medium
Implement floating 'Get In Touch' button (sticky footer, 48px tap target) or back-to-top affordance; auto-hide on scroll-down, show on scroll-up.
-
Verify hamburger menu UX medium
Confirm menu auto-closes after link selection, nav icons render >16px on small screens, and menu persists on scroll (sticky header); test on iPhone SE and Android 375px devices.
Performance
Score remains respectable at 2.31s LCP, but 'reduce unused JavaScript' flag persists unchecked—you're leaving 20-30% performance gains on the table while claiming to be a technical partner.
Issues Found
- LCP at 2.31s functional but not premium-tier (Vercel/Stripe achieve 0.8-1.2s); introduces friction on 4G or mid-range devices
- Unused JavaScript flagged but unaddressed—polyfills, vendor libraries, or non-critical scripts bloat main bundle; tree-shaking opportunity ignored
- TBT at 0ms is good, but unused JS could spike interaction smoothness during user interactions
Recommendations
-
Tree-shake unused JavaScript high
Audit bundle dependencies, remove polyfills for unsupported browsers, code-split vendor scripts, and defer non-critical animations to next-paint.
-
Optimize LCP to <1.5s medium
Preload critical CSS/fonts, lazy-load below-fold images, minimize hero image filesize, and ensure primary font loads inline.
-
Monitor CWV quarterly low
Set up Lighthouse CI in deployment pipeline to catch regressions; establish 'Core Web Vitals passing' as merge gate.
Think you can beat 64/100?
Get your site brutally analyzed by the same AI. 8 scores, a punch list of fixes, 60 seconds.