Performanceintermediate
Make My Project Faster
Asks for measurement before changes, so you fix the actual bottleneck.
When to use it
Performance
Lovable Prompt
My project loads slowly. Diagnose before changing anything. 1. Identify the largest contributors to load time: image weight, blocking scripts, request waterfalls, or slow database queries. 2. Tell me what you found, ranked by impact. 3. Then fix them in order, starting with the biggest. Specifically check: - Images that are larger than their displayed size, or not lazy-loaded. - Data requests that wait on each other instead of running in parallel. - Queries selecting all columns when only a few are used, or filtering columns without indexes. - Third-party scripts blocking the initial render. - Layout shift caused by images and embeds without reserved space. Report the before and after for each change.
Why it works
Requiring a ranked diagnosis before changes prevents scattergun optimisation.
Was this prompt helpful?
You might also need
- GuideHow to Improve Lovable Loading SpeedFind the actual cause of a slow project — images, queries, waterfalls or scripts — before changing anything.
- AnswerHow do I improve Lighthouse scores?Run Lighthouse to find your worst-scoring category, fix the top 2-3 flagged issues (usually images, unused JavaScript, or render-blocking resources), and re-run it to confirm before moving on.
- AnswerHow do I improve Core Web Vitals?Focus on the three metrics Google measures — LCP (loading), INP (interactivity), and CLS (visual stability) — and fix the specific one flagged as poor, usually starting with images for LCP.
- AnswerHow do I lazy-load images?Ask Lovable to add native lazy-loading to images below the fold while keeping the hero/first-visible image loading eagerly, so visitors aren't downloading offscreen images before they're needed.
