Minimize HTTP requests
SkillMediahttp-requests is a skill that guides an AI agent through auditing a web page's HTTP requests and reducing the ones that slow down page loads. It explains how DNS lookups, connections, and handshakes add latency, and it directs the agent to verify the actual bottleneck in DevTools, Lighthouse, or field data before recommending changes.
Available today. Use it from your connected AI after setup.
No other account needed.
Have a skill-capable agent setup where skills can be added.
Then ask your AI: use the Minimize HTTP requests skill
What your AI can do with it
- Walks an audit of a page's HTTP requests and counts them
- Explains how DNS lookups, TCP connections, and TLS handshakes add latency
- Verifies bottlenecks in DevTools, Lighthouse, or field data before recommending fixes
- Suggests fixes like bundling files, using SVG sprites, and inlining critical resources
- Recommends enabling HTTP/2 and targets under 50 requests for initial page load
- Reviews routes, assets, and loading behavior, flagging files or requests that add cost
Getting started
- Have a skill-capable agent setup where skills can be added.
- Add the http-requests skill to the agent's available skills.
- Open or point the agent at the web page whose load performance you want to audit.
- Ask the agent to audit the page's HTTP requests and follow the skill's check, fix, and explain steps.
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
- Aug 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.
- How are bottlenecks verified?
- The skill instructs verifying the actual bottleneck in DevTools, Lighthouse, or field data before recommending changes.
- What fixes does it suggest?
- Bundling files, using SVG sprites for icons, inlining critical resources, and implementing HTTP/2.
- How long does an audit take?
- The skill's metadata lists an estimated time of 20 (minutes) and marks it as intermediate difficulty.
Advanced
- Item type
- skill
- Key
http-requests- Source
- github.com/thedaviddias/front-end-checklist