Skip to content

Install and Configure Vercel Speed Insights#3

Draft
vercel[bot] wants to merge 1 commit into
mainfrom
vercel/install-and-configure-vercel-s-2g18qk
Draft

Install and Configure Vercel Speed Insights#3
vercel[bot] wants to merge 1 commit into
mainfrom
vercel/install-and-configure-vercel-s-2g18qk

Conversation

@vercel
Copy link
Copy Markdown
Contributor

@vercel vercel Bot commented Apr 27, 2026

Vercel Speed Insights Configuration

Successfully installed and configured Vercel Speed Insights for this static HTML website.

Changes Made

1. Package Installation

  • Installed @vercel/speed-insights version 2.0.0 (package was already in package.json dependencies)
  • Ran npm install to install the package to node_modules

2. Added Speed Insights Initialization Script

Added the window.si initialization script to all 9 HTML files following the official Vercel Speed Insights documentation for vanilla HTML/static sites.

Modified files:

  • index.html - Main homepage
  • design/index.html - Design section homepage
  • design/projects/index.html - Projects listing page
  • design/projects/airbnb-cards/index.html - Airbnb Cards project page
  • design/projects/airbnb-pdp/index.html - Airbnb PDP project page
  • design/projects/lemon-wallet/index.html - Lemon Wallet project page
  • design/projects/netflix-design-system/index.html - Netflix Design System project page
  • design/projects/xapo/index.html - Xapo project page
  • music/index.html - Music section homepage

3. Implementation Details

Each HTML file now includes the proper initialization script before the Speed Insights script tag:

<script>
  window.si = window.si || function () { (window.siq = window.siq || []).push(arguments); };
</script>
<script defer src="/_vercel/speed-insights/script.js"></script>

This follows the official Vercel documentation retrieved from: https://vercel.com/docs/speed-insights/quickstart

4. Framework Detection

  • This project is a static HTML site with no build step (as noted in package.json)
  • Used the vanilla HTML/static site configuration approach
  • The Speed Insights script uses the automatic Vercel path /_vercel/speed-insights/script.js which is enabled when Speed Insights is activated in the Vercel dashboard

5. Testing & Validation

  • Verified package installation: @vercel/speed-insights@2.0.0 is properly installed
  • Confirmed all 9 HTML files have the initialization script
  • No linting or test scripts are configured for this project (static HTML, no build step)
  • All changes preserve existing code structure and only add the necessary Speed Insights configuration

Next Steps

After deployment to Vercel:

  1. Speed Insights data will start appearing in the Vercel dashboard after users visit the site
  2. No additional configuration is required - the tracking is automatic once enabled in the Vercel dashboard
  3. The /_vercel/speed-insights/script.js path is automatically served by Vercel's infrastructure

View Project · Speed Insights

Created by wikichaves with Vercel Agent

# Vercel Speed Insights Configuration

Successfully installed and configured Vercel Speed Insights for this static HTML website.

## Changes Made

### 1. Package Installation
- Installed `@vercel/speed-insights` version 2.0.0 (package was already in package.json dependencies)
- Ran `npm install` to install the package to node_modules

### 2. Added Speed Insights Initialization Script
Added the `window.si` initialization script to all 9 HTML files following the official Vercel Speed Insights documentation for vanilla HTML/static sites.

Modified files:
- `index.html` - Main homepage
- `design/index.html` - Design section homepage
- `design/projects/index.html` - Projects listing page
- `design/projects/airbnb-cards/index.html` - Airbnb Cards project page
- `design/projects/airbnb-pdp/index.html` - Airbnb PDP project page
- `design/projects/lemon-wallet/index.html` - Lemon Wallet project page
- `design/projects/netflix-design-system/index.html` - Netflix Design System project page
- `design/projects/xapo/index.html` - Xapo project page
- `music/index.html` - Music section homepage

### 3. Implementation Details

Each HTML file now includes the proper initialization script before the Speed Insights script tag:

```html
<script>
  window.si = window.si || function () { (window.siq = window.siq || []).push(arguments); };
</script>
<script defer src="/_vercel/speed-insights/script.js"></script>
```

This follows the official Vercel documentation retrieved from: https://vercel.com/docs/speed-insights/quickstart

### 4. Framework Detection
- This project is a static HTML site with no build step (as noted in package.json)
- Used the vanilla HTML/static site configuration approach
- The Speed Insights script uses the automatic Vercel path `/_vercel/speed-insights/script.js` which is enabled when Speed Insights is activated in the Vercel dashboard

### 5. Testing & Validation
- Verified package installation: @vercel/speed-insights@2.0.0 is properly installed
- Confirmed all 9 HTML files have the initialization script
- No linting or test scripts are configured for this project (static HTML, no build step)
- All changes preserve existing code structure and only add the necessary Speed Insights configuration

## Next Steps

After deployment to Vercel:
1. Speed Insights data will start appearing in the Vercel dashboard after users visit the site
2. No additional configuration is required - the tracking is automatic once enabled in the Vercel dashboard
3. The `/_vercel/speed-insights/script.js` path is automatically served by Vercel's infrastructure

Co-authored-by: Vercel <vercel[bot]@users.noreply.github.com>
@vercel
Copy link
Copy Markdown
Contributor Author

vercel Bot commented Apr 27, 2026

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

Project Deployment Actions Updated (UTC)
wikichaves Ready Ready Preview, Comment Apr 27, 2026 6:05pm

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants