Enable HTTP/2 or HTTP/3
SkillMediahttp2 is a skill for AI agents that audits slow page loads, heavy assets, and rendering delays related to enabling HTTP/2 or HTTP/3. It guides the agent to verify the actual bottleneck in DevTools, Lighthouse, or field data before recommending changes, then check whether the server serves resources over HTTP/2
Available today. Use it from your connected AI after setup.
No other account needed.
Have an agent that can load skills, and add the http2 skill to its available skills.
Then ask your AI: use the Enable HTTP/2 or HTTP/3 skill
What your AI can do with it
- Audit slow page loads, heavy assets, and rendering delays tied to HTTP/2 or HTTP/3
- Verify the actual bottleneck in DevTools, Lighthouse, or field data before recommending ch
- Check whether a server serves resources over HTTP/2 or HTTP/3 using browser DevTools or on
- Enable HTTP/2 or HTTP/3 in a web server such as Nginx or Apache, or via a CDN or load bala
- Review routes, assets, and loading behavior, flagging files or requests that add unnecessa
- Explain the advantages of HTTP/2 and HTTP/3 over HTTP/1.1, such as multiplexing and header
Getting started
- Have an agent that can load skills, and add the http2 skill to its available skills.
- Have access to the page or server you want to audit, plus DevTools, Lighthouse, or field data for measurement.
- Ask the agent to audit slow page loads or rendering delays related to HTTP/2 or HTTP/3.
- Review the agent's findings, including the measurement method used to confirm the bottleneck.
- Apply the recommended fix in your web server or CDN/load balancer, then re-check the protocol in use.
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
- Aug 2026
Questions
- What does this skill check?
- It verifies that the server is serving resources over HTTP/2 or HTTP/3, using browser DevTools or online checkers, and audits slow page loads, heavy assets, or rendering delays related to enabling these protocols.
- How do I enable HTTP/2 or HTTP/3?
- Enable it in your web server (Nginx, Apache) or via a CDN/load balancer. The skill's references include full implementation details and framework-specific guidance.
Advanced
- Item type
- skill
- Key
http2- Source
- github.com/thedaviddias/front-end-checklist