Audit JavaScript page redirects, confirm their impact on loading time with performance measurements, and identify where server-side 301 or 302 redirects can replace them. Get specific findings and an explanation of loading and search indexing concerns.
Use when auditing slow page loads, heavy assets, or rendering delays related to Avoid JavaScript-based redirects. Verify the actual bottleneck in DevTools, Lighthouse, or field data before recommending changes.
Review JavaScript page redirects and get help identifying and correcting those that delay loading. It checks uses of window.location and similar mechanisms, then examines their impact through DevTools, Lighthouse, or data collected during actual use. When a problem is confirmed, it considers replacing the redirect with a server-side 301 or 302 response. Findings identify the relevant files or requests and explain the measurement method used.
Use it when there is a noticeable wait between opening a page and reaching another URL, or when reviewing code that includes redirects. It also helps explain why a browser has to download and execute the script before redirecting, and how this can affect search engine indexing.
window.location and check their impact on loading.”Actual causes of delay must be confirmed through measurement before recommending changes. Moving redirects to the server requires working with web server or edge configuration.
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.
JavaScript redirects force an additional round-trip after the initial page load, significantly increasing the time users spend waiting for content.
window.locationCheck the project for instances where JavaScript is being used for page-level redirects (e.g., window.location).
Replace JavaScript-based redirects with server-side 301 or 302 redirects in your web server or edge configuration.
Explain why server-side redirects are faster and more SEO-friendly than client-side JavaScript redirects.
Review the routes, assets, and loading behavior that affect Avoid JavaScript-based redirects. 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/js-redirects
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.