Post

One thing I’m experimenting with for a performance audit: Using RUM data + @debugbear.com MCP to build synthetic tests based on how the product is actually used RUM → real user behaviour → MCP → representative synthetic tests www.debugbear.com/docs/mcp #WebPerf #RUM #MCP

debugbear.comAccess Web Performance Data With The DebugBear MCP Server | DebugBearConnect AI assistants like Claude and ChatGPT to DebugBear using the Model Context Protocol (MCP) to run tests, query metrics, and manage projects.

The Projekt

@wearetheprojekt.bsky.social

Lab runs on a fast laptop with a warm cache are how a Lighthouse 98 ships with a bad INP. Scripting synthetics from the paths RUM says people actually take fixes that. Copy the p75 device on the checkout page, not the dev's MacBook.

Joan León

@nucliweb.net

100%. The goal is lab tests that look like real users: same devices, same conditions, same paths. The MCP is making that loop really fast.

30/9/26, 7:55 am0 reposts0 likes

The Projekt

@wearetheprojekt.bsky.social

That feedback loop is the bit synthetic testing usually skips. RUM gives you the route; the MCP gives the lab a believable itinerary.