Performance remediation — high-level pointers (local fallback)

rapidash’s audit tells you what is slow. The detailed, current fix procedures — exact caching config, CDN setup, image pipeline, version-specific steps — live in the team wiki (set OUTLINE + OUTLINE_API_URL and the report links them directly). This file is the minimal high-level fallback for when the wiki isn’t configured: direction only, deliberately not step-by-step, so there’s no detailed content to drift out of sync with the wiki.

• Poor LCP — the largest element renders too late. Preload the hero image/font, serve it from a CDN, and remove render-blocking work ahead of it.
• High INP / TBT — the main thread is busy too long. Break up long tasks, defer non-critical JS, and trim third-party scripts.
• High CLS — content shifts as it loads. Reserve space for images/ads/embeds and avoid injecting content above existing content.
• Slow TTFB — the server responds slowly. Add full-page/edge caching and check origin/database latency.
• Render-blocking resources — CSS/JS block first paint. Inline critical CSS, defer the rest, and async/defer non-essential scripts.

Full playbook → the team wiki’s performance reference (caching, CDN, image and JS delivery, per-metric procedures). Configure the wiki to have rapidash surface the live versions in its report.