speedtest

librespeed/speedtest

Self-hosted Speed Test for HTML5 and more. Easy setup, examples, configurable, mobile friendly. Supports PHP, Node, Multiple servers, and more

Ship status

Still shipping

Pushed in the last 30 days.

Last push
Sep 27, 2026
5 days ago
Ship score
75/100
How it is calculated →
Stars, last 7 weeks
Stars, weekly: 15,068 → 15,199 (Aug 18 – Sep 29, 2026)
+71 stars in the 28 days to 2026-09-29

Shipping: pushed in the last 30 days · slowed: quiet for 31–120 days · silent: no push in over 120 days.

Repo facts

What GitHub reports.

Stars
15.2K
Forks
2.5K
Open issues
13
Watchers
261
Primary language
JavaScript
Created
Mar 4, 2016
Owner
librespeed · Organization

Open issues are the issues and pull requests GitHub reports as open; watchers are the accounts subscribed to the repository. OSI-approved license — GitHub’s own license field, not legal advice. 57 startups in the directory ship primarily in JavaScript.

Topics

#hacktoberfest#html5-speedtest#internet-speed#internet-speed-checker#librespeed#php#speedtest#web-worker#xhr

How it got here

What the classifier decided, and when.

Read by Jev, TypeSafe’s classifier, on Sep 22, 2026, which did not call this an open-source startup — it chose a package or library instead, and put os_startup at 33% (self-hostable 98%, hosted offering 28%). The classifier reads only the repository’s name, description and homepage; it can be wrong, and a probability under 0.5 puts a listing in the review queue rather than out of the directory. This one is in that queue, waiting for a person — removing a listing is a pull request a human opens.

Listed since the 2025-09 crawl. Answered by jev-1.13.0. How the classification works →

Embed your status

Put this badge on your README.

OSSEAN ship status: shipping — last push 2026-09-27This is the badge for librespeed/speedtest, as served from the URL below.
[![OSSEAN: shipping](https://ossean.com/badge/librespeed/speedtest.svg)](https://ossean.com/librespeed/speedtest)

Updates daily, from the last push GitHub saw.

Honest caveat: GitHub proxies README images through Camo and rewrites the anchor with rel=“nofollow”, so a README embed sends you referral traffic and brand, not link equity. The link is dofollow wherever you control the markup — your docs, your landing page, your blog. The snippet uses your frozen OSSEAN slug, so it survives a repo rename.