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.
65
78%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
Passed
No findings from the security scan
Fix and improve this skill with Tessl
tessl review fix ./skills/lazy-above-fold/SKILL.mdApplying 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/en/rules/performance/lazy-above-fold
48405aa
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.