Skip to content
Back to skills

Angular Performance Ng Optimized Image Adoption

ASecurity

Adopt Angular's NgOptimizedImage for post-upgrade image performance improvements when the app is already stable and the goal is to optimize priority images, preconnects, responsive sizing, and loading behavior in a controlled slice.

  • 4 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added October 2, 2026
developmenttypescriptgoangularperformance

Security analysis

A100/100

Scanned October 2, 2026

npx -y skills add janpereira-dev/ngAutoPilot --skill angular--performance--ng-optimized-image-adoption --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Angular Performance Ng Optimized Image Adoption?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Angular  Performance  Ng Optimized Image Adoption
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/janpereira-dev-angular-performance-ng-optimized-image-adoption/badge)](https://www.skillsdirectory.com/skills/janpereira-dev-angular-performance-ng-optimized-image-adoption)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
id: angular.performance.ng-optimized-image-adoption
name: NgOptimizedImage Adoption
description: >
  Adopt Angular's NgOptimizedImage for post-upgrade image performance improvements when the app is already stable and the goal is to optimize priority images, preconnects, responsive sizing, and loading behavior in a controlled slice.
stack:
  - Angular
  - TypeScript
category: performance
status: stable
version: 0.10.0
owner: NgAutoPilot
triggers:
  - NgOptimizedImage
  - image performance
  - LCP optimization
compatibility:
  angular:
    min: "15"
---

# NgOptimizedImage Adoption

## Purpose

Adopt `NgOptimizedImage` for post-upgrade image performance work.

## When to Use

- The app is stable on the target Angular version.
- Image performance is a current optimization target.
- The team wants to improve LCP and image loading behavior incrementally.

## When Not to Use

- The app is still in a version upgrade.
- The issue is a functional bug unrelated to images.

## Required Inputs

- image-heavy routes
- hero assets
- responsive image sizes
- build and runtime constraints

## Procedure

1. Pick image-heavy screens first.
2. Replace priority images with `NgOptimizedImage`.
3. Add explicit sizes and loading hints.
4. Validate layout shifts and image fetches.

## Do

- Optimize the most visible images first.
- Check preconnect and priority behavior.
- Validate local and production builds.

## Do Not

- Do not rewrite every image usage blindly.
- Do not mix this change with an upgrade hop.
- Do not assume all images should be eager.

## Review Checklist

- [ ] Priority images are optimized.
- [ ] Layout remains stable.
- [ ] Performance impact is measured or noted.

## Expected Output

1. Image slice optimized.
2. Remaining image debt.
3. Performance notes.
4. Follow-up list.

## Exit Criteria

- The image slice is validated.
- Remaining opportunities are documented.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…