browser-perf-runner

browser-perf-runner lets you check how fast a web page renders by doing something clever: you send a pull request (basically a proposed code change) to the project's GitHub repository, and it runs a performance test for you automatically.

Here's how it works in practice. The repository is connected to a continuous integration service called Travis CI, which watches for new pull requests. When you submit one, that service springs into action and runs a tool called browser-perf against whatever web page URL you've specified. browser-perf measures things like how smoothly a page scrolls, how quickly it paints content to the screen, and other rendering metrics that affect how fast the page feels to actual users. The results come back through the pull request, so you can see them right there in GitHub.

This setup would appeal to someone like a frontend developer or a product manager who wants a quick, no-fuss way to benchmark a web page without installing performance testing tools locally or setting up a complicated testing pipeline. For example, if you're about to ship a redesign of your landing page and want to confirm it didn't get noticeably slower, you could submit a pull request here and get measurements back without touching your own codebase.

The notable thing about the project is its unconventional "pull request as a trigger" design. Instead of asking you to install software, configure a testing environment, or remember command-line flags, it turns GitHub itself into the interface. That said, the README is extremely sparse and doesn't explain exactly how to format your pull request, what information to include, or how to read the results. You'd likely need to look at existing pull requests in the repository to figure out the pattern.