My app shows icons (UI icons, social icons, feature checkmarks) and I set it up early without thinking about cost. I want to know what my icon approach is actually costing. Audit and fix my icon loading: 1. Identify how icons are delivered: an icon font (Font Awesome and friends), a full SVG sprite, an icon component library that bundles every icon, individual SVG files, or inline SVGs. 2. Count what I actually use versus what I ship. Loading a 100KB+ icon font or a library bundle with 1,500 icons to display 20 of them is the usual finding. 3. Check for multiple systems at once: a font and an SVG library and inline SVGs, added at different times by different prompts. Consolidate on one. 4. Recommend the right target approach for my scale: for a small icon set, inline SVGs or a small custom sprite of only the icons I use; for a large set, a component library with proper tree-shaking. Avoid icon fonts for new setups: they block text rendering, fail accessibility checks without care, and show as empty boxes or flash of unstyled icons when the font is slow. 5. Implement the change, keeping the visual output identical, and make sure each icon that conveys meaning has an accessible name while purely decorative ones are hidden from assistive tech. Don't churn every icon usage in the codebase if a targeted change to the loading mechanism gets most of the win. The deliverable is the audit (used vs shipped), the consolidated implementation, and the size difference.