Browser Performance Tools

Example workflows

Starting points built from this record, not transcripts of a run. Each prompt is written the way it should be sent, as one paragraph, and each is worth editing before you send it.

1. 01

   Stand it up from scratch

   You have read the record and want Browser Performance Tools working in a real project rather than a sandbox.

   Set up Browser Performance Tools in this project — profile Core Web Vitals, CPU, memory, and long tasks. Walk it end to end, tell me exactly what you changed, and flag anything I have to switch on myself before it works.

   Expected outcome

   A working setup, a plain list of what changed, and a short list of anything left for you to switch on. Check that list before assuming it is done.

2. 02

   Catch a regression that tanks LCP

   The record lists this as one of the jobs Browser Performance Tools is meant for, so it is a fair first test of whether it fits your app.

   In this project, use Browser Performance Tools for catch a regression that tanks LCP. Build the smallest version that a real user could complete end to end, keep the change scoped to that path, and tell me how to test it myself.

   Expected outcome

   One complete path a user can walk, the files and settings that changed, and the steps to test it. Walk it yourself before you ship it.

3. 03

   Review it before you publish

   Browser Performance Tools is wired in and you are about to put it in front of people. This is the pass that catches the half-configured version.

   Review how this project uses Browser Performance Tools before I publish. Check core Web Vitals capture and CPU and long-task profiling, list anything that is missing, misconfigured, or only half wired, fix what is safe to fix, and tell me what you left alone and why.

   Expected outcome

   A findings list split into what was fixed and what was left, with a reason for each. Anything left alone is yours to decide on.

4. 04

   Investigate a memory leak in a dashboard

   A second job the record lists for Browser Performance Tools, useful once the first path works.

   Extend this project so Browser Performance Tools also covers investigate a memory leak in a dashboard. Reuse what is already wired rather than adding a parallel setup, and tell me what you reused and what is new.

   Expected outcome

   A second path built on the same setup, plus a note on what was shared and what was added.

Frequently asked

• What is Browser Performance Tools?

  Browser Performance Tools is Lovable's Testing feature: Profile Core Web Vitals, CPU, memory, and long tasks. Extends Browser Testing with performance profiling: Core Web Vitals (LCP/CLS/INP), CPU usage, long tasks, and memory.

• Is Browser Performance Tools GA or in beta?

  Browser Performance Tools is generally available (GA) on Lovable.

• What Lovable plan includes Browser Performance Tools?

  Browser Performance Tools is available on all Lovable plans.

• When did Browser Performance Tools launch?

  Browser Performance Tools launched on Apr 2, 2026.

• Generate files and analyze dataSame category, also GA · Apr 2026
• Project MonitoringSame category · May 2026
• Browser TestingSame category, also GA · Feb 2026