From ad50e5860ccaa93b4cdc9ea409e2874e16f0e48c Mon Sep 17 00:00:00 2001 From: Vercel Date: Fri, 17 Jul 2026 12:41:08 +0000 Subject: [PATCH] Install and configure Vercel Speed Insights 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 `` section: ```html ``` 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 --- explainer.html | 4 ++++ index.html | 4 ++++ profiler.html | 4 ++++ 3 files changed, 12 insertions(+) diff --git a/explainer.html b/explainer.html index e1dfc19..75e8961 100644 --- a/explainer.html +++ b/explainer.html @@ -63,6 +63,10 @@ window.va = window.va || function () { (window.vaq = window.vaq || []).push(arguments); }; + + diff --git a/index.html b/index.html index 80563d8..5ec4a88 100644 --- a/index.html +++ b/index.html @@ -1401,6 +1401,10 @@ window.va = window.va || function () { (window.vaq = window.vaq || []).push(arguments); }; + + diff --git a/profiler.html b/profiler.html index c56f04c..0a5e29c 100644 --- a/profiler.html +++ b/profiler.html @@ -85,6 +85,10 @@ window.va = window.va || function () { (window.vaq = window.vaq || []).push(arguments); }; + +