Use when auditing slow page loads, heavy assets, or rendering delays related to Optimize CSS file size. Verify the actual bottleneck in DevTools, Lighthouse, or field data before recommending changes.
71
87%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
Passed
No findings from the security scan
Large CSS files block rendering and increase the time it takes for the browser to construct the CSSOM, leading to a slower First Contentful Paint.
Audit the size of CSS files and identify those exceeding recommended limits (e.g., > 50KB gzipped).
Minify CSS, remove unused styles, and consider splitting large stylesheets into smaller, page-specific files.
Explain how CSS file size affects the critical rendering path and browser performance.
Review the routes, assets, and loading behavior that affect Optimize CSS file size. Flag exact files, requests, or rendering steps that add unnecessary network, CPU, or layout cost, and describe the measurement method used to confirm the issue.
For full implementation details, code examples, and framework-specific guidance,
see references/rule.md.
Rule page: https://frontendchecklist.io/en/rules/performance/css-file-size
48405aa
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.