Dallas skyline illustration

CYC26 / Frontend

Remote Agents, or: How I Fixed Our Page's Performance Without Really Doing Anything

Improving performance on a frontend, javascript-heavy, React SPA is an uphill (and often losing) battle. The brunt of the work is a long-tail of missed memoization opportunities, inefficient algorithms, and painstaking fixes. It also just so happens to be an outstanding candidate for agentic engineering. The key piece is that fixes here are verifiable: an agent can run a profile, identify a potential bottleneck, make a code change, and verify that the change improved performance! In this talk I'll describe the architecture of the system I orchestrated to continuously submit verified and ready-to-merge PRs, our findings, and some of the challenges and learnings I came across during the project.

Session abstract

What you’ll learn

Improving performance on a frontend, javascript-heavy, React SPA is an uphill (and often losing) battle. The brunt of the work is a long-tail of missed memoization opportunities, inefficient algorithms, and painstaking fixes. It also just so happens to be an outstanding candidate for agentic engineering. The key piece is that fixes here are verifiable: an agent can run a profile, identify a potential bottleneck, make a code change, and verify that the change improved performance! In this talk I'll describe the architecture of the system I orchestrated to continuously submit verified and ready-to-merge PRs, our findings, and some of the challenges and learnings I came across during the project.