Optimization Log
An optimization log turns "tuning" into a professional, auditable process. You can prove what worked, revert what broke, and avoid guesswork.
Why This Matters
Without a log, optimization becomes guesswork. You make 10 changes, performance improves, but you cannot identify which change helped (or which one introduced a regression). A structured log:
- Proves impact with before/after metrics for each change.
- Enables rollback by documenting how to reverse every change.
- Builds client trust with professional documentation.
- Prevents conflicts by recording tool assignments (e.g., Perfmatters handles CSS, LSCache handles page caching).
Optimization Log Template
Track every change in a structured table:
| Step | Change Made | Tool Used | Result | Metrics Impact | Status | Notes |
|---|---|---|---|---|---|---|
| 1 | Disabled Cloudflare auto-minify | Cloudflare | OK | Avoid double-minify conflicts | Kept | |
| 2 | Remove unused CSS | Perfmatters | OK | LCP: ___ -> ___ | Kept | Added exclusions for nav/menu |
| 3 | Delay JS | Perfmatters | OK | INP: ___ -> ___ | Kept | Excluded critical scripts |
| 4 | Preload hero image | Perfmatters | OK | LCP: ___ -> ___ | Kept | |
| 5 | Enable guest mode | LSCache | OK | TTFB/cache hit improved | Kept | |
| 6 | Enable Brotli + HTTP/3 | Cloudflare | OK | Network handshake improved | Kept | |
| 7 | Lazy load offscreen images | Perfmatters | OK | Bytes reduced | Kept | LCP excluded |
| 8 | Menu regression fix | Perfmatters | Fixed | UI restored | Kept | Added exclusion for menu script |
Rule: log every change immediately.
Rollback Plan
If an optimization breaks something, follow a feature-by-feature rollback approach. Do not disable an entire plugin at once:
| Issue | Rollback Action |
|---|---|
| CSS broken layout | Disable "Remove Unused CSS" temporarily |
| JS buttons not working | Disable "Delay JS" temporarily |
| Page blank or 500 error | Disable all Perfmatters optimizations |
| Cache loop issue | Disable LSCache Guest Optimization |
| Site shows old version | Purge Cloudflare cache + LSCache |
| Broken scripts | Check browser console + add JS exclusions |
Always rollback feature-by-feature, not plugin-by-plugin. Disabling an entire plugin removes 10 optimizations when only 1 caused the issue.
Before/After Metrics Table
Capture these metrics before starting and after completing optimization:
| Metric | Before | After | Gain |
|---|---|---|---|
| LCP (Mobile) | |||
| INP | |||
| CLS | |||
| FCP | |||
| TTFB (Global) | |||
| Page Size | |||
| HTTP Requests | |||
| PSI Score (Mobile) | |||
| PSI Score (Desktop) |
Save screenshots of PageSpeed Insights results as proof for clients and for your own reference.
Final Settings Record
After completing optimization, document the final configuration snapshot:
| Category | Setting |
|---|---|
| PHP Version | e.g., 8.3 |
| Web Server | OpenLiteSpeed / Nginx |
| Cloudflare Status | Active, SSL Full (Strict), APO enabled |
| LSCache Settings | Page TTL, Guest Mode, ESI status |
| Perfmatters Settings | CSS optimization, JS delay, preload list |
| Lazy Load Config | Excluded images, threshold |
| CDN Cache Status | HIT ratio, Edge TTL |
| TTFB Values | Homepage, product page, search |
Client Delivery Template
For client-facing optimization projects, prepare a delivery report:
| Section | Content |
|---|---|
| Speed Summary | One-paragraph overview of what was achieved |
| Before/After Comparison | Side-by-side metrics with screenshots |
| Technical Stack Summary | Server, caching, CDN, and optimization tool configuration |
| Core Web Vitals Proof | PageSpeed Insights screenshots showing "Good" status |
| Maintenance Recommendations | Monthly checks, update cadence, monitoring alerts |
| Support Contact | How to reach you for issues or questions |
Checklist
- Optimization log table created and maintained for every change.
- Rollback plan documented for each optimization.
- Before/after metrics captured with screenshots.
- Final settings snapshot recorded.
- Client delivery report prepared (if client project).
- Log stored in accessible location (Notion, Git, shared docs).
Summary
An optimization log transforms ad-hoc performance work into a professional, auditable process. Log every change with its tool, result, and metrics impact. Document rollback steps for each optimization. Capture before/after metrics to prove value. This discipline ensures that every optimization project is repeatable, reversible, and demonstrably effective.