web-performancelisted
Install: claude install-skill sharabarinillia/SEO-GEO-Vercel-Playbook-Skill
# Web performance without visible change
Every page view costs requests and bytes, and on Vercel Pro requests are what a team runs out of
first. The aim: the same design, fewer requests, fewer bytes, faster first paint.
**Trade-off rule:** changes nobody can see (caching, formats, lazy loading, chunking) can just be
done. Changes people could notice (softer video, fewer animations, a missing feature) need the
person's decision: name the saving and the visible cost.
## Steps
1. **Measure first** on a deployment (local preview servers don't compress):
```bash
BASE=https://<deployment> PAGES=/,/services/x/ node <skill>/scripts/measure-requests.cjs
```
It reports requests and KB for a first visit and the next page, desktop and phone, by type,
plus redirects, 404s and other hosts. How to read it:
[references/measuring.md](references/measuring.md).
2. **Fix the biggest cost first**, usually in this order:
- **Caching headers** so shared files load once per visitor (`vercel-static-config`).
- **Video**: short loops, `preload="none"`, loaded near the viewport, phone copies:
[references/video.md](references/video.md).
- **Images**: AVIF/WebP at 2–4 widths, correct `sizes`, lazy below the fold.
- **Fonts**: 2–3 self-hosted variable WOFF2 files.
- **Requests that repeat**: inline logo, `favicon.ico`, `apple-touch-icon.png`, no links through
redirects, no 404s.
- **JavaScript**: heavy code in lazy chunks; below-the-fold animation set up