optimize-page-images

Audit local page images against rendered slot constraints and byte budgets.

22|3|Updated Jul 28, 2024
One-click install
npx skills add https://github.com/webdevcody/go-mailing-list --skill optimize-page-images
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: optimize-page-images
Source: https://github.com/webdevcody/go-mailing-list/tree/main/.claude/skills/optimize-page-images
Command: npx skills add https://github.com/webdevcody/go-mailing-list --skill optimize-page-images

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill finds the real, measurable image waste on a specific UI page by comparing on-disk image size and pixel dimensions to the rendered layout slot, then recommends concrete fixes that reduce bytes and improve image loading behavior.

Core Features & Use Cases

  • Per-image measurement from source: Reads each referenced local image to capture actual file bytes and pixel dimensions, then quantifies mismatch vs. the rendered slot.
  • Actionable optimization findings: Flags oversize sources, wrong formats, missing width/height, missing responsive sizes, priority discipline issues, and missing lazy-loading for below-the-fold images.
  • Budget-driven recommendations: Uses surface-specific byte budgets to propose targeted resize and format decisions, producing an audit table and a ranked fix list.

Quick Start

Ask for an audit by route or file with the phrase: "audit images on this page" (for example, "/dashboard") and request the per-image findings table so you can choose which fixes to apply.

Frequently Asked Questions about optimize-page-images

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I audit page images to cut real bytes and improve Core Web Vitals?

To audit page images, resolve on-disk paths to measure actual file bytes and pixel dimensions against rendered layout slots. This generates an audit table with budget-driven findings to identify oversize sources and improve Core Web Vitals.

What is the best way to find image optimization issues in a Next.js or TanStack frontend?

The best way to find image optimization issues is analyzing the JSX structure for slot evidence alongside disk measurements. This flags missing width/height attributes, wrong formats, missing responsive sizes, and absent lazy-loading for below-the-fold images in Next.js or TanStack components.

How do I apply byte budgets to responsive images during frontend performance optimization?

Apply byte budgets to responsive images by comparing on-disk pixel dimensions against the rendered slot constraints from the JSX structure. This produces a ranked fix list proposing targeted resize and format decisions to reduce overall page weight for frontend performance optimization.

Does this image optimization approach work with remote or dynamically generated images?

This image optimization approach does not work with remote or dynamically generated images. It explicitly skips REMOTE and DYNAMIC images that cannot be measured, requiring the presence of resolved local image references on disk to quantify the mismatch versus the rendered slot.

Can I automatically fix image loading and priority discipline issues found during an audit?

You cannot automatically fix image loading and priority discipline issues immediately. The system operates in a report-only phase, presenting an audit table and ranked fix list until you explicitly select specific fixes to apply for the flagged responsive images.