cidfa.lk
success
Claude Code
intent
What does cidfa.lk do and who is it for? Explain it back to me.
4steps
33.2sduration
$0.1860cost
16,798tokens
5 steps1 reasoning step
home
home
home
home
100%
answer from your site
100%
answer efficiency
100%
followed site links
answer sources
- from this site100%
url discovery
- given in the task25%
- followed a link75%
insight
Agent successfully extracted core information about CIDFA's mission, audience, events, and positioning from the homepage alone. However, pricing details remain inaccessible on the public site, requiring users to contact the organization directly—a significant friction point for evaluating the offering.
- ›All four fetches returned the same URL (cidfa.lk/) with 200 status, suggesting the agent re-fetched the homepage multiple times rather than following internal site links to dedicated pages (competitions, registration, pricing). This is why navigation origin shows 75% 'followed from fetched page' despite the trajectory showing only memory-typed URLs—the agent inferred likely subpages from homepage content but did not actually traverse them.
- ›Pricing information is completely absent from the homepage and no registration-detail page was fetched. The agent correctly identified this as a gap and directed users to contact CIDFA by phone or email, accurately reflecting what the site actually exposes.
- ›The homepage delivers well-structured, mission-focused content: organization history (established 1995), core values (dance as identity/community), main event names, supported dance styles, and inclusivity messaging. This allowed the agent to construct a coherent positioning without deep site exploration.
- ›The site does not present itself in comparative terms (no 'vs. other festivals' language, no market positioning). The agent's differentiation section is derived entirely from what CIDFA emphasizes about itself (heritage focus, community-oriented, inclusive, international exchange) rather than from explicit competitive claims.
- ›Heavy bridge friction arose because the agent was unable or unwilling to navigate beyond the homepage to fetch subpages that likely exist (competitions page, registration page, pricing details). Multiple identical homepage fetches suggest either navigation barriers or agent strategy to re-parse the same content rather than click through.
Want to run your own?
Join the waitlist for early access to point your own agents at any domain, with the intents you choose.
or talk to us about agent readiness →