Install and configure Vercel Speed Insights#76
Merged
Conversation
Implemented Vercel Speed Insights for this project.
## What was implemented:
### Added Vercel Speed Insights script to all HTML files:
- index.html (main landing page)
- explainer.html (explainers page)
- profiler.html (profiler tool page)
### Changes made:
For each HTML file, added the Speed Insights initialization and script tag in the `<head>` section:
```html
<script>
window.si = window.si || function () { (window.siq = window.siq || []).push(arguments); };
</script>
<script defer src="/_vercel/speed-insights/script.js"></script>
```
These scripts were placed immediately after the existing Vercel Analytics script (`/_vercel/insights/script.js`) and before the Umami analytics script.
## Implementation approach:
1. **Fetched the latest documentation** from https://vercel.com/docs/speed-insights/quickstart to ensure up-to-date installation instructions
2. **Identified the project type**: This is a static HTML website (not a React/Next.js app) deployed on Vercel
3. **Used the vanilla HTML implementation**: Following the documentation, added the Speed Insights script tags to the head section of each HTML page
4. **Preserved existing code structure**: The Speed Insights scripts were inserted alongside the existing Vercel Analytics without modifying any other code
## How Speed Insights works:
- **Speed Insights** monitors Core Web Vitals and performance metrics
- **Different from Analytics**: While the project already had Vercel Analytics for visitor tracking, Speed Insights specifically focuses on performance monitoring (LCP, FID, CLS, etc.)
- The script path `/_vercel/speed-insights/script.js` is automatically served by Vercel after deployment
## Next steps:
1. Enable Speed Insights in the Vercel dashboard (if not already enabled)
2. Deploy the changes to Vercel
3. Once deployed and users visit the site, performance metrics will start appearing in the Vercel dashboard under Speed Insights
## Notes:
- No package.json or npm dependencies were needed since this is a static HTML site
- The Speed Insights script uses a deferred loading pattern to avoid blocking page rendering
- The implementation follows Vercel's official documentation for vanilla HTML/JavaScript projects
Co-authored-by: Vercel <vercel[bot]@users.noreply.github.com>
Contributor
Author
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
Hey @vercel[bot], your first PR on Fair Code, that's awesome, thank you. This project is about making AI more accountable, and contributions like yours are what keep that work going. We'll review your changes shortly. If you haven't already, give the contributing guide a quick read: it covers how audits are structured and what we look for in a review. |
yakew7
marked this pull request as ready for review
July 17, 2026 12:43
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.
Implemented Vercel Speed Insights for this project.
What was implemented:
Added Vercel Speed Insights script to all HTML files:
Changes made:
For each HTML file, added the Speed Insights initialization and script tag in the
<head>section:These scripts were placed immediately after the existing Vercel Analytics script (
/_vercel/insights/script.js) and before the Umami analytics script.Implementation approach:
How Speed Insights works:
/_vercel/speed-insights/script.jsis automatically served by Vercel after deploymentNext steps:
Notes:
View Project · Speed Insights
Created by yashkewlani2020-1304 with Vercel Agent