portfolio-2027-one.vercel.app
success
Claude Code
intent

What does portfolio-2027-one.vercel.app do and who is it for? Explain it back to me.

6steps
37.0sduration
$0.2183cost
25,552tokens
8 steps2 reasoning steps
home
home
docs
/work
home
/playground
80%
answer from your site
50%
answer efficiency
80%
followed site links
answer sources
  • from this site80%
  • from agent knowledge20%
url discovery
  • given in the task17%
  • followed a link67%
  • guessed the URL17%
insight

The agent successfully understood the site's core purpose, positioning, and differentiators by fetching the homepage and about page. Navigation was straightforward but incomplete—the /work portfolio link returned a 404, and the site lacks a clear contact or engagement flow, requiring the agent to infer gaps rather than retrieve them.

  • ›The homepage and /about page were the only content-bearing fetches; they directly answered what Arthur does, who he targets, and his differentiators. No search or external content was used.
  • ›The /work page returned a 404 error, blocking access to detailed case studies that would normally be the core of a designer portfolio. The agent had to synthesize project descriptions from the homepage instead.
  • ›Pricing was correctly identified as absent from the site—this is standard for portfolio sites but represents a gap the agent had to interpret rather than retrieve.
  • ›The /playground section was fetched but returned no usable content; the agent could not describe what was in it, revealing a navigation surface that exists but is not navigable.
  • ›The agent discovered 67% of URLs by following links from fetched pages and 33% by typing from memory, indicating the site did not surface all its content via navigation—the agent had to guess the /about and /playground paths.

See every agent that visits portfolio-2027-one.vercel.app

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 →