Why does my Lovable app get slower as I add features?

Why this happens

No single feature usually causes a slowdown on its own. The problem is cumulative:

• Every new page or component can add its own data fetch, sometimes duplicating one that already exists elsewhere.
• New dependencies (a date picker library, a chart library, an icon set) each add to the bundle size.
• State and effects written for one feature can trigger re-renders in unrelated components if they share context or props carelessly.
• Old, unused code from earlier iterations often isn't removed — it just sits there adding weight.

How to keep it in check

1. Periodically audit, don't just build forward. Every so often, ask:

Review this project for unused components, duplicate data fetching, and unnecessary dependencies. List what you find before removing anything.

2. Reuse existing data fetches instead of writing new ones for the same data — ask Lovable to check if a hook/query already exists before adding one.
3. Watch bundle size growth over time, not just at launch.
4. Remove features you actually don't use rather than leaving them dormant in the codebase.

What usually goes wrong

• Treating performance as a one-time task at launch rather than an ongoing habit — it always regresses as scope grows.
• Adding a new library for a single small feature when a lighter, purpose-built solution (or an existing dependency) would do.
• Not noticing duplicated logic because each feature was built in its own chat session without checking what already existed — Project knowledge can help by recording what patterns already exist in the app.

Run a Lighthouse check every few major features, not just once, so slowdowns get caught early rather than discovered as one big backlog.