Minimize HTTP requests
SkillMediahttp-requests is a skill for AI agents that guides an audit of a web page's HTTP requests, showing how DNS lookups, connections, and handshakes add latency. It helps verify the actual bottleneck in DevTools, Lighthouse, or field data before recommending changes to reduce excess requests that slow down page loads.
Use Minimize HTTP requests in Claude, ChatGPT or Ahel Desktop
Free. Sign in, add Minimize HTTP requests and connect your AI. About a minute.
Also: Claude Code · Cursor · Codex
Then ask your AI: use the Minimize HTTP requests skill
Details
Instructions available. Your AI can read the instructions. Execution depends on the setup they require.
Account requirements not reviewed. Check the skill instructions before use; ahel provides instructions and does not run this skill.
No other account needed.
Have an agent that can load skills.
What your AI can do with it
- Walks through auditing a page's HTTP requests
- Explains how DNS lookups, connections, and handshakes add latency
- Verifies bottlenecks using DevTools, Lighthouse, or field data
- Suggests bundling files to reduce request count
- Recommends SVG sprites and inlining critical resources
- Advises enabling HTTP/2
Getting started
- Have an agent that can load skills.
- Add the http-requests skill to the agent's available skills.
- Give the agent a page to audit for slow loads, heavy assets, or rendering delays.
- The agent will verify the bottleneck in DevTools, Lighthouse, or field data before suggesting fixes.
What this skill tells your AI
The instructions your AI receives, as published by thedaviddias/front-end-checklist in skills/http-requests/SKILL.md and read by ahel’s review.
Each HTTP request incurs network overhead—DNS lookup, TCP connection, and TLS handshake add latency. Reducing requests significantly improves initial load time.
Quick Reference
- Each HTTP request adds latency (DNS, TCP, TLS handshakes)
- HTTP/2 multiplexing reduces but doesn't eliminate request overhead
- Bundle critical CSS/JS, use SVG sprites for icons
- Target under 50 requests for initial page load
Check
Count the number of HTTP requests this page makes and identify opportunities for reduction.
Fix
Reduce HTTP requests by combining files, using sprites, inlining critical resources, and implementing HTTP/2.
Explain
Explain how each HTTP request adds latency and why minimizing requests improves performance.
Code Review
Review the routes, assets, and loading behavior that affect Minimize HTTP requests. 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/http-requests
Signals
- GitHub stars
- 74k
- Forks
- 7k
- Last commit
- Oct 2026
Questions
- When should this skill be used?
- Use it when auditing slow page loads, heavy assets, or rendering delays related to minimizing HTTP requests.
- Does it recommend changes right away?
- No. It first verifies the actual bottleneck in DevTools, Lighthouse, or field data before recommending changes.
- What fixes does it suggest?
- Bundling files, using SVG sprites, inlining critical resources, and enabling HTTP/2.
Advanced
- Item type
- skill
- Key
http-requests- Source
- github.com/thedaviddias/front-end-checklist
github.com/thedaviddias/front-end-checklist