https://ecoalf.com/ · Analyzed on October 1, 2026 · 15 checks
This report is a snapshot of the page as it was on October 1, 2026 at 15:16 UTC. Like any performance audit, it reflects that moment: websites change often, so the live page may differ today.
Analysis summary
1 critical3 warnings
Critical
1 image visible on load is lazy-loaded
Lazy loading is meant for images further down the page. Applied to an image users see right away, it makes the browser wait before downloading it. It is the main image of the page.
What to do: Ask your development team to remove loading="lazy" from the images visible when the page opens.
Warning
The page downloads 1.6 MB of JavaScript
JavaScript is the most expensive resource for a phone: it has to be downloaded, parsed and executed, and while that happens the page responds slowly to taps and scrolls.
What to do: Ask your development team to review which scripts are needed on this page, remove unused ones, and split the rest so each page only loads what it uses.
Warning
2 preloaded fonts are not used
The page asks the browser to download fonts with top priority that are not used on the visible part of the page. That bandwidth competes with the content users are waiting for.
What to do: Ask your development team to remove the preload hints for fonts that are not used above the fold.
Warning
Scripts from 13 external domains
Each external provider (analytics, ads, chat, tag managers…) adds connections, downloads and work for the browser, and you do not control when they change.
What to do: Review with your team which external tools are still needed, and ask developers to load the rest after the main content.
Want an expert to review this?
Joan León reviews your report and tells you what to fix first, in a 30-minute call or in writing. €299 + VAT.
TIP— Copy this prompt to fix these issues with your AI agent
I'm working on fixing web performance issues on https://ecoalf.com/.
A performance analysis ("Above-the-Fold Lazy Images") found the following problems:
1. 1 above-the-fold image(s) have lazy loading applied — they should load eagerly
2. The LCP element is lazy-loaded — this directly delays the largest contentful paint
3. 1 image(s) use loading="lazy" above the fold
Please analyze my codebase and suggest specific code changes to fix these issues.
Focus on above-the-fold image loading.
Paste this into Claude Code, Gemini CLI, Codex, Cursor, or any AI agent. Add your relevant code files as context for best results.
Above-the-Fold Lazy Images
https://ecoalf.com/
Visible images that load too late1 found
Problematic images
1
Native lazy loading
1
JS/data-src lazy loading
0
LCP affected
Yes
The likely LCP image is lazy loaded. This often delays the main content by hundreds of milliseconds.
→Remove loading="lazy" from images that are visible on initial load.
→Use fetchpriority="high" on the real hero image or other likely LCP candidate.
→Keep lazy loading for images below the fold or inside hidden UI such as tabs and accordions.
TIP— Copy this prompt to fix these issues with your AI agent
I'm working on fixing web performance issues on https://ecoalf.com/.
A performance analysis ("Above-the-Fold Lazy Images") found the following problems:
1. 1 above-the-fold image(s) have lazy loading applied — they should load eagerly
2. The LCP element is lazy-loaded — this directly delays the largest contentful paint
3. 1 image(s) use loading="lazy" above the fold
Please analyze my codebase and suggest specific code changes to fix these issues.
Focus on above-the-fold image loading.
Paste this into Claude Code, Gemini CLI, Codex, Cursor, or any AI agent. Add your relevant code files as context for best results.
Want an expert to review this?
Joan León reviews your report and tells you what to fix first, in a 30-minute call or in writing. €299 + VAT.
Web performance consultant at PerfReviews and author of WebPerf Snippets, the open source collection of performance scripts that powers every check in this tool. The findings and recommendations follow the same criteria used in real client audits.