About this tool
Review image exports before deployment so loading, decoding, and fetchpriority hints are coordinated for hero/LCP assets while non-critical rows avoid unnecessary prioritization.
The Image Loading Attribute Consistency Checker examines the interplay between loading, decoding, and fetchpriority attributes on each image element to detect conflicting signals. It catches contradictions like fetchpriority=high paired with loading=lazy, or decoding=sync on large non-critical images, that undermine the browser's resource scheduling.
- Parses rows in URL|image|loading|decoding|fetchpriority|context|size format and normalizes URLs with an optional base URL.
- Flags conflicting directives such as loading=lazy with fetchpriority=high, critical rows missing high priority, and sync decoding usage in sensitive contexts.
- Supports configurable per-page limits for high-priority and decoding=sync rows plus a critical deferred-size budget for practical triage.
How to use Image Loading Consistency
Upload image attribute data including loading, decoding, and fetchpriority values for each image along with its criticality and viewport position. The tool cross-references all three attributes against best-practice alignment rules and flags rows where the combined hints send contradictory signals to the browser.
When this tool is useful
- Audit loading, decoding, and fetchpriority attributes together before releasing template or CMS image changes.
- Catch cross-attribute conflicts on hero/LCP rows where mixed hints can weaken browser prioritization behavior.
- Prioritize pages where non-critical images are over-prioritized or sync decoding is overused.
Practical tips
- Use one exported row format for all image hints so QA can compare loading, decoding, and fetchpriority in a single pass.
- Keep fetchpriority=high reserved for true hero/LCP candidates and avoid pairing it with loading=lazy.
- Set per-page budgets for high-priority and decoding=sync usage to expose regressions before release.
Why people use this tool
Modern browsers use loading, decoding, and fetchpriority as a combined signal set to schedule image fetches and decode work. When these attributes contradict each other, the browser cannot optimize effectively, often falling back to conservative defaults that delay critical images or over-prioritize unimportant ones, directly harming LCP and visual stability.
Related search intents
image loading attribute consistency checker, loading decoding fetchpriority checker, img loading hint audit, lcp image attribute alignment tool.