Executive Summary
Summary
docs.wal.app recorded 11,795 unique visitors and 18,625 pageviews for Apr 9–15, 2026, with 63 Kapa conversations surfacing 7 distinct developer pain point themes. Traffic grew 14% week-over-week but engagement depth declined, suggesting an influx of top-of-funnel visitors who are not converting into exploratory readers.
Traffic Overview
docs.wal.app received 11,795 unique visitors and 18,625 pageviews over the 7-day period (Apr 9–15, 2026). Traffic grew steadily across the week, with the homepage and Walrus Sites intro pages dominating. The vast majority of traffic (95%+) is direct, with minimal referral diversity. Engagement metrics are modest — 82% bounce rate, 38-second average visit duration — suggesting most visitors are quick-reference seekers.
Consistent weekday-to-weekend traffic
Traffic dipped on Apr 10–11 (Thu–Fri: 1,222–1,381 visitors) then rebounded strongly Mon–Tue (Apr 14–15: 2,016–2,142 visitors), suggesting a primarily weekday professional audience.
Improving daily trajectory
Daily visitors grew from 1,880 on Apr 9 to 2,142 on Apr 15 — a 14% increase over the week — indicating sustained or growing momentum rather than a one-time spike.
Walrus Sites content is a major engagement driver
The /walrus-sites/intro pages collectively rival the homepage in raw pageviews and vastly outperform it in scroll depth (100% vs 10%), making Walrus Sites the most compelling content area.
Recent traffic quality lower than 30d baseline
The 7d bounce rate (82%) and views/visit (1.36) are worse than the 30d figures (67%, 1.62), suggesting the recent visitor cohort is less exploratory — possibly driven by direct-link sharing or broader awareness campaigns.
Top 20 Pages
| # | Page | Insight |
|---|---|---|
| 1 | / | 6,683 visitors and 8,674 pageviews — by far the most visited page, with only 10% scroll depth and 46s on page, meaning most users are scanning and moving on or bouncing. |
| 2 | /walrus-sites/intro (+ .html variant) | Combined ~4,214 visitors and ~6,084 pageviews. 100% scroll depth on both variants signals this is highly read content — a key entry point for Walrus Sites. The duplicate .html URL suggests legacy or redirect inconsistency. |
| 3 | /docs/getting-started | 1,191 visitors with 100% scroll depth — the primary onboarding page is well-engaged, though relatively few visitors reach it from the homepage. |
| 4 | /docs/sites/introduction/components | 358 visitors, 43% scroll depth, 20% bounce — a meaningful secondary destination for users exploring Walrus Sites architecture. |
| 5 | /docs/operator-guide/storage-nodes/commission-governance | 107 visitors but 78% bounce rate and 77% scroll depth — operators who land here are engaged but it may not be well-linked to related content. |
Referral Sources
| Source | Type | Insight |
|---|---|---|
| Direct / None | Organic | 11,181 visitors (94.8% of all traffic) arrive directly. This dominance suggests most users bookmark the docs, arrive via CLI/SDK links, or come from non-tracked sources like Discord or email. |
| docs.wal.app | Organic | 339 visitors referred from internal pages — healthy internal navigation, though still a small fraction of total traffic. |
| Organic | 203 visitors with 77% bounce rate but 53s duration — organic search visitors are modestly engaged. SEO remains a minor channel. | |
| wal.app | Organic | 38 visitors with 48% bounce rate and 102s duration — referrals from the main product site are highly engaged, spending nearly 2x the average time. |
| chatgpt.com | AI / Chatbot | 10 visitors with 40% bounce rate and 161s duration — AI-referred users are highly engaged, spending over 2.5x the site average on-page. A small but high-quality traffic source. |
| docs.sui.io | Organic | Only 2 visitors but 1,049s average duration — extremely high engagement from this cross-ecosystem referral, suggesting Sui developers are deep researchers when they arrive. |
| walrus.site | Organic | 12 visitors, 528s average duration — referrals from Walrus-hosted sites are among the most engaged users, likely builders or power users. |
chatgpt.com
10 visitors with 161s average session duration — over 4x the site average — indicating AI-referred users arrive with specific, deep questions and engage thoroughly with the docs.
Top Referrer URLs
Exact referring URL or domain and the number of visits driven from each. Direct (no referrer) is excluded.
Page ↔ Kapa Theme Correlations
High-traffic pages mapped to the Kapa themes they correspond to.
| Page | Related Kapa Theme | Insight |
|---|---|---|
| /docs/getting-started | Mainnet Setup and CLI Onboarding | 1,191 visitors with 100% scroll depth yet CLI onboarding questions remain the 2nd-highest Kapa theme. |
| /walrus-sites/intro | Blob Storage Methods and Write Interfaces (CLI, HTTP API, SDK) | 6,084 combined pageviews on intro content correlate with the top Kapa theme on blob storage interfaces. |
| /docs/sites/introduction/components | Blob ID and Sui Object ID Relationship | 43% scroll depth suggests users leave before resolving blob ID vs. Sui object ID confusion. |
| /docs/operator-guide/storage-nodes/commission-governance | Token Management and Coin Operations (WAL/SUI) | 78% bounce rate suggests operators lack onward links to WAL token management guidance. |
| / | Global Blob Enumeration and Indexing Limitations | 10% scroll depth means enumeration limitation warnings buried in docs go unseen by most visitors. |
| /docs/getting-started | Epoch System and Timing | Epoch context is absent from the primary onboarding page, leaving new users to ask Kapa instead. |
| /walrus-sites/intro | Blob Lifecycle Management (Expiry, Extension, Deletion) | High readership of intro content with no lifecycle FAQ nearby drives expiry questions to Kapa. |
| /docs/operator-guide/storage-nodes/commission-governance | Mainnet Setup and CLI Onboarding | Operator page's isolation from CLI setup flow forces first-timers to abandon or ask Kapa. |
Notable Takeaways
Blob storage is the single largest driver of Kapa questions despite being the site's most-read topic
13 Kapa conversations on blob storage; /walrus-sites/intro has 6,084 pageviews and 100% scroll depthHigh readership of intro content is not resolving practical storage method questions, revealing a gap between conceptual and procedural documentation.
ChatGPT-referred users spend 4x longer on-site than the weekly average
161s average duration for chatgpt.com vs. 38s site-wide average across 10 AI-referred visitorsAI assistants are already pre-qualifying high-intent users, making Walrus docs an increasingly important AI-answer source worth optimizing.
Bounce rate worsened 15 percentage points versus the 30-day baseline in a single week
7d bounce rate 82% vs. 30d bounce rate 67%The recent traffic cohort is significantly less exploratory, suggesting bulk direct-link sharing is flooding the site with low-intent visitors.
Blob ID and object ID confusion is tied for 2nd-highest Kapa theme despite components page traffic
9 Kapa conversations; /docs/sites/introduction/components has 358 visitors and only 43% scroll depthUsers leave the components page before reaching ID disambiguation content, directly generating avoidable Kapa questions.
Developer Pain Point Themes
This week's 63 Walrus conversations centered on blob storage mechanics, mainnet onboarding friction, and blob/object ID confusion. Key pain points include CLI setup, blob enumeration limitations, and token management workflows.
Blob Storage Methods and Write Interfaces (CLI, HTTP API, SDK)
Developers cannot confidently store or retrieve blobs without comparing three underdocumented interfaces.
Mainnet Setup and CLI Onboarding
First-time mainnet friction at key import and wallet funding blocks developers before any meaningful usage.
Global Blob Enumeration and Indexing Limitations
Users hit hard dead ends with no documented workaround, eroding trust in the platform's observability.
Blob ID and Sui Object ID Relationship
ID confusion causes failed retrievals and wasted debugging time for developers bridging Sui and Walrus.
Token Management and Coin Operations (WAL/SUI)
Missing CLI examples for coin merging and WAL transfer block users from completing basic transactions.
Epoch System and Timing
Without epoch duration reference, developers cannot reliably plan blob storage and renewal windows.
Recommended Actions
Add a multi-interface blob storage comparison guide to the getting-started flow
Create a single page comparing CLI, HTTP API, and TypeScript SDK storage and retrieval with runnable examples.
13 Kapa conversations this week make this the highest-volume unresolved pain point.
Publish a streamlined mainnet quickstart covering install, key import, wallet funding, and first upload
Single-page end-to-end guide targeting first-time mainnet users with no prior Sui CLI experience.
9 onboarding-related conversations and a 14% week-over-week visitor increase signal rapid new-user growth.
Document blob ID vs. Sui object ID distinction with a prominent lookup reference
Add an ID disambiguation section to the components page above the current 43% scroll-depth exit point.
9 Kapa conversations and low components page scroll depth confirm users leave before finding this information.
Publish a blob enumeration limitations explainer with alternative tooling guidance
Short doc explaining why global blob listing is unavailable and linking to Walruscan and archive RPC nodes.
9 conversations hit dead ends with no documented path forward, directly harming developer trust.
Add WAL token management CLI examples covering coin merging and transfer to the operator guide
Append a WAL coin operations section to the existing operator guide with concrete CLI invocations.
6 conversations on token operations and a 78% bounce rate on the commission-governance page signal a navigation gap.
Add an epoch FAQ section with current epoch info and walrus info command reference to getting-started
Inline epoch duration, end-time lookup, and Walrus-vs-Sui epoch differences into the onboarding page.
5 Kapa conversations on epoch timing originate from users who already read the getting-started page.
Build a Walrus docs AI-readiness audit to improve answer quality from ChatGPT and similar agents
Audit top Kapa themes against current page structure to identify content gaps that LLMs cannot answer correctly.
ChatGPT-referred users spend 161s on-site, indicating AI is already a meaningful discovery channel worth optimizing.