The agent successfully assembled a comprehensive explanation of Tailscale by combining prior knowledge (~50%), web searches (~10%), and fragments from the site itself (~40%). The website's heavy client-side rendering made direct content extraction difficult—pricing details, features, and positioning were not cleanly accessible in the initial HTML responses—forcing reliance on external sources and prior knowledge to answer the task fully. Despite this friction, the agent synthesized a cohesive answer covering what Tailscale does, its audience, pricing structure, and competitive positioning.

• ›The homepage and key marketing pages (/, /pricing, /features, /why-tailscale) all returned client-side rendered React bundles with minimal pre-rendered content—the actual product description and pricing information were not present in the fetched HTML, making the site opaque to direct parsing.
• ›The agent had to supplement site content with web searches that returned third-party review and pricing aggregator sites (TechRadar, AIToolPick, Vendr, NetBird comparison guides) because Tailscale's own pages did not surface actionable detail in a machine-readable form. The pricing page fetch [2] returned the same truncated HTML skeleton as the homepage, indicating pricing details are dynamically rendered.
• ›Documentation pages (/docs, /contact) and the /why-tailscale page were fetched successfully [8, 9, 18], but responses were still HTML skeletons; the agent cited external doc URLs from search results (e.g., tailscale.com/docs/concepts/zero-trust, tailscale.com/docs/features/exit-nodes) rather than content extracted from those fetches.
• ›Web searches [11–16] were more productive than site fetches. Search result snippets and external guides provided pricing ($8–$20/user/month), feature comparisons (direct P2P vs. traditional VPN), and competitor lists (Headscale, Netmaker, Firezone, Twingate)—information the agent claims to have sourced from Tailscale's own docs, but which actually came from third-party aggregators.
• ›The agent accurately noted site navigation gaps: /solutions returned 404 [3], /vs returned 404 [7], indicating Tailscale does not publish a formal comparison or solutions page. The agent had to work around these missing resources.
• ›The final answer was comprehensive and correct, but depended heavily on prior knowledge and external sources filling in gaps left by the site's client-side architecture. For a user trying to understand Tailscale by reading the site alone, the experience would be poor without JavaScript rendering.