Refactoring A Website with Modern CSS Tricks
summary
Shows an audit workflow: run Project Wallace and CSS Stats, use Chrome coverage to surface a concrete example like 64.8% unused CSS, flag spacing resets and specificity hotspots, identify legacy grid fallbacks and third‑party carousel risk, propose a component‑by‑component refactor with a temporary override file (e.g. defend.css), measure before/after with file‑size and load‑time deltas, attach refactors to planned feature work, and deliver small, testable wins instead of a full rebuild.
AI-written summary · about
chapters (6)
- 0:00Introduction
- 8:53Why refactoring CSS matters
- 14:12Auditing legacy CSS
- 22:37Business case for refactoring
- 31:24Practical refactoring steps
- 38:47Conclusion and key takeaways








