Investigate chains of dependent resource requests that delay a page’s first display. Use performance measurements to identify bottlenecks, then reduce waiting by embedding essential CSS or preloading important assets discovered late in the chain.
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.
Investigates long chains of dependent resource requests that hold up a page’s initial display. It finds cases where one file must finish downloading and processing before the next request can begin, then considers ways to shorten the chain needed for rendering. The options include embedding critical CSS in HTML and using preload for essential files that are discovered later.
Use it when a page takes too long to show its first content, or when you want to find out whether file loading order causes the delay. It helps organize proposed changes and verification methods around specific files, requests, and rendering steps.
preload could shorten dependencies.”Before recommending changes, it requires confirming the bottleneck with DevTools, Lighthouse, WebPageTest, or data from actual use. It also identifies how to measure the issue, so conclusions are supported by measurements rather than impressions from reading code alone.
This overview was written by AI (OpenAI Codex) from the public SKILL.md. Check the original below for the exact behavior.
AI rated this skill on four points using only the contents of its SKILL.md. Stars and popularity are not taken into account.
The total counts each point as A = 25, B = 15, C = 5. Rated by AI (OpenAI Codex) as of Oct 23, 2026. Treat it as a guide and read the original before installing.
Review the instructions the agent will receive before you install.
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/rules/performance/critical-request-chains
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Create and review custom 404 pages that help visitors recover from broken or moved links through search and navigation. Check the rendered page and HTTP response so missing content returns a proper 404 status.
Audit or create a dedicated About page that explains a website’s purpose and identifies its people or organization. Review the rendered output and supporting information, including expertise and contact details, to find gaps.
Review and add automated accessibility checks for components, pages, and continuous integration workflows. Use axe-based tools to detect structural and attribute issues, while identifying checks that still need keyboard or screen reader testing.
Review sign-in, registration, multi-factor authentication, and account recovery for accessibility barriers. Find blocked paste, difficult code entry, and inaccessible backup methods, then suggest authentication paths that support password managers, autofill, or device approval.
Review form errors, success messages, and live updates so screen reader users receive important notifications. Check the HTML delivered to the browser, announcement settings, display duration, and dismissal controls, then identify specific elements that need changes.
Review HTML tables so screen reader users can understand how headers and data relate. Check header markup, table descriptions, and merged cells, then identify specific fixes and ways to verify them.