From 88 to 100 PSI: Claude Code for Front-End Optimisation
A developer used Claude Code as a debugging and implementation partner to push their site's PageSpeed Insights mobile score from 88 to 100 (an article template went from 74 to 100). The post on r/ClaudeAI details the hands-on workflow — not a one-shot fix, but a series of targeted interventions.
Key Optimisations Achieved
- Responsive images + srcset: Claude identified that the mobile hero image was larger than needed, then generated responsive image variants and added
srcsetattributes. - LCP preload: Added a responsive preload for the LCP image using
<link rel="preload" as="image" imagesrcset="...">. - Forced reflow fix: Replaced a header scroll listener (which caused forced layout on scroll) with
IntersectionObserver. - Font audit: Identified which font weights were actually in use and removed unused ones.
- Build-time image dimensions: Added
widthandheightattributes to markdown images at build time to eliminate layout shifts. - Removed font preloads on article pages: Counterintuitive but effective — preloaded fonts were competing with the hero image for bandwidth on throttled mobile. Since fonts used
font-display: swap, removing preloads let the LCP image load faster.
Effective Prompting Pattern
The developer found Claude Code works best with specific diagnostic threads. Instead of vague prompts, feed it PSI findings and ask for the smallest safe patch. Example pattern: feed the PageSpeed Insights finding, ask Claude to inspect the relevant component, then request a minimal fix rather than a broad refactor.
Human Judgment Still Required
Some optimisations felt too aggressive visually — the author bumped logo quality back up while staying at 100. Below-the-fold images and styling trade-offs needed human decisions. Claude Code accelerated the iteration, but the developer still had to balance performance, accessibility, and design quality.
Full Write-Up
The author published a longer technical version with specific CWV changes and before/after numbers at goodrich.digital.
📖 Read the full source: r/ClaudeAI
👀 See Also
Opus 4.7 Broke 40% of Prompts; Fix Was Structuring CLAUDE.md and Skills
After Opus 4.7 degraded ~40% of prompts across 6 setups, a fractional head of AI fixed it by replacing ad-hoc prompts with structured Skill files, hierarchical CLAUDE.md, and separate memory files — reducing token usage 22% and iteration turns from 3-4 to 1-2.
Automating OAuth Token Refresh for Bots Using Claude Code
A Reddit user shares a method to prevent OAuth token expiration by configuring Claude Code to automatically refresh tokens every 8 hours, keeping bots running continuously without manual intervention.
Cut Token Costs by 95% with OpenClaw's Seven Optimization Techniques
A comprehensive guide detailing seven techniques to reduce AI agent token consumption by 95%+, including tree-structured boot files, AI auto-compression, local model offloading, and cron-based CPU tasks.
AGENTS.md Done Right: A 25% Correctness Boost — or a 30% Drop
Augment Code tested AGENTS.md files head-to-head: the best ones rival a model upgrade from Haiku to Opus; the worst ones hurt output. Decision tables, procedural workflows, and progressive disclosure win.