Check whether images visible when a page first opens are unnecessarily lazy loaded, meaning their loading is deferred. Verify rendering delays with performance measurements, then guide changes to loading attributes and request priority.
Use when auditing slow page loads, heavy assets, or rendering delays related to Disable lazy loading for above-the-fold content. Verify the actual bottleneck in DevTools, Lighthouse, or field data before recommending changes.
Run score Not tested
See how to installThis skill checks images visible when a page first opens for loading="lazy", which defers their loading. It uses measurements to determine whether delayed loading of a main image or other initially visible images affects Largest Contentful Paint (LCP), the time it takes for the main content to appear. It identifies the files or network requests involved and suggests removing the lazy loading attribute or reviewing priority with fetchpriority="high".
Use it when a large image at the top of a page takes too long to appear, or when you want to understand how image loading settings affect LCP. It also helps check whether images in the initial view are configured to start downloading early enough.
loading="lazy" delays their display.”Before suggesting improvements, it checks the actual cause using DevTools, Lighthouse, or field data. It considers fetchpriority="high" as an option for bringing forward the loading of important images.
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.
Applying lazy loading to hero images or other primary content can cause a significant delay in how quickly users perceive the page as loaded.
loading="lazy" for images in the initial viewportReview the page's images and check for loading="lazy" on any images that are likely to be in the initial viewport (above-the-fold).
Remove loading="lazy" from above-the-fold images and consider using fetchpriority="high" instead.
Explain why lazy loading above-the-fold content negatively impacts perceived performance and LCP.
Review the routes, assets, and loading behavior that affect Disable lazy loading for above-the-fold content. Flag exact files, requests, or rendering steps that add unnecessary network, CPU, or layout cost, and describe the measurement method used to confirm the issue.
For full implementation details, code examples, and framework-specific guidance,
see references/rule.md.
Rule page: https://frontendchecklist.io/rules/performance/lazy-above-fold
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.