# In-depth INP optimization with DebugBear RUM 🔎

Canonical: https://brew.new/browse/templates/email/pt1_k97q3c8yc73e20s877cap2ac458e5g40

Brand: debugbear.com
Category: newsletter

![Preview of In-depth INP optimization with DebugBear RUM 🔎](https://cdn.brew.new/email-preview-c20f447834e88773-tracking_r57pbmryx08qfb3e87krctnp618dt6yx-1789001779072.png)

## Email content

Hi there,

Google's Interaction to Next Paint metric isn't easy to optimize. It depends on what visitors are interacting on, but Google doesn't provide any data to help with that.

Real user monitoring is the solution! Identify slow pages, slow UI elements, and specific slow scripts that are causing poor INP.

Have you checked out the DebugBear optimize flow? It guides you through your data step by step.

After selecting a specific page or template, you can see what scripts are slowing down interactions.

The "script invoker" tells you why the code is running. For example, the script could still be initializing, or a task might have perviously been scheduled with setTimeout. Or, it's actually processing the user interaction, whether as part of a global event handler or directly in response to the user input.

You can always take a more detailed look at specific page views to see:

What led up to the user interaction

What page element the user interacted with

How much time each script that delayed the interaction took.

Any questions about your RUM data? Just reply to this email and we'll help you out!

Regards,

Matt

You're receiving this message as a user of DebugBear. If you prefer to not receive these messages anymore, feel free to unsubscribe. Our postal address is DebugBear Ltd, 269 Farnborough Rd, Farnborough GU14 7LY, United Kingdom. Sent with Userlist

[Open and remix this design](https://brew.new/browse/templates/email/pt1_k97q3c8yc73e20s877cap2ac458e5g40)

[Browse email designs](https://brew.new/browse/templates)