OpenParable
Skip to content
← Back to skills

JS File Size

Testing & Quality
js-file-size

JS File Size is an Agent Skill for testing & quality published in the thedaviddias/Front-End-Checklist repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

Use when auditing slow page loads, heavy assets, or rendering delays related to Optimize JavaScript bundle size. Verify the actual bottleneck in DevTools, Lighthouse, or field data before recommending changes.

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/thedaviddias/Front-End-Checklist/blob/HEAD/skills/js-file-size/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/js-file-size, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

Optimize JavaScript bundle size

Excessive JavaScript increases parse and execution time, especially on low-end devices, leading to sluggish user experiences and high data costs.

Quick Reference

  • Keep individual JS bundles under 200KB (compressed)
  • Large bundles delay Time to Interactive (TTI) and First Input Delay (FID)
  • Use code-splitting and tree-shaking to reduce unused code

Check

Review the JavaScript bundle sizes and identify any files exceeding 200KB (Gzip/Brotli).

Fix

Implement code-splitting, tree-shaking, and dependency audits to reduce the size of the JavaScript bundles.

Explain

Explain how large JavaScript files impact the main thread and delay user interactivity (FID/TTI).

Code Review

Review the routes, assets, and loading behavior that affect Optimize JavaScript bundle size. 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/js-file-size