kadukessler.com
success
Claude Code
intent

What does kadukessler.com do and who is it for? Explain it back to me.

3steps
33.2sduration
$0.1499cost
13,585tokens
6 steps3 reasoning steps
home
home
home
83%
answer from your site
67%
answer efficiency
100%
followed site links
answer sources
  • from this site83%
  • from agent knowledge17%
url discovery
  • given in the task33%
  • followed a link67%
insight

The agent successfully retrieved and synthesized Kadu Kessler's portfolio to answer the evaluation task. The site was navigable but required multiple fetches of the same homepage URL—the agent did not discover or follow internal navigation links, relying instead on repeated memory-typed calls that returned the same root page with different response framings.

  • ›All content-bearing steps fetched the same URL (kadukessler.com/) typed from memory, not discovered via on-site navigation. The site does not appear to expose internal links or a sitemap, forcing the agent to re-fetch the root to extract different answer facets from what may be a single-page application or server-side dynamic rendering.
  • ›The homepage successfully returned actionable information about Kadu's specialization, projects, skills, and employment status in a machine-readable narrative form, allowing the agent to extract answers to all four core questions (what, who, pricing, differentiation) without requiring third-party sources.
  • ›Pricing information was genuinely absent from the site (not missed by the agent), which the agent correctly identified and explained contextually—this is a portfolio, not a marketplace—rather than guessing or hallucinating rates.
  • ›The agent's 'confusing/missing' section (unclear availability, vague call-to-action) represents model inference about portfolio UX gaps rather than unsurfaced site content; these are reasonable observations but not grounded in fetched page details, indicating potential over-interpretation.
  • ›The site's single-page or shallow structure reduced friction for discovery but also meant the agent had no secondary pages to follow, limiting how much navigation 'from links' could occur (only 67% of discovery came from following links; 33% from typed memory—skewed heavily toward memory because there were few alternative paths to take).

See every agent that visits kadukessler.com

Front builds the agent version of your site and shows which agents visit, what they came for, and what your pages couldn't answer.

or talk to us about agent readiness →