Eliminate render-blocking resources
SkillMediarender-blocking is a skill for AI agents that audits slow page loads by finding render-blocking resources. It verifies the actual bottleneck in DevTools, Lighthouse, or field data before recommending changes, so fixes target heavy assets and rendering delays that really matter.
Use Eliminate render-blocking resources in Claude, ChatGPT or Ahel Desktop
Free. Sign in, add Eliminate render-blocking resources and connect your AI. About a minute.
Also: Claude Code · Cursor · Codex
Then ask your AI: use the Eliminate render-blocking resources 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 AI agent that can load skills.
What your AI can do with it
- Find render-blocking resources on a page
- Audit slow page loads and heavy assets
- Verify bottlenecks in DevTools before recommending changes
- Check Lighthouse results for rendering delays
- Use field data to confirm the actual bottleneck
Getting started
- Have an AI agent that can load skills.
- Add the render-blocking skill to the agent's available skills.
- Have access to the page you want to audit and its performance data.
- Ask the agent to audit the page for render-blocking resources and slow loads.
What this skill tells your AI
The instructions your AI receives, as published by thedaviddias/front-end-checklist in skills/render-blocking/SKILL.md and read by ahel’s review.
Render-blocking resources prevent the browser from painting anything on the screen, leading to a "white screen" effect and poor user experience.
Quick Reference
- Load non-critical CSS and JS asynchronously using
defer,async, or media queries - Inline critical CSS to allow the page to start rendering immediately
- Avoid
@importin CSS as it creates serial request chains
Check
Review the page's resources and identify any CSS or JavaScript files that are blocking the initial render of the page.
Fix
Update the loading strategy for render-blocking resources by using defer, async, or inlining critical styles.
Explain
Explain how render-blocking resources impact the First Contentful Paint (FCP) and how to resolve them.
Code Review
Review the routes, assets, and loading behavior that affect Eliminate render-blocking resources. 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/render-blocking
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 eliminating render-blocking resources.
- 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 work with for verification?
- It verifies bottlenecks using DevTools, Lighthouse, or field data.
Advanced
- Item type
- skill
- Key
render-blocking- Source
- github.com/thedaviddias/front-end-checklist
github.com/thedaviddias/front-end-checklist