Mission 18: Purging the Redundancy
You are granted access to the "Code Integrity Scanner" which has analyzed `olympus-main.css`. The scan reveals several unused selectors related to decommissioned systems.
Mission Objective
Step 1 / 1
System Briefing: Code Debt and Bloat
The flagship Olympus Mons has been in service for 50 years. Its primary stylesheet contains code for dozens of decommissioned systems, making it a bloated relic. This "code debt" increases download times and parsing complexity, causing a noticeable lag on the bridge. Your mission is to purge the redundant code.
The Impact of Unused CSS
Unused CSS rules might seem harmless, but they create unnecessary overhead. The browser still has to download, parse, and evaluate every rule to build the CSS Object Model (CSSOM), even if a rule doesn't apply to any element on the current page. Removing this dead weight is a critical performance optimization.
Tools for Detection
In a real-world scenario, you would use automated tools to detect unused CSS. Browser developer tools (like the Coverage tab in Chrome DevTools) and build tools (like PurgeCSS) can analyze your pages and stylesheets to report which rules are not being used, allowing for safe removal.