Review images needed when a page first opens, checking file size, display dimensions, and loading priority. Identify changes to preload settings and lazy loading that help the main visual content appear sooner.
Use when reviewing image assets, markup, and CDN or build transforms related to Prioritize loading critical images. Check encoded size, rendered size, loading strategy, and above-the-fold impact together.
Run score Not tested
See how to installThis skill identifies images needed immediately after a page opens and helps review how to load them first. It checks image file size, displayed dimensions, and loading methods together to find issues affecting LCP, the time until the main content appears. It points to the relevant files or components and suggests settings such as fetchpriority='high' and preloading hero images.
Use it when a large image at the top of a page takes too long to appear, or when you want to check whether images visible at first have lazy loading enabled. The review can cover image assets alongside HTML, CDN settings, and image transformation settings used during the build. This lets you examine the initial images’ loading behavior across those parts of the page’s setup.
Changes are checked using the browser’s DevTools. The review also includes removing loading='lazy' from images above the fold.
This overview was written by AI (OpenAI Codex) from the public SKILL.md. Check the original below for the exact behavior.
AI checked the SKILL.md for operations that need care and for setup requirements. The score comes only from actually running the skill (hands-on test).
Not counted in the score. Rated by AI (OpenAI Codex) as of Oct 23, 2026. Treat it as a guide and read the original before installing.
Review the instructions the agent will receive before you install.
The Largest Contentful Paint (LCP) is often an image—prioritizing its load can improve LCP by 20-40%, directly impacting Core Web Vitals and SEO.
Identify which images are critical for initial render and ensure they load with high priority.
Add fetchpriority='high' to critical images and use preload for hero images.
Explain how prioritizing critical images improves Largest Contentful Paint (LCP).
Review image assets, markup, and delivery configuration related to Prioritize loading critical images. 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/rules/images/critical-images
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Create and review custom 404 pages that help visitors recover from broken or moved links through search and navigation. Check the rendered page and HTTP response so missing content returns a proper 404 status.
Audit or create a dedicated About page that explains a website’s purpose and identifies its people or organization. Review the rendered output and supporting information, including expertise and contact details, to find gaps.
Review and add automated accessibility checks for components, pages, and continuous integration workflows. Use axe-based tools to detect structural and attribute issues, while identifying checks that still need keyboard or screen reader testing.
Review sign-in, registration, multi-factor authentication, and account recovery for accessibility barriers. Find blocked paste, difficult code entry, and inaccessible backup methods, then suggest authentication paths that support password managers, autofill, or device approval.
Review form errors, success messages, and live updates so screen reader users receive important notifications. Check the HTML delivered to the browser, announcement settings, display duration, and dismissal controls, then identify specific elements that need changes.
Review HTML tables so screen reader users can understand how headers and data relate. Check header markup, table descriptions, and merged cells, then identify specific fixes and ways to verify them.