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.
63
75%
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
Fix and improve this skill with Tessl
tessl review fix ./skills/critical-request-chains/SKILL.mdLong 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
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.