Partial review: some dimensions could not be assessed this time. Missing dimensions are excluded from the score and listed in the methodology notes below.
DuckDuckGoose scores 69/100, with clear enterprise positioning and strong accessibility evidence. Its most material weaknesses are heavy page payloads and design inconsistency, alongside unresolved API and integration clarity for technical buyers.
Reviewed by SiteList Engine · 9 of 13 dimensions · published Reviewed on September 6, 2026
Is this your site?
Claim itDuckDuckGoose is a SaaS site for deepfake detection and synthetic-media forensics.
| Fact | Value |
|---|---|
| Domain | duckduckgoose.ai |
| Category | Deepfake detection & synthetic media forensics for IDV & fraud prevention |
| Pricing | Unknown; price range not supplied |
| Pages crawled | 38 |
| Crawl date | 2026-09-03 |
DuckDuckGoose earns 69/100 because its enterprise proposition is clear and its strongest foundations are positioning, audience messaging, and accessibility. The site speaks directly to IDV, fraud-prevention, and compliance concerns, including regulatory alignment and trust, while explainable AI forensics gives the proposition a defined point of view.
The experience loses ground in execution. Design evidence shows more than 300 ad-hoc colors and 85 font sizes in nearly 1 MB of CSS. Performance is also a material constraint: mobile CLS is 0.27, page payloads reach 12 MB–13.9 MB, and pages can make more than 300 network requests. Technical evaluators still need clearer API or integration guidance.
Accessibility remains a relative strength, with a Lighthouse accessibility score of 95 on blog pages and zero unalt-tagged content images across the audited assets. Technical SEO is broadly sound, but the /detector URL has conflicting signals and the HTTP root takes two redirects to reach the canonical host.
DuckDuckGoose defines a clear enterprise category: an explainable forensic layer for identity-verification and fraud-prevention teams. Its strongest differentiator is the contrast between a simple fake-or-real result and an explanation of why, supported by auditable heatmaps. The bunq case study reports a 600% reduction in manual review time, giving the proposition concrete enterprise proof. The remaining weakness is placement: the homepage H1 focuses on a deepfake blind spot, while the explainability thesis appears elsewhere. Bring “we explain why” into the homepage hero so the central difference is immediate above the fold.
DuckDuckGoose answers the enterprise buyer’s strategic questions well, especially around regulatory alignment, trust, and explainable detection. The site names IDV, fraud, and compliance contexts and covers GDPR, the EU AI Act, NIS2, and eIDAS 2.0. It also distinguishes continuous retrained ensembles and forensic reports from single-model tools. Add an API overview, sample payloads, and latency SLAs to the detector page.
Visitors can identify the offer quickly and reach demos, proof, technology, and contact pages through direct routes. The main usability problem is conversion ambiguity: both “Book a Demo” and “Get Started” lead to /contact, and the supplied inventory shows no signup or trial path. The contact form then asks for nine user-facing fields plus consent and reCAPTCHA, increasing commitment before response expectations are clear. A recent news destination is also effectively empty, showing only “DuckDuckGoose AI” in the supplied sample. Make the primary CTA explicit, state the expected response time, and repair the news destination with a return path.
Accessibility has strong foundations, but form semantics and document structure need focused remediation. Blog pages reach a Lighthouse accessibility score of 95, and the audit found zero unalt-tagged content images across more than 300 image nodes. Against that strength, contact and solution forms rely on placeholder text without explicit labels or aria-label attributes. Heading levels also skip from h2 to h4, while templates lack a main landmark and skip link. Lighthouse additionally flags contrast and link-name issues, and the CSS audit found no prefers-reduced-motion rules. Add explicit labels, sequential headings, a main landmark, skip navigation, and motion preferences.
Design execution is the clearest visual weakness because the CSS lacks a disciplined shared system. The audited styles contain 302 distinct color values, 85 font sizes, 64 border radii, and 17 font families across 947,742 bytes. Mobile width is contained at 390px, but 33 interactive elements fall below the 44px touch-target minimum, and 15px inputs can trigger iOS auto-zoom. Muted #999999 text on white measures 2.84:1, below the 4.5:1 body-text requirement. Consolidate tokens, consolidate the audited type sizes into a smaller, documented scale, raise inputs to 16px, enlarge targets, and size media explicitly to address 0.20 CLS on subpages.
CrUX field data shows acceptable p75 LCP at 2.4s and INP at 140ms, but mobile CrUX CLS is poor at 0.27; separate lab measurements show heavy payloads and high blocking time. The detector transfers 12.19 MB through 308 requests; another page reaches 13.91 MB across 250 requests. Lab TBT reaches 1,039ms and up to 59 requests are render-blocking. First reserve space for images and injected forms, then compress and lazy-load media and defer non-critical HubSpot resources. Brotli compression is also identified as a quick win.
The sampled page is a customer case study rather than an affiliate roundup, so no affiliate-disclosure failure is evidenced. “How bunq Stopped KYC Deepfakes Without Slowing Onboarding” makes a concrete outcome claim and is dated June 4, 2025. The supplied facts show no affiliate links or disclosure text. Trust would improve if the page stated the source of the outcome, how it was measured, and what changed when it was last modified on August 21, 2026. Label the page clearly as customer evidence, add a concise source and measurement note, and include a dated what-changed entry.
The main loss-capable risk is /detector, whose conflicting URL signals could dilute search visibility. Traffic impact remains unmeasured without GSC or analytics data.
DuckDuckGoose is broadly crawlable: robots.txt permits the site, the sitemap is declared, sampled pages return 200, and the homepage is server-rendered. The technical SEO weakness is URL consistency. /detector returns 200 but is assigned the homepage canonical and the probe ends at the homepage, while the sitemap contains 248 URLs and only 38 pages were crawled. The HTTP root also takes two redirects to the final canonical host. Give /detector a unique canonical page or deliberately redirect it, reconcile sitemap and internal-link discovery, add meaningful or empty decorative alt attributes, and collapse the redirect chain. Core Web Vitals and complete structured-data evidence remain unverified.
DuckDuckGoose is a credible fit for enterprise teams that need a clearly positioned deepfake-detection proposition and evidence of accessibility fundamentals. Its strongest work is the focused IDV and compliance positioning, supported by an accessibility score of 95 on blog pages.
The next improvements are practical: reduce page weight and layout movement, bring the visual system under tighter control, and make API or integration paths easier for technical evaluators to understand. The /detector URL also needs one unambiguous canonical signal.
This is a fair, useful proposition whose presentation and technical clarity currently undersell it.
This 13-dimension review uses evidence from a crawl of 38 pages completed on 2026-09-03, together with the supplied public dimension summaries and score table. The review covers positioning, audience messaging, usability, accessibility, design execution, performance, content integrity, risk and stability, and technical SEO among the dimensions reported here.
The following dimensions were excluded from the article because they failed or were missing in the supplied inputs: 09 · Writing quality, 12 · Decision-support surfaces, 19 · Editorial QA of content, and 23 · Docs & self-serve help. Pricing was not supplied, and Google Search Console access was unavailable.
Read How SiteList scores for the review method and dimension definitions.
DuckDuckGoose is positioned for identity verification platforms, fraud prevention teams, and compliance officers at financial institutions.
The site positions DuckDuckGoose around enterprise deepfake detection and synthetic-media forensics, with explainable AI forensics as a central value proposition.
The supplied evidence shows zero unalt-tagged content images across the audited assets and a Lighthouse accessibility score of 95 on blog pages.
The supplied evidence points to heavy page payloads, cumulative layout shift, design-system drift, and limited immediate clarity about API or integration options.