Browsertime-autobuild

Browsertime-autobuild is an automated tool that ensures your website performance testing software is always up to date.

  • Tools & Utilities
Browsertime-autobuild is an automated tool that ensures your website performance testing software is always up to date. Every time the developers improve the core code, this app automatically builds a fresh, ready-to-use version, saving you the hassle of manual installations and updates.

Platform availability

Available on 1 of 10 platforms

  • Unraid (not listed)
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox
  • Helm (not listed)
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)
  • Any server (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

69/100 Good

Maintained
100last commit 16 days ago
Popular
56652 GitHub stars
Easy to install
250 install platforms, install notes, Docker image
Light to run
No data

Based on 3 of 4 factors.

GitHub stars
652
Open issues
2
Last commit
2026-11-05
Latest release
v29.0.0
License
Apache-2.0
Activity
rising

Checked 16 days ago - source: GitHub (sitespeedio/browsertime)

Resources & Compatibility

ARM (e.g. Raspberry Pi) is not supported.

Checked 54 days ago - source: Docker Hub image tags and published docs

First-install notes

  • Install the command-line tool first Run `npm install -g browsertime` so Node.js puts the `browsertime` command where your computer can find it, then try `browsertime https://example.com`. Without that global install, the command usually isn't recognized and the test can't start. source
  • Use a Firefox profile template if needed If your tests need saved Firefox settings or extensions, point Browsertime at that profile with `--firefox.profileTemplate` and your profile folder. Without this, Firefox may start with defaults and your test could miss the login state or add-on behavior you expected. source
  • Set up gnirehtet for Android tethering For Android reverse tethering, install `gnirehtet` and make sure the folder containing it is in your PATH, then use the `--gnirehtet` flag. If it isn't in PATH, Browsertime can't start the tethering helper and the Android connection setup can fail. source

Fetched 53 days ago - each note links to its source

Alternatives (6)

  • GTmetrix - GTmetrix is a free tool that analyzes your page's speed performance.
  • New Relic - Pinpoint and solve performance issues in your Ruby, Java, .NET, PHP and Python apps with real user, application and server monitoring.
  • Pingdom - Monitors uptime, downtime, and website performance in real time using synthetic and real user data, with instant alerts, customizable repor…
  • SpeedCurve - Monitor the front-end performance and build of your website.
  • Upzilla - Monitor your website, server, API, application, service and get notified if your resources have some problems with availability.
  • browsertime - Browsertime is a tool that analyses website performance.

Checked 39 days ago - source: AlternativeTo

Common questions

Why won't the browsertime command start after using the autobuild?

Install the command-line tool globally with npm install -g browsertime so Node.js places the browsertime command where the system can find it. Without the global install, the command usually isn't recognized and the test can't start.

How do I run tests with an existing Firefox login profile or extensions?

Point Browsertime at your profile folder with --firefox.profileTemplate. If you don't set it, Firefox may start with defaults and the test can miss the expected login state or add-on behavior.

How do I configure Android reverse tethering for Browsertime tests?

Install gnirehtet, make sure the folder containing it is in PATH, and use the --gnirehtet flag. If it isn't in PATH, Browsertime can't start the tethering helper and the Android connection setup can fail.

Answers sourced from github.com, github.com

Community

Collected 48 days ago - public community threads