Optimise images for faster loading
SkillMediaOptimized is a skill for reviewing image assets, markup, and CDN or build transforms related to optimise images for faster loading. It checks encoded size, rendered size, loading strategy, and above-the-fold impact together, so an agent can flag what slows a page down and suggest fixes.
Use Optimise images for faster loading in Claude, ChatGPT or Ahel Desktop
Free. Sign in, add Optimise images for faster loading and connect your AI. About a minute.
Also: Claude Code · Cursor · Codex
Then ask your AI: use the Optimise images for faster loading 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
- Review image assets, markup, and CDN or build transforms
- Check encoded size of images
- Check rendered size of images
- Evaluate loading strategy for images
- Assess above-the-fold impact of images together with size and loading
Getting started
- Have an AI agent that can load skills.
- Add the optimized skill to the agent's available skills.
- Ask the agent to review the images, markup, or CDN and build transforms on a page.
- Review the agent's findings on encoded size, rendered size, loading strategy, and above-the-fold impact.
What this skill tells your AI
The instructions your AI receives, as published by thedaviddias/front-end-checklist in skills/optimized/SKILL.md and read by ahel’s review.
Unoptimised images are the most prevalent cause of page bloat. A DSLR-quality JPEG with EXIF data can be 8MB; the same image optimised for web delivery is under 200KB with no visible quality difference. Lighthouse's 'Efficiently encode images' audit reports potential savings that, when fixed, directly improve LCP and reduce bandwidth costs.
Quick Reference
- Strip EXIF metadata from all JPEG/WebP images before deployment—it adds unnecessary bytes
- JPEG: quality 80 with
progressive: true(mozjpeg); PNG: run pngquant at quality 65-80 - SVG: run through SVGO to remove editor artefacts and reduce file size
- Lighthouse flags images reducible by 4KB+ as 'Efficiently encode images' opportunities
Check
Audit all image assets in this project for optimisation issues: 1) Run Lighthouse and check the 'Efficiently encode images' audit—it flags images that could be reduced by 4KB or more. 2) Check if JPEG images use progressive encoding (better perceived performance). 3) Check if images retain EXIF/IPTC metadata (adds unnecessary bytes). 4) Check if PNG images could be quantised (pngquant) for smaller files. 5) Check if SVG files contain unnecessary editor metadata, comments, or redundant attributes. Report each image with its current size and estimated savings.
Fix
For each unoptimised image: 1) JPEG: re-encode with mozjpeg at quality 80 with progressive=true. 2) PNG: run pngquant at quality 65-80 for lossy compression, or oxipng for lossless. 3) WebP: encode at quality 80. 4) AVIF: encode at quality 60 with effort 6. 5) SVG: run through SVGO to remove editor metadata, comments, and redundant attributes. 6) Strip EXIF metadata from all JPEG/WebP images. For each image, show the before/after file size and percentage reduction.
Explain
Explain what image optimisation means technically. JPEG compression works by converting pixel data to frequency components (DCT) and quantising the high-frequency data—quality settings control how aggressively this quantisation occurs. PNG uses lossless DEFLATE compression, but colour quantisation (pngquant) can massively reduce file size with minimal visible change. EXIF metadata (GPS, camera model, timestamps) adds kilobytes to images with no benefit for web users. Progressive JPEG encoding allows the browser to show a low-resolution version immediately while the full image loads, improving perceived performance.
Code Review
Review image assets, markup, and delivery configuration related to Optimise images for faster loading. Flag exact files or components where format choice, sizing, or loading behavior violates the rule, and describe how to confirm the fix in DevTools.
For full implementation details, code examples, and framework-specific guidance,
see references/rule.md.
Rule page: https://frontendchecklist.io/en/rules/images/optimized
Signals
- GitHub stars
- 74k
- Forks
- 7k
- Last commit
- Oct 2026
- Hacker News mentions
- 20
Questions
- When should this skill be used?
- Use it when reviewing image assets, markup, and CDN or build transforms related to optimising images for faster loading.
- What does it check?
- It checks encoded size, rendered size, loading strategy, and above-the-fold impact together rather than looking at each in isolation.
- Does it change the images itself?
- The description covers reviewing and checking; it does not state that the skill edits or transforms images on its own.
Advanced
- Item type
- skill
- Key
optimized- Source
- github.com/thedaviddias/front-end-checklist
github.com/thedaviddias/front-end-checklist