strasbourg-esport.fr
success
Claude Code
intent
What does strasbourg-esport.fr do and who is it for? Explain it back to me.
20steps
81.6sduration
$0.8898cost
355,943tokens
34 steps14 reasoning steps6 searches
home
home
/tarifs
docs
docs
/lan
/univers
/animations
/billetterie
/tickets
search
/e/strasbourg-esport-d…
/contact
search
search
/2026/08/19/league-of-…
/strasbourg-esport-day…
search
search
search
79%
on-site discovery
43%
reliability
29%
link following
path origin
- previous resource29%
- web search21%
- prior knowledge50%
insight
The agent successfully assembled a comprehensive understanding of Strasbourg Esport Days by combining the official site's minimal landing page with external sources (news articles, Eventbrite, blog posts). The official website itself is poorly navigable—most direct page guesses (tarifs, pricing, contact, animations, billetterie) returned 404s, forcing the agent to rely on web search and prior knowledge to answer what the event is, who it's for, pricing, and competitive positioning.
- ›The official site (steps [1], [8]) returned only HTML shells without extractable content; the agent could not read visible text from the raw responses, making direct site navigation useless. Instead, web search results (step [15], [22]) and external ticketing/news pages (steps [17], [24], [26]) provided all substantive information: event dates, pricing (€9–€12), activities (LAN tournaments, VR, cosplay), and regional differentiation.
- ›The agent had to guess or infer most page paths (/tarifs, /billetterie, /contact, /animations, /univers) based on common French site conventions; all returned 404s. Only the homepage and /lan route returned 200s, yet the /lan page content was similarly opaque in the raw HTML, suggesting a JavaScript-heavy site that doesn't render its content server-side or isn't crawlable by conventional means.
- ›The site is a thin event-promotion landing page without self-contained, machine-readable documentation. Pricing, schedule, activity details, and competitive context had to be sourced from Eventbrite, news articles (Pokaa, Blog-jeu), and web search snippets—not from the official domain. The agent explicitly noted missing pages, unclear registration flow, and incomplete program details as gaps in the site's accessibility.
- ›The agent cited its sources as the official site (for branding/date) plus external pages (Pokaa, Blog-jeu, Eventbrite) in the final answer, signaling that the official site alone could not have answered the task. The heavy reliance on web search (21% of fetch sources) and prior knowledge (50%) reflects poor site surface area.
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 →