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 Minimize critical request chains. Verify the actual bottleneck in DevTools, Lighthouse, or field data before recommending changes.
| Test case | Without → With | Effect | Δ tokens | Δ turns |
|---|---|---|---|---|
| case-12 | ✓→✗ | ▼ Worse | -16% | 0% |
| case-01 | ✓→✓ | = Same ✓ | 48% | 0% |
| case-02 | ✓→✓ | = Same ✓ | 43% | 0% |
| case-03 | ✓→✓ | = Same ✓ | 53% | 0% |
| case-04 | ✓→✓ | = Same ✓ | 2% | 0% |
Long chains of dependent requests delay the initial rendering of the page, as each resource must wait for its parent to be fetched and processed.
preload hints for essential assets found deep in the chainIdentify long chains of dependent requests that block the critical rendering path using Lighthouse or WebPageTest.
Flatten the request chain by inlining critical resources or using preload hints for essential assets.
Explain how critical request chains impact the Time to First Paint and how to optimize the rendering path.
Review the routes, assets, and loading behavior that affect Minimize critical request chains. 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/critical-request-chains
Other measured skills in the registry, with their headline benchmark lift.