Enable Vercel Speed Insights Integration#2
Merged
Conversation
# Vercel Speed Insights Implementation
## Summary
Successfully implemented Vercel Speed Insights for the Bottled project. This is a static HTML website that already had Vercel Analytics integrated.
## Changes Made
### Added Speed Insights to All HTML Pages
Added the required Speed Insights script tags to all 6 HTML files in the project:
1. **public/index.html** - Home page
2. **public/about.html** - About page
3. **public/read.html** - Find a bottle page
4. **public/write.html** - Throw a bottle page
5. **public/status.html** - Bottle status page
6. **public/admin.html** - Admin panel
### Implementation Details
For each HTML file, I added the following code before the closing `</body>` tag, right after the existing Vercel Analytics script:
```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 HTML implementation pattern from the Vercel Speed Insights documentation, which does not require installing the `@vercel/speed-insights` package for static HTML projects.
## Why This Approach
- **Framework**: This is a static HTML project (not React, Next.js, Vue, etc.)
- **No Package Installation**: Per Vercel's documentation, HTML implementations don't need the `@vercel/speed-insights` npm package
- **Script Location**: Scripts are placed before `</body>` to ensure proper loading after page content
- **Consistent Pattern**: Maintained consistency with the existing Vercel Analytics implementation
## Next Steps
Once deployed to Vercel with Speed Insights enabled in the dashboard:
1. The `/_vercel/speed-insights/script.js` route will be automatically available
2. Performance metrics (Core Web Vitals) will begin collecting after user visits
3. Data can be viewed in the Vercel dashboard under the Speed Insights tab
## Files Modified
- public/about.html
- public/admin.html
- public/index.html
- public/read.html
- public/status.html
- public/write.html
All changes are source code only - no build artifacts, dependencies, or lock files were modified since this is a static HTML project with no package dependencies for Speed Insights.
Co-authored-by: Vercel <vercel[bot]@users.noreply.github.com>
Contributor
Author
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
joenb33
marked this pull request as ready for review
February 21, 2026 23:56
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Vercel Speed Insights Implementation
Summary
Successfully implemented Vercel Speed Insights for the Bottled project. This is a static HTML website that already had Vercel Analytics integrated.
Changes Made
Added Speed Insights to All HTML Pages
Added the required Speed Insights script tags to all 6 HTML files in the project:
Implementation Details
For each HTML file, I added the following code before the closing
</body>tag, right after the existing Vercel Analytics script:This follows the HTML implementation pattern from the Vercel Speed Insights documentation, which does not require installing the
@vercel/speed-insightspackage for static HTML projects.Why This Approach
@vercel/speed-insightsnpm package</body>to ensure proper loading after page contentNext Steps
Once deployed to Vercel with Speed Insights enabled in the dashboard:
/_vercel/speed-insights/script.jsroute will be automatically availableFiles Modified
All changes are source code only - no build artifacts, dependencies, or lock files were modified since this is a static HTML project with no package dependencies for Speed Insights.
View Project · Speed Insights
Created by joenb33 with Vercel Agent