Enable HTTP/2 or HTTP/3
SkillMediahttp2 is a skill for AI agents that diagnoses slow page loads by checking whether HTTP/2 or HTTP/3 is enabled. When a site has heavy assets or rendering delays, the agent verifies the actual bottleneck in DevTools, Lighthouse, or field data before recommending any changes.
Use Enable HTTP/2 or HTTP/3 in Claude, ChatGPT or Ahel Desktop
Free. Sign in, add Enable HTTP/2 or HTTP/3 and connect your AI. About a minute.
Also: Claude Code · Cursor · Codex
Then ask your AI: use the Enable HTTP/2 or HTTP/3 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 and use skills.
What your AI can do with it
- Check whether HTTP/2 or HTTP/3 is enabled on a site
- Audit slow page loads and rendering delays
- Identify heavy assets contributing to load time
- Verify the actual bottleneck in DevTools
- Confirm findings against Lighthouse or field data before recommending changes
Getting started
- Have an agent that can load and use skills.
- Add the http2 skill to the agent's available skills.
- Ask the agent to audit a slow page load or check if HTTP/2 or HTTP/3 is enabled.
- Review the agent's findings and any recommended changes.
What this skill tells your AI
The instructions your AI receives, as published by thedaviddias/front-end-checklist in skills/http2/SKILL.md and read by ahel’s review.
Modern HTTP protocols significantly reduce the impact of latency and allow multiple resources to be downloaded simultaneously over a single connection, leading to much faster page loads.
Quick Reference
- Enable HTTP/2 or HTTP/3 for request multiplexing
- Eliminate the need for resource concatenation
- Reduce overhead with header compression
Check
Verify that the server is serving resources over HTTP/2 or HTTP/3 using browser DevTools or online checkers.
Fix
Enable HTTP/2 or HTTP/3 in your web server (Nginx, Apache) or via a CDN/load balancer.
Explain
Explain the advantages of HTTP/2 and HTTP/3 over HTTP/1.1, such as multiplexing and header compression.
Code Review
Review the routes, assets, and loading behavior that affect Enable HTTP/2 or HTTP/3. 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/http2
Signals
- GitHub stars
- 74k
- Forks
- 7k
- Last commit
- Oct 2026
- Hacker News mentions
- 2
Questions
- When should this skill be used?
- Use it when auditing slow page loads, heavy assets, or rendering delays related to enabling HTTP/2 or HTTP/3.
- Does it recommend changes right away?
- No. It verifies the actual bottleneck in DevTools, Lighthouse, or field data before recommending changes.
- What tools does it use to verify bottlenecks?
- DevTools, Lighthouse, or field data.
- Does it enable HTTP/2 or HTTP/3 for me?
- The skill diagnoses whether HTTP/2 or HTTP/3 is enabled and recommends changes; it does not state that it applies server configuration itself.
Advanced
- Item type
- skill
- Key
http2- Source
- github.com/thedaviddias/front-end-checklist
github.com/thedaviddias/front-end-checklist