Enable Vercel Web Analytics and Speed Insights

[petradonka]

Summary

Pass webAnalytics: { enabled: true } and speedInsights: { enabled: true } to the Astro Vercel adapter so the trackers are actually injected.

Why

@vercel/analytics and @vercel/speed-insights are already in package.json, and the CSP in vercel.json already allowlists va.vercel-scripts.com and vitals.vercel-insights.com — but the Astro Vercel adapter only adds the tracker <script> tags when you opt in via these options. Without them, the live HTML on docs.warp.dev has no Vercel script tags, so both the Analytics and Speed Insights tabs in the Vercel project stay at 0 visitors / 0 RUM samples (currently showing -100% over the last 7 days).

Verification

npm run build succeeds locally. The rendered dist/index.html now contains the Vercel Analytics initialization stub:

window.va = window.va || function () { (window.vaq = window.vaq || []).push(arguments); };

After deploy, the Vercel Analytics dashboard for the docs project should start populating within a few minutes.

---

Conversation

Co-Authored-By: Oz oz-agent@warp.dev

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
docs	Ready	Preview, Comment	Apr 30, 2026 7:40pm

[petradonka]

Closing — this PR isn't needed.

The <Analytics /> and <SpeedInsights /> v2 components are already wired up in src/components/CustomHead.astro (lines 3–4, 49–50) and the trackers are loading on every page (/_vercel/insights/script.js and /_vercel/speed-insights/script.js both return 200).

The reason both Vercel dashboards show 0 visitors / 0 RUM samples is that the ingestion endpoints are 404'ing:

/_vercel/insights/view              404
/_vercel/speed-insights/vitals      404

Vercel only mounts those routes after the feature is enabled in the project dashboard. Fix is to click Enable on both the Analytics and Speed Insights tabs of the docs project in Vercel and redeploy — no code change needed.

Per the official Astro adapter docs, with @vercel/analytics@1.4.0+ (we're on v2) the webAnalytics: { enabled: true } adapter flag should NOT be used; the <Analytics /> component is the supported path. So this PR's adapter changes would have been redundant at best and conflicting at worst.