Three production battles from a real ~1,000-page PHP/MySQL site on shared cPanel hosting. No shell, no pipeline - just patterns that survived contact.
The DJ Calendar's homepage scored a 7.0s Largest Contentful Paint. Three fixes did the heavy lifting: killing render-blocking font CSS via self-hosted WOFF2 pushed across the file set, cutting the render chain, and cache-aware verification so every fix was provably live (LiteSpeed caches HTML for 5 minutes - unverified fixes are guesses).
Full teardown with the three verification traps in between: 7.0s to 2.3s: The Core Web Vitals Takedown.
Every artist page, genre hub and tag page carried clean JSON-LD - and a GEO audit confirmed the site welcomes AI crawlers (robots, llms.txt, byte-identical ai.txt). The architecture behind it: two parallel genre systems, 13 bio-keyword configs and 6 curated hubs, all verified by artist NAME, not card counts - because str_contains over-matches short tokens and wrong-entity matches are worse than none.
How it's built: Make Your Site Legible to AI Crawlers.
Pasting code changes into a production file through a browser file manager is how sites die. The fix: token-gated PHP workers that back up before writing, count every needle string, verify the patch byte-exact, auto-restore on failure, and delete themselves after reporting. Earned live: a 2-byte length-check false-restore, a double-needle patch, and opcache ghosts all became checklist rules.
The pattern, open source: guarded-deploy-workers - and play with it in the browser.