Add New BPM Browser Performance Metrics plugin initial release

[sagaraggarwal86]

Hi,

I'd like to submit a new plugin — BPM (Browser Performance Metrics) — for inclusion in the repository.

This plugin fills a gap that I personally ran into while running browser-based load tests with WebDriver Sampler: JMeter gives you response times, but tells you nothing about what the browser actually experienced. BPM fixes that by tapping directly into Chrome DevTools Protocol during test execution.

What it does:

• Captures Core Web Vitals (LCP, FCP, CLS, TTFB) per transaction, live during the test run
• Calculates a composite performance score so you can see at a glance which transactions are degrading under load
• Highlights cells against configurable SLA thresholds — no manual post-processing needed
• Captures network requests, runtime errors, and console errors alongside vitals
• Detects and surfaces the primary improvement area per transaction (frontend vs backend vs stability)
• Supports filtering by time offset, transaction name, and regex — retroactively, without re-running the test
• Zero overhead on the test run itself — collection is async and non-blocking

Why it's useful:

• Browser performance problems (slow rendering, layout shifts, large payloads) are invisible to standard JMeter listeners — this plugin makes them visible
• Teams running WebDriver-based tests can now correlate server response time with actual browser rendering quality in one place
• The AI report saves hours of manual analysis for teams that need to present results to non-technical stakeholders

Plugin is on Maven Central (io.github.sagaraggarwal86:bpm-jmeter-plugin:1.0.0), Apache 2.0 licensed, and targets JMeter 5.6.3 / Java 17.

Happy to answer any questions or make adjustments to the entry.

[sagaraggarwal86]

Sample_HTML_Report.html
Attached sample report

[undera]

As I said earlier for other PRs, I don't plan to accept more plugins with "AI Analysis" features. Join efforts with existing one.

[sagaraggarwal86]

@undera Sure, which one. I don't see any listener plugin which produce browser rendering related metrics at transaction level. Also AI is just 5% part of plugin for two sections only. 95% analysis is part of Java coding. Also, AI just provide descriptions, you don't need AI to use this plugin. Listener GUI is enough to track down issue and provide insight without AI

[sagaraggarwal86]

i will re-submit after removing 5% of AI code.. easy to implement.