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 Keep page weight under 1500KB. Verify the actual bottleneck in DevTools, Lighthouse, or field data before recommending changes.
| Test case | Without → With | Effect | Δ tokens | Δ turns |
|---|---|---|---|---|
| case-01 | ✗→✓ | ▲ Improved | 72% | 0% |
| case-06 | ✗→✓ | ▲ Improved | -18% | 0% |
| case-07 | ✗→✓ | ▲ Improved | -43% | 0% |
| case-09 | ✗→✓ | ▲ Improved | -43% | 0% |
| case-12 | ✗→✓ | ▲ Improved | 26% | 0% |
Page weight directly correlates with load time—a 1.5MB page takes 3-5 seconds on 4G mobile. Every 100KB reduction improves user experience, especially on slower networks.
Analyze the total page weight including all resources. Check if it's under 1500KB (ideally under 500KB).
Optimize this page to reduce its total weight through image optimization, code minification, and removing unnecessary resources.
Explain how page weight impacts loading time, especially on mobile networks, and affects user experience.
Review the routes, assets, and loading behavior that affect Keep page weight under 1500KB. 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/page-weight
Other measured skills in the registry, with their headline benchmark lift.