Install any skill in seconds. Free to start, no credit card required.
Get Started Free →Use when auditing slow page loads, heavy assets, or rendering delays related to Enable text-based compression. Verify the actual bottleneck in DevTools, Lighthouse, or field data before recommending changes.
| Test case | Without → With | Effect | Δ tokens | Δ turns |
|---|---|---|---|---|
| case-12 | ✓→✗ | ▼ Worse | 5% | 0% |
| case-17 | ✓→✓ | = Same ✓ | -16% | 0% |
| case-01 | ✓→✓ | = Same ✓ | -8% | 0% |
| case-02 | ✓→✓ | = Same ✓ | -19% | 0% |
| case-03 | ✓→✓ | = Same ✓ | 5% | 0% |
Compressed assets download faster, reducing the time to first paint and improving the overall perceived performance, especially on slower mobile networks.
Verify that text-based resources are served with Content-Encoding: gzip or br headers.
Enable Gzip or Brotli compression in your web server (Nginx, Apache) or CDN settings.
Explain how text-based compression works and its impact on asset delivery speed.
Review the routes, assets, and loading behavior that affect Enable text-based compression. 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/compression
Other measured skills in the registry, with their headline benchmark lift.