Open source · Web performance

Image Format Readiness

Inspect one exported HTML file and its local images before release. Check declared dimensions, alternative text, loading hints, format policy and byte budgets without uploading the page.

v0.1.0 · Node.js 22+ · MIT

Browse source and run locally · Web development at Edilec

Run two public image exports

Both examples use checked-in synthetic local files and the same pinned demonstration matrix.

Passing export

node examples/run-clean.mjs

The clean export checks one 40 × 20 PNG with declared dimensions, an empty decorative alt attribute and lazy loading. It reports pass with zero findings.

Inspect the clean example

Byte budget and dimension failures

node examples/run-failing.mjs

The failing export checks a 250,001 bytes PNG with no declared HTML dimensions. It reports two errors: image-byte-budget-exceeded and intrinsic-dimensions-undeclared.

Inspect the failing example

Dark conceptual image tiles moving through an image quality-check gate
Conceptual illustration generated for this page. The public examples below contain synthetic local files; this image is not a tool screenshot or performance measurement.

What this check can tell you

The CLI reads one exported HTML file and local image headers offline; it does not optimize images, rewrite HTML, fetch remote media, or prove that an image loads correctly in a browser. Unsupported or ambiguous evidence returns incomplete instead of pass. The checked-in matrix is a pinned demonstration policy, not current browser support. Review responsive sources, visual quality and real loading behavior separately.

Inspect the demonstration matrix

Continue the review

Make image checks part of a web release

Discuss a bounded image QA workflow with Edilec. Share only material you are permitted to disclose.

Discuss a web image QA workflow